W3C home > Mailing lists > Public > public-poiwg@w3.org > August 2011

Re: Proposal: The "POI as a simple collection of links" data model

From: Thomas Wrobel <darkflame@gmail.com>
Date: Sat, 13 Aug 2011 12:20:00 +0200
Message-ID: <CADVvL4mDcXvgJPWMd-JprEcDdbKkxRAgf15iq1Tc737x9xWJbA@mail.gmail.com>
To: roBman@mob-labs.com
Cc: "public-poiwg@w3.org" <public-poiwg@w3.org>
I think seeing  POIs as fundamentally link based is certainly the way
to go. We talked at some point of "physical hyperlinks" and its always
stuck in my head as that.

I also agree it should be serialisable as Triples/RDF/N3 if desired -
as this gives lots of flexibility for deployment methods (Ive always
been rather skeptically of html5 being the primary way it will be
But to be able to guaranty storage in "flat" forms like that we must
exclude any xml hierarchy's for anything other then deployment
specific optimisation.

I also generally think location will be dealt with inline most of the
time, and content and description as links, but keeping it flexible
enough to handle other things inline is a good idea.


Reviews of anything, by anyone;
Please try out my new site and give feedback :)

On 7 August 2011 05:47, Rob Manson <roBman@mob-labs.com> wrote:
> Hi Karl,
> if we aim to make this standard work within html5 then you're absolutely
> right.
> However, if it's targeting other types of browsers and other contexts
> then I think there is some merit in being able to serialise the payload
> of a link (the bit between the >*< ) while still identifying it's
> canonical source (href=canonical_source).  It is definitely a logical
> possibility.
> And if the standard supported this but did not require it then html5
> compatibility could still be maintained too (maybe as a profile).
> roBman
> On Sat, 2011-08-06 at 20:26 -0400, Karl Dubost wrote:
>> Hi,
>> FYI
>> This following one will not work.
>> > external link with inline content
>> >
>> >   <link rel="thing" href="url_to_canonical_source_for_thing_stuff">
>> >     serialised inline thing stuff goes here
>> >   </link>
>> The browser will auto-correct the link by closing it and putting the text outside. Not what you expect.
>> http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1096
Received on Saturday, 13 August 2011 10:20:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:48:30 UTC