[osis-core] is osisRef a list or a single value?

[Todd Tillinghast]

Patrick,

In osisCore.1.5.xsd osisRef it is a single value.  We have made
annotateRef a list of what was allowed in osisRef in I 1.5 (with a grain
oriented tweak).

In osisCore.1.9.6.xsd osisRef is a list in the same way that annotateRef
is a list.  This actually solves some encoding problems we have had in
the past but also introduces an element of complexity to osisRef.  This
is not particularly bothersome because that same complexity already
exists with annotateRef.

This is backward compatible and solves the long standing issue of how to
encode a reference to discontinuous text, because the discontinuous
parts can be individual whitespace separated values in the osisRef.

Todd

> -----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:44 AM
> To: osis-core@bibletechnologieswg.org
> Subject: Re: [osis-core] osisSubjects?
> 
> Todd,
> 
> Todd Tillinghast wrote:
> > Patrick,
> >
> >
> <snip>
> 
> > Should the body be the form of osisRef or annotateRef?  Currently
there
> > is one subject for subject element so osisRef is probably the most
> > consistent?
> >
> 
> Reading between the lines I may have screwed something up. Currently
> osisRef can be a list, using the same mechanism as osisID.
> 
> Or do you mean we constrain the <subject> in prose to only be one?
> 
> Hope you are 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