w3c / w3c/activitystreams

Extension properties in the AS2 namespace

Open
#696 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Section 2.1 says:

Implementations MAY also use additional properties and values not defined in the JSON-LD @context with the understanding that any such properties will likely be unsupported and ignored by consuming implementations that use the standard JSON-LD algorithms.

I think the best practice as of this date is to use an extension context. Adding ad-hoc properties can cause conflicts if they are used with different semantics by different implementations.

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.

Research direction

Start with Section 2.1 of the Activity Streams 2.0 specification and review the surrounding guidance on JSON-LD contexts. Check how extension contexts are described elsewhere in the specification. Done means the section clearly addresses the risks of ad-hoc properties and gives consistent guidance on extension contexts, with any needed wording agreed by maintainers.

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
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.