W3C home > Mailing lists > Public > public-lod@w3.org > February 2012

Re: [http-range14] how to publish RDF for Information Resources

From: Sergio Fernández <sergio.fernandez@fundacionctic.org>
Date: Fri, 17 Feb 2012 08:52:27 +0100
Message-ID: <CAMR8oe0j7KPZ2yLBMhUxsi8n5ojjTofJoLmuYeG_yPeeEqj3ZA@mail.gmail.com>
To: Yang Squared <yang.square@gmail.com>
Cc: public-lod@w3.org
Dear Yang,

I'd not recommend you not to use an information resource as the
identifier of your resource. Then, according httpRange-14, you don't
need to perform such redirection between the different representations
of your resource. Of course might be useful to link them, but that
depends on each concrete format; for instance, from HTML to RDF you
could use a meta tag on your markup.


On 17 February 2012 03:19, Yang Squared <yang.square@gmail.com> wrote:
> Hi all,
> I have an Web architecture question here.
> Assume I have a information resource URI  http://example.com/homepage.html
> I would like to publish a RDF metadata
> (http://example.com/data/homepagerdf) about this information resource (e.g.
> homepage isCreatedBy steve). What publishing mechanism can I use?
> since http://example.com/homepage.html is an Information Resource, when
> dereferencing it, we should get that homepage.html document returned. How
> can we possible redirect to a RDF?
> Content negotiation can use to serve two different representation of the
> resource, but both representation is for the same resource. So we cannot use
> it.
> 303 can redirect one information resources to another information resource,
> e.g. http://example.com/homepage.html
> --303--> http://example.com/data/homepagerdf --200-->RDF
> but in this way, when I dereferencing the
> original http://example.com/homepage.html it did not result as a
> homepage.html itself and got a RDF. So there is a paradox here.
> Can anyone please suggest anything? Or the conclusion is that the RDFa (or
> by using the link element to RDF) is the only way to publish RDF metadata
> for information resources?
> I am writing a paper and I would like to conclude that there will be no case
> that a hashURI publishing mechanism and 303 redirection can be used for
> Information Resource to publish RDF metadata. Do you have any object case?
> ------------------------------
> One may recommend me to use RDFa. However, I consider that the RDFa is not
> ideal solution to publish Linked Data at all.
> First of all, embedding metadata together with data prohibits the
> independent curation of data and metadata. Secondly, following the
> principles of the Web Architecture, any distinct resource of significance
> should be given a distinct URI, but in this approach a single URI is used to
> identify two information resources. In general, the RDFa embedded metadata
> approach can be replaced by using the <link> element href in XHTML to
> pointing to an external RDF document, where the rel=”meta” attribute can be
> used to indicate a relationship between resources.
> Thanks a lot,
> Yang Yang
> -----------------------------------
> Web and Internet Science
> Room 3027 EEE Building
> Electronics and Computer Science
> University of Southampton, SO17 1BJ
> Tel: +44(0)23 8059 8346
> twitter: @yang_squared

Sergio Fernández
CTIC - Technological Center
Parque Científico y Tecnológico de Gijón
C/ Ada Byron, 39 Edificio Centros Tecnológicos
33203 Gijón - Asturias - Spain
Tel.: +34 984 29 12 12
Fax: +34 984 39 06 12
E-mail: sergio.fernandez@fundacionctic.org
Privacy Policy: http://www.fundacionctic.org/privacidad
Received on Friday, 17 February 2012 07:53:17 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:29:57 UTC