Conversation

recently I stumbled upon https://github.com/w3c/activitystreams/issues/616#issuecomment-2498990563 and (apart from this concrete issue) it make me think about how _new_ users to the protocol understand the use of multiple languages

The problem why the #ActivityPub #Specification has a deep learning curve:

In order to understand the use of multiple languages, you need to read at least 4 specifications.
Any user of the software can say: I speak language X in quality Y.
It might not be obvious to new users that it is the according
- HTTP "accept-language" header
like e.g. "de,en-US;q=0.7,en;q=0.3"

The default language is defined in the
- JSON-LD spec. as described in above issue

The primer to read about how to use it is in the
- AS Core specs.
https://www.w3.org/TR/activitystreams-core/#naturalLanguageValues

while the properties are described in the
- Vocabulary specs.
e.g. https://www.w3.org/TR/activitystreams-vocabulary/#dfn-name

While this is understandable and fine for me, it might be confusing to new or non-tech-implementors …
#i18n #language #specs #html #jsonld #as

/ @evan