[dxwg] Short i18n review checklist (#1504)

riccardoAlbertoni has just created a new issue for https://github.com/w3c/dxwg:

== Short i18n review checklist ==
Look at  [Short i18n review checklist](https://www.w3.org/International/i18n-drafts/techniques/shortchecklist) for more context on the questions.

-----------

1. [ ] _If the spec (or its implementation) contains any natural language text that will be read by a human (this includes error messages or other UI text, JSON strings, etc, etc),_

None of the specific features added in DCAT 3 introduces variations on how the text is managed.
This aspect hasn’t changed since DCAT 2.

Language codes are associated with text and are shown in the examples of the DCAT 3 specification.
The specification of text direction depends on the syntax in which DCAT is serialized. DCAT is likely to inherit the solutions made available in RDF (see a discussion of alternatives https://w3c.github.io/rdf-dir-literal/#bcp47_based)

See issues 
- https://github.com/w3c/dxwg/issues/959
- https://github.com/w3c/dxwg/issues/958
    
2. [ ] _If the spec (or its implementation) allows content authors to produce typographically appealing text, either in its own right, or in association with graphics._

N/A

3. [ ] _If the spec (or its implementation) allows the user to point into text, creates text fragments, concatenates text, allows the user to select or step through text (using a cursor or other methods), etc._

N/A  

4. [ ] _If the spec (or its implementation) allows searching or matching of text, including syntax and identifiers_

N/A  - DCAT inherits solutions from serializations and models defined in other specifications.

5. [ ] _If the spec (or its implementation) sorts text_

N/A

6. [ ] _If the spec (or its implementation) captures user input_

N/A

7. [ ] _If the spec (or its implementation) deals with time in any way that will be read by humans and/or crosses time zone boundaries_

None of the specific features added in DCAT 3 introduces a variation on how the time /date-related terms are managed.

Moreover, legacy terms from DCAT 2 ( e.g.,  [`dcat:startDate`](http://www.w3.org/ns/dcat#startDate)) encode as [`rdfs:Literal`](https://www.w3.org/TR/rdf-schema/#ch_literal "http://www.w3.org/2000/01/rdf-schema#Literal")  using the relevant ISO 8601 Date and Time.

8. [ ] _If the spec (or its implementation) allows any character encoding other than UTF-8._

N/A  - DCAT inherits solutions from serializations and models defined in other specifications.

9. [ ] _If the spec (or its implementation) defines markup._

N/A  - DCAT inherits solutions from serializations and models defined in other specifications.

10. [ ] _If the spec (or its implementation) deals with names, addresses, time & date formats, etc_

N/A  - DCAT inherits solutions from serializations and models defined in other specifications.

11. [ ] _If the spec (or its implementation) describes a format or data that is likely to need localization._

N/A  - DCAT inherits solutions from serializations and models defined in other specifications.

12. [ ] _If the spec (or its implementation) makes any reference to or relies on any cultural norms_

N/A 


Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1504 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 2 May 2022 12:45:03 UTC