Proposal: Reconsider the use of URI formatting

[MarkDavidson]

Per a discussion list post by Dave Cridland (emphasis mine):

2. Identifiers as URIs.

Message, Subscription, and Result IDs have been required to be URIs - this seems fairly unhelpful. I see two possible uses for having a URI here. Firstly, it gives a restrictive syntax likely to be reasonable easy to embed in a number of wire protocols (ie, mappings). Secondly, it allows a consistent resolvable reference. Clearly the reuse rules are such that using these for resolution would be problematic, and given that there's no scheme given the URIs don't contain any resolution information - they're simply an opaque identifier.

I suggest that a simple restrictive syntax is used here instead; perhaps printable ASCII characters (or letters/digits/hyphen).

The action would be to possibly choose a different formatting rule, as Dave suggests.

[JasonKeirstead]

I wish that these IDs - along with all IDs throughout STIX and TAXII - would just be changed to be UUIDs that follow RFC 4122.