Looks like they changed respec so you don't use exclamation points at all now. To override a reference in a normative section and make it informative you use ?. See https://respec.org/docs/#references

Looks like they changed respec so you don't use exclamation points at all now. To override a reference in a normative section and make it informative you use ?. See https://respec.org/docs/#references

Wow. I did not realize this!

Ya, I'm sure it's broken other references we have. I've fixed the three in this PR for now, but will do a more thorough check of all the specs and clean them up again.

Sigh. I do not like such backward compatible changes. Oh well... let that be the fight of somebody else...

Glad to see that you have referred to charmod-norm. It would be useful to mention the order of Unicode normalization and Unicode full case folding, i.e., normalization should precede case folding.

(Related PR in charmod-norm: w3c/charmod-norm#215)

@xfq the text now says (in #1680, that is):

All File Names within the same directory MUST be unique following NFC normalization [[TR15]] and then case folding [[Unicode]].

(followed by the charmod reference, of course). Is that o.k.?

@iherman The current text says:

All File Names within the same directory MUST be unique following NFC normalization [TR15] and then full case folding [Unicode].

i18n WG discussed this in teleconference and I drew the action to respond here. We don't think it is necessary to mention NFC in the requirement. If you want to refer to charmod-norm normatively, you can refer to Unicode Canonical Case Fold Normalization Step.

If you want to refer to Unicode and UAX #15 normatively, you can change "NFC normalization" to "Unicode normalization" (or to "NFC or NFD normalization") so the spec won't limit people to NFC.

@xfq I have created #1692 to handle this. The full paragraph now says:

<p id="ocf-fn-cn">All File Names within the same directory MUST be unique following Unicode 
normalization [[UAX15]] and then full case folding [[Unicode]]. (Refer to 
<a href="https://www.w3.org/TR/charmod-norm/#CanonicalFoldNormalizationStep">Unicode 
Canonical Case Fold Normalization Step</a> [[?CHARMOD-NORM]] for more information.)</p>

Can you approve or comment on #1692? Thx.

One small addendum. There are four types of Unicode normalization: two canonical normalization forms (NFC/NFD) and two compatibility forms (NFKC/NFKD). You do not intend the Kompatibility forms to be used here, so I would at least say "Unicode canonical normalization".

One small addendum. There are four types of Unicode normalization: two canonical normalization forms (NFC/NFD) and two compatibility forms (NFKC/NFKD). You do not intend the Kompatibility forms to be used here, so I would at least say "Unicode canonical normalization".

Done.