Explain why publishers would use an extension in section 5 "Extensibility"

Open Beginner friendly
#775 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
74/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Domain
documentation

Research direction

Start at section 5, “Extensibility,” in the Activity Streams 2.0 specification and read the surrounding discussion. Update that section so it explains why publishers use extensions and acknowledges additional properties and types outside the listed Vocabulary; done means the rationale is clear before the existing extension details.

Written by the indexing model from the issue text.

Description

Next version

We jump right into discussing extensions without discussing why publishers would use them.

We should note that all Activity Streams 2.0 object types can include additional properties, and can have types that aren't listed in the Vocabulary.

Dominant language
HTML
Stars
313
Forks
70
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from w3c/activitystreams

All issues in w3c/activitystreams

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.