search

w3c / i18n-request

Horizontal review requests are made via issues in this repo, and tracked by our radar.
https://github.com/orgs/w3c/projects/91/views/1
1 stars 7 forks source link

Bitstring Status List v1.0 2024-01-21 > 2024-02-13 #222

Closed msporny closed 5 months ago

msporny commented 8 months ago

Name of your specification

Bitstring Status List v1.0

URL of your specification

https://w3c.github.io/vc-bitstring-status-list/

Does your specification include an Internationalization Considerations section?

When does the review need to be finished?

2024-02-13

What has changed since any previous review?

This is the first review.

Please point to the results of your own self-review

https://github.com/w3c/vc-bitstring-status-list/issues/132

Where and how should the i18n WG raise issues?

https://github.com/w3c/vc-bitstring-status-list/issues/

Pointer to any explainer for the spec

https://github.com/w3c/vc-bitstring-status-list/blob/main/explainer.md

Other comments

Our apologies, we thought we had submitted this review request when we submitted the TAG review request, but we failed to do so.

We were hoping to enter CR next month, but are gated by this review (the WG believes it is done enough to enter CR). We do not believe that there is much to be said on this specification from an i18n standpoint, so expect the review to be quick, but of course, defer to your group to determine the outcome.

aphillips commented 8 months ago

Thanks @msporny. This looks like a straightforward review and we should be able to complete it by the requested date of 2024-02-13. (Unless you actually meant last February?)

msporny commented 8 months ago

Thanks @msporny. This looks like a straightforward review and we should be able to complete it by the requested date of 2024-02-13.

Awesome, thank you! Apologies again for failing to file the review when we meant to (last June).

(Unless you actually meant last February?)

*lol* Err, sorry, meant this Feb (corrected)... no time machine necessary.