- From: Ivan Herman <ivan@w3.org>
- Date: Fri, 8 Oct 2010 17:16:44 +0200
- To: Shane McCarron <shane@aptest.com>
- Cc: Toby Inkster <tai@g5n.co.uk>, Mark Birbeck <mark.birbeck@webbackplane.com>, RDFa Working Group WG <public-rdfa-wg@w3.org>
- Message-Id: <71F86E80-D1D5-46AA-9E71-2E9BF073727C@w3.org>
On Oct 8, 2010, at 17:11 , Shane McCarron wrote: > I agree that these vocabularies have defined terms that are URIs. But only opengraph has told people to use them in conjunction with RDFa in a way that is incorrect - right? Actually, no exactly. They are consistent with themselves, because they provide a bad model for what they want to do and they force people to use a bad model to avoid that URI vs. string issue. Ivan > > On 10/8/2010 5:14 AM, Toby Inkster wrote: >> On Thu, 7 Oct 2010 11:52:48 +0100 >> Mark Birbeck<mark.birbeck@webbackplane.com> wrote: >> >>> My understanding of the use-case described was not 'hey >>> everyone...let's just make literals and URIs the same', but rather the >>> motivation was that authors wanting to use something like OGP might >>> accidently use @property/@content instead of @rel/@resource/@href. >> Authors using: >> >> <meta property="og:url" content="http://example.com/" /> >> >> Are not doing so accidentally but intentionally. This is the correct >> use of the OGP vocab. OGP is certainly not the only place where URIs >> may appear as literals deliberately. >> >> See, for instance: >> <http://purl.org/NET/uri> >> <http://open.vocab.org/docs/canonicalUri> >> > > -- > Shane P. McCarron Phone: +1 763 786-8160 x120 > Managing Director Fax: +1 763 786-8180 > ApTest Minnesota Inet: shane@aptest.com > > ---- Ivan Herman, W3C Semantic Web Activity Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 PGP Key: http://www.ivan-herman.net/pgpkey.html FOAF: http://www.ivan-herman.net/foaf.rdf
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Friday, 8 October 2010 15:17:00 UTC