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

Implemented Issue 380 #397

Merged
merged 1 commit into from
Jun 14, 2022
Merged

Implemented Issue 380 #397

merged 1 commit into from
Jun 14, 2022

Conversation

b0bkaT
Copy link
Contributor

@b0bkaT b0bkaT commented Jun 2, 2022

Changed observable:inReplyTo to an owl:DatatypeProperty with an rdfs:range of xsd:string.

This Pull Request resolves all requirements of Issue 380.

Review steps taken:

  • Pull request is against correct branch
  • CI passes in (CASE/UCO) feature branch
  • CI passes in (CASE/UCO) current unstable branch (merge-commit)
  • 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)

Changed observable:inReplyTo to an owl:DatatypeProperty with an
rdfs:range of xsd:string.
@ajnelson-nist
Copy link
Contributor

Thanks, @b0bkaT !

I'm converting this to Draft until the Solutions Approval vote passes.

@ajnelson-nist ajnelson-nist marked this pull request as draft June 2, 2022 18:35
@ajnelson-nist ajnelson-nist linked an issue Jun 3, 2022 that may be closed by this pull request
11 tasks
@ajnelson-nist ajnelson-nist marked this pull request as ready for review June 14, 2022 16:13
@ajnelson-nist ajnelson-nist merged commit 500d3aa into develop Jun 14, 2022
@ajnelson-nist ajnelson-nist deleted the Feature-Issue-380 branch June 14, 2022 16:13
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.

observable:inReplyTo should behave the same as observable:messageID
2 participants