[osis-core] x- usage?

Patrick Durusau osis-core@bibletechnologieswg.org
Tue, 01 Jul 2003 13:49:13 -0400


Todd,

Will see this change (experimental so everyone comment) in the release 
later this afternoon (1.4.62).

Patrick

Todd Tillinghast wrote:
> Patrick and Steve,
> 
> Yes to "x-" for ALL cases of "type" attributes.
> 
> Currently we have not defined any enumerated values for subType.  
> 
> I say we also put "x-" on ALL subTypes and reserve the right to define
> values in the future.  This would also make type and subType consistent
> with each other.
> 
> When we create named simple and complex types in the "next" release
> (after 1.5) it might be a good idea to create a simple type in the style
> of "osisDivs" for all elements (the enumerated lists would be empty
> initially).  This would create the potential to extend only the
> enumerated types in a derived schema if we decided we didn't want to
> bloat the core schema with type values specific to different type of
> documents.
> 
> Todd
> 
> 
> 
>>-----Original Message-----
>>From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
>>admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
>>Sent: Tuesday, July 01, 2003 6:23 AM
>>To: osis-core@bibletechnologieswg.org
>>Subject: Re: [osis-core] x- usage?
>>
>>Steve,
>>
>>Steven J. DeRose wrote:
>>
>>
>>>On element that do *not* provide any predefined type values, should
>>
> we
> 
>>>still restrict users to prefixing their values with "x-", so that we
>>>can safely reseerve values later if we want to, and so that user
>>>extensions are always readily findable?
>>
>>Fine by me.
>>
>>Recall that elements may have attributes defined as globalWithType
> 
> (has
> 
>>attributes type and subtype, both as xs:string). Would your proposal
>>require both to have the "x-" prefix for all values?
>>
>>Attributes are also defined in globalWithoutType, which allows an
>>element to have a defined type but it also has a subtype with
> 
> xs:string.
> 
>>Same question for the subtype attribute here?
>>
>>Already have the simpleType "attributeExtension" so we can just set
> 
> the
> 
>>type/subtype attribute type to that. If later define a type of an
>>element, just union the enumeration with "attributeExtension."
>>
>>Fairly clean and requires minimal changes.
>>
>>Comments, suggestions?
>>
>>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!