[osis-core] <work> attributes

[Patrick Durusau]

Troy,

Apologies if it was unclear! No intent to define a reference system!

Just saying this document defines a reference system. (Note: Not saying 
anything about how it does that. Completely undefined, at this point, by 
OSIS.)

Does put us in the position of resolving the much larger question you 
raise below and doing so in an orderly manner (however long that takes).

Hope you are having a great day!

Patrick

Troy A. Griffitts wrote:

> Hey guys,
>     My apologies for not following things in the past couple weeks, 
> and I realize I don't have much place to comment at this late time, 
> but help me understand the changes that are being made.
>
> In pros, are we trying to make a way to declare a reference system?  
> If so, I'm very leary to agree we've all thought about it and concur 
> on a mechanism.
>
> Patrick: "You might have a look at a few new attributes that are 
> required on work"
>
> :)
>
> We could talk thru the reprecussions of declairing a refSystem like 
> this, but I'm not sure we could do a good job by Wednesday.  Harry, 
> and others all had good input on this subject, and I think it is a 
> much larger matter and due more concession before we officially bless 
> a mechanism for which people will run out and start defining a whole 
> mess of stuff :)
>
> Anyway, just my 2c.
>
>     -Troy.
>
>
>
>
>
> Patrick Durusau wrote:
>
>> Guys,
>>
>> Apologies for not drawing attention to this addition earlier. It was 
>> added due to discussions Steve and I had in Covington.
>>
>> The <work> element has three required attributes:
>>
>> <xs:attribute name="osisWork" type="osisWorkType" use="required"/>
>>
>> Same as always.
>>
>> <xs:attribute name="type" type="osisWorkClass" use="required"/>
>>
>> <xs:simpleType name="osisWorkClass">
>>
>>           <xs:restriction base="xs:string">
>>
>>        <xs:enumeration value="content"/>
>>
>>        <xs:enumeration value="declaration"/>
>>
>>           </xs:restriction>
>>
>> </xs:simpleType>
>>
>> Which allows a work to be declared as "content" or as a declaration 
>> (did not want to say refSystem as you could have a list of names, 
>> translation table from one reference system to another, etc.).
>>
>> <xs:attribute name="subType" type="osisWorkSubClass" use="required"/>
>>
>> <xs:simpleType name="osisWorkSubClass">
>>
>>    <xs:union memberTypes="osisContentWorks osisDeclarationWorks 
>> attributeExtension"/>
>>
>> </xs:simpleType>
>>
>> <xs:simpleType name="osisContentWorks">
>>
>>           <xs:restriction base="xs:string">
>>
>>        <xs:enumeration value="Bible"/>
>>
>>        <xs:enumeration value="Commentary"/>
>>
>>        <xs:enumeration value="Lexicon"/>
>>
>>        <xs:enumeration value="Literary"/>
>>
>>        <xs:enumeration value="Other"/>
>>
>>        <xs:enumeration value="Sacred"/>
>>
>>           </xs:restriction>
>>
>> </xs:simpleType>
>>
>> <xs:simpleType name="osisDeclarationWorks">
>>
>>           <xs:restriction base="xs:string">
>>
>>           <xs:enumeration base="NameList"/>
>>
>>           <xs:enumeration value="RefSystemMap"/>
>>
>>        <xs:enumeration value="RefSystem"/>
>>
>>           </xs:restriction>
>>
>> </xs:simpleType>
>>
>> Note that osisWorkSubClass is the joinder of two different classes of 
>> works plus the attribute extension.
>>
>> We should have documented it as soon as we wrote it down, but didn't. 
>> :-(
>>
>> Hope everyone is having a great day!
>>
>> Patrick
>>
>>
>
>
> _______________________________________________
> osis-core mailing list
> osis-core@bibletechnologieswg.org
> http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
>

-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
Patrick.Durusau@sbl-site.org
Chair, V1 - Text Processing: Office and Publishing Systems Interface
Co-Editor, ISO 13250, Topic Maps -- Reference Model

Topic Maps: Human, not artificial, intelligence at work!