search

HydraCG / Specifications

Specifications created by the Hydra W3C Community Group
Other
138 stars 26 forks source link

i18n support #153

Closed binhle410 closed 3 years ago

binhle410 commented 6 years ago

Is there yet a way to support i18n for a Resource?

tpluscode commented 6 years ago

I don't think it's been discussed... ever? Maybe a long time ago on the mailing list.

That said, you could get some quick win with RDF/JSON-LD support for multiple languages. Not sure what you are looking for, so your mileage may vary.

I see this as two fold:

  1. Translating the API Documentation, which should be simple enough to introduce by using languages in the descriptions
  2. Having the API actually accept and work with multiple translations of resources. That is something that would require more though on how to tackle.
lanthaler commented 6 years ago

As Tomasz already mentioned, JSON-LD (and RDF in general) already has built-in support for multi-language strings. See http://www.w3.org/TR/json-ld/#string-internationalization

Is there anything else you are looking for @binhle410?

tpluscode commented 3 years ago

Closing as this seems answered and inactive

alien-mcl commented 3 years ago

OK. I believe it is resolved.