Eugene Eric Kim wrote:
>
> On Thu, 12 Apr 2001, Murray Altheim wrote:
>
> > I don't think either Purple or PLink (I think I'm going to simply call
> > it "plink" instead) avoids any of the classic link maintenance issues.
>
> Purple supports statement IDs (the address in parentheses) in addition to
> hierarchical IDs, just like Augment. The idea is for statement IDs to be
> permanent. So links to statement IDs won't break with new versions of the
> document, assuming that the statement IDs still exist in those later
> versions.
Maybe I'm not understanding this correctly, so please elaborate. If one
preprocesses an HTML file to add the hID and sID links, the result is a
document with an overlay of structural and sequential links representative
of the structure of the document at the time the process was run. If an
editor adds a third paragraph to section four, what was, say, "D3 (12)"
now becomes "D4 (13)". Links made to this paragraph in earlier versions
of the document now point to the newly added paragraph.
Is there something in the way Purple works that avoids this? Doesn't
adding or deleting paragraphs break links made to earlier versions of
these targets?
> Obviously, there's no way to enforce this practice. But Purple encourages
> this by providing a tool and describing a methodology for managing IDs and
> versions.
I'm gonna have to RTFM on this I guess. Unless one hand-manages these
links, I'm not clear how this works.
Murray
...........................................................................
Murray Altheim <mailto:altheim@eng.sun.com>
XML Technology Center
Sun Microsystems, Inc., MS MPK17-102, 1601 Willow Rd., Menlo Park, CA 94025
In the evening
The rice leaves in the garden
Rustle in the autumn wind
That blows through my reed hut. -- Minamoto no Tsunenobu
This archive was generated by hypermail 2.0.0 : Tue Aug 21 2001 - 17:58:04 PDT