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

[Steve DeRose]

At 04:31 PM -0400 08/21/02, Harry Plantinga wrote:
>Hmmm.  Well, no matter how you handle a hypertext link, isn't
>it semantically different from a reference?

*That* is a really interesting question. Are you saying basically 
that the defining criterion of links is traversal? That's certainly 
reasonable, though it's not the XLink or RDF view. I'm not sure what 
I think on that one.

>
>In any case, some time ago I asked how simple hypertext links
>should be translated into OSIS -- use the <reference> element?
>The answer was to add the <a> element.
>
>-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 4:24 PM
>>  To: osis-core@bibletechnologieswg.org
>>  Subject: Re: [osis-core] osisCore_Candiate_1.1_003 - 11 osisRef URLs
>>
>>
>>  Harry,
>>	Though I see your point, doesn't this assume
>>  presentation?  If I'm
>>  printing a Bible, I might just want to add a \super 1 after
>>  the enclosed
>>  phrase and have a footnote that says, \super 1See: James 1:19
>>
>>	I'll let you guys decide as you may have other reasons
>>  for using <a>
>>  rather than <reference>.
>>
>>	My only feeling on the matter is that it seems we've
>>  done a good job
>>  staying a degree away from what might be considered
>>  presentation tags,
>>  or mandating HOW to deal with something, as opposed to just making
>>  claims ABOUT something.
>>
>>
>>	-Troy.
>>
>>
>>
>>  Harry Plantinga wrote:
>>  > 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
>>  >>
>>  >>
>>  >>
>>
>>
>>


-- 

Steve DeRose -- http://www.stg.brown.edu/~sjd
Chair, Bible Technologies Group -- http://www.bibletechnologies.net
Email: sderose@speakeasy.net
Backup email: sjd@stg.brown.edu