W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > August 2007

Re: [RDFa Syntax] @resource and @href

From: Mark Birbeck <mark.birbeck@formsPlayer.com>
Date: Mon, 20 Aug 2007 13:11:50 +0100
Message-ID: <a707f8300708200511t4dbe5b68n923caeca6d8af1dd@mail.gmail.com>
To: "Ivan Herman" <ivan@w3.org>
Cc: "Hausenblas, Michael" <michael.hausenblas@joanneum.at>, "W3C RDFa task force" <public-rdf-in-xhtml-tf@w3.org>, "Shane McCarron" <shane@aptest.com>, "Ben Adida" <ben@adida.net>, "Steven Pemberton" <steven.pemberton@cwi.nl>

Sorry, I'm being dim, and thought that Ivan was replying to the point
about the best practices document which came out of the telecon
discussion of Michael's proposal.

Ivan--we've already agreed not to add this to the spec, since as you
correctly point out, from a triple point of view there is nothing to
say because there is no difference between @href and @resource. We
agreed that the only distinction we really want is between a navigable
resource and a non-navigable one. (Which may or may not be based on
information resources and the like, but it doesn't have to be--you
could use @resource for an information resource if you are not
bothered about the user being able to navigate to it.)

Michael--I've been flushed out as not being in favour of the best
practices document without even realising it. :)

Sorry for any confusion...

On 20/08/07, Mark Birbeck <mark.birbeck@x-port.net> wrote:
> I do agree with Ivan, although I'll go with the majority decision if
> other people think there is no problem.
>
> I think we should certainly ensure that we 'do the right thing' in the
> primer, so that people can see examples of different use-cases or
> @resource and @href. But in addition to Ivan's concerns, I'd also like
> to add that we might be getting a few too many documents floating
> around, and the primer and syntax documents should really be where we
> focus our efforts.
>
> On 20/08/07, Ivan Herman <ivan@w3.org> wrote:
> > Michael,
> >
> > with all due respect: I do not think we should go there.
> >
> > There are huge discussions on what information and non-information
> > resources are, whether they are the right names, etc, etc; let us not go
> > there. Also: from an RDF perspective, a URI is a URI, regardless of what
> > they refer to (ie, informational or non-informational resource), which
> > makes it even messier. Finally: no RDFa parser could check this
> > requirement...
> >
> > Yes, I was in favour and I am in favour of using @resource in general,
> > but we have agreed to allow for @href everywhere and there is no need to
> > reopen that discussion. Having both actually helps the RDFa author to
> > fine tune the generated triples; that is as far as we should go in my
> > view...
> >
> > My two pence...
> >
> > Ivan
> >
> > Hausenblas, Michael wrote:
> > >
> > > I had a quick look at the RDFa Syntax [1] document
> > > and did not actually find any usage of @resource.
> > > (BTW, Shane, I did not find any @resource declarations in
> > > the DTDs [2] and [3] - did I miss something?)
> > >
> > > Further, Ivan recently stated in [4]:
> > >
> > >  'I was always in favour of @resource, and @href only
> > >   in the dedicated place, ie, in <a>:-)'
> > >
> > > So, to assist people in using @resource and @href 'correctly',
> > > I'd like to propose the following addition to the RDFa Syntax.
> > >
> > > <PROPOSAL>
> > >
> > > 'As per TAG finding httpRange-14 [5] the value of @href
> > >  MUST be an information resource, and the value of @resource
> > >  MAY be an information resource. RDFa authors SHALL use a URI
> > >  that identifies a non-information resources for the value
> > >  of @resource.'
> > >
> > > </END_OF_PROPOSAL>
> > >
> > > As an aside: The two RDFa test cases TC 31 [6] and
> > > TC 32 [7] already demonstrate this 'good practice':
> > >
> > > TC 31
> > > =====
> > >
> > >  <p about="#wtw">
> > >   The book <b>Weaving the Web</b> (hardcover) has the ISBN
> > >   <span rel="dc:identifier"
> > >         resource="urn:ISBN:0752820907">0752820907</span>.
> > >  </p>
> > >
> > > TC 32
> > > =====
> > >
> > >  <p about="#wtw">
> > >   The book <b>Weaving the Web</b> (hardcover) has the ISBN
> > >   <a rel="dc:identifier"
> > >      resource="urn:ISBN:0752820907"
> > >
> > > href="http://www.amazon.com/Weaving-Web-Tim-Berners-Lee/dp/0752820907">0
> > > 752820907</a>.
> > >  </p>
> > >
> > > Cheers,
> > >       Michael
> > >
> > > [1] http://www.w3.org/MarkUp/2007/ED-rdfa-syntax-20070812/
> > > [2] http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd
> > > [3] http://www.w3.org/MarkUp/DTD/xhtml-hypertext-1.mod
> > > [4]
> > > http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Aug/0121.
> > > html
> > > [5] http://www.w3.org/2001/tag/issues.html#httpRange-14
> > > [6]
> > > http://www.w3.org/2006/07/SWD/RDFa/testsuite/xhtml1-testcases/Test0031
> > > [7]
> > > http://www.w3.org/2006/07/SWD/RDFa/testsuite/xhtml1-testcases/Test0032
> > >
> > > ----------------------------------------------------------
> > >  Michael Hausenblas, MSc.
> > >  Institute of Information Systems & Information Management
> > >  JOANNEUM RESEARCH Forschungsgesellschaft mbH
> > >  Steyrergasse 17, A-8010 Graz, AUSTRIA
> > >
> > >  <office>
> > >     phone: +43-316-876-1193 (fax:-1191)
> > >    e-mail: michael.hausenblas@joanneum.at
> > >       web: http://www.joanneum.at/iis/
> > >
> > >  <private>
> > >    mobile: +43-660-7621761
> > >       web: http://www.sw-app.org/
> > > ----------------------------------------------------------
> > >
> >
> > --
> >
> > Ivan Herman, W3C Semantic Web Activity Lead
> > Home: http://www.w3.org/People/Ivan/
> > PGP Key: http://www.ivan-herman.net/pgpkey.html
> > FOAF: http://www.ivan-herman.net/foaf.rdf
> >
> >
>
>
> --
>   Mark Birbeck, formsPlayer
>
>   mark.birbeck@formsPlayer.com | +44 (0) 20 7689 9232
>   http://www.formsPlayer.com | http://internet-apps.blogspot.com
>
>   standards. innovation.
>


-- 
  Mark Birbeck, formsPlayer

  mark.birbeck@formsPlayer.com | +44 (0) 20 7689 9232
  http://www.formsPlayer.com | http://internet-apps.blogspot.com

  standards. innovation.
Received on Monday, 20 August 2007 12:12:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:15:09 GMT