- From: John Graybeal <graybeal@mbari.org>
- Date: Wed, 28 Jan 2009 08:37:19 -0800
- To: Dan Brickley <danbri@danbri.org>
- Cc: Alan Ruttenberg <alanruttenberg@gmail.com>, "Seaborne, Andy" <andy.seaborne@hp.com>, Semantic Web <semantic-web@w3.org>
We had a number of numeric terms that we could not store as RDF/XML 'in their native form' the way we wanted, so they were published with an underscore in front and a prefLabel attribute. Don't know if that's the question you asked, but addresses the point of whether people really run into this. I agree it's a problem with RDF/XML and shouldn't be worked around in OWL. john On Jan 27, 2009, at 11:54 PM, Dan Brickley wrote: > > On 28/1/09 02:12, Alan Ruttenberg wrote: >> The "possible" refers to the cases where RDF/XML can't serialize RDF, >> for instance in the cases that predicates whose URIs localnames begin >> with a number. In those cases one can't construct a qname for the URI >> and since predicates are always written as tags in RDF/XML this just >> can't be serialized in RDF/XML. >> >> So "possible" means possible in the absolute sense. > > Another potential work-around here is for the exporting system to > generate a new (eg. tag: URI) property name, declare it as an > equivalent-property of the original, and serialize using that. This > does somewhat distort the original content, of course. > > Have any of these problematic properties been spotted "in the wild"? > Perhaps it would be possible to probe Sindice or other crawlers, > although of course if the data isn't publish-able in RDF/XML that > would affect the stats. Still there is N3, Turtle etc data out there. > > cheers, > > Dan
Received on Wednesday, 28 January 2009 16:38:08 UTC