My favorites | Sign in
Project Home Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 32: Void v2 - creation of void:isPartOf or such
3 people starred this issue and may be notified of changes. Back to list
Status:  Done
Owner:  Michael.Hausenblas
Closed:  Apr 2010


Sign in to add a comment
 
Reported by f...@fgiasson.com, May 27, 2009
As per my discussion on #swig:


http://chatlogs.planetrdf.com/swig/2009-05-27.html#T16-08-26
May 27, 2009
Project Member #1 Michael.Hausenblas
(No comment was entered for this change.)
Labels: Milestone-Release2.0
May 27, 2009
Project Member #2 K.J.W.Al...@gmail.com
to summarise, the issue is that voiD's advocated use of dcterms:isPartOf to link a
document containing triples to a dataset (which is the superset of those triples), 
makes the term rather generic and vague, and it would be better to have a more
specific property ?
May 29, 2009
Project Member #3 Michael.Hausenblas
(No comment was entered for this change.)
Owner: K.J.W.Alexander
Jun 16, 2009
Project Member #4 K.J.W.Al...@gmail.com
Jun and I say that we should have a new property, but we don't yet suggest a good
name for it (I prefer something like void:semantics to void:isPartOf)

see:

http://blogs.talis.com/n2/archives/485
Labels: -Priority-Medium Priority-High
Jun 16, 2009
#5 f...@fgiasson.com
Hi Keith!

Good that you consider it. The name of the property is just the last step :)

So, you are proposing something like:

<some-instance> void:semantics <some-dataset>?

What would be the definition of such a property?


Thanks,


Fred
Jun 19, 2009
Project Member #6 K.J.W.Al...@gmail.com
Hi Fred, Well ... not quite ... the idea is still to link from the document to the 
dataset, but with more exact semantics. It would be similar to the log:semantics 
property used by CWM, which means something like "this document represents the 
semantics of this graph"

In this case, void:semantics would mean "this document represents the graph which is 
a part of this dataset".


I should explain - the use case that we had for suggesting dct:isPartOf was purely 
so that when you dereference a LOD URI, you have  a link that you can follow back to 
the dataset.

Maybe you have a different use case?

Keith
Jun 23, 2009
Project Member #7 jun.zhao...@googlemail.com
Comments about http://www.w3.org/2000/10/swap/log#semantics from the log vocabulary
is the following:

"The log:semantics of a document is the formula. achieved by parsing representation
of the document. For a document in Notation3, log:semantics is the log:parsedAsN3 of
the log:contents of the document. For a document in RDF/XML, it is parsed according
to the RDF/XML specification to yield an RDF formula a subclass of N3 log:Formula).

[Aside: Philosophers will be distracted here into worrying about the meaning of
meaning. At least we didn't call this function "meaning"! In as much as N3 is used as
an interlingua for interoperability for different systems, this for an N3 based
system is the meaning expressed by a document.]

(Cwm knows how to go get a document and parse N3 and RDF/XML it in order to evaluate
this. Other languages for web documents may be defined whose N3 semantics are
therefore also calculable, and so they could be added in due course. See for example
GRDDL, RDFa, etc)"

http://www.w3.org/2000/10/swap/log#semantics

Aug 13, 2009
Project Member #9 jun.zhao...@googlemail.com
Keith will take a look at how people are using dcterms:isPartOf and void:subset in
the existing voiD files.

Aug 13, 2009
Project Member #10 richard....@gmail.com
If we really need a new property, please don't call it void:semantics, that's much too abstract, and the dreaded 
S-word should be avoided anyway.

I would prefer something descriptive, maybe void:inDataset or void:isPartOfDataset.
Aug 27, 2009
Project Member #11 K.J.W.Al...@gmail.com
(No comment was entered for this change.)
Status: Accepted
Labels: -Priority-High Priority-Medium
Aug 27, 2009
Project Member #12 richard....@gmail.com
Stuart Williams commented the following:

| Section 5.1:
| Hmmm... lots of scope for confussion.
|
| <document.rdf> dcterms:isPartOf <void.ttl#MyDataset> .
|
| Kind of curious from the point of view of having previously established
| sparql, uriLookup and dump endpoints why one would be remotely interested
| in <document.rdf> as being a part of the dataset (unless separately it was
| a dataset in its own right with it's own set of endpoints etc).
Oct 24, 2009
#13 cygan...@googlemail.com
I'm now convinced we should have our own property here. Reason: Let's say you state the license of your dataset 
in your voiD file. Having a triple <> void:inDataset </void.ttl#MyDataset> in my documents allows an inference 
that the license applies to the triples in the documents. If it's just dcterms:isPartOf, then that inference cannot 
be made, because the weak semantics (“it's part of another resource”) really makes it hard to support an 
inference about licenses and IPR rights.

Candidate names: void:isPartOf, void:inDataset, void:isPartOfDataset. I vote for something that explicitly 
mentions "dataset", for clarity.
Nov 5, 2009
Project Member #14 Michael.Hausenblas
group resolved this to use void:inDataset with rdfs:range void:Dataset and
rdfs:domain foaf:Document, Keith to check back with Tom re licensing and update guide 2.0
Nov 5, 2009
Project Member #15 K.J.W.Al...@gmail.com
OK. so we agree on void:inDataset with domain of foaf:Document and range of void:Dataset

we may want to take special care in the working of the rdfs:comment to ensure it is
clear how licenses apply.

I will ask other legally inclined people at Talis to see if they can offer input.
Nov 12, 2009
Project Member #16 richard....@gmail.com
Proposal: as part of the documentation, say something like: "SHOULD not specify multiple void:inDataset for the 
same document. Rather, create a new void:Dataset that contains both as a subset, and link to that. Because then 
you can explicitly add stuff like license to the joint dataset"
Jan 18, 2010
Project Member #17 Michael.Hausenblas
(No comment was entered for this change.)
Labels: Prodcut-vocab
Jan 18, 2010
Project Member #18 Michael.Hausenblas
(No comment was entered for this change.)
Labels: Product-vocab
Jan 18, 2010
Project Member #19 Michael.Hausenblas
(No comment was entered for this change.)
Labels: -Prodcut-vocab
Jan 25, 2010
Project Member #20 Michael.Hausenblas
swapped ownership with Keith re  Issue 46  as per IRC chat
Owner: Michael.Hausenblas
Apr 22, 2010
Project Member #21 Michael.Hausenblas
updated guide re this, see https://code.google.com/p/void-impl/source/detail?r=95
Apr 22, 2010
Project Member #22 Michael.Hausenblas
agreed to close on 2010-04-22, adding prop to voc still pending, see
https://code.google.com/p/void-impl/wiki/Vocabulary2Updates
Status: Done
Sign in to add a comment

Powered by Google Project Hosting