Re: [w3ctag/design-reviews] I18N String-Meta and WebIDL (Issue #716)

I18N has been requesting metadata for some time and there are different dispositions depending on the specification and its needs. There are 18 specifications in the list below. Separately I am reviewing specs that preceded our efforts in this area as well as the list of potential new specifications.

First, JSON-LD added features to the specification allowing document and item level metadata.

The following specifications either added support using JSON-LD or are in the process of doing so:

* WOT Thing Description
* pub-manifest
* activity-pub
* web-annotation

Some specifications added locally defined metadata (i.e. their own `language` and `direction` fields in natural language values and which are similar to the `Localizable` type described elsewhere in this request):

* appmanifest
* miniapp-manifest
* TTML
* activitystreams (based on WebAppManifest)

One specification (WebAuthn) defined its own serialization scheme; we are still working with them on the details of that scheme.

The following specs are in one way or another waiting on this discussion or have proceeded:

* secure-payment-confirmation
* payment-request
* vocab-duv
* mediacapture
* web-share
* micro-pub
* SHACL

SHACL probably should have adopted the JSON-LD approach. micro-pub entangles metadata with the question of localizable error messages and so might not apply.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/716#issuecomment-1079134635
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/716/1079134635@github.com>