This repository has been archived by the owner on Jan 27, 2022. It is now read-only.
Add Review and Comment types #227
Assignees
Labels
Comments
stencila-ci
added a commit
that referenced
this issue
Nov 16, 2020
# [0.47.0](v0.46.5...v0.47.0) (2020-11-16) ### Bug Fixes * **Review, Comment:** Move comments to CreativeWork ([b9bad70](b9bad70)) ### Features * **Comment:** Add comment aspect ([3c06245](3c06245)), closes [/github.com//pull/228#discussion_r522498602](https://github.com//github.com/stencila/schema/pull/228/issues/discussion_r522498602) * **Comment:** Add comment type ([89e93a3](89e93a3)), closes [#227](#227) * **Review:** Add review type ([0779830](0779830)), closes [#227](#227)
|
🎉 This issue has been resolved in version 0.47.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is a proposal to add two new
CreativeWorktypes:ReviewandComment.These will be used to implement reviews of executable preprints, specifically as the target for decoding of source content such as Google Comments and GitHub PRs as well as semantic selectors for CSS styling in Thema.
For
ReviewI suggest the following properties (beyond those inCreativeWork):itemReviewed:Thing(as defined in schema.org)reviewAspect:Text(as defined in schema.org)I don't think we should add
reviewRatingat this time (wait until there is a need for that) andreviewBodydoes not need to be added since it is provided for bycontentonCreativeWork(but we should provide an alias). See also Google's structured data recommendations for reviews: https://developers.google.com/search/docs/data-types/review-snippet.For
CommentI suggest the following properties (beyond those inCreativeWork):parentItem:Comment(as defined in schema.org)replies:Comment[](a custom extension)I am proposing
repliesbecause it makes more sense for in-memory and visual (HTML) representation of inter-comment relations.repliesis similar toitemsforList.The text was updated successfully, but these errors were encountered: