[osis-core] Identification of deutero-canonical material

[Patrick Durusau]

Todd,

Todd Tillinghast wrote:
> Chris and Patrick,
> 
> Should the "editons" attribute be a list?

Actually it is already NMTOKENS, which give you a list.

To be consistent, however, should we use the same list mechanism that we 
use for other attribute lists?

Note that NMTOKENS gets you valid name tokens only. Different from what 
we allow with the various regexes.

Anyone for osisGenRegex on "editions?"

Hope you are having a great day!

Patrick


> 
> It is possible for there to be more than one kind of edition.  For
> example the CEV would have the deuterocanonical edition related things
> but there are also 5 edition variations that apply to both the
> "protestant"? and "deuterocanonical" editions.  There are wide and
> narrow edition differences AND there are there are 5 different note
> variation editions.
> 
> For poetry in a wide edition they could use <lb edition="wide"/> and
> later in the same <l> use <lb edition="narrow"/>.
> 
> For notes they could indicate <note edition="deuterocanonical global"
> type="crossReference"> for notes that are deutercanonical AND only in
> the global edition.
> 
> It would be handy to be able to use this "edition" mechanism for all of
> these purposes.  Do you think this is outside of the purpose of this
> attribute?
> 
> Todd
> 
> 
>>-----Original Message-----
>>From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
>>admin@bibletechnologieswg.org] On Behalf Of Chris Little
>>Sent: Friday, February 20, 2004 4:07 PM
>>To: osis-core@bibletechnologieswg.org
>>Subject: Re: [osis-core] Identification of deutero-canonical material
>>
>>Patrick Durusau wrote:
>>
>>
>>>Chris,
>>>
>>>
>>>>USFM provides \dc, \fdc, and \xdc for marking deutero-canonical
>>>>material, notes related to deutero-canonicals, and cross-references
>>>
> to
> 
>>>>deutero-canonical books respectively.
>>>>
>>>>In most of these cases, <seg type="deuterocanonical">...</seg>,
>>>
> would
> 
>>>>be a good solution.  Identifying deutero-canonical books/sections
>>>>might require a new <div> type.
>>>>
>>>>The canonical value would not be sufficient to handle all of these
>>>>cases since, whether it refers to proto-canonical or
>>>
> deutero-canonical
> 
>>>>material, a note is always not canonical.
>>>
>>>
>>>The notes from Dallas indicate:
>>>
>>>
>>>>global "editions" attribute = "NMTOKENS" for suppression/inclusion
>>>
> of
> 
>>>>portions of texts. But required if used to be used
>>>>consistently. Default behavior, if marked, make appropriate choice,
>>>>default is to include or if not instructions about the NMTOKEN,
>>>>include.
>>>
>>>
>>>Does that solve the problem of \dc, \fdc, and \xdc?
>>
>>Looks good to me.  I think we should include in the manual an exmaple
>>that specifically suggests using a standardized value such as
>>"deuterocanonical" since this is a common use, worth
> 
> quasi-standardization.
> 
>>>BTW, is the function of \xdc to allow removal of references that
>>>otherwise occur in a work when deutero-canonical material is
>>
> removed?
> 
>>If I understand your question correctly, then yes.  \xdc marks
>>cross-references to deutero-canonical books.  If deutero-canonical
>>material is not rendered, then neither are cross-references to that
>>material.
>>
>>--Chris
>>
>>_______________________________________________
>>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!