< Return to Ballot details
Vote Details
| Ballot: Approve Custom Properties (STIX 2.0-1, Section 5.1) text as working draft |
Company:ThreatConnect, Inc. |
Vote:No |
Comment:Nay, as it runs counter to the principles of a parsable standard.
Understand if the intent is to be similar to "X-headers" in HTTP
I'd worry that the proposed implementation allows producers to define a "de-facto standard" for add'l fields, which must be parsed by each recipient, at the mercy of the expectations of each producer for format and content |
|
