- From: Luc Moreau <L.Moreau@ecs.soton.ac.uk>
- Date: Wed, 18 Jan 2012 10:13:35 +0000
- To: public-prov-wg@w3.org
Hi Paul, It seems that the problem is not specific to prov-o, but also applies to prov-dm (but phrased differently). Currently, the prov-dm document requires entities to be identifiable. Probably, we even mean for them to have an identifier! I came across a similar problem, trying to encode parameters of the Provenance Challenge 1 workflow. I am getting something like: entity(pc1:a26,[pc1:label="slicer param 2",prov:type="http://openprovenance.org/primitives#String",pc1:value="-y .5"]) Should the domain specific "pc1:value" attribute become a prov attribute for interoperability? Luc On 01/18/2012 09:40 AM, Provenance Working Group Issue Tracker wrote: > PROV-ISSUE-222 (used-objectproperty): Datatype property for used? [Ontology] > > http://www.w3.org/2011/prov/track/issues/222 > > Raised by: Paul Groth > On product: Ontology > > Currently, prov-o:used is defined as an objectproperty. This is fine. However, we've be doing some modeling here at the VU where the parameter to a program is a string. Currently, this is not modelled using a prov-o:used edge but it seems like it should be. Is there anyway we can support this? > > My first inclination is to define a corresponding datatype property but this make break the semantics of entity... > > Another option might be to suggest using a blank node with the string attached using an application specific predicate. > > Suggestions? > > > > -- Professor Luc Moreau Electronics and Computer Science tel: +44 23 8059 4487 University of Southampton fax: +44 23 8059 2865 Southampton SO17 1BJ email: l.moreau@ecs.soton.ac.uk United Kingdom http://www.ecs.soton.ac.uk/~lavm
Received on Wednesday, 18 January 2012 10:14:07 UTC