-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
prov-template: "Non Prov" statements #156
Comments
I did some more experiments regarding arbitrary namespaces in attribute-value pairs and found out the following: while it seems possible to include attributes such as dc:partOf in the template, they only appear in the expanded doc when the associated value is not a variable: the simple template document with bindings prefix prov: http://www.w3.org/ns/prov# . expands to document ignoring the part of relationship, while explicitly setting the "target" of dc:partOf document is being copied to the expanded doc document Moreover, as described in the PROV Template Specification at https://provenance.ecs.soton.ac.uk/prov-template-2014-06-07/ it is stated that statement level variables can occur also at attribute position, enabling to declare things like document and expanding accordingly. The example above, however, gets ignored too during expansion: document I think that enabling template declarations such as entity(var:lowerEntity, [var:attr1='var:value1']) would be quite helpful |
Hello!
In the book "Provenance: An Introduction to PROV", there is a recipe 4.1.9 "Modeling Sub-Activities" where it is suggested that the DC-terms vocabulary should be used to represent "part of" relationships between activities.
I tried to include that in a PROV template, but such "non prov statements" obviously get ignored during expansion.
My question would therefore be if there is any workaround in this regard, or I simply have to live with being limited to the PROV vocabulary when using PROV-template?
Thanks and best regards,
Doron
The text was updated successfully, but these errors were encountered: