W3C home > Mailing lists > Public > public-rdf-wg@w3.org > June 2011

Re: long-range datatyping and rdfa/microdata

From: Dan Brickley <danbri@danbri.org>
Date: Fri, 10 Jun 2011 14:07:09 +0200
Message-ID: <BANLkTim=qU0aZsGX+hZHCOcSOwnDgkB5MA@mail.gmail.com>
To: Steve Harris <steve.harris@garlik.com>
Cc: Richard Cyganiak <richard@cyganiak.de>, RDF WG <public-rdf-wg@w3.org>
On 10 June 2011 13:58, Steve Harris <steve.harris@garlik.com> wrote:

>> Well foaf:age does not currently have a datatype set, for the
>> verbosity reasons you give. Perhaps datatype annotations can be added
>> into RDFa 1.1 profiles?
> Honestly I'm not convinced that the datatyping matters in this kind of situation, if someone says their age is "39"^^xsd:string, so what. The FOAF world (as will be any schema where the data is so widely used) is full of nonsense like foaf:age "twelve", foaf:age "79b8c9c56b0b879941b3cd424b1af2bc", foaf:age "三十九"@zh and so on, the fact that some of them aren't tagged as xsd:integers doesn't even register on the scale of the kind of nastiness you have to cope with.

Yes, I was never expecting instance publishers (of RDFa or any similar
markup) to add that stuff.

Hopefully quality issues will be partially addressed when people
actually start using this sort of data for apps that people care about
(SEO or whatever). Right now, there is almost no incentive to get
things right.

> If you're trying to calculate the average age of people interested in frogs, then you just have to ignore anything that doesn't cast cleanly to an integer.

So you don't see any value in knowing in advance which properties are
intended to be castable to integers?

Received on Friday, 10 June 2011 12:07:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:59 UTC