srophe / srophe-eXist-app

DEPRECATED eXist code for Syriaca.org: The Syriac Reference Portal
GNU General Public License v3.0
10 stars 11 forks source link

Displaying links to works within abstracts (INDO and REF for URIs in TEI) #536

Open nathangibson opened 8 years ago

nathangibson commented 8 years ago

Currently the XSLT does not render links to works that are inside abstracts. @davidamichelson how should we markup these references to works? For example, the abstract for http://wwwb.library.vanderbilt.edu/exist/apps/srophe/person/2784 is

Bishop of Iconium connected with the Cappadocian Fathers. Syriac translations of works attributed to him include an encomium on Basil, and a hagiographic work about Athanasius of Alexandria.

There are 3 options I know of:

nathangibson commented 8 years ago

FYI, option 1 is what I've been using so far.

wsalesky commented 8 years ago

I added a template for option 1.

See: http://wwwb.library.vanderbilt.edu/exist/apps/srophe/person/2784

nathangibson commented 8 years ago

Thanks! That looks great and does the trick for now. I guess we will still need to figure out whether we want to break TEI guidelines and put a ref on the bibl.

davidamichelson commented 8 years ago

Hi @wsalesky and pulling our LAWDI old man @paregorios and also @tacarlson into this discussion.

So following this discussion on the TEI-L it looks we might need to reconsider how we handle URIs in our various data templates: https://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1504&L=TEI-L&D=0&1=TEI-L&9=A&I=-3&J=on&d=No+Match%3BMatch%3BMatches&z=4&P=23902

Thoughts:

There are two ways to mark a URI: `<persName @ref> or <idno @type=”URI”> <persName @ref=”http://syriaca.org/person/13”>Ephrem

Ephremhttp://syriaca.org/person/13` Note: TEI:person is of limited use to us since it can only be used in a few places. Technically our assertions of the URI with persName are not semantically correct since we are indicating the person not the name, but this is not possible in TEI and our usage is a common work around. As indicated in the discussion the second example actually fits LOD usage better since it points to a URI for the person and not a document defining the person. Switching to this method would also help with uniformity on this particular issue (see above) because we could mark up TEI:bibl (which does not allow att.canonical: `@ref`) in this way: ```an encomium on Basilhttp://syriaca.org/work/382 Using TEI:idno instead of @ref would be a major change across our templates but could be done in a script. Thoughts?
nathangibson commented 8 years ago

@wsalesky @dlschwartz Do you remember how we resolved this? I think we decided to continue using @ref on the persNames and placeNames, but did we decide for sure to use <bibl>...<ptr> for references to works?

wsalesky commented 8 years ago

@nathangibson I do not think we did resolve it. I think we are leaning toward tei:idno, but I do not know that we have made this a policy, and we have not made data changes.

nathangibson commented 8 years ago

Note that we may currently be using two different formats (title with ref and bibl with ptr) in our data. Once we decide on a standard we should standardize the data.