Giovanni,
I think I see your argument here and I tend to agree up to a certain
point. What makes me wonder is that it is *you* stating this ;)
Seriously, I very much believe in self-descriptive documents, etc. I do
prefer simple things that work. However, voiD is just the next logical
step
Hi LODers,
There seems to be quite a bit of stuff about being able to map things, and
so we need to know latlong for the stuff we are considering.
But, saying where things are by adding latlong is not the True Linked Data
Way.
Well, in general.
The right way is to say where things are by saying
Hi Hugh LODers,
This seems to be about knowledge modelling and context. Your first
sentence is telling me a very general context/application - you want to
be able to map things. For that you need the lat/long [or you could buy
lots of lovely OS data and we'd give you a point for the exact
Hi Tom,
I'm interested in VoCamp, and Oxford sounds good to me.
And, er, since I've just arrived on this list, hello!
Ian
Ian Dickinson http://www.hpl.hp.com/personal/Ian_Dickinson
HP Laboratories Bristol mailto:[EMAIL
Hi Ian,
Welcome :) Good to see you here, and glad that VoCamp (and Oxford) sound
good to you.
More details in due course no doubt.
Cheers,
Tom.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dickinson,
Ian J. (HP Labs, Bristol, UK)
Sent: 12
Just to report that Kingsley has nailed the problem. It looks as though
the RDF Browser is getting to the RDF via the HTML page, relying on a
link rel=alternate ... entry in the head of the HTML page, rather
than using a 303 redirection strategy to access the RDF directly.
I have added a
On Thursday 12 June 2008, Kingsley Idehen wrote:
Lets use ESW Wiki to arrange meetups, you will see how this has been
done for prior events, most recently ESWC 2008 :-)
Good idea!
I put up this page:
Hi there,
I've done data integration based on SPARQL in a restricted domain,
not web-scale (see SemWIQ presentation at ESWC08 [1]). But the issues
are similar. We need some descriptions about sites, owner, license,
etc. In our case this is provided upon registration of data sources at
2008/6/12 Yves Raimond [EMAIL PROTECTED]:
Hello again!
As an example is worth 1000 words, I just made up one for this
void:example property.
http://moustaki.org/void/void.n3 describes some aspects of one of the
DBtune dataset. It links, through the void:example property, towards a
RDF
I see VOID as going past the need to have a search engine in order to
decide which sparql endpoints you need to use to effectively make
particular queries based on sample graphs provided by either SPARQL
construct queries on the dataset sparql end point or by way of an
example document specifying
All of your described functionalities are a subset of what semantic
sitemaps are for [1].
Specs aside, the paper [2] might be of interest to some is that we
went to some distance in conceptually explaining what publishing and
retrieving rdf
data on the web means, e.g. using linked open data
Andreas,
Licence: yes i agree, it will be added to the sitemap extention much
like it happens in microformats already.
if you want to use RDF i believe this is what you're looking for
http://validator.creativecommons.org/
Statistics:
i'd tend to see this use case as a low level one that
Hi Michael,
let me clarify that it wasnt really meant to be to: michael you were
just there when i replied to the general idea and not you in
particular :-)
step after semantic sitemaps (it actually is thought to extend it in
terms of using the sc:datasetURI as the entry point, see also
Most of the functionality is there. I disagree with the artificial
restrictions on sparql graph names being either singular or completely
arbitrary.
Also, it would be an improvement to specify this information in RDF
rather than in XML as sitemaps does if people are expecting to be able
to
XML is a step forward. The thing started in RDF with something called
semantic crawling ontology (sorry the link is broken, will have it
fixed tomorrow http://www.sindice.com/semantic-crawling-ontology.html
) which had all the terms fo the sitemap in RDF already.Originally we
wanted to propose a
2008/6/13 Giovanni Tummarello [EMAIL PROTECTED]:
XML is a step forward. The thing started in RDF with something called
semantic crawling ontology (sorry the link is broken, will have it
fixed tomorrow http://www.sindice.com/semantic-crawling-ontology.html
) which had all the terms fo the
16 matches
Mail list logo
