-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default Language Context MAY -> SHOULD #354
Comments
It is not necessary to provide that property in the context to associate all strings with a language. But I agree that such a note might be helpfull. |
Ah yes, i follow your reasoning. Perhaps a note then? |
So, I think this is a valid Activity Streams document: {
"@context": "https://www.w3.org/ns/activitystreams",
"@language": "fr",
"type": "Note",
"name": "Une note brève"
} I vastly prefer this to the version with @jasnell If this is the case, maybe we can just recommend that documents SHOULD include the |
While this is valid, having the |
It's interesting how the JSON-LD playground handles it: versus |
Accidentally closed |
Yeah, if you look at the normalized result for the first, you'll see that the |
@lanthaler Do you have any suggestion or opinion regarding this issue ? |
RESOLVED: Resolve issue #354 of Activity Streams with a SHOULD that points out the importance of explicitly marking up language of natural language properties if you know the language, and use such markup for some examples, and points out that it's not in every example because we want to avoid the copypaste EN everywhere thing |
This is a comment on #352 (raised here so that i18n folks are notified).
The section Default Language Context says:
We were previously explaining that associating language with strings is often necessary when it comes to presenting them to a user (eg. to prevent Chinese users being presented with Japanese font glyphs). Could we either change MAY to SHOULD, or at least add a note to say that actually language information is quite important (since very few developers seem to recognise that)?
The text was updated successfully, but these errors were encountered: