Make the reference to The Unicode Standard undated #618
Conversation
| }, | ||
| "ISO10646": { | ||
| publisher: "International Organization for Standardization", | ||
| href: "https://www.iso.org/standard/76835.html", |
There was a problem hiding this comment.
Removing this means there's no link at all to this reference, and that it is the only reference in the spec without a link.
That seems like a non-ideal result. Specref doesn't have any link to 10646 that I can find. @himorin do you know if there's any other way to reference this important document? I wonder if i18n has a guide for how to reference it, for example.
There was a problem hiding this comment.
Removing this means there's no link at all to this reference, and that it is the only reference in the spec without a link.
Do you mean without URL?
ISO does not offer URLs to the latest edition of the standard.
There was a problem hiding this comment.
As pointed during call (sorry Ive missed at that period), I also could not find any canonical pointer to the newest version of 10646. ICS does not work on this front nor search box does not change URL.
Also for character collection we refer for ja subset, I could not find any pointer within Unicode one. I haven't checked entire UTS or else, but seems missIng in Unicode. (or may have some replacement by General Category or something??)
There was a problem hiding this comment.
For other specs, I suppose most of text refer Unicode but not 10646, which seems not in xref neither(??)...
There was a problem hiding this comment.
Also for character collection we refer for ja subset, I could not find any pointer within Unicode one. I haven't checked entire UTS or else, but seems missIng in Unicode.
I think you might be right. See https://www.unicode.org/versions/Unicode17.0.0/core-spec/appendix-c/
Few applications are expected to make use of all of the characters defined in ISO/IEC 10646. The conformance clauses of the two standards address this situation in very different ways. ISO/IEC 10646 provides a mechanism for specifying included subsets of the character repertoire, permitting implementations to ignore characters that are not included (see normative Annex A of ISO/IEC 10646). A Unicode implementation requires a minimal level of handling all character codes—namely, the ability to store and retransmit them undamaged. Thus the Unicode Standard encompasses the entire ISO/IEC 10646 repertoire without requiring that any particular subset be implemented.
So maybe we can have a dated reference to a specific edition of ISO/IEC 10646 strictly for the Japanese collections.
There was a problem hiding this comment.
downloaded ISO PDF and checked about collection.
Collections are defined in normative Annex A Collections of graphic characters for subsets, and defined collections 301 to 321 represent whole UCS, like 303 for Unicode 3.1 (detailed in Annex A.3). So, I suppose this will not be in Unicode side, but just in ISO. CJK collections, from 370, are defined in Annex A.4 subsections and refer source reference file for CJK Unified Ideographs (CJKSrc). Collections from 370 to 375 (and 380-389) are marked as fixed collection, so these will not be changed by newer edition of ISO 10646 (p2751 of 10646:2000).
So, in total, I'd agree to use dated reference.
|
The Timed Text Working Group just discussed
The full IRC log of that discussion<nigel> Subtopic: Make the reference to The Unicode Standard undated #618<nigel> github: https://github.com//pull/618 <cpn> Pierre: The ISO platform doesn't offer URLs to the latest edition of the standard <cpn> Gary: Unless we want to refer to Unicode instead? <cpn> scribe+ cpn <cpn> Nigel: Why not refer to Unicode? <cpn> Pierre: Other specs refer to it <cpn> ... ARIB refers to collections, and I want to make sure that's in the Unicode standard, not only in ISO <cpn> Nigel: I checked the ISO website, they have a mechanism for adding dated and undated links to ISO specs, but I couldn't find access to the database they use <cpn> Pierre: Could change the reference from ISO 10646 to Unicode and be done <cpn> ... It's free to download from ISO <cpn> Nigel: To answer this, there should be precedent from elsewhere in W3C <cpn> Pierre: What about TTML2? <cpn> ... That references the Unicode spec <cpn> ... The ISO reference came up in response to ARIB, but everywhere else we reference Unicode <cpn> Gary: CSS Selectors links to Unicode. The two are functionally equivalent <cpn> Pierre: I'll just reference Unicode <cpn> Gary: Sounds good <cpn> Nigel: Sounds good <nigel> SUMMARY: Change 10646 reference to Unicode |
Closes #617