[osis-core] osisCore_Candiate_1.1_003 - 11 osisRef URLs

[Todd Tillinghast]

YIPES!

We are free to create a mechanism OUTSIDE the document that provides
hyperlink type behavior based on <reference> elements.  The reference
should merely be an identifier and not include information related to a
retrieval transport protocol, request mechanism, or even imply a
specific document location.

Todd

> Todd,
> 
> This group decided to add an <a> element some time ago, while you were
> off the list.
> 
> What I am proposing now is a way of using the <a> element to link to a
> document/location specified by an osisRef.
> 
> -Harry
> 
> 
> > -----Original Message-----
> > From: owner-osis-core@bibletechnologieswg.org
> > [mailto:owner-osis-core@bibletechnologieswg.org] On Behalf Of
> > Todd Tillinghast
> > Sent: Wednesday, August 21, 2002 3:20 PM
> > To: osis-core@bibletechnologieswg.org
> > Subject: RE: [osis-core] osisCore_Candiate_1.1_003 - 11 osisRef URLs
> >
> >
> > We had discussed an <a> element at one point and decided not
> > have such an element.  The decision was that we would
> > consider in a future release support of XLink and XPointer
> > type expressions in a reference like element or even in an
> > enhanced <reference> element.
> >
> > All sorts of reasons not to put an <a> element in.
> >
> > If you need an href in you presentation then it is possible
> > to create an <a href=".."/> element in your output.  We could
> > provide a mechanism to specify an URL for a work in the
> > <work> element.  More thought needed.
> >
> > Todd
> >
> >