[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti-stix] Proposal - Simplify UUID Requirements/Language
+1 This is very simple, very clean and removes the arbitrary limitation to UUIDv4. I would still prefer to define one identifier for all objects rather than having a separate deterministic-id spec but if we are not going to reach consensus on that then I prefer Patâs proposed change to the
spec for identifier. Sean Barnum Principal Architect FireEye M: 703.473.8262 E: sean.barnum@fireeye.com From: <cti-stix@lists.oasis-open.org> on behalf of Patrick Maroney <pmaroney@darklight.ai> Iâm repeating a proposal Iâve made twice before in hopes it will be considered and accepted/rejected solely on its merits. We have not re-established voting rights, so I cannot make a motion. However, I believe it is a simple solution to the STIX Identifier discourse and its adoption would allow us to move on to more complex issues. Proposal
Type Name: identifier
An identifier universally
and uniquely identifies a SDO, SRO, Bundle, or Marking Definition. Identifiers MUST follow the form object-type--UUID,
where object-type is the exact value (all type names are lowercase strings, by
definition) from the type property of the object being identified or referenced and
where the UUID is an RFC 4122-compliant UUID. The UUID MUST be generated
according to the algorithm(s) defined in RFC 4122, [RFC4122].
Please note the following assertions:
Patrick Maroney Merlin â Advisor to Kings DarkLight Email: patrick.maroney@darklight.ai This e-mail (including any attachments) may contain information that is private, confidential, or protected by attorney-client or other privilege. If you received
this e-mail in error, please delete it from your system without copying it and notify sender by reply e-mail so our records can be corrected. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]