-
Notifications
You must be signed in to change notification settings - Fork 7
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
domain of gcis:relatedProject is the intersection of publication and dataset #143
Comments
based on the discussion of in USGCRP/gcis/pull/235. I suggest we change the domain to
|
Fine here aside from the grammatical issue in the definition. |
Also, to what aspect of the Project is the entity attributed? The existence, creation, etc? |
Is there a difference between ascribing an entity's existence vs it's creation? Definition of PROV Attribution:
Roles can be used to with a qualified Attribution (see example at http://www.w3.org/TR/prov-o/#Attribution) to specify the role the agent had in the activity that generated the entity. |
Shouldn't it be "wasRelatedTo", not just "relatedTo"? Change "A project the entity is attributed to." I assume the use cases are: a. Project A was related to Project B. However, should we be more specific and use terms like "wasAffiliatedWith", Examples: c. Project A was affiliated with Project B. On Wed, Sep 2, 2015 at 11:22 AM, Stephan Zednik notifications@github.com
Robert Wolfe, NASA GSFC @ USGCRP, o: 202-419-3470, m: 301-257-6966 |
This property is used to assign attribution of some entity to a project. The super-property is A general 'relatedTo' property would be a different property. The two use cases @rewolfe provides are not appropriate a sub-property of |
I'll defer to @rewolfe going forward with this ticket. |
Okay, I am sorry that I misunderstood the context. So, an example would be: Dataset A was related to Project B. I think this is pretty general, but it may be okay. More typical term So to relate a dataset to a project, we need two triples: Dataset A was produced by Activity B. Activity B was related to Project C. Again, a more typical term way of relating an activity and project would be: Activity B was performed under Project C. or Activity B was part of Project C. I'm not sure if this helps. On Sep 3, 2015 9:14 AM, "justgo129" notifications@github.com wrote:
|
@rewolfe The current definition of This means that the statement In PROV attribution has the following definition - Attribution is the ascribing of an entity to an agent. When an entity e is attributed to agent ag, entity e was generated by some unspecified activity that in turn was associated to agent ag. Thus, this relation is useful when the activity is not known, or irrelevant. So in PROV attribution is a shorthand for saying: This conforms to your suggested statements:
|
@zednis Got it! Thanks for being patient in helping me understand this. So, yes, I'm okay with the definition: "A project the entity is attributed On Fri, Sep 4, 2015 at 12:37 PM, Stephan Zednik notifications@github.com
Robert Wolfe, NASA GSFC @ USGCRP, o: 202-419-3470, m: 301-257-6966 |
I am ok with "An entity ascribed to a project through an unspecified activity" if everyone else is. I was trying to follow the grammatical structure that dublin core terms uses in their comments, but I don't think it works well in this case. |
👍 |
+1 On Fri, Sep 4, 2015 at 2:08 PM, justgo129 notifications@github.com wrote:
Robert Wolfe, NASA GSFC @ USGCRP, o: 202-419-3470, m: 301-257-6966 |
ok, updated proposal with the new comment text:
Since I think we already have consensus I will wait a bit and baring any objections I will submit the pull request. |
+1 |
@zednis @xgmachina now that #147 has been merged, please feel free to proceed editing the turtle templates where necessary. It may also impact #17. |
I believe this domain would be the intersection of
gcis:Publication
andgcis:Dataset
rather than the union.I think we should generalize the domain.
The text was updated successfully, but these errors were encountered: