Design Principles for Activities, Entities und Actors

bequrios commented 6 months ago

How to combine the prov: elements to form a paf:Affair

bequrios commented 6 months ago

Open Questions for Design Principles

[ ] prov:wasInvalidatedBy to the activity is temporally wrong, should probably be prov:invalidated to the entity but it would not be visible on the entity anymore
[ ] maybe there should be links between entities that state the status of the former entity like prov:invalidated or prov:complemented
[ ] maybe a decision entity should link to the entities that are decided upon by using paf:basedOn as subclass of prov:wasDerivedFrom
[x] maybe it should be stated that a paf:ProposalActivity can only "build" the proposal by prov:used to the entities (and not by creating a new proposal entity that links via prov:wasCreatedBy to the proposal activity to ensure uniform proposal activities. This would mean that all entities that build the proposal must have been created in advance. --> is implemented in this way in paf.link
[x] additional data to entities (like the exact voting result in addition to the main result accepted or rejected) should probably be added like the main data with rdf:predicate with something like e.g. paf:meta to allow to get the additional data clearly separated from the main info (specified by rdf:predicate) and all the other data like e.g. prov:wasGeneratedBy, rdf:predicate should be allowed only once, paf:meta can occur multiple times --> applied in the MoPo examples
[ ] how to model a proposal that goes to different recipients (e.g. proposal for abandonment goes to National Council and Council of States)?

bequrios commented 6 months ago

no deep nestet entities
less repetition if e.g. multiple motions with same text (e.g. 2019 P 19.3668 etc)

Lots of URIs have to be created (if one does not use blank nodes, this would also be true for other schemes)
Which entities belong to which "affair" is only visible through ViewPoints

if an affair is registered after a long history (e.g. mopo), the complete activities are not known and some information has to be encoded as entities (like original autor of the mopo) and not as actor of the activity

bequrios commented 1 month ago

Question regarding chpaf classes: Does it make sense to always have chpaf classes (and not use paf classes) in the concrete data?

--> yes, always use chpaf: classes