You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The VA-SEPIO model defines specific subtypes of the Statement class to support the different perspectives on Statements that DPs / Implementations are wanting to create:
Furthermore, VA-SEPIO defines the EvidenceLine class which currently does not descend from Statement (but could).
The paradigm should be vetted generally, and then used/referenced explicitly in Profiles (at present the metakb-cvc work uses these classes but don't acknowledge them - instead referencing only the abstract 'Statement' class from the Core IM)
The text was updated successfully, but these errors were encountered:
mbrush
changed the title
Review / apply Proposition Assessment statement v Evidence Line Statement paradigm in profiles.
Review / vet the VA-SEPIO Statment hierarchy and its application in Profiles
Jan 9, 2023
mbrush
changed the title
Review / vet the VA-SEPIO Statment hierarchy and its application in Profiles
Review / vet the VA-SEPIO Statement hierarchy and its application in Profiles
Jan 9, 2023
@mbrush is this still relevant? Can you re-characterize specifically what needs to be done so that we can assign it to an individual or group? Please weigh the value of the task vs the priorities currently on our list. If this can be deferred, feel free to archive or ice box this issue.
The VA-SEPIO model defines specific subtypes of the Statement class to support the different perspectives on Statements that DPs / Implementations are wanting to create:
Furthermore, VA-SEPIO defines the EvidenceLine class which currently does not descend from Statement (but could).
The paradigm should be vetted generally, and then used/referenced explicitly in Profiles (at present the metakb-cvc work uses these classes but don't acknowledge them - instead referencing only the abstract 'Statement' class from the Core IM)
The text was updated successfully, but these errors were encountered: