Re: Proposed change to the charter, section 4. Deliverables, Recommendation Track

* Peter F. Patel-Schneider <pfpschneider@gmail.com> [2014-08-07 17:41-0700]
> 
> 
> On 08/07/2014 05:24 PM, Eric Prud'hommeaux wrote:
> >
> >On Aug 7, 2014 12:44 AM, "Peter F. Patel-Schneider" <pfpschneider@gmail.com
> ><mailto:pfpschneider@gmail.com>> wrote:
> > >
> > > Well, I did present what I thought was a good neutral set of deliverables,
> >namely
> > >
> > >
> > > 1. A syntax and semantics for shapes specifying how to construct shape
> > > expressions and how shape expressions are evaluated against RDF graphs.
> > >
> > > 2. An RDF vocabulary for expressing these shapes in RDF triples, so they can
> > > be stored, queried, analyzed, and manipulated with normal RDF tools.
> > >
> > > 3. OPTIONAL A specification of how shape verification interacts with
> > > inference.
> >
> >I think this one feel off radar. Did you see any support for this?
> 
> Well, it was supposed to be a better version of the normalization requirement.

I think I'm not getting the connection. I'd expect that inference
would allow one to say that e.g. a myco:Employee is subclass of a
foaf:Person before enforcing a rule that required the foaf:Person arc
on employee records. I thought that normalization was about
predictably ordering the arcs. Is my model wrong, or perhaps one
conversationed morphed into the other? More importantly to my task at
hand, should I continue to track this?


> > > 4. OPTIONAL A compact, human-readable syntax for expressing shapes.
> > >
> > > peter
> > >
> > >
> > >
> > >

-- 
-ericP

office: +1.617.599.3509
mobile: +33.6.80.80.35.59

(eric@w3.org)
Feel free to forward this message to any list for any purpose other than
email address distribution.

There are subtle nuances encoded in font variation and clever layout
which can only be seen by printing this message on high-clay paper.

Received on Friday, 8 August 2014 01:33:19 UTC