Syriaca Main ODD File

Syriaca Main ODD File Daniel Schwartz

for use by whoever wants it

http://www.example.org/ns/nonTEI

created on Tue May 20 2014 09:06:59 GMT-0500 (CDT)

My TEI Customization starts with modules tei, core, textstructure and header

start date Arabic Arabic of any variety or period Garshuni Arabic Garshuni in unvocalized or undetermined Syriac script Garshuni in West Syriac script Arabic Garshuni in vocalized West Syriac script Garshuni in East Syriac script Arabic Garshuni in vocalized East Syriac script Coptic Coptic of any variety or period Old Church Slavonic Old Church Slavonic German German of any variety or period Baumstark German Romanization Names or terms Romanized into German according to the standards adopted by Anton Baumstark's Geschichte der syrischen Literatur. Modern Greek Modern Greek after A.D. 1453 English English of any variety or period GEDSH English Romanization Names or terms Romanized into English according to the standards adopted by the Gorgias Encyclopedic Dictionary of the Syriac Heritage LAH English Romanization Names or terms Romanized into English according to the standards adopted by the Late Antique Historiography project. Syriaca.org Alternate English Romanization Names or terms Romanized into English by Syriaca.org using alternate methods for indexing purposes. Spanish Spanish French French of any variety or period BHS French Romanization Names or terms Romanized into French according to the standards adopted by the Bibliotheca Hagiographica Syriaca BHS French Romanization Names or terms Romanized into French according to the standards adopted by the Bibliotheca Hagiographica Syriaca Ge'ez Ge'ez Ancient Greek Ancient Greek to A.D. 1453 Armenian Classical or Modern Armenian Italian Italian Georgian Classical or Modern Georgian Latin Latin of any variety or period Malayalam Malayalam of any variety or period Malayalam Garshuni Malayalam Garshuni in vocalized East Syriac script Dutch Dutch Portuguese Portuguese Russian Russian Syriac Syriac of any variety or period Syriac in Estrangela script Syriac in Estrangela script West Syriac Syriac in vocalized West Syriac script East Syriac Syriac in vocalized East Syriac script Syriac in Melkite script Syriac in Melkite script. Note: This is not an ISO code but a private use code for Melkite employed by Syriaca.org until an ISO code is created Sogdian Sogdian Turkish Turkish

All elements should have an xml:lang value, either inherited from an ancestor element or declared explicitly. See the Syriaca.org documentation for more information on the usage of particular tags. Note that xml:lang describes the language of the content of the node. For indicating the language of a work or bibliographic resource, see the documentation about the textLang and lang elements.

End date tags usable The name used by Syriaca.org for document titles, citation, and disambiguation. These names have been created according to the Syriaca.org guidelines for headwords: http://syriaca.org/documentation/headwords.html. An anglicized version of a name created by Syriaca.org used to facilitate searching in English. contains the name of a language mentioned in etymological or other linguistic discussion. Inside a bibl element, this refers to the language of the version to which the bibl refers. The contents of lang should be a BCP-47 code. Error: The lang element is only allowed inside a bibl element. la Chronicon Syriacum 1

Syriaca.org uses the lang element inside bibl elements for modern translations and ancient versions to indicate the language of the version to which the bibl refers. This is different from the xml:lang attribute which shows the language of this element, and also different from the textLang element which describes the language of the bibliographic item. (In some cases this is different from the language of the version. For example, the bibliographic item may point to an English translation of an ancient Armenian version.)

