Hi Karl,<div><br></div><div>I first asked about this over a year ago, and got no response (see <a href="http://n4.nabble.com/Linking-to-a-specific-location-in-an-article-td357981.html">http://n4.nabble.com/Linking-to-a-specific-location-in-an-article-td357981.html</a>). As I didn't really have time for the project I was wanting it for (linking the table of contents entries in dictionary articles like in the ISBE to that section in the lengthy article), I didn't end up pursuing it. I did look at the OSIS manual, and it didn't seem to have any support for doing it with either the <a> element and <a name> or with placing a marker in some other way, nor did OSIS refs support such things. It was a long time ago, though, so my memory could be faulty. Another possibility I considered but did not investigate further was using the identifier for an OSIS section and putting in an <a name> element based on that and then linking to it. This would work fine for the section navigation problem, but is probably </div>
<div><br></div><div>I would support the use of links to arbitrary points in an OSIS / ThML document, especially if modules where it made sense used it. I don't have strong opinions on how to represent it, but I do think that the HTML support is reasonably well known and seems to work. That being said, if work needed to be done to make BPBible support it I probably wouldn't do it any time soon (probably not until there were modules using it).</div>
<div><br></div><div>Jon<br><br><div class="gmail_quote">On Thu, Mar 18, 2010 at 2:13 PM, Karl Kleinpaste <span dir="ltr"><<a href="mailto:karl@kleinpaste.org">karl@kleinpaste.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
As folks here know, I continue to generate ThML modules, mostly due to<br>
its simplicity of use via its "HTML plus goodies" nature, the goodies<br>
being <note>, <scripRef>, and some <div> cases. I'm looking for<br>
information or opinion about whether something I've worked on, currently<br>
specific to ThML, has an equivalent interpretation in OSIS.<br>
<br>
This week, I've done some work in Xiphos so as to be able to support<br>
#anchor references. The immediate use is for how I roll my own NET and<br>
NETnote modules, NET being my most-used translation these days. In NET,<br>
I generate this kind of footnote content:<br>
<br>
<note><a href="sword://NETnote/Ge1:2#n13">Note 13</a></note><br>
<br>
Now, in Xiphos, passing over a footnote marker "*n", "Note 13" goes to<br>
the previewer, as a link. Clicking the link kicks our main URL handler,<br>
separating module+verse reference from anchor, navigates the reference<br>
(in both Bible and commentary), then jumps to the anchor.<br>
<br>
Similarly, NETnote now has each note self-identified thus:<br>
<br>
<a name="n13" href="sword://NETnote/Ge1:2#n13"><font size="-1"><b>13 -</b></font></a><br>
<br>
This provides the anchor reference name to be used from the NET<br>
footnote, and also makes each note self-clickable, meaning that I can<br>
click a footnote marker within NETnote itself (whether it's from the<br>
current verse or not), to induce that footnote to home to top of pane<br>
and force the Bible pane to navigate to the relevant verse as well.<br>
<br>
This content is easy and directly implementable for paired (companion)<br>
modules like NET + NETnote. Another use case for this markup is<br>
e.g. the possibility of bookmark references in genbooks, where<br>
/The/Section/Under/This/Complicated/Key may be very long, and<br>
availability of references to individual paragraphs could be very<br>
useful. Tack on #paragraph12 to such a key, and now getting to a<br>
particular reference in a 50-paragraph theological thesis section<br>
becomes easy.<br>
<br>
I'm thinking about this kind of issue especially in terms of user<br>
content authoring, that is, Xiphos now has personal commentary,<br>
prayerlists and journals, and highlighter-style verse annotations, all<br>
due to user requests for more user-contributed content. Users who want<br>
to author serious content in their own personal commentaries or journals<br>
should be able to provide these kinds of markers in their own content,<br>
and to reference others' markers when they write.<br>
<br>
Two problems, for which I'd like to see comment:<br>
<br>
[a] This capability is Xiphos-specific at the moment; I'm not aware that<br>
any other Sword UI contemplates #anchor-specific navigation. How do<br>
others feel about making such a capability available?<br>
<br>
[b] One question is whether there is a semantic equivalent of #anchor in<br>
OSIS. Does the syntax for osisRef provide for subsection indication?<br>
Can it escape the filtration system so as to arrive at the app in this<br>
kind of URL #anchor? Generally, what's the state of osisRef support?<br>
<br>
--karl<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</blockquote></div><br></div>