[xml-h] picking up the thread
Sat Jan 18 15:09:37 GMT 2003
Fair enough, though I think "where the links go" is a pretty basic data
modeling issue. Combined with the rules for markup, it sets the terms
on which you can build the links.
I'd still like to step back from the how brigade
(I see this very much related to the ID'ness args on tag list)
and ask what the 'end user' i.e. customers want out of links,
then look at data modelling and the more usual world of how
to achieve it.
As an author I want to say quite a bit when I author a link.
I want (end result) the end user to be able to navigate
across that link to the target.
I want the link content to be informative
THis will take you out of this page
This will take you to fred bloggs site
(inference, if you aren't connected don't go there)
If your pipe is dead slow don't bother
If you're interested in this excursion go see
I want the app that's rendering the link to ensure its available
(compare the mac sad face with the 404 == bsod) and tell me kindly
that it ain't working, even why its not working?
I want to get back if needed (bookmark this page).
I want to go to the right place in the page (no cranky HTML
If the app can offer more, then we're into USP's.
I'd prefer this sort of end user (author and recipient) discussion
to preceed the how to do it discourse.
That's what I intended to get at on the tag list.
More information about the xml-hypertext