Branch/Resource Model: Activity

archesproject / ARM_Working_Group

Arches Resource Model Working Group. A repo for community reviewed Arches branches, models, and packages

2 stars 2 forks source link

Branch/Resource Model: Activity #18

Open annabelleee opened 6 years ago

annabelleee commented 6 years ago

activity_20180509

Branch/Resource Model for Activity as discussed during May 2018 meetings. JSON pending.

Steps to completion (updated):

[x] Metadata
[x] Diagram (using ARM WG notation)
[ ] Sample Data
[ ] Sample Concepts
[ ] JSON of Arches branch based on diagram in ARM WG github repo
[ ] Vote in comments to officially approve branch

azaroth42 commented 6 years ago

Activity Model: simple_activity_model

Habennin commented 6 years ago

I sketched this out again with the crm properties made explicit in the google sheet issue 18

https://docs.google.com/spreadsheets/d/1EYk1yhhBNWrKbVB0jV_1j8NJ-Egi5zWha7QrVvYvw3s/edit?usp=sharing

I think the two representations are in agreement. One question I ran into it is what we will do about roles in activities? This seems like something we will have to address and bypassed in this model. It is awkward to represent in general because it is a property of a property but somehow we will have to tackle either on this branch or another.

azaroth42 commented 6 years ago

Ha! I ran into the role vs technique question yesterday for Production.

The way we have done it is with part_of to another Activity node with a different classified_as.

So if there is a painted sculpture, then there's three production nodes -- the main one that represents everything, and then one for the painting part carried out by the painter, and one for the sculpting part, carried out by the sculptor. Those would be techniques, but "creator" vs "contributor" might be an example of technique-less roles.

adamlodge commented 6 years ago

Initial swing at Arches implementation of the Activity branch. A few notes:

This is implemented as a branch, but I think it would be straitforward to transform to a standalone model
I hid the "label" node's widget on the card. Guessing this will be a common pattern.
Assumes only one level of Activity part. Note the "Activity Part" node. I think there is a conversation to be had about if/how to model n levels of nested parts in this and other graphs. As it stands, I think the modeler needs to define how many nested levels are allowed in a graph.
Both Place and Timespan are modeled as semantic nodes because they are assumed to, in a real implementation, be extended by glomming on outside branches.
I added the txt extension to the uploaded file just to make it save on github. Just remove the .txt and it will work. https://app.zenhub.com/files/119609623/2e7bd45c-1d82-4f55-aaa9-fd0710a685be/download

annabelleee commented 5 years ago

FOR BRANCH: https://www.archesproject.org/arm-wg-activity-branch/