Comments on: Namespaces in queries, part 3 http://richard.cyganiak.de/blog/2006/10/namespaces-in-queries-part-3/ A weblog by Richard Cyganiak Wed, 03 Aug 2011 12:16:08 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Ora Lassila http://richard.cyganiak.de/blog/2006/10/namespaces-in-queries-part-3/#comment-12778 Ora Lassila Sat, 28 Oct 2006 14:47:50 +0000 http://dowhatimean.net/2006/10/namespaces-in-queries-part-3#comment-12778 Isn't it great when everyone immediately pounces on you when you innocently post something on your blog. In this case, you have to understand that you were advocating dismantling a mechanism that's absolutely crucial to the Semantic Web; indeed one might say that a big reason why the Semantic Web was built this way was exactly to get away from name conflicts and any ambiguity about what concepts one is talking about. So no wonder people are up in arms. This is sacred stuff. :-) Isn’t it great when everyone immediately pounces on you when you innocently post something on your blog. In this case, you have to understand that you were advocating dismantling a mechanism that’s absolutely crucial to the Semantic Web; indeed one might say that a big reason why the Semantic Web was built this way was exactly to get away from name conflicts and any ambiguity about what concepts one is talking about. So no wonder people are up in arms. This is sacred stuff. :-)

]]> By: Dan Brickley http://richard.cyganiak.de/blog/2006/10/namespaces-in-queries-part-3/#comment-12684 Dan Brickley Fri, 27 Oct 2006 12:51:28 +0000 http://dowhatimean.net/2006/10/namespaces-in-queries-part-3#comment-12684 Better I think to consider this a kind of SPARQL authoring tool. Just as I often write crappy HTML-2-ish text files, then I run "tidy -m asxml index.html" to turn them into XHTML, one might write pseudo-SPARQL and then feed it through a tool to insert extra prefixes etc. A bit of perl that reads #include ~/stdsparql and adds in some extra lines might be useful? Better I think to consider this a kind of SPARQL authoring tool. Just as I often write crappy HTML-2-ish text files, then I run “tidy -m asxml index.html” to turn them into XHTML, one might write pseudo-SPARQL and then feed it through a tool to insert extra prefixes etc.

A bit of perl that reads
#include ~/stdsparql

and adds in some extra lines might be useful?

]]> By: Gregory Williams http://richard.cyganiak.de/blog/2006/10/namespaces-in-queries-part-3/#comment-12657 Gregory Williams Fri, 27 Oct 2006 01:58:46 +0000 http://dowhatimean.net/2006/10/namespaces-in-queries-part-3#comment-12657 Another approach might be to convince endpoint maintainers to pre-define namespaces appropriate to their data. Thus, an endpoint with information about people could maintain default values for the prefixes 'foaf' and 'rel', while a photograph endpoint might pre-define 'foaf', 'album', 'dc', and 'dcterms'. You'd still have to type the namespace in the QName, but there'd be no need to explicitly write out the prefix declaration. Another approach might be to convince endpoint maintainers to pre-define namespaces appropriate to their data. Thus, an endpoint with information about people could maintain default values for the prefixes ‘foaf’ and ‘rel’, while a photograph endpoint might pre-define ‘foaf’, ‘album’, ‘dc’, and ‘dcterms’. You’d still have to type the namespace in the QName, but there’d be no need to explicitly write out the prefix declaration.

]]> By: JHendler http://richard.cyganiak.de/blog/2006/10/namespaces-in-queries-part-3/#comment-12644 JHendler Thu, 26 Oct 2006 22:20:50 +0000 http://dowhatimean.net/2006/10/namespaces-in-queries-part-3#comment-12644 We use SPARQL in a lot of ways, incluyding a lot of the sort of interactive thing you are talking about - but that doesn't make us (MINDSWAPpers) less interested in namespaces - rather it makes us moreso - often we pull things from different sites where a common string (like :name) may be used in different ways than we use it, or someone else does - so when we see foaf:name we don't want to assume it is the same as doap:name (which might be the name of a project) or random:name which might be some mathematical identity function, etc. etc - if you just want to display things to a user, it may not matter than much, but if you merge these things, you need to be able to control when we want things to merge and when we don't -- some simple OWL is crucial to this, btw - one can express equivalence and difference between these things, allowing for much better control JH We use SPARQL in a lot of ways, incluyding a lot of the sort of interactive thing you are talking about – but that doesn’t make us (MINDSWAPpers) less interested in namespaces – rather it makes us moreso – often we pull things from different sites where a common string (like :name) may be used in different ways than we use it, or someone else does – so when we see foaf:name we don’t want to assume it is the same as doap:name (which might be the name of a project) or random:name which might be some mathematical identity function, etc. etc – if you just want to display things to a user, it may not matter than much, but if you merge these things, you need to be able to control when we want things to merge and when we don’t — some simple OWL is crucial to this, btw – one can express equivalence and difference between these things, allowing for much better control
JH

]]>