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

[Todd Tillinghast]

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
 
> 
> Harry,
> 	I was under the impression that <reference> was designed
> specifically for
> things like hyperlinks (or _whatever_ referencing mechanism is used
for
> the presentation media).
> 
> 
> 
> Harry Plantinga wrote:
> > We currently have no way to make a simple hypertext
> > link using the osisRef system.  We can make a <reference>,
> > but that's not a hypertext link.  I propose we define
> > a URL syntax for osisRefs.
> >
> >   a) <a href="osis:Bible.KJV:Matt.1.1">
> >
> > or, If you prefer more (and more distinctive) syntax,
> >
> >   b)  <a href="osis://Bible.KJV:Matt.1.1">
> >
> > I suppose an alternative would be to add an osisRef attribute
> > to the a element, so you could write
> >
> >   c) <a osisRef="Bible.KJV:Matt.1.1">
> >
> > In the first two examples, osis: is the protocal name, like
> > http or ftp.  Processing software would presumably convert
> > such links to regular http:// URLs in the conversion from
> > OSIS to HTML.
> >
> > What needs to be done?
> >
> >   - pick a syntax
> >   - document it
> >   - for option a or b, figure out if it is possible to
> >     'register' the osis: protocol name
> >   - patch netscape to handle such URLs (maybe somewhat later)
> >
> > -Harry
> 
>