https://github.com/anewton1998/draft-regext-rdap-extensions/issues/53
>> Section 2.4.7, paragraph 1 >> The styling convention used in [RFC9083] for JSON names is often called >> "camel casing", in reference to the hump of a camel. In this style, the >> first letter of every word, except the first word, composing a name is >> capitalized. This convention was adopted to visually separate the namespace >> from the name, with an underscore between them. Extension authors SHOULD >> use camel casing for JSON names defined in extensions. > Why is it recommended and what are the negative consequences of not following > this recommendation? [JS] Because of the precedence/status quo. > Also this is somehow inconsistent when 2.4.3. is actually recommending the > opposite when it comes to object class name. [JS] That’s an interesting observation. Perhaps, object class name could also be camel-cased for consistency with JSON member names?
_______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
