- From: Irene Polikoff <irene@topquadrant.com>
- Date: Wed, 19 Nov 2014 22:23:03 -0500
- To: "'Arnaud Le Hors'" <lehors@us.ibm.com>
- Cc: <public-data-shapes-wg@w3.org>
- Message-ID: <098401d00471$4baeb220$e30c1660$@topquadrant.com>
Hi Arnaud, What I meant was that the answer to the question 'what is the rdf type triple' doesn't change depending on whether the triple was inferred or asserted. It is a triple with rdf:type predicate. I do agree that the role of inferencing is a topic to address. Irene From: Arnaud Le Hors [mailto:lehors@us.ibm.com] Sent: Wednesday, November 19, 2014 9:32 PM To: Irene Polikoff Cc: public-data-shapes-wg@w3.org Subject: RE: Can Shapes always be Classes? Hi Irene, While I agree with you that serialization doesn't matter, until we decide whether any inferencing is performed or not, we can't say that "it also doesn't matter if the triple was generated by inference or not". That's why I raised ISSUE-1 Entailment regime <http://www.w3.org/2014/data-shapes/track/issues/1> http://www.w3.org/2014/data-shapes/track/issues/1 -- Arnaud Le Hors - Senior Technical Staff Member, Open Web Standards - IBM Software Group "Irene Polikoff" <irene@topquadrant.com> wrote on 11/19/2014 05:14:50 PM: > From: "Irene Polikoff" <irene@topquadrant.com> > To: <kcoyle@kcoyle.net>, <public-data-shapes-wg@w3.org> > Date: 11/19/2014 05:15 PM > Subject: RE: Can Shapes always be Classes? > > Karen, > > rdf:type triple is a triple with rdf:type as a predicate. I think this is > quite unambiguous and doesn't need additional definition. Where is the > confusion? > > RDF/XML serialization of such triple may look something like (from one of > the links you provided): > > < <http://dati.camera.it/ocd/persona.rdf/p305757> http://dati.camera.it/ocd/persona.rdf/p305757> > rdf:type foaf:Person ; > > or it may look like this in the abbreviated form: > > <foaf:Person rdf:about=" <http://dati.camera.it/ocd/persona.rdf/p305757> http://dati.camera.it/ocd/persona.rdf/p305757"> > > But why does it matter? In both cases, this is still the same triple with > rdf:type as a predicate. I am confused why are we talking about > serializations here? > > For the purposes of our discussion, it also doesn't matter if the triple was > generated by inference or not, as long as it exists. > > Irene > > -----Original Message----- > From: Karen Coyle [ <mailto:kcoyle@kcoyle.net> mailto:kcoyle@kcoyle.net] > Sent: Wednesday, November 19, 2014 7:05 PM > To: public-data-shapes-wg@w3.org > Subject: Re: Can Shapes always be Classes? > > > > On 11/19/14 3:18 PM, Holger Knublauch wrote: > > I am not sure what point you are trying to make here. The above means > > that the resource has rdf:type edm:WebResource. > > Holger, > > Agreed that that's what it "means", but you keep saying: "rdf:type triples" > - which to me says: > > A rdf:type B (in RDF/XML) > B a A (in turtle) > > If instead you instead mean "typed subjects", then that expands what I was > understanding. (But doesn't convince me that this is one-to-one with shapes > that need validation.) > > So what I glean from this is that you are focused on types, except those > subjects typed by inferencing. Is that the case? > > Perhaps we can then clarify exactly what falls under "rdf:type triples" > -- and what doesn't. And whether untyped data, such as Dublin Core Elements > 1.1 in RDF, has a fallback to rdf:Resource. > > kc > > -- > Karen Coyle > kcoyle@kcoyle.net <http://kcoyle.net/> http://kcoyle.net > m: 1-510-435-8234 > skype: kcoylenet/+1-510-984-3600 > > >
Received on Thursday, 20 November 2014 03:23:38 UTC