RE: Temporal validity: alternative for dcterms:valid?

OWL-Time handles this with the class time:Instant (and time:Interval). time:Instant has a choice of properties - time:inDateTime whose range is the class time:DateTimeDescription, which provides a choice of representations time:inXSDDateTime whose range is the familiar 7-element

RE: Temporal validity: alternative for dcterms:valid?

OK - I understand. However, I'm generally wary of inventing new microsyntaxes. We already have (i) time position - 7 information items in a string (ii) WKT Back in the day I was responsible for developing DCMI:Period, DCMI:Box, DCMI:Point. I now regret those, since it was essentially just

RE: Temporal validity: alternative for dcterms:valid?

OK - let's put it on the agenda for Time activity. If necessary there can be a vote! -Original Message- From: Svensson, Lars [mailto:l.svens...@dnb.de] Sent: Thursday, 14 January 2016 8:05 AM To: Cox, Simon (L, Clayton) ; frans.kni...@geodan.nl Cc: public-lod@w3.org

RE: Temporal validity: alternative for dcterms:valid?

> an interval datatype similar to the ISO 8601 format > ("2007-03-01T13:00:00Z/2008-05-11T15:30:00Z") -- where start and end could be > any xsd temporal datatype -- would be useful. Perhaps we can include that in > the time deliverable. time:Interval already exists in OWL-Time, which will be

RE: Please publish Turtle or JSON-LD instead of RDF/XML [was Re: Recommendation for transformation of RDF/XML to JSON-LD in a web browser?]

Yes – double nesting – this is what GML* does. It makes instance documents trivial to transform to valid RDF, but confuses the hell out of most XSD-RDF converters. Simon Cox *Geography Markup Language. From: Timothy W. Cook [mailto:t...@mlhim.org] Sent: Friday, 4 September 2015 9:34 PM To:

RE: Discovering a query endpoint associated with a given Linked Data resource

There is the SPARQL Service Description vocabulary. http://www.w3.org/TR/sparql11-service-description/ From: Nandana Mihindukulasooriya [mailto:nmihi...@fi.upm.es] Sent: Wednesday, 26 August 2015 6:46 PM To: public-lod public-lod@w3.org Subject: Discovering a query endpoint associated with a

RE: referencing a concept scheme as the code list of some referrer's property

Thomas - I've come to the same conclusion. my:property1 rdfs:range some:codeA . my:property2 rdfs:range some:codeB . some:codeA rdfs:subClassOf skos:Concept . some:codeB rdfs:subClassOf skos:Concept . some:item1 a some:codeA . # also a skos:Concept because of subclass relationship some:item2