Joe D Willliams wrote:
[...]
> > dkr takes a "v" attribute to designate a version of a
> > document.
>
> > put in a <meta> element
> > containing plink's document generation date.
>
> > site map topic map that would act as a sort
> > of online revision control system.
>
> OK, now you two are close to having defined a
> reasonably complete baseline capability and
> backed it up reasonable implementations.
> So now it is time for our webmaster to pick 5-8
> elements of current bootstrap web site and start a
> DKR on the bootstrap web site to allow navigation
> within web pages.
plink already has a customization feature so that a user can
determine which elements are divisions, and which are "significant":
% java plink -d "h1|h2|h3|h4" -e "p|blockquote|pre" -x source.html
although right now it doesn't do anything intelligent with truly
empty elements like <img />. I also added a feature so that the letter
function (that generates the "A" in "4A") now goes up to 701 ("4ZZ").
> As this develops, code sharing should occur and within
> a month or so we converge to a single encoding of
> this tool.
Could you please briefly describe this process? I've never used
sourceforge.net in this capacity.
> Please note that each hID and sID link should have
> a unique ID. In the published markup, "hID" and "sID"
> are CSS classes and ID is a unique "IDREF", so that all links
> can be retrieved in a nice list, or individually
> I assume that the hID and sID links are decendents
> of the info item between the current hID/sID
> combination and the previous hID/sID combo.
> A main idea is to be able to retrieve a list of these
> for use in mapping the DKR contents.
Actually, my classes are "plink" and "plinks", as I think it
a bit dangerous to label things without plink, to avoid conflict
with existing markup. I hope this weekend to add a clean-plink
function, and perhaps get it ready to release.
> When this gets a little further along, then let's consider
> how this markup might work in DKR structures that
> might use other ways to display/store information than
> XML (XHTML).
Currently, plink isn't limited to XHTML. It defaults to a set of
XHTML element types for divisions and significant elements, but
this is customizable by the user. Although I do understand your
question to be about non-XML issues, too.
Murray
...........................................................................
Murray Altheim, SGML/XML Grease Monkey <mailto:altheim@eng.sun.com>
XML Technology Center
Sun Microsystems, 1601 Willow Rd., MS UMPK17-102, Menlo Park, CA 94025
the wood louse sits on a splinter and sings to the rising sap
ain't it awful how winter lingers in springtimes lap -- archy
This archive was generated by hypermail 2.0.0 : Tue Aug 21 2001 - 17:58:04 PDT