What are we gaining here? The verb/objectType tokens are not user facing data. Here we end up with a million mappings to canonicalize the multilingual terms into the English form so processors can understand them. Why?
We already have a simple route to internationalization: the processor is responsible for mapping the verb to a displayable string anyway. My own processor does a table lookup in order to compose an internationalized activity string. This kind of feature would make that job harder, not easier
Verbs and objectTypes don't need a language context. That is implied: the reader's language. Processors already know what language to render the presentation text in.
> -----Original Message-----
> str...@googlegroups.com] On Behalf Of James M Snell
> Sent: 19 July 2014 20:34
> Subject: Language Context in Verb and ObjectType identifiers
> You received this message because you are subscribed to the Google Groups
> "Activity Streams" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to activity-strea...@googlegroups.com.
> To post to this group, send email to activity...@googlegroups.com.
> Visit this group at http://groups.google.com/group/activity-streams.
> For more options, visit https://groups.google.com/d/optout.