Digital Syriac Corpus Documentation

URI Policies

Digital Syriac Coprus maintains stable URIs for the texts it contains. The following guidelines will usually be relevant only to Digital Syriac Corpus editors and partner projects, not to ordinary users.

Entity URIs

Digital Syriac Corpus uses the following URI formats to identify each entity (i.e. each text). Navigating to one of these URIs will display a human-readable HTML page, but please note that these URIs identify the entity being described and not the page that describes it.

Entity Type URI Format Example XPath
Text https://syriaccorpus.org/\d+ http://syriaca.org/place/1 /TEI/teiHeader/fileDesc/publicationStmt/idno[@type='URI' and starts-with(.,'https://syriaccorpus.org')]

URIs for each entity are displayed directly underneath the name or title of the entity. The entity URI may also be queried using the XPath code in the table above. (A TEI namespace is assumed.)

The numbers at the end of the URI are essentially random and do not correspond to any other numbered or ordered system. Due to the process by which records are created, there are sometimes unassigned URIs between URI numbers.

URIs for HTML Pages

Each entry describing a Digital Syriac Corpus entity has a human-readable HTML page. While this page may be reached by navigating to the entity URI, the URI for the HTML page itself is the entity URI plus the suffix ".html". This is important for RDF assertions. For example, http://syriaca.org/place/78.html is the page describing the place identified by http://syriaca.org/place/78.

URIs for TEI Records

Each entry describing a Digital Syriac Corpus entity also has a TEI-XML record. The URI for this record is the entity URI plus the suffix "/tei". For example, https://syriaccorpus.org/1/tei is the TEI record describing the text identified by http://syriaca.org/1.