XNRL

Date:      Sun, 31 Dec 2000 20:11:15 -0800
From:      Tim Bray <tbray@textuality.com>
To:        XML-Dev Mailing list <xml-dev@xml.org>
Subject:   XNRL

The idea, most fully worked out by Jonathan Borden, of overloading the HTML <link> element to serve as related-resource xlinks, is cool, but I see two problems with it:

1. I'd like to tie the xlink to the related resource to the prose that defines it 2. If you overload <link>, you get into difficulties with href= vs xlink:href=... - due to parts of the design of namespaces and xlink that make several people uncomfortable, but the problem is there.

#1 is probably solve-able by giving the <link>s an id= and pointing at them from the prose, but that feels a bit awkward. #2 I think is a real problem (or am I missing something?).

So, here's a plan B proposal...

http://www.textuality.com/xml/xnrl.html.

So far, there's no place for media-type, is it really useful to dispatch on at the end of the day? Lots of other things could be done, but this is a place for the dare-to-do-less principle.

I went and locked up xnrl.org, but it was a Bad Network Solutions Day and it kinda croaked halfway through, the actual name isn't important.

Time to de-geek and do New Year's Eve stuff... best of the millennium to y'all. -T

Prepared by Robin Cover for The XML Cover Pages archive. See also references in "Namespaces in XML."

SEARCH Advanced Search ABOUT Site Map CP RSS Channel Contact Us Sponsoring CP About Our Sponsors NEWS Cover Stories Articles & Papers Press Releases CORE STANDARDS XML SGML Schemas XSL/XSLT/XPath XLink XML Query CSS SVG TECHNOLOGY REPORTS XML Applications General Apps Government Apps Academic Apps EVENTS LIBRARY Introductions FAQs Bibliography Technology and Society Semantics Tech Topics Software Related Standards Historic	XNRL Date: Sun, 31 Dec 2000 20:11:15 -0800 From: Tim Bray <tbray@textuality.com> To: XML-Dev Mailing list <xml-dev@xml.org> Subject: XNRL The idea, most fully worked out by Jonathan Borden, of overloading the HTML <link> element to serve as related-resource xlinks, is cool, but I see two problems with it: 1. I'd like to tie the xlink to the related resource to the prose that defines it 2. If you overload <link>, you get into difficulties with href= vs xlink:href=... - due to parts of the design of namespaces and xlink that make several people uncomfortable, but the problem is there. #1 is probably solve-able by giving the <link>s an id= and pointing at them from the prose, but that feels a bit awkward. #2 I think is a real problem (or am I missing something?). So, here's a plan B proposal... http://www.textuality.com/xml/xnrl.html. So far, there's no place for media-type, is it really useful to dispatch on at the end of the day? Lots of other things could be done, but this is a place for the dare-to-do-less principle. I went and locked up xnrl.org, but it was a Bad Network Solutions Day and it kinda croaked halfway through, the actual name isn't important. Time to de-geek and do New Year's Eve stuff... best of the millennium to y'all. -T Prepared by Robin Cover for The XML Cover Pages archive. See also references in "Namespaces in XML."