[osis-core] Requiring OSISID (open milestone) OSISIDREF (close milestone)

[Patrick Durusau]

Todd,

I think there may be a problem with requiring the OSISID on all opening 
milestones and OSISIDREF on all closing milestones. I know Chris was 
opposed to requiring ID on all elements, does this create a problem for 
anyone? I have left it as Todd proposed so we can look at it in "action" 
so to speak if that helps.

<verseStart OSISID="Matt.1.1" /> .....<verseEnd OSISIDREF="Matt.1.1" />

Comments?

Patrick

Todd Tillinghast wrote:

>(Do not consider the attached files as the official release from
>Patrick.)  The hope is that the schemas attached are complete and
>demonstrate the adjusted reference/ID/IDREF strategy we work on Wed
>afternoon.
>
>Following are the changes made to OSIS_0106.xsd:
>0) Removed the include statement that included "selectedRoleNames.xsd"
>in OSISCore_0107.xsd.  (OSISCore_0107.xsd replaces OSIS_0106.xsd and is
>"abstract")
>1) Moved list items that are more likely subject to change and/or may be
>changed based on the document being encoded.  (divOSIS, namesOSIS,
>notesOSIS, noteTypesOSIS, role, and languageType are all in
>OSISLists_0107.xsd) The only benefit here is that we can always add them
>in later but it does allow for the creation of different instances for
>different purposes in the future.)  I'm not sure how you will take to
>this but it seemed to make sense to me so I did it.  Take it or leave
>it, but you were already including "role".  
>2) Created OSISScripture_0107.xsd that defines OSISID, OSISIDREF,
>OSISIDREFS, and ReferenceType and includes OSISCore_0107.xsd and
>OSISLists_0107.xsd.  (OSISCore_0107.xsd is not valid on its own.)
>
>3) Changed globalAttributes as follows:
>OLD
>	<xs:attributeGroup name="globalAttributes">
>		<xs:attribute name="ID" type="OSISID" use="optional"/>
>		<xs:attribute name="IDREF" type="OSISIDREF"
>use="optional"/>
>		<xs:attribute name="IDREFS" type="OSISIDREFS"
>use="optional"/>
>		<xs:attribute name="lang" type="languageType"
>use="optional"/>
>		<xs:attribute name="reference" type="ReferenceType"
>use="optional"/>
>		<xs:attribute name="referenceEnd" type="ReferenceType"
>use="optional"/>
>		<xs:attribute name="type" type="xs:string"
>use="optional"/>
>	</xs:attributeGroup>
>NEW
>	<xs:attributeGroup name="globalAttributes">
>		<xs:attribute name="lang" type="languageType"
>use="optional"/>
>		<xs:attribute name="reference" type="ReferenceType"
>use="optional"/>
>		<xs:attribute name="referenceEnd" type="ReferenceType"
>use="optional"/>
>		<xs:attribute name="type" type="xs:string"
>use="optional"/>
>	</xs:attributeGroup>
>
>
>4) Created new attributeGroups as follows for milestones and substitued
>them for globalAttributes in milestone elements.
>	<xs:attributeGroup name="startMilestoneAttributes">
>		<xs:attribute name="OSISID" type="OSISID"
>use="required"/>
>		<xs:attribute name="OSISIDREF" type="OSISIDREF"
>use="optional"/>
>	</xs:attributeGroup>
>	<xs:attributeGroup name="endMilestoneAttributes">
>		<xs:attribute name="OSISID" type="OSISID"
>use="optional"/>
>		<xs:attribute name="OSISIDREF" type="OSISIDREF"
>use="required"/>
>	</xs:attributeGroup>
>
>
>5) Added "reference" and "referneceEnd" back into <div> as
>ReferenceType.
>
>
>6) Changed divType to type in <div>.  (Did this just so Josephus, etc
>would validate.)  I can go either way on the name.
>
>7) Made "attachFigure" and "endAttachFigure" <figure> type ReferenceType
>8) Put back "noteStart" and "noteEnd" attributes in <note> and make them
>type ReferenceType
>9) Fixed the typo in noteTypePart to be the union of notePartsOSIS and
>attribute extension rather than notesOSIS
>10) Changed the requirement that there be at least one element as a
>child of <div>.
>11) Still missing is a place to state the document's default reference
>system. 
>12) Although [ $ # : ] are valid as a part of the value of a normal
>attribute they are NOT valid when a part of an xs:ID.  In the absence of
>any other ideas I decided to use .. to separate the reference system
>from the reference itself.  Whatever the delimiter this new strategy
>allows for reference systems with only a single reference system and for
>those with multiple.  Any better ideas for the delimiter between the
>reference system and the reference itself?
>
>JOSEPHUS TEST
>I created a OSISJosephus_0107.xsd that allows for BOTH Bible.*
>references as well as Josephus.* references.  In case OSISID is
>restricted to ONLY Josephus references, while having references to both
>the Bible and Josephus.  I also did not allow shortened Bible references
>(reference="Ps.43.1" is not allowed but the form "Bible.Cath..Ps.43.1"
>is required). 
>
>I edited the Josephus.xml from the URL Chris sent earlier and it now
>conforms to references as presented in OSISJosephus_107.xsd.
>
>(Chris and Troy, I was not sure on the following text that I got the
>references correct.  Should it be Josephus..life.19 as shown below or
>Josephus..3.19?  The original text had reference="19".
>
>								<p>How
>Josephus could say here that the Jewish laws forbade them to "spoil even
>their enemies, while yet, a little before his time, our Savior had
>mentioned it as then a current maxim with them, "Thou shalt love thy
>neighbor, and hate thine enemy," <reference
>reference="Matt.5.43">Matthew 5:43</reference>, is worth our inquiry. I
>take it that Josephus, having been now for many years an Ebionite
>Christian, had learned this interpretation of the law of Moses from
>Christ, whom he owned for the true Melah, as it follows in the
>succeeding verses, which, though he might not read in St. Matthew's
>Gospel, yet might he have read much the same exposition in their own
>Ebionite or Nazarene Gospel itself; of which improvements made by
>Josephus, after he was become a Christian, we have already had several
>examples in this his life, <reference reference="Josephus..life.3">sect.
>3</reference>, <reference  reference="Josephus..life.13">13</reference>,
><reference  reference="Josephus..life.15">15</reference>, <reference
>reference="Josephus..life.19">19</reference>, <reference
>reference="Josephus..life.21">21</reference>, <reference
>reference="Josephus..life.23">23</reference>, and shall have many more
>therein before its conclusion, as well as we have them elsewhere in all
>his later writings.</p>
>)
>
>
>
>Bible.TEV TEST
>I have a version of the TEV in this new format that further demonstrates
>the strategy.
>
>This test can be further extended to demonstrate how various reference
>system strategies can be validated.
>
>If this is not clear or if you have a question call me in the morning.
>(817) 428-8633 (After 8:00 Central Time is better.)
>
>
>(I am sending the actual encoded files under a separate email.)
>Todd
>

-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
pdurusau@emory.edu