Tihomir Surdilovic
Tihomir Surdilovic
@n3wscott In the JSON Schema data is defined as being one of two types, object or string: ```json "data": { "type": ["object", "string"] } ``` but array type should not...
@duglin It cannot alternate. It's either-or: https://github.com/cloudevents/spec/blob/master/spec.json#L12
IMO having both data and data_base64 is confusing. especially when you can define datacontenttype.
@kevinbader +1, I also think that if you allow "data" to be of type string, then datacontenttype+data is enough. There is no need for data_binary imo. wdyt?
@deissnerk thank you for the explanation! Got one more question: CE also defines the "dataschema" property as "Identifies the schema that `data` adheres to." Could we then not define our...
@deissnerk added contentEncoding as part of the overall json schema update - pr https://github.com/cloudevents/spec/pull/563 Would you mind reviewing this pr? Thanks.
@JBBianchi @cdavernas do you want to change the description per last comment before we merge this ?
@cdavernas do you want to apply @JBBianchi last comment or are we good to merge this?
> Yet a user starting a workflow instance does not know what the output of this workflow is. What is the expected to get when the workflow finishes? A JSON...
One thing I would like not to have to run into is users having to remove generated workflow state data just to conform to some shema. For example Foreach State...