Sebastian Lasse<p>recently I stumbled upon <a href="https://github.com/w3c/activitystreams/issues/616#issuecomment-2498990563" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/w3c/activitystreams</span><span class="invisible">/issues/616#issuecomment-2498990563</span></a> and (apart from this concrete issue) it make me think about how _new_ users to the protocol understand the use of multiple languages</p><p>The problem why the <a href="https://digitalcourage.social/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ActivityPub</span></a> <a href="https://digitalcourage.social/tags/Specification" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Specification</span></a> has a deep learning curve:</p><p>In order to understand the use of multiple languages, you need to read at least 4 specifications.<br>Any user of the software can say: I speak language X in quality Y.<br>It might not be obvious to new users that it is the according <br>- HTTP "accept-language" header <br>like e.g. "de,en-US;q=0.7,en;q=0.3"</p><p>The default language is defined in the <br>- JSON-LD spec. as described in above issue</p><p>The primer to read about how to use it is in the <br>- AS Core specs.<br><a href="https://www.w3.org/TR/activitystreams-core/#naturalLanguageValues" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">w3.org/TR/activitystreams-core</span><span class="invisible">/#naturalLanguageValues</span></a></p><p>while the properties are described in the <br>- Vocabulary specs.<br>e.g. <a href="https://www.w3.org/TR/activitystreams-vocabulary/#dfn-name" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">w3.org/TR/activitystreams-voca</span><span class="invisible">bulary/#dfn-name</span></a> </p><p>While this is understandable and fine for me, it might be confusing to new or non-tech-implementors …<br><a href="https://digitalcourage.social/tags/i18n" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>i18n</span></a> <a href="https://digitalcourage.social/tags/language" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>language</span></a> <a href="https://digitalcourage.social/tags/specs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>specs</span></a> <a href="https://digitalcourage.social/tags/html" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>html</span></a> <a href="https://digitalcourage.social/tags/jsonld" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>jsonld</span></a> <a href="https://digitalcourage.social/tags/as" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>as</span></a> </p><p>/ <span class="h-card" translate="no"><a href="https://cosocial.ca/@evan" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>evan</span></a></span></p>