This was done as a different issue because we had already called out the use of the JSON-LD feature, @language, and that's not controversial.

What is controversial is having both the @language in the @context and making use of the **Map properties RECOMMENDED even if there is only one language version of the property. That would leave us with the complicated version of the document below:

{
  "@context": {
    "@vocab": "http://www.w3.org/ns/activitystreams",
    "@language": "en"
  },
  "type": "Note",
  "nameMap": {
    "en": "A simple note"
  },
  "summaryMap": {
    "en": "This is the summary of the simple note."
  },
  "contentMap": {
    "en": "This is the content of the simple note."
  }
}

I think we can get along with just using the JSON-LD version of @context, which we specifically call out in the document, and which we use for other parts of the specification (like extensions). So if we don't make the *Map version of properties RECOMMENDED, we'd have a more tractable document like this:

{
  "@context": {
    "@vocab": "http://www.w3.org/ns/activitystreams",
    "@language": "en"
  },
  "type": "Note",
  "name": "A simple note",
  "summary": "This is the summary of the simple note.",
  "content": "This is the content of the simple note."
}

It would still be possible to use the first version, of course; but the second version would be OK.

**Map fields become a SHOULD #341

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions