Supplemental: Re: [osis-core] osisIdentifier

[Patrick Durusau]

Todd, Chris,

Done and done.

Now have OSIS and osisRef.

Hope you are having a great day!

Patrick

Todd Tillinghast wrote:
> Chris,
> 
> I am fine with leaving in "OSIS".
> 
> The question is who is going to act in the role to maintain the set of
> identifiers and review and approve requests.  This may be a topic for
> the next meeting.
> 
> Todd
> 
> 
>>-----Original Message-----
>>From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
>>admin@bibletechnologieswg.org] On Behalf Of Chris Little
>>Sent: Friday, October 17, 2003 11:20 AM
>>To: osis-core@bibletechnologieswg.org
>>Subject: RE: Supplemental: Re: [osis-core] osisIdentifier
>>
>>
>>I feel like we should retain <identifier type="OSIS">.  A large part
> 
> of
> 
>>describing its possible values is just algorithmic, as Todd's example
>>illustrates.  And even if we want data for the registry to be supplied
> 
> by
> 
>>3rd parties, I think the BTG should ultimately be responsible for
>>coordination of an authoritative list of values.  (If desired, I'm
> 
> sure
> 
>>Troy or I could design an actual database & interface for collecting &
>>reporting OSIS-approved identifiers.)
>>
>>--Chris
>>
>>On Fri, 17 Oct 2003, Todd Tillinghast wrote:
>>
>>
>>>Patrick,
>>>
>>>(The way I understand it.) The idea with <identifier
>>>type="OSIS">Bible.es.RVR.1960</identifier> is that the value is a
>>>"standardized" identifier defined by the BibleTechnologies working
>>>group.  However, we have not determined that we want to act in that
>>
> role
> 
>>>nor have we defined a mechanism for declaring and maintaining such a
>>>list.
>>>
>>>The more likely reality is that each genre of texts will establish a
>>>"naming authority".  For example, the Forum of Bible Agencies may
>>
> act as
> 
>>>the naming of authority for the Bibles of its member Bible agencies
>>
> (and
> 
>>>possibly for modern translations by other non-Member Bible
>>
> agencies).
> 
>>>This would leave the naming of ancient text to a group like the SBL.
>>>
>>>In answer to your question, we can deprecate <identifier
>>
> type="OSIS"> if
> 
>>>we want to OR leave it.  I would say we should leave it ONLY if we
>>>intend to act as a "naming authority", which at this point seems
>>
> like a
> 
>>>role better left to a third party.
>>>
>>>So yes, add in <identifier type="OSISREF"> (or <identifier
>>>type="osisRef"> with mixed case because this is not an acronym).
>>>
>>>This would lead to:
>>><osisText osisWorkID="x">
>>>   <header>
>>>      <work osisWork="x">
>>>         ....
>>>         <identifier
>>>type="osisRef">fbaWorkNames:Bible.es.RVR.1960</identifier>
>>>      </work>
>>>      <work osisWork="fbaWorkNames">
>>>         <title>Fellowship of Bible Agencies Bible Translation
>>>Names</title>
>>>         ...
>>>      </work>
>>>   </header>
>>></osisText>
>>>
>>>This
>>>
>>>
>>>>-----Original Message-----
>>>>From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
>>>>admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
>>>>Sent: Friday, October 17, 2003 9:46 AM
>>>>To: osis-core@bibletechnologieswg.org
>>>>Subject: Supplemental: Re: [osis-core] osisIdentifier
>>>>
>>>>Todd,
>>>>
>>>>We already have:
>>>>
>>>><xs:enumeration value="OSIS"/>
>>>>
>>>>so change to:
>>>>
>>>><xs:enumeration value="OSISREF"/> ?
>>>>
>>>>Note the all caps. Did that on subject to clue people in that this
>>>
> is
> 
>>>>not an actual osisRef but that the content of the element should
>>>
> be.
> 
>>>>Hope you are having a great day!
>>>>
>>>>Patrick
>>>>
>>>>Todd Tillinghast wrote:
>>>>
>>>>>It seems that we could do the same thing with osisIdentifier
>>>>
> that
> 
>>>are
>>>
>>>>>discussing for <subject>.
>>>>>
>>>>>Todd
>>>>>
>>>>>
>>>>>_______________________________________________
>>>>>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!
>>>>
>>>>
>>>>_______________________________________________
>>>>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
>>>
>>
>>_______________________________________________
>>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!