Website:
http://i-semantics.tugraz.at/triplification-challenge
Contact: Bernhard Schandl bernhard.scha...@univie.ac.at
Hi,
I agree with Pat in that case, that it would just be easier not to put
restrictions
in the abstract rdf syntax at all, instead of complicating things all over
the place.
There are pragmatic reasons why sentences such as
http://bblfish.net/#hjs name Henry .
are not going to be
* Bernhard Schandl - Department of Distributed and Multimedia Systems,
University of Vienna, Austria
* Charlie Abela - Department of Intelligent Computer Systems
University of Malta, Malta
* Tudor Groza - Digital Enterprise Research Institute (DERI), National
University of Ireland, Galway, Ireland
* Gunnar
/conferences/?conf=psd2010 no later than
midnight Pacific Daylight Time on July 9, 2010.
Accepted papers will be published in the workshop proceedings.
== WORKSHOP ORGANIZERS ==
* Laura Dragan - Digital Enterprise Research Institute (DERI),
National University of Ireland, Galway, Ireland
* Bernhard
/Challenge/2010
I-Semantics Website: http://i-semantics.tugraz.at/triplification-challenge
Contact: Bernhard Schandl bernhard.scha...@univie.ac.at
Hi,
- serve html at http://www.example.org/doc/alice.html always
- serve rdf/xml at http://www.example.org/doc/alice.rdf always
Right?
Correct!
I want to throw in another question, are there currently arguments for or
against the two alternatives:
http://www.example.org/doc/alice.html
/Personal_Semantic_Data or by emailing the workshop
organizers.
== WORKSHOP ORGANIZERS ==
* Laura Dragan - Digital Enterprise Research Institute (DERI), National
University of Ireland, Galway, Ireland (laura.dra...@deri.org)
* Bernhard Schandl - Department of Distributed and Multimedia Systems
Peter,
It is a good thing that the subject URI is an HTTP URI available from
your server but that is only the start of the story. The rest of the
story needs other servers to give your data more context.
In your example the fact that there
is a link can only be figured out using some
Hi,
On Mar 8, 2010, at 02:33 , Hugh Glaser wrote:
Design Issue Number 2 (http://www.w3.org/DesignIssues/LinkedData.html) says:
Use HTTP URIs so that people can look up those names.
I wholeheartedly agree with this statement.
doi, urn suck.
It is hard to work out what they mean (resolve),
Hi,
On Mar 8, 2010, at 10:28 , Peter Ansell wrote:
Can you explain in more detail what the problem is with using
DOI/URN/...-based identifiers internally, and expose them as
de-referenceable HTTP URIs on-the-fly? One can even include a reference to
the plain URN and thus map distinct
Hi Christoph,
I.e. the reasoning in
http://www.w3.org/2001/tag/doc/httpRange-14/2007-05-31/HttpRange-14#iddiv1138805816
(essentially the same as what you said above) is clear to me from a
philosophical point of view, but not from a technical one. I'm taking a more
pragmatic view here, as
Hi Chris,
The new DBpedia data set describes more than 2.9 million things,
including
282,000 persons, 339,000 places, 88,000 music albums, 44,000 films,
15,000
video games, 119,000 organizations, 130,000 species and 4400
diseases. The
DBpedia data set now features labels and abstracts for
On Nov 12, 2009, at 14:13 , Bernhard Schandl wrote:
I would be interested in statistics per resources, e.g., the average
and maximum number of triples per subject. Can you provide such
numbers?
Sorry, this is maybe a little bit too unspecific; especially the
distribution of triple
Juan,
Let me rephrase: I urge everybody to try to explain what Linked Data
and the
Semantic Web is to 1) web developer 2) CEO 3) VC investors 4) my
parents 5)
Oprah!
Except of 1), don't try to explain what Linked Data is: show them cool
applications instead and how they can benefit from
Hi Juan,
I think that's a nice idea and I would like to join the event. Btw, we
are planning a similar event in Vienna, located and scheduled near
ESTC 2009, which we call Linked Data Camp, more about this will be
posted soon under http://www.linkeddatacamp.org and
Hi,
is there any way to limit the number of triples returned by a DESCRIBE
query? The LIMIT clause of sparql obviously applies to the number of
result bindings, but each result binding may lead to an arbitrary
number of triples.
Consider the following queries against dbpedia:
SELECT
Hi Richard,
On Jul 11, 2009, at 12:26 , Richard Cyganiak wrote:
When it comes to opaque or mnemonic URIs, there is a tradeoff
between reusability and longevity. Entirely opaque URIs are less
likely to be re-used and linked to than mnemonic ones. The practices
in How To Publish are really
Hi,
Unfortunately, I want to employ an RDFS reasoner AND use the
foaf:holdsAccount to point to /non/Online Accounts. I can't use it
because
my /non/online Accounts WILL be interpreted as foaf:OnlineAccounts,
which I
want to be satisfiably false (but is provably true).
Clearly.
To fix
Mark,
And everyone knows at least one way to publish HTML, don't they?
I disagree. Most people know how to enter text into a form, but they
have no clue what HTML is all about, how it comes that one line of
text is bigger while the other is smaller, how backlinks and
permalinks are
Dan,
Yeah, my [4] is at my threshold of tolerance for chaos in a diagram.
I wanted a way to show the core of the FOAF spec in a picture, so
tried (despite similar concerns to those mentioned in this thread)
the style of putting domain/range directly in an instance-like style.
I think
However many newbies to RDF and ontologies are confused by this,
because the triple
foaf:Agent foaf:holdsAccount foaf:OnlineAccount .
is actually not contained in the ontology.
What needs to be communicated is that:
[ a foaf:Agent ] foaf:holdsAccount [ a foaf:OnlineAccount ] .
instead.
21 matches
Mail list logo
