name versus nameMap clarification
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 313
- Forks
- 70
- PR merge metrics
- No merged PRs in 30d
Description
Please Indicate One:
- Editorial
- Question
- Feedback
- Blocking Issue
- Non-Blocking Issue
Please Describe the Issue:
Activity Vocabulary Object only mentions name, but Activity Streams Object mentions both name and nameMap. The Activity Vocabulary name property shows an example where the property is named name (example 117) and one where it is named nameMap (example 118).
- Should the Activity Vocabulary Object specify that it has both
nameandnameMapinstead of onlyname? - If it is correct that Object has both of these properties, is
namemeant to always bexsd:stringandnameMapmeant to always berdf:langString?
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
Compare the Activity Vocabulary Object definition with the Activity Streams Object definition and review the linked name property examples 117 and 118. Trace how the specification defines name, nameMap, xsd:string, and rdf:langString, then document the discrepancy and update the relevant specification text once the intended property rules are confirmed.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100