[osis-core] RE: Work Issue

[Todd Tillinghast]

Patrick,

> 
> Todd,
> 
> Todd Tillinghast wrote:
> 
> >Partick,
> >
> >I don't think that more problems are created with the proposed
solution,
> >only problems are eliminated.
> >
> >The following seems VERY clean and straight forward.  Only values
within
> >the THIS <work>-><refSystem>->id can be used as prefixes in osisIDs,
and
> >can be used in addition to <work>->osisWork in osisRefs.
> >
> >
> And how does this differ from simply declaring that the first
refSystem
> is the default for osisIDs and any other can be use for osisRefs?
Simply
> saying that to be the case?
> 
> 
> ><osisText osisIDWork="kjv1612">
> >	<work>
> >		lots of metadata
> >		<refSystem id="kjv1612">Bible.KJV1612</refSystem>
> >		<refSystem
> >id="hebrewRefSystemThisDoc">Bible.Hebrew</refSystem>
> >	</work>
> >	<header>
> >		<work osisWork="nrsv1988">
> >			lots of metadata
> >		</work>
> >		<work osisWork="hebrewRefSystem">
> >			no or metadata other than that of "kjv1612"
> >			<refSystem
> >id="hebrewRefSystem">Bible.Hebrew</refSystem>
> >		</work>
> >	</header>
> >	<div>
> >		<verse osisID="kjv1612:Ps.1.1
> >hebrewRefSystem:Ps.1.2">.</verse>
> >
> >		<!-- equivalent, using the default prefix -->
> >		<verse osisID="Ps.1.1 hebrewRefSystem:Ps.1.2">.</verse>
> >
> >
> Note this is inconsistent with your earlier statement:

Sorry, this is an error in my example, and a very bad one at that! It
should read.
<verse osisID="Ps.1.1 hebrewRefSystemThisDoc:Ps.1.2">.</verse>

> 
> >Only values within
> >the THIS <work>-><refSystem>->id can be used as prefixes in osisIDs,
> 
> Since the hebrewRefSysem:Ps.1.2 is NOT in the THIS <work> which I
assume
> is the first work element. (It would be helpful if you would identify
the
> document/elements by ID and not THIS work as I still don't have any
idea
> what that means. Note also that I think the syntax for your osisID is
> invalid in the current schema as we don't allow spaces in osisIDs.
> 
> This is simply the mapping problem smuggled in under another name. If
you
> have some legitimate reason for wanting markup to do mapping, I would
like
> to hear it. So far, all I see is a breaking of the current ID syntax
for
> no appreciable gain.

Read the Pros and Cons and tell me if you disagree with them or how you
see things differently.

> 
> I suppose in some sense it is clean and staightforward but I can't see
the
> problem to be solved. No one is going to inconsistently use two
reference
> systems for IDs in a single work. If they do, well that is just an
error.
> 
> Sorry Todd, I keep seeing this as an attempt to put mapping into
markup
> and that is just not a viable solution. What is your objection to
putting
> it in software?
> 

I in my view this has nothing to do with mapping but everything to do
with clearly encoding what is meant.

> I'm going to bed now. I will get up and have another go at this in the
> morning.
> 
> Patrick
> 
> 
> 
> 
> 
> >		....
> >
> >		<reference osisRefs="hebrewRefSystemThisDoc:Ps.1.2"/>
> >		<reference osisRefs="Ps.1.1"/>
> >		<reference osisRefs="hebrewRefSystem:Ps.1.2"/>
> >		<reference osisRefs="nrsv1988:Ps.1.1"/>
> >	</div>
> ></osisText>
> >
> >
> >Alternatively, with the current schema, any <work>->osisWork value
can
> >be used as a prefix in either an osisRef or an osisID.
> >
> ><osisText osisIDWork="kjv1612">
> >	<header>
> >		<work osisWork="kjv1612">
> >			lots of metadata
> >			<refSystem>Bible.KJV1612</refSystem>
> >		</work>
> >		<work osisWork="hebrewRefSystemThisDoc">
> >			repeat metadata in "kjv1612"
> >			<refSystem>Bible.Hebrew</refSystem>
> >		</work>
> >		<work osisWork="nrsv1988">
> >			lots of metadata
> >		</work>
> >		<work osisWork="hebrewRefSystem">
> >			no or metadata other than that of "kjv1612"
> >			<refSystem
> >id="hebrewRefSystem">Bible.Hebrew</refSystem>
> >		</work>
> >	</header>
> >	<div>
> >		<verse osisID="kjv1612:Ps.1.1
> >hebrewRefSystem:Ps.1.2">.</verse>
> >
> >		<!-- equivalent, using the default prefix -->
> >		<verse osisID="Ps.1.1 hebrewRefSystem:Ps.1.2">.</verse>
> >
> >		....
> >
> >		<reference osisRefs="hebrewRefSystemThisDoc:Ps.1.2"/>
> >		<reference osisRefs="Ps.1.1"/>
> >		<reference osisRefs="hebrewRefSystem:Ps.1.2"/>
> >		<reference osisRefs="nrsv1988:Ps.1.1"/>
> >	</div>
> ></osisText>
> >
> >Pro: Only one place (<work>->osisWork) to find the prefix for either
an
> >osisID or an osisRef
> >
> >Pro: Current schema, no change
> >
> >Con: osisIDs self-identify elements within THIS document.  As such,
the
> >appropriate place for the reference systems used is within the THIS
> ><work> element.
> >
> >Con: An osisID can be an identifier of a different document when it
is
> >identifying the current document.
> >
> >Con: The non-default <work> element referenced by the prefix in
osisIDs
> >should have exactly the same set of sub-elements as the THIS <work>
> >element, with the exception of the <refSystem> element.  This seems
> >prone to error.
> >
> >Con: An osisRef might use the "osisWork" value of the non-default
<work>
> >element for osisIDs and get inconsistent results, if the sub-elements
> >other than the <refSystem> element are not identical to those in the
> >THIS <work>.
> >
> >Thoughts?
> >
> >Todd
> >


Todd