[osis-core] reference systems: Issue 1

[Todd Tillinghast]

If we are going to make to "compromise" to use works simply as the
"namespace" and not use reference system as the "namespace" which would
likely result in only two or three reference systems in common use for
Bibles, we should make every effort to avoid the NEED to perform
transformations (or check for a transformation) between identifiers in
different namespaces.  

In many cases for Bibles (other works will not have as many versions,
editions, and reference systems) we should be able to use Bible:B.C.V as
self-identifiers in osisID as well as references in osisRef.  If a
references is made to a specific work Bible.tev:B.C.V and we can know
that the transformation between Bible and tev is identity by virture of
the case of the "t" in "tev" then so special software is required to
perform the transformation.

Further there would be no need even define a transformation if a simple
convention is in place.  (Ex: Bible.niv.-1993.en would require not
transformation be defined at all AND if the case were Bible.NIV.-1993.en
and Bible.NIV.-1999.en and Bible.NIV.student then not transformation
would need be made between the Bible.NIV versions.

Todd

> 
> The proposal assumes that if there is a reference system
> xxx.yyy, then there is also a reference system xxx and a
> xxx <--> xxx.yyy transformation. The transformation can be
> the identity in some cases, but there is always a transformation.
> 
> There's no "fallback" in the sense that no transformation is
> required, but fallback is always possible in the sense that
> we can perform the necessary transformation with existing
> information.
> 
> Bible, Bible.French, and Bible.French.LSV need not be related
> in any way except that there is a Bible <--> Bible.French
> transformation and a Bible.French <-->Bible.Frency.LSV.
> 
> -Harry
> 
> 
> > In some cases the identifiers separated by "." only specify a
> > more specific work and in other cases a transformation is required.
> >
> > In the case of Bible.NIV.1993.en:Ps.45.3 I can simply drop
> > ".NIV.1993.en" and use "Ps.45.3" as Bible.Ps.45.3 or drop
> > ".1993.en" and use "Ps.45.3" as Bible.NIV:Ps.45.3 without
> > translation, BUT with Bible.French.LSV:Ps.45.3 there is a
> > transformation required at by French.  Do we want to create
> > namespaces that require transformation of "fall back"?  If we
> > do how can we indicate that a transformation is required.
> >
> > Possible solution: use upper case letters to identify that an
> > identifier requires a transformation.
> >
> > Example:
> > Bible.niv.en:Ps.45.3 does not require a transformation when
> > falling back to Bible.
> >
> > Bible.French.lsv:Ps.43.3 does require a transformation when
> > falling back to Bible:Ps.44.3 but does not require a
> > transformation when falling back to Bible.French:45.3!
> >
> > There is a problem when using numbers because they have not
> > case.  We could force identifiers in the "namespace" to start
> > with case oriented identifier and/or we could reserve a
> > transformation identifier.  (Ex:
> > Bible.niv.-1993.en)
> >
> > Todd
> >