Should, should not in non-normative section 1.2
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 313
- Forks
- 70
- PR merge metrics
- No merged PRs in 30d
Description
Relationship to JSON Activity Streams 1.0.
The terms displayName, verb, title and objectType should be treated as reserved terms that SHOULD NOT be used within Activity Streams 2.0 documents. When encountered in an Activity Streams 2.0 document, they SHOULD be processed in accordance to the guidelines listed in B. Deprecated Activity Streams 1.0 Syntax
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with section 1.2 and compare the quoted wording with the linked JSON Activity Streams 1.0 relationship and Appendix B references. Done means the use of “should,” “should not,” “SHOULD,” and “SHOULD NOT” is consistent with the section’s non-normative status and the project’s editorial intent.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100