You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... in addition to our current "human readable labels" which are just a record of the exact term ID, i.e. the last part of the schema.org official URLs for each term.
@tfrancart's example is a good starting point, whilst working towards supporting labels and descriptions in multiple languages.
In Schema.org site coding terms, we could:
Run a one-off process to expand the current labels from camel case into a word separated string. Note: I believe we have a current test that checks that the label matches the term id, that will need changing.
Introduce code to display the default label/description (not language tagged) when the user interface language (probably defaulting to english) is matched to a language tagged label/description.
Encourage interested groups to provide translations of labels/descriptions. Maybe worth as a start looking at what the new 'intelligent' version of Google Translate can do. I believe the current coding could support the use of separate language specific definition files for labels and descriptions only.
Of course introducing language specific versioning will open up requests for a totally language independent interface. ;-)
... in addition to our current "human readable labels" which are just a record of the exact term ID, i.e. the last part of the schema.org official URLs for each term.
See also https://lists.w3.org/Archives/Public/public-schemaorg/2017Feb/0023.html discussion thread.
The text was updated successfully, but these errors were encountered: