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

[Todd Tillinghast]

I agree that a <reference> element does not cause text to be underlined.
But we are talking about XML and not HTML.  Even if there were an <a
href="..."/> element that does not mean that is a hyperlink.  It is up
to the schema to define the syntax and for software to treat an element
in XML as a hyperlink.  Hyperlinks for presentation in HTML can be
created in a variety of ways.  

The introduction of an <a> element seems to take us into encoding
presentation type information.  

I am also not sure what the uses for an <a> element would be.  Can you
help me out here?

Todd
> 
> Troy,
> 
> My understanding (which could of course be wrong) is that the
> <reference> element says that there is a reference or allusion, but it
> doesn't have the same hyperlink semantics of <a>. That is, it doesn't
> cause the text to be underlined, and it doesn't replace the doc with
the
> referenced doc when the link is clicked.
> 
> -Harry
> 
> > -----Original Message-----
> > From: owner-osis-core@bibletechnologieswg.org
> > [mailto:owner-osis-core@bibletechnologieswg.org] On Behalf Of
> > Troy A. Griffitts
> > Sent: Wednesday, August 21, 2002 3:14 PM
> > To: osis-core@bibletechnologieswg.org
> > Subject: Re: [osis-core] osisCore_Candiate_1.1_003 - 11 osisRef URLs
> >
> >
> > 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
> >
> >
> >