You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In section 3.3, sorting, we have a conflicting statement.
For the Collection and Manifest Endpoints, objects MUST be sorted in ascending order by the date the object first appeared in the TAXII Collection (i.e., the added date).
Then further down we have
For the Collections Endpoint, Collections MUST be sorted and MAY be sorted in any order.
The text was updated successfully, but these errors were encountered:
Section 3.3, which discusses sorting, is worded such that many first-time readers incorrectly conclude that the specification makes incompatible statements about sorting rules.
The proposed change is that the wording be clarified so that first-time readers do not make this conclusion. Normative changes are not proposed.
We talked about this at the F2F and have proposed text in the document to address this.
jordan2175
changed the title
Conflicting statement in sorting section of specification
Statements about Sorting Appear to Conflict, Don't
Feb 5, 2018
jordan2175
changed the title
Statements about Sorting Appear to Conflict, Don't
Statements About Sorting Appear to Conflict But on Closer Reading Do Not - Needs Clarification
Feb 5, 2018
In section 3.3 the text now reads, and I believe is more clear for first time readers:
For Object and Manifest Endpoints, objects returned MUST be sorted in ascending order by the date the object first appeared in the TAXII Collection (i.e., the added date). The most recently added object is last in the list.
The Collections Endpoint MUST return Collection Resources in a consistent sort order across multiple requests.
In section 3.3, sorting, we have a conflicting statement.
For the Collection and Manifest Endpoints, objects MUST be sorted in ascending order by the date the object first appeared in the TAXII Collection (i.e., the added date).
Then further down we have
For the Collections Endpoint, Collections MUST be sorted and MAY be sorted in any order.
The text was updated successfully, but these errors were encountered: