[osis-core] <seg type="otPassage"> and migration paths

[Patrick Durusau]

Todd,

"what an enumerated type on <seg> of otPassage buys us"...is avoidance 
of the semantics (and implied default rendering) of <q> with type 
="otPassage".

First thoughts on migration path:

If Troy agrees, we could perhaps return to <seg type="x-otPassage"> and 
document that this use of <seg> with "x-" attribute value is intended 
for proposed element on which there is insufficient agreement or time to 
be included in the schema.

In other words, it is a possible migration path and users should be 
aware that <seg "x-*****"> may become full elements in a later release 
of the schema. Since stylesheets should (IMHO) be tied to specific 
schema releases, if we document the transition from <seg type="x-****" 
to a named element, then it should not be that difficult for users to 
make the transition.

Second thoughts on migration path:

Note that having the "x-" prefix, however, since it is always allowed on 
type for <seg> does not guarantee that all users will use the new 
element. With an enumerated type, should the type go away in a future 
release, we can enforce the transition, to some degree to the new named 
element.

I think having a somewhat enforceable migration path is a good thing.

Hope everyone is at the start of a great day!

Patrick

Todd Tillinghast wrote:
> Patrick and Troy,
> 
> First let me say that we need to create an official mechanism for
> encoding the "otPassage" phenomenon.
> 
> I am not sure what an enumerated type on <seg> of otPassage buys us.
> The way I understand it <seg> is for things that are not otherwise
> handled by the schema.  By making an enumerated type on <seg> we are
> saying the way to do something is <seg type="otPassage">.  
> 
> It would seem that in the future we intend to create an alternative
> solution and have to deprecate <seg type="otPassage"> in favor of either
> an element or an enumerated type for <q>.
> 
> Why not do one of the following:
> 1) Stay with either <seg type="x-otPassage> or <q type="x-otPassage> and
> work this out in a later release
> 2) Create an <otPassage> element (I understand the reluctance to change
> the schema this late)
> 3) Create <q type="otPassage> (I understand Troy's position against this
> solution)
> 
> Todd
> 
> 
>>-----Original Message-----
>>From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
>>admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
>>Sent: Thursday, October 23, 2003 4:38 PM
>>To: osis-core@bibletechnologieswg.org
>>Subject: [osis-core] osisCore.1.9.9.4
>>
>>Guys,
>>
>>Getting closer all the time!
>>
>>Note that I have added an enumerated type on <seg> of otPassage. That
>>allows Troy to avoid default rendering of quotes but also allows me to
>>avoid trying to add another content model when I am already tired.
>>
>>Should Troy's analysis of usage prove accurate, which it very well
> 
> may,
> 
>>we may need to revisit this issue for this type of passage and others.
>>For my part, if "the very stones would cry out," the Rolling Stones
> 
> that
> 
>>is, we may need to revisit this issue. ;-)
>>
>>I think this is about as close as I can get today. Please run your
>>various texts against it and let me know the results.
>>
>>Really do appreciate all the hard work!
>>
>>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
> 


-- 
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!