Error: An idno is required. The type attribute on bibl elements may be an RDF class defining the type of work or item. These will typically begin with either the prefix lawd: (http://lawd.info/ontology) or syriaca: Work A Conceptual Work groups together one or more Written Works which have the same intellectual source. E.g. The Iliad, as opposed to a particular manuscript witness or edition of the Iliad. See http://lawd.info/ontology/ConceptualWork. Edition A published (whether officially or not) Written Work that relies on one or more Written Works as sources. See http://lawd.info/ontology/Edition. Citation A Citation models a bibliographic reference as a resource. See http://lawd.info/ontology/Citation. Manuscript Any text-bearing object, which usually embodies a Conceptual Work and which may be a source for an Edition or Translation. Catalogue A Citation of a catalogue. Modern Translation A modern Written Work that translates one or more other Written Works that embody the same Conceptual Work. A subtype of http://lawd.info/ontology/Translation. Ancient Version An ancient Written Work that translates one or more other Written Works that embody the same Conceptual Work. A subtype of http://lawd.info/ontology/Translation. The ana attribute on bibl elements should contain one or more Syriaca.org subject URIs beginning with http://syriaca.org/subject/ The type attribute on idno defines the kind of identifier contained in the text value. Custom types not listed here may be used so long as they are standard and clearly recognizable (for example, "CPG" for Clavis Patrum Graecorum numbers for work entities). Where available, URIs are always preferred over other types of identifiers. A Uniform Resource Identifier. The Syriaca.org URI for the entity being described in the current document is contained in an idno of this type. An International Standard Book Number, used to identify books. An International Standard Serial Number, used to identify serial publications, such as journals. A digital object identifier, used to identify objects. However, the preferred method for including DOIs is with an idno of type "URI", prefixed by http://dx.doi.org/. For example, http://dx.doi.org/10.1006/reli.1997.0085. An identifier for a saint used by Fiey, Jean Maurice. Saints Syriaques. Princeton, N.J.: The Darwin Press, Inc., 2004. (http://syriaca.org/bibl/650) An identifier for a hagiographic work from Bibliotheca Hagiographica Syriaca. (http://syriaca.org/bibl/649) An identifier for a hagiographic work from Bibliotheca Hagiographica Orientalis. (http://syriaca.org/bibl/1314) An identifier for a work from Clavis Patrum Graecorum. (http://syriaca.org/bibl/2081) Should contain the URI of the author from the Syriac Biographical Dictionary, unless no record yet exists for the author. Specifies the connection of the author to the work, selected from http://syriaca.org/documentation/author-editor-roles.xml . The attribute value should contain the above URL followed by a hash (#) and the xml:id of the role. For example, http://syriaca.org/documentation/author-editor-roles.xml#pseudo . This is not required if normal authorship is assumed (rather than pseudonymous or questionably attributed authorship). It is also not required if the connection is unknown. Gregorius Bar Hebraeus — ܓܪܝܓܘܪܝܘܣ ܒܪ ܥܒܪܝܐ

Inside the main bibl of a work entity, authors are linked to their record in the Syriac Biographical Dictionary using a URI in the ref attribute. For the purpose of displaying the author's name on the work's HTML page, the English and Syriac headwords are included as persName elements separated by a dash. The nature of the author's connection to a work may be further specified using the role attribute on author.

Should contain the URI of the editor from the Syriac Biographical Dictionary, unless no record yet exists for the editor. Specifies the connection of the editor to the work, selected from http://syriaca.org/documentation/author-editor-roles.xml . The attribute value should contain the above URL followed by a hash (#) and the xml:id of the role. For example, http://syriaca.org/documentation/author-editor-roles.xml#translator . This is recommended, but not required if the type of connection is unknown. Gregorius Bar Hebraeus — ܓܪܝܓܘܪܝܘܣ ܒܪ ܥܒܪܝܐ

Inside the main bibl of a work entity, editors are linked to their record in the Syriac Biographical Dictionary using a URI in the ref attribute. For the purpose of displaying the editor's name on the work's HTML page, the English and Syriac headwords are included as persName elements separated by a dash. The nature of the editor's connection to a work may be further specified using the role attribute on editor.

Predominantly in Syriac with Arabic glosses

When possible, all work records should include the textLang element with at least a mainLang attribute indicating the primary language of the conceptual work using a BCP 47 code. The element should not contain any text unless additional explanation is needed beyond the machine-readable language codes.

specifies how the date is associated with the entity (work, person, etc.) to which it refers the date a work was originally composed the date a work was revised the date a work was translated

Provides a terminus post quem. Use this when the exact date is not known. See the Syriaca.org documentation for editorial conventions regarding dates.

Provides a terminus ad quem. Use this when the exact date is not known. See the Syriaca.org documentation for editorial conventions regarding dates.

mid-late 13th century

Dates should include both a machine-readable version (using attributes like when, notBefore, notAfter) and a human-readable version as text in the element content. See the Syriaca.org documentation for editorial conventions regarding dates.

2 parts 11 chapters approximately 200 folios approximately 550 pages

Should contain a measure element which provides both machine-readable attribute values and human-readable text. For work entities, the extent element is recommended to give a sense of the size of the work.

page folio part chapter stanza verse paragraph section word character

When describing the extent of written or conceptual works, the unit is required, but may be expressed using whatever terms are native to the particular work or most appropriate to it (section, chapter, verse, etc.). An approximate or sample measurement of the number of folios or pages the work comprises may also be used to give a general sense of the size of the work.

2 parts 11 chapters approximately 200 folios approximately 550 pages

Measures should be given using both machine-readable values (in the quantity and unit attributes) and human-readable text (in the element content). See extent regarding describing the extent of a conceptual work.

Describes the function of the note. This attribute is recommended and determines how the note is displayed on the page. A general brief (1-3 sentence) description of an entity (person, place, work, etc.) that facilitates identification. A note of this type should be included in the record whenever possible. A description that provides more or different details from that of the abstract. For example, this type of note may be used to describe the way a person was remembered in hagiography, regardless of the historicity of that description. A note to help distinguish this entity (person, place, work, etc.) from another one. A note describing the content of a work. If provided, this should give more detail than the abstract. A note providing further information about the topical range of the work and its relation to larger works. The incipit of a work or manuscript. The explicit of a work or manuscript. The prologue of a work. This type is typically provided for hagiographic works only. A note concerning the textual relations between works. (Consider whether a relation could be used instead.) A note describing uncertain data in the record. A note describing data that is included in the record but is known to be incorrect. A note describing how the record should be corrected or read differently. A note highlighting potentially problematic or confusing issues with the record or its source material. A note logging the reason(s) for deprecating a particular data point. A note that cannot be categorized as any other type. The first part of Bar Hebraeus' Chronicle ; an account of secular history from the time of Adam until Bar Hebraeus' own time (the 13th century). This work should be distinguished from the Arabic History of the Dynasties, which reflects a similar structure but has significant differences, including some additions that may be from Islamic sources. Through the 12th century, this work is largely an abridgement of Michael the Syrian's Chronicle. The portion following this is particularly valuable for its representation of events during Bar Hebraeus' own lifetime. Secular world history from Creation through the 13th century A.D. Part of a larger work which also contains an ecclesiastical history. ܐܠܗܐ ܥܕܪ ܠܡܚܝܠܘܬܝ. ܡܒܪܟ ܐܢܬ ܗܘ ܡܪܝܐ ܘܡܪܐ ܕܟܠ ܫܘܪܝܐ ܘܫܪܝܐ: ܐܢܬ ܗܘ ܩܕܡܝܐ ܘܐܢܬ ܗܘ ܐܚܪܝܐ. ܘܠܘܬܟ ܡܬܛܝܒܐ ܟܠ ܡܪܕܝܬܐ: God, help my feebleness! Blessed be Thou, Lord, and Lord of the Universe, the beginning and the end; Thou art the First, and Thou art the last. With Thee every course of action is prepared.

Notes are used for various kinds of text. In entity records, Syriaca.org typically uses notes as containers for sentence-length to paragraph-length text. The type attribute is required and determines how the note is displayed on the page.

Error: The relation element must contain either @mutual or both @active and @passive together. Describes the general category of relationship, which may be used in addition to ref to determine how the relation should be displayed in the interface. A relation between a work and the larger work of which it is a part. See label. A relation that disambiguates an entity from others. A relation that does not belong in a more specific category. A relation pointing to the manuscript witnesses of an edition or translation. A relation pointing to the original (or other-) language source of a translation. An RDF property applicable to the relation. This may be a custom Syriaca.org property, such as one found at http://syriaca.org/documentation/relations.html or one from an external vocabulary such as SNAP or LAWD.

This should contain either the full URI of a Syriaca.org entity (person, place, work, etc.), or a hash URI (fragment identifier introduced with #) for a node within the document. A full URI is preferred where one exists. When the relation is serialized as RDF, the value of active identifies the subject resource.

This should contain identifiers for two or more Syriaca.org entities or nodes, either as full URIs, or as hash URIs (fragment identifiers introduced with #) in the case of nodes within the document. When the relation is serialized as RDF, a triple is created for each pairing of values in mutual, such that each entity referenced in mutual is represented in different triples as a subject and as an object.

ar تاريخ الزمان

This relation links the bibl describing a translation to the bibl from which it was translated. Note the use of both a type in addition to a ref to make the relation more specific. It is also linked to the work entity containing it.

part 1

This relation shows that the work described in this record is part 1 of a larger work.

relation is used to link Syriaca.org entities to each other, when possible in a semantically robust, RDF-friendly way. The values of active, ref, and passive should be construable as RDF triples. For this reason, ref is required, as is either active and passive, or mutual. The relation may also contain text inside a desc if such must be visualized on the record, but this text should be standardized to the extent possible.

Error: @subtype and @n are required when relation//label/@type='order'. Indicates that the label is used to designate the order of the parent item within a larger sequence, for example, as part of a larger work. If this type is used, a subtype and n are also required.

If used with @type="order", the subtype should reflect the kind of thing being ordered.

If used with @type="order", n should contain the numeric value of the order of the parent item within a larger sequence.

part 1

This relation shows that the work described in this record is part 1 of a larger work.

When used in a desc within a relation having @ref="dct:isPartOf", label can be used to used to designate the order of the parent item within a larger sequence. In this case, type, subtype, and n are all required and the text content of label should contain a human-readable description (e.g., "part 1").