Comments (2)
We talked about this at the F2F and the consensus of the room was to make this change. That is change version and media_type to be single strings and due atomic elements for manifest resources.
from cti-taxii2.
After discussion at the F2F and over slack, this issue was sent to the email list twice, asking for objections. Since no objections were given, this has been implemented. The changes were made in section 5.6.1. Just to be clear, the version and media_type properties were changed from being a list of strings to a single string. This also means that the plurality of the property names as also changes to be singular.
The manifest type description now says:
The manifest-entry type captures metadata about a single version of an object, indicated by the id property. The metadata includes information such as when that version of the object was added to the Collection, the version of the object itself, and the media type that this specific version of the object is available in.
The version property description is now greatly simplified to be just:
The version of this object. For objects in STIX format, the STIX modified field is the version.
from cti-taxii2.
Related Issues (20)
- Rename the spec_versions url filter parameter to be singular HOT 1
- Make the TAXII Envelope contain a list of objects not a bundle HOT 2
- Add text to explain status counts when server has yet to start processing request HOT 1
- Consider renaming the status value of pending to processing HOT 1
- What is the purpose of Discovery API roots having different domains in the list of api_roots ? HOT 2
- API Root Resource does not define the URL of the resource? HOT 2
- Typo in url prop of section 5.4 HOT 2
- Change integer to be 54 bits in size per RFC 7493 HOT 1
- If collections permission has false for CanRead and CanWrite, does user have permissions to see existence of Collection?
- RFE: Add additional Supported Fields to TAXII Filtering HOT 1
- Potential confusion with errors when adding duplicate objects
- Potential Confusion on Get Object Manifests
- Potentially misleading table in TAXII spec
- Typos in the TAXII spec
- Manifest & Versions Resource missing `next` Property HOT 1
- Additional URL query parameters
- Match field formatting
- "Incorrect" Spelling
- TAXII filtering is ambiguous when handling spec_version and version match fields
- Advanced filtering capability
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cti-taxii2.