RE: HLink

Crawling is obviously as fundamental as searching.

Regarding confining links to  head vs. body perspective, that is up to a particular vocabulary isn't it?  I mean not all vocabs are going to have that
distinction, despite its effectiveness for html.    head vs body seems oriented towards hiding stuff
from users, to me at least.

Think about link@rel="next".  This little piece of Atom is very powerful, although I suppose it could conceivably
be confined to a head/header, it is valuable to convey that a given representation is spread over > one request, regardless
of where in the document it falls.

When you think of XML in general, we often get caught up trying to serve huge representations in one go.  Leveraging web architecture
and hypertext via the above construct (doesn't have to be limited to Atom, right?), we could allow clients
to pull in results as necessary.

Cheers
Peter

________________________________
From: Stephen D Green [mailto:stephengreenubl@gmail.com]
Sent: July 8, 2013 04:02
To: Rushforth, Peter
Cc: public-xmlhypermedia@w3.org
Subject: Re: HLink

I agree that XPath adds too much unnecessary
complexity. If part of the idea is to support bots
and crawlers it might be too much for them.

Supporting 'header' level links is clearly a must.
Not so sure whether support for links within the
actual XML ('body') is so important though, is it?

----
Stephen D Green


On 5 July 2013 16:37, Rushforth, Peter <Peter.Rushforth@nrcan-rncan.gc.ca<mailto:Peter.Rushforth@nrcan-rncan.gc.ca>> wrote:
Hi Stephen,

AF seems to have both in-line and out-of-line semantics, and the HLink note seems to me to be a type of AF.
(maybe I'm wrong, I'm just learning about AF after all).

But regarding dret's blog piece:

"the main idea is that links are identified by XPath-based selectors"

even using XPath, which I do love (well, version 2.0 at least), I think is too complex.  I think you
need to have a what you read is what you get approach to hypertext.

I am in favour of "no fancy tricks", as far as possible, and I think this falls under the "fancy tricks" rubric.

Cheers,
Peter

________________________________
From: Stephen D Green [mailto:stephengreenubl@gmail.com<mailto:stephengreenubl@gmail.com>]
Sent: July 5, 2013 10:25
To: Rushforth, Peter
Cc: public-xmlhypermedia@w3.org<mailto:public-xmlhypermedia@w3.org>
Subject: Re: HLink

A search ('hateoas hlink') turned up this blog which might be of interest
http://dret.typepad.com/dretblog/2009/06/link-discovery-for-xml.html.
Very little else (which in itself is quite interesting).

----
Stephen D Green


On 5 July 2013 14:54, Stephen D Green <stephengreenubl@gmail.com<mailto:stephengreenubl@gmail.com>> wrote:
We could think about what an HATEOAS
implementation using HLink and XML would look like.

I'm assuming (not 100% clear reading the W3C Note)
that HLink can be used with XML outside of XHTML.
There is the example given in the Note of using it with
some plain old XML
<home xmlns="http://www.example.com/markup" />.

----
Stephen D Green


On 5 July 2013 14:00, Stephen D Green <stephengreenubl@gmail.com<mailto:stephengreenubl@gmail.com>> wrote:
http://www.xml.com/pub/a/2002/09/25/hlink.html is where I found reference to it.


----
Stephen D Green


On 5 July 2013 13:57, Rushforth, Peter <Peter.Rushforth@nrcan-rncan.gc.ca<mailto:Peter.Rushforth@nrcan-rncan.gc.ca>> wrote:
Sure, let's talk about HLink.  I haven't seen that before.  What does it do?

How does it improve on XLink?

Cheers,
Peter