Skip to content
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

Review / vet the VA-SEPIO Statement hierarchy and its application in Profiles #96

Open
mbrush opened this issue Dec 14, 2022 · 1 comment
Assignees

Comments

@mbrush
Copy link
Contributor

mbrush commented Dec 14, 2022

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:

Statement
    DomainStatement
    PropositionAssessmentStatement

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)

@mbrush 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 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
@larrybabb
Copy link
Contributor

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants