[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: ***SPAM*** Resource relationships

  • From: "Liam R. E. Quin" <liam@fromoldbooks.org>
  • To: Hans-Juergen Rennau <hrennau@yahoo.de>, "xml-dev@l..." <xml-dev@l...>
  • Date: Sun, 14 Jun 2020 10:03:50 -0400

Re: ***SPAM***   Resource relationships
On Sat, 2020-06-13 at 20:24 +0000, Hans-Juergen Rennau wrote:
>  Liam, please help me make sure that I understand you correctly, when
> you say:"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."Do you mean *URI construction* from instance data? Do
> you want to point out this difference: whilst XLink presupposes
> ready-to-use URIs contained in attributes, it fails to address the
> construction of URIs from document data, e.g. in the style of URI
> templates (RFC 6570)?

I mean two things.

First, one should have been able to have said, in this vocabulary, that
some element's content is connected to other documents as a link;
second, one should have been able to have constructed an IRI (they were
URLs back then) in the manner of URI templates, yes.

Consider potential explicitly-marked-up links in the following:

  <p>When <place>King’s College</place> was founded, the circle had not
  yet been invented, which is why <person>John Wood</person> wrote his
  seminal <work><title>Rectangles and Quadrangles</title></work>.</p>

One might have,
   <link match="place" method="get" uri="lower-case(translate(' ', '-', 
.))" />
   <link match="work[title]" uri="/search">
     <with-param name="title" select="title" />
   </link>
(with missing components such as method, server, port etc. having
sensible defaults based on context).

Combining this with mapping elements to HTML equivalents for search
engine purposes, and maybe with automatic/external namespaces that i
proposed at one point, would be a very different approach than XML
Schema :) and would be more focused on meeting needs of people who use
Web browsers and Web search.

Around the time XLink was being developed, though, there were still
SGML people saying the Web wouldn't last, wouldn't scale, would go away
soon.

-- 
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



[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!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
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.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.