[osis-core] empty tag / milestone proposal

Wed, 19 Jun 2002 08:38:25 -0400

(Got a delayed start this morning getting house guests on the road. 
Expect the next version just after NOON East Coast time.)

Troy,

XML treats <head></head> and <head/> as syntactically equivalent. Unless 
an element has required content (in other words, elements that must 
occur)  I think you already have milestones. (Am I missing something here?)

Since <div> is mixed content, you could write all of the elements that 
may occur in <div> as empty elements, or so I am reading the XML spec.

I may be missing the purpose of the patch. Is it to add the mstart, 
mstop attributes? Is so, can I add them to global?

I would like to leave the generic milestone for cases where people want 
to use standard containers and yet also do some milestone markup.

Patrick

Troy A. Griffitts wrote:

> Attached is a proposal to allow some elements to be used as empty 
> milestones optionally.  Please consider applying this patch.
>
> I would also suggest removing the generic milestone element, but this 
> patch does not do this.
>
>
>------------------------------------------------------------------------
>
>--- osisCore_1test12.xsd.orig	Tue Jun 18 19:45:00 2002
>+++ osisCore_1test12.xsd	Tue Jun 18 20:13:05 2002
>@@ -308,6 +308,7 @@
>                            <xs:element ref="w"/>
> 		</xs:choice>
> 		<xs:attributeGroup ref="globalAttributes"/>
>+		<xs:attributeGroup ref="milestoneAttributes"/>
> 	   </xs:complexType>
> </xs:element>
> 
>@@ -765,6 +766,7 @@
> 			   <xs:element ref="w"/>
> 		</xs:choice>
> 		<xs:attributeGroup ref="globalAttributes"/>
>+		<xs:attributeGroup ref="milestoneAttributes"/>
> 	   </xs:complexType>
> </xs:element>
> 
>@@ -798,6 +800,7 @@
> 		<xs:attribute name="next" type="xs:string" use="optional"/>
> 		<xs:attribute name="prev" type="xs:string" use="optional"/>
> 		<xs:attributeGroup ref="globalAttributes"/>
>+		<xs:attributeGroup ref="milestoneAttributes"/>
> 	   </xs:complexType>
> </xs:element>
> 
>@@ -895,6 +898,7 @@
> 		<xs:attribute name="next" type="xs:string" use="optional"/>
> 		<xs:attribute name="prev" type="xs:string" use="optional"/>
> 		<xs:attributeGroup ref="globalAttributes"/>
>+		<xs:attributeGroup ref="milestoneAttributes"/>
> 	   </xs:complexType>
> </xs:element>
> 
>@@ -976,6 +980,7 @@
> 		<xs:attribute name="prev" type="xs:string" use="optional"/>
> 	        <xs:attribute name="who" type="xs:string" use="optional"/>
> 		<xs:attributeGroup ref="globalAttributes"/>
>+		<xs:attributeGroup ref="milestoneAttributes"/>
> 	   </xs:complexType>
> </xs:element>
> 
>@@ -1027,6 +1032,7 @@
> 		</xs:choice>
> 		<xs:attribute name="changeType" type="changeType" use="optional"/>
> 		<xs:attributeGroup ref="globalAttributes"/>
>+		<xs:attributeGroup ref="milestoneAttributes"/>
> 	   </xs:complexType>
> </xs:element>
> 
>@@ -1059,6 +1065,7 @@
> 		<xs:attribute name="next" type="xs:string" use="optional"/>
> 		<xs:attribute name="prev" type="xs:string" use="optional"/>
> 		<xs:attributeGroup ref="globalAttributes"/>
>+		<xs:attributeGroup ref="milestoneAttributes"/>
> 	   </xs:complexType>
> </xs:element>
> 
>@@ -1117,6 +1124,11 @@
> 	<xs:attribute name="outCite" type="osisRef" use="optional"/>
> </xs:attributeGroup>
> 
>+<!-- allow some container elements to be left empty and used as milestones. eg. either <verse verseID="jn.1.1">In the beginning...</verse> OR <verse verseID="jn.1.1" mStart="jn.1.1"/>In the beginning...<verse mEnd="jn.1.1"/> -->
>+<xs:attributeGroup name="milestoneAttributes">
>+	<xs:attribute name="mStart" type="xs:string" use="optional"/>
>+	<xs:attribute name="mEnd" type="xs:string" use="optional"/>
>+</xs:attributeGroup>
> 
> <!-- simple types -->
> 
>@@ -1369,4 +1381,4 @@
> 	<xs:union memberTypes="roleOSIS attributeExtension"/>
> </xs:simpleType>
> 
>-</xs:schema>
>\ No newline at end of file
>+</xs:schema>
>

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