Re: Encoding an incomplete date as xsd:dateTime

Heiko, Another solution (that may be overkill for your needs) is to use the Time ontology[1] rhw [1] http://www.w3.org/TR/owl-time/ On 2014-02-10, at 10:37 AM, Heiko Paulheim wrote: > Hi all, > > xsd:dateTime and xsd:date are used frequently for encoding dates in RDF, > e.g., for birthdays in

Re: Which datatype to use for time intervals

Lars, I also use the Time Ontology http://www.w3.org/TR/owl-time/ - it handles most cases nicely and can even handle broken dates that are sometimes present in historical records (like February 31st) [1]. Rob [1] http://blog.muninn-project.org/node/57 On 2013-11-12, at 9:47 AM, Svensson, Lars

Re: How to publish SPARQL endpoint limits/metadata?

Agreed, a few small additions to void would go a long way to making automated query engines. Either that or good quality HTTP error reporting? -Rob On 2013-10-08, at 11:45 AM, Leigh Dodds wrote: > Hi, > > As others have suggested, extending service descriptions would be the > best way to do thi

Re: Minimizing data volume

Frans, The nice thing about a sparql server is that you get what you ask for. If you want only the "Feature" without the geometry, you can do that. If you only want whatever centroid the Feature is linked to, you can do that. If you want everything, you can do that. At worst, you can 'count' t

Re: Linked data sets for evaluating interlinking?

I would add that in many cases, unlikeness (owl:differentFrom) is as valuable as equivalence. All my best, rhw On 2013-08-26, at 4:08 PM, Hugh Glaser wrote: > Hi Cristina, > Some interesting issues you raise. > One of them is how people publish links (which enables your analysis). > There are t

Re: YASGUI: Web-based SPARQL client with bells ‘n wistles

Guilty as charged. Need to fix that. best, rhw On 2013-08-20, at 3:13 PM, Ghislain Atemezing wrote: > Hi Hugh, > > [[ My 2 cents ]] >> I went looking for equivalences (:-)), and found a lot (but not all) of >> owl:sameAs dbpedia objects that seem to have crept in as strings, e.g. >>

Re: Representing NULL in RDF

Given a document date, age is an important feature in disambiguating identity since it loosely relates to date of birth. It's also used in many situations where a date of birth would create personal privacy issues. Most properties change over time. The LOD community has a bias for facts that a

Re: Publication of scientific research

On 27-Apr-13, at 12:52 PM, Daniel Schwabe wrote: I just spent an hour this week removing "last-accessed: 01-01-2012" data from my reference list, so I could get inside a page limit. Why? The data is (slightly) valuable, so why remove it? Page limit is a tree-ware hangover. I blame the confer

Re: Publication of scientific research

On 25-Apr-13, at 10:41 AM, Phillip Lord wrote: Scientists would rather eat their dogs than give up their favoured editing environments. And chew off their own (or their RA's) foot as well. Most conference submission / reviewing software already asks for the basic meta-data boilerplate to he

Re: Public SPARQL endpoints:managing (mis)-use and communicating limits to users.

On 19-Apr-13, at 8:04 AM, Leigh Dodds wrote: Hi, On Fri, Apr 19, 2013 at 11:55 AM, Kingsley Idehen wrote: ... If you have OFFSET and LIMIT in use, you can reflect the new state of affairs when the next GET is performed i.e, lets say you have OFFSET 20 and LIMIT 20, the URL with OFFSET 40 is

Re: Public SPARQL endpoints:managing (mis)-use and communicating limits to users.

Hi Rob, There is a fundamental problem with HTTP status codes. Lets say a user submits a complex but small sparql request. My server sees the syntax is good and starts to reply in good faith. This means the server starts the http response and sends an 200 OK Some results are being send Howev

Re: Public SPARQL endpoints:managing (mis)-use and communicating limits to users.

On 18-Apr-13, at 8:53 AM, Jerven Bolleman wrote: Many of the current public SPARQL endpoints limit all their users to queries of limited CPU time. But this is not enough to really manage (mis) use of an endpoint. Also the SPARQL api being http based suffers from the problem that we first sen