Closed ioggstream closed 1 year ago
@darrelmiller @eemeli Do you think we should use normative language to address the yaml vs yml issue?
The proposed addition of "so only one SHOULD be used" sounds good to me.
The following statement
so only one SHOULD be used
could conflict with
.yaml
is preferred.
If we want to use normative language (which we avoided), we can just say .yaml is RECOMMENDED
(but we decided to avoid normative language).
@eemeli wdyt on .yaml
RECOMMENDED?
Uppercase RECOMMENDED
? Isn't that normative? How about just lowercase should
?
The AD suggestion is to use normative language @richsalz. If we don't want to do it, I think that the current text is ok and that we can just avoid normative language.
I do have two concerns:
I do not have any strong opinions here, and tbh would be fine with any of the options proposed so far. This sounds like a conversation that ought to be happening on a PR.
@eemeli if it's ok for you, we can just confirm that we agree to avoid normative statements here, like we decided in #68
Avoiding normative statements here is ok with me.
[x] Section 3.3: "SHOULD only use one extension between yaml and yml"
[x] 4. ----- FAQ Section:
FAQ is useful to track closed discussion. Relevant parts have been added to the spec