Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#116 closed enhancement (invalid)

Use datatypes in RDF

Reported by: Earle Martin Owned by: Earle Martin
Priority: normal Milestone:
Component: openguides Version: svn
Severity: normal Keywords: RDF
Cc:

Description

We should be doing things like:

<dc:date rdf:datatype="http://purl.org/dc/elements/1.1/W3CDTF">2006-04-20T07:20:10Z</dc:date> <dc:format rdf:datatype="http://purl.org/dc/elements/1.1/IMT">text/html</dc:format> <dc:language rdf:datatype="http://purl.org/dc/elements/1.1/ISO639-2">en</dc:language>

Change History (5)

comment:1 Changed 15 years ago by crschmidt@…

There's no practical benefit from this, and numerous costs. This makes working with the RDF more difficult, and it doesn't help with anything in our situation, or in any I can think of.

comment:2 Changed 15 years ago by Earle Martin

Okay, I'll take your word for it - could you mention the costs here, for posterity's sake?

comment:3 Changed 15 years ago by crschmidt@…

  1. Many RDF frameworks do not do datatypes properly. The big ones -- RAP, Redland, etc. -- don't suffer from this, but rdf datatypes are probably the single least used area of the RDF specification.
  2. In cases where it is used, RDF triple-pattern matches *must* specify the RDF datatypes -- this means that anything which is now trying to match on 'en' would have to search for both 'en' and 'en'<datatype>, which is annoying in the best case, and damn near impossible to do in the worst case.
  3. None of the dc: RDF datatypes that you linked have any definition, so if we *were* to do this, terms that actually fit the bill would be needed -- these probably exist somewhere, but definitely not the ones you linked, none of which are defined.

comment:4 Changed 15 years ago by Earle Martin

Resolution: invalid
Status: newclosed

Okay - thanks. Closing this one then.

comment:5 Changed 15 years ago by Dave Beckett

yes you should be using datatypes. SPARQL will allow you to datatype comparisons and especially with dates, that's a good thing. You should at least be using xsd:dateTime.

Note: See TracTickets for help on using tickets.