[osis-core] header elements

[Patrick Durusau]

Todd,

Todd Tillinghast wrote:
> Patrick,
> 
> This seems reasonable, but if we use the children of <work> in the new
> <titlePage> element we may need osisID, n, xml:space, script, and
> canonical.
> 

Hmmm, yeah, that's right.

> Now that I am looking at the list I am not sure of the purpose of role
> and resp for any element.
> 
role is unique to creator and actor (I think). It is not part of the 
globals.

resp is a responsibility attribute that allows the encoder to say who 
thought this was "X". Useful for abbreviations/expansions, notes (who 
wrote the note), etc. Does not have to be global. Depends on whether we 
think we can come up with all the cases where it should occur. Obviously 
not on osisText, osisCorpus, probably not on div but that depends. Am I 
saying this is the division in the text and is that disputed?

Hope you are having a great day!

Patrick


> Todd
> 
> 
>>-----Original Message-----
>>From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
>>admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
>>Sent: Tuesday, September 23, 2003 8:48 AM
>>To: osis-core@bibletechnologieswg.org
>>Subject: [osis-core] header elements
>>
>>Guys,
>>
>>Shouldn't we create another global attribute set for header elements?
>>
>>Creator now has:
>>
>>role  roleType  optional
>>annotateRef  annotateRefType  optional
>>annotateWork  xs:string  optional
>>annotateType  annotationType  optional
>>ID  xs:ID  optional
>>osisID  osisIDType  optional
>>resp  xs:string  optional
>>type  attributeExtension  optional
>>subType  attributeExtension  optional
>>n  xs:string  optional
>>xml:lang  xs:language  optional
>>xml:space  xs:NCName    preserve
>>script  osisScripts  optional
>>canonical  xs:boolean  optional
>>
>>Actually should only have:
>>
>>role  roleType  optional
>>ID  xs:ID  optional
>>type  attributeExtension  optional
>>subType  attributeExtension  optional
>>xml:lang  xs:language  optional
>>
>>Other header elements to conform as necessary.
>>
>>Could just put the attributes in since it is a fairly small amount or
>>create a simpleType, headerAttributes.
>>
>>Would leave data and title as they are, since they occur elsewhere in
>>the schema.
>>
>>Actually need to do the same for osisText, osisCorpus, etc.
>>
>>Would make it less complicated and perhaps less confusing if someone
>>prints out XMLSpy type documentation.
>>
>>Comments?
>>
>>Hope everyone is having a great day!
>>
>>Patrick
>>
>>
>>--
>>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!
>>
>>
>>_______________________________________________
>>osis-core mailing list
>>osis-core@bibletechnologieswg.org
>>http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
> 
> 
> _______________________________________________
> 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!