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 we forgot to remove the paragraph about the object search endpoint back when we removed that endpoint when we were finalizing TAXII 2.0. Since we no longer have an object search endpoint, I suggest that we remove this paragraph. The text that we should remove is:
For the Object Search Endpoint, objects MUST be sorted in ascending order by the date the object first appeared in object search (i.e., the added date). If an object would appear multiple times, all appearances after the first appearance MUST be omitted from the result. That is, if an object would have appeared first in the list and again halfway down, only the first entry should be present in the result.
The text was updated successfully, but these errors were encountered:
The proposal I sent to the email list is to just remove this paragraph as it is left over from when we had an Object Search endpoint. Since that endpoint does not exist, I believe we should just remove the text that talks about it. I made a call for objections to the list.
The following text has been removed from section 3.3 Sorting:
For the Object Search Endpoint, objects MUST be sorted in ascending order by the date the object first appeared in object search (i.e., the added date). If an object would appear multiple times, all appearances after the first appearance MUST be omitted from the result. That is, if an object would have appeared first in the list and again halfway down, only the first entry should be present in the result.
In section 3.3 we forgot to remove the paragraph about the object search endpoint back when we removed that endpoint when we were finalizing TAXII 2.0. Since we no longer have an object search endpoint, I suggest that we remove this paragraph. The text that we should remove is:
The text was updated successfully, but these errors were encountered: