Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
mastodon.gamedev.place is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server focused on game development and related topics.

Administered by:

Server stats:

5.1K
active users

mastodon.gamedev.place: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#as

2 posts2 participants0 posts today
Public *
Sebastian Lasse

recently I stumbled upon github.com/w3c/activitystreams 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.
w3.org/TR/activitystreams-core

while the properties are described in the
- Vocabulary specs.
e.g. w3.org/TR/activitystreams-voca

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

GitHubname versus nameMap clarification · Issue #616 · w3c/activitystreamsBy JacksonBailey
ExploreLive feeds
About