Just randomly wondered where `contentMap` was defined in the Activity* suite of specs and learned it is here:

Activity Streams 2.0

(www.w3.org)

I did not realize there is also a `nameMap` and a `summaryMap`, since all three properties are defined as natural language properties (formally, that they are tagged in the Activity Vocabulary document with "rdf:langString")

@darius the xMap properties are a json-ld feature to avoid everyone having to do this instead

content: {@\value: "hello world", @\language: "en"}

so you do instead

contentMap: {en: "hello world"}

and it expands into the prior

@trwnh I continue to not understand the utility of most things json-ld, but there are a lot of things it took me years to understand the utility of so my position is: huh, ok

@darius jsonld is basically a way to transform any arbitrary json into an entity-attribute-value graph model

in this case i think the more natural way would have been to just use the @ value and @ language form, but i guess @ signs are scary? idk

@trwnh some people have very strong preferences about how they want to parse data structures. It is probably less about @ and more about aesthetically not needing to filter an array of objects by their "language" value in order to pluck out the content of a given language from the resultant object. (To me it's all bad and I don't have a particular preference)