From: Norman Walsh <ndw@nwalsh.com>
To: Gregory Leblanc <GLeblanc@cu-portland.edu>
Cc: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: Linking collections (was: RE: I'm trying to set up docbook-tools. ..)
Date: Mon, 10 Jul 2000 07:03:00 -0000 [thread overview]
Message-ID: <87wviugk0h.fsf@nwalsh.com> (raw)
Message-ID: <20000710070300.yFhkaOgEXw91YxarMJA1Stdgd02viYqmZAw9TewYfzU@z> (raw)
In-Reply-To: <A5F46F4ED18FD211ABEE00105AC6CF07010938DB@email.cu-portland.edu>
/ Gregory Leblanc <GLeblanc@cu-portland.edu> was heard to say:
| > -----Original Message-----
| > From: Norman Walsh [ mailto:ndw@nwalsh.com ]
| > SGML doesn't really have a good cross-document linking
| > solution (though
| > you can cobble one together, see my tutorials about olink on
| > nwalsh.com).
http://nwalsh.com/docbook/dsssl/doc/olinksemantics.html
| it, but I'd appreciate a pointer if you read this before I find it. There
| really needs to be a good way to link between separate documents for a lot
| of things. That's one of the biggest problems that the LDP has right now.
| It's very hard to reference other documents because all you can do is say
| "read document named X", and not do a very good job linking to that
| document, or even better, to a specific section of that document.
It's one of the biggest problems XML has right now, IMHO. It should
be/will/is possible to build a solution with XPointer and XLink, but I
don't know of an out-of-the-box one available now.
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | All our foes are mortal.--Val\'ery
http://nwalsh.com/ |
next prev parent reply other threads:[~2000-07-10 7:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 6:36 Linking collections (was: RE: I'm trying to set up docbook-tools...) Gregory Leblanc
2000-12-27 6:36 ` Norman Walsh [this message]
2000-07-10 7:03 ` Linking collections (was: RE: I'm trying to set up docbook-tools. ..) Norman Walsh
2000-12-27 6:36 Gregory Leblanc
2000-12-27 6:36 ` Peter Toft
2000-08-03 15:39 ` Peter Toft
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wviugk0h.fsf@nwalsh.com \
--to=ndw@nwalsh.com \
--cc=GLeblanc@cu-portland.edu \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).