|
[XML-DEV Mailing List Archive Home]
[By Thread]
[By Date]
[Recent Entries]
[Reply To This Message]
Re: Re: ***SPAM*** Resource relationships
- From: Tim Bray <tbray@textuality.com>
- To: "Liam R. E. Quin" <liam@fromoldbooks.org>
- Date: Sat, 13 Jun 2020 11:08:58 -0700
I'm still disappointed about XLink's failure to catch on. I still think it'd solve significant real-world problems that I still encounter. But obviously the browser builders didn't see it that way and maybe they were right. That said, at the point in history when XLink appeared, the browser-builder politics and dysfunction were pretty nasty, so perhaps there's an element of bad luck at work. Can't complain too much, XML enjoyed a massive stroke of good luck by arriving at a time when there was no decent open interchange format at all and a massive undiscovered hunger for such a thing.
On Sat, 2020-06-13 at 05:33 +0000, Hans-Juergen Rennau wrote:
>
> QUESTION 1. Why is XLink little adopted
It solved the wrong problem. That is, the primary use case it addressed
was, markup to include in one's doucment that could be identified by
soeone outside one's own organization or domain as a link. But that is
solving someone else's problem.
What was needed was something like HyTime Architectural Forms, to say,
in this DTD, in this document, such-and-such an attribute, or element,
or combination, represents a link, and _this_is how you construct the
URL from it.
But the working group became mired in arguments and politics.
It should be noted that some of the features XLink provides still have
no standard counterpart in HTML. Practical use cases and examples may
have made a difference, but HTML already had a/@href and img/@src, and
these canbe used in XML DTDs as easily as XLink.
A regret that i have is that an architectural forms route might have
let us say, "in this vocabulary, the following elements are paragraph-
like and these other ones are phrase-like", enabling search engines to
present useful snippets.
> - can you identify important mistakes or omissions?QUESTION 2.
> Imagining for a moment, XLink were widely adopted, would a "link::"
> axis in XPath make sense, enabling expressions like: /
> ancestor::airports / child::airport / link::airportDetails / @name
Or a follow() function maybe. Note that XLink permits multiple links on
an element, so one would need a way to say which links were of
interest.
Liam
--
Liam Quin, https://www.delightfulcomputing.com/
Available for XML/Document/Information Architecture/XSLT/
XSL/XQuery/Web/Text Processing/A11Y training, work & consulting.
Barefoot Web-slave, antique illustrations: http://www.fromoldbooks.org
_______________________________________________________________________
XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.
[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
|
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format
| RSS 2.0 |
 |
| Atom 0.3 |
 |
| |
Stylus Studio has published XML-DEV in RSS and ATOM formats,
enabling users to easily subcribe to the list from their preferred news reader application.
|
Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website.
they were not included by the author in the initial post. To view the content without the Sponsor Links please
click here.
|
|
Cart
