[v1.3 review] Should "event_type" have a pattern constraint?

[garethsb]

IS-07 uses the "pattern": "^[^\\s\\/]+(\\/[^\\s\\/]+)*$" for its "event_type".

Should this be applied to IS-04 v1.3 Source/Flow "event_type" in IS-04 and Receiver caps "event_types"?

[andrewbonney]

As things stand I'd suggest not. Ideally it'd be nice to decouple new Source/Flow attributes from the IS-04 spec (which may eventually be covered by the parameter registers or similar). As such I'd prefer to avoid imposing this validation here, but perhaps to record it via mini-schemas in another repository.

[garethsb]

OK. Let's mark this as 'enhancement' to revisit post-v1.3.