You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 18, 2024. It is now read-only.
In the Vocabulary Workgroup meeting July 27th we touched upon the topic of casing/delimiters for event attributes.
For top level attributes, CloudEvents enforces an "all lowercase letters and numbers only", but for the content of the data attribute (where we presumably would put all or most of our attributes) the CloudEvents specification does not provide any restrictions.
In the "Prior Arts" part of the Cloud Events primer several other event-like data structures are listed, and they seem to fall mostly into either the camelCase or the hyphen-separated category.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In the Vocabulary Workgroup meeting July 27th we touched upon the topic of casing/delimiters for event attributes.
For top level attributes, CloudEvents enforces an "all lowercase letters and numbers only", but for the content of the
data
attribute (where we presumably would put all or most of our attributes) the CloudEvents specification does not provide any restrictions.In the "Prior Arts" part of the Cloud Events primer several other event-like data structures are listed, and they seem to fall mostly into either the camelCase or the hyphen-separated category.
What do we want for our own attributes?
Beta Was this translation helpful? Give feedback.
All reactions