- From: Satya Sahoo <satya.sahoo@case.edu>
- Date: Wed, 2 Nov 2011 11:56:58 -0400
- To: James Cheney <jcheney@inf.ed.ac.uk>
- Cc: Provenance Working Group WG <public-prov-wg@w3.org>
Received on Wednesday, 2 November 2011 16:00:02 UTC
I am not sure the issue is similar to "assertion" - "asserted statement" and "inferred statement" are similar to "asserted class hierarchy" and "inferred class hierarchy" in OWL or "asserted triple" and "inferred triple" in RDF. Best, Satya On Wed, Nov 2, 2011 at 11:51 AM, James Cheney <jcheney@inf.ed.ac.uk> wrote: > I suppose "statement" has a similar problem to "assertion" though - e.g. > "inferred statement" sounds a little strange too (to me). > > --James > > On Nov 2, 2011, at 3:45 PM, Satya Sahoo wrote: > > Hi, > I like James suggestion for using "Statement" instead of either > "expression" or "record". > > 0 (in favor of "Entity statement", "xxx statement"). > > Best, > Satya > > On Wed, Nov 2, 2011 at 8:01 AM, James Cheney <jcheney@inf.ed.ac.uk> wrote: > >> 0 - I think either "expression" or "record" is fine. "Statement" would >> also be fine - in my view these are closer to declarative statements than >> "expressions" that you'd evaluate in a programming language. "Record" >> might be confusing if the entities are also records, but this is true for >> "expression" and "statement" too. >> >> --James >> > > The University of Edinburgh is a charitable body, registered in > Scotland, with registration number SC005336. > >
Received on Wednesday, 2 November 2011 16:00:02 UTC