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

Apply semi-open vocabulary patterns #100

Merged
merged 1 commit into from
Aug 22, 2022
Merged

Apply semi-open vocabulary patterns #100

merged 1 commit into from
Aug 22, 2022

Conversation

ajnelson-nist
Copy link
Member

@ajnelson-nist ajnelson-nist commented Aug 19, 2022

This Pull Request is a downstream application of UCO CP-100, with the rdf:List reversion of UCO Issue 406 applied.

Coordination

  • Tracking in Jira ticket ONT-484
  • Pull request is against correct branch
  • Pull Request is in, or reverted to, Draft status before Solutions Approval vote has passed.
  • CI passes in (CASE/UCO) feature branch
  • CI passes in (CASE/UCO) current unstable branch (c57ddea)
  • Impact on SHACL validation reviewed for CASE-Examples
  • Impact on SHACL validation remediated for CASE-Examples (N/A)
  • Impact on SHACL validation reviewed for casework.github.io
  • Impact on SHACL validation remediated for casework.github.io (N/A)
  • Solutions Approval vote logged on corresponding Issue (N/A)

This is a downstream application of two proposals:

* UCO CP-100 implemented the suggested-value enforcement pattern for
  semi-open vocabularies.
  This was a part of UCO 0.8.0.
* UCO Issue 406 adjusted the implementation pattern from UCO CP-100 to
  account for an OWL requirement on `rdf:List` usage.
  This has been approved for UCO 1.0.0.

A third proposal adjusting the CASE vocabulary namespace, UCO Issue 435,
would also apply, but has not had an approval vote yet.  Due to vote and
other Git logistics, that will be handled separately.

No effects were observed on Make-managed files.

References:
* [UCO OC-12] (CP-100) UCO's idea of "Open vocabulary" does not agree
  with its implementation with owl:oneOf
* ucoProject/UCO#406
* ucoProject/UCO#435

Signed-off-by: Alex Nelson <[email protected]>
@ajnelson-nist ajnelson-nist added this to the CASE 1.0.0 milestone Aug 19, 2022
ajnelson-nist added a commit to casework/CASE-Examples that referenced this pull request Aug 19, 2022
A follow-on patch will regenerate Make-managed files.

References:
* casework/CASE#100

Signed-off-by: Alex Nelson <[email protected]>
ajnelson-nist added a commit to casework/CASE-Examples that referenced this pull request Aug 19, 2022
References:
* casework/CASE#100

Signed-off-by: Alex Nelson <[email protected]>
ajnelson-nist added a commit to casework/casework.github.io that referenced this pull request Aug 19, 2022
A follow-on patch will regenerate Make-managed files.

References:
* casework/CASE#100

Signed-off-by: Alex Nelson <[email protected]>
ajnelson-nist added a commit to casework/casework.github.io that referenced this pull request Aug 19, 2022
References:
* casework/CASE#100

Signed-off-by: Alex Nelson <[email protected]>
@plbt5 plbt5 merged commit a495369 into develop Aug 22, 2022
@plbt5 plbt5 deleted the Feature-UCO-CP-100 branch August 22, 2022 12:37
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

Successfully merging this pull request may close these issues.

3 participants