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
The current metadata properties in the specification don't define data model and serialization formats for all metadata properties. This should be fairly straightforward to fix by defining this sort of stuff in the definitions for each metadata property.
The text was updated successfully, but these errors were encountered:
The structure used to communicate this metadata MUST be a map of properties. Each property name MUST be a string. Each property value MUST be a string, map, list, boolean, or null. The values within any complex data structures such as maps and lists MUST be one of these data types as well.
I think you're correct that some metadata properties such as created define the data type of their value, whereas this is currently missing for others such as accept.
The current metadata properties in the specification don't define data model and serialization formats for all metadata properties. This should be fairly straightforward to fix by defining this sort of stuff in the definitions for each metadata property.
The text was updated successfully, but these errors were encountered: