data2health / contributor-attribution-model

A simple data model to represent contributions made by agents to research artifacts
3 stars 0 forks source link

Capturing multiple roles in a Contribution #17

Open mbrush opened 5 years ago

mbrush commented 5 years ago

With respect to capturing multiple roles in a given Contribution object, the spec currently says the following:

A contribution connects a single agent to a single Artifact, but we allow for a single Contribution object to capture multiple roles played by the agent in generating the artifact. This pattern can be used to provide a more concise representation when an agent plays multiple roles, and data creators do not wish to capture details of each role played (i.e. how, when, and where each was realized). In cases where such details for each role are required, separate Contribution objects should be created for each role played.

Questions:

  1. Is this clear to folks?
  2. Is this what we want? Or should we say only one role per Contribution?
mbrush commented 5 years ago

One issue is that it may allow >1 way to record the same information. But I think we would be clear that it is up to a given implementation to specify a single approach in their system, and ensure compliance.

mellybelly commented 5 years ago

I like the way it is now. The multiple roles option for the same contribution entity is simple for applications; for those times when you need multiple roles with different time attributes, you can create different triples with the same artifact URI.