Comments (6)
-
if someone intended to publish a new marking definition for an object from TLP Green to TLP Amber then they would also republish the objects because the objects themselves presumably have changed somehow to warrant going back from more open disclosure to more closed disclosure. this use case is covered by modification rules on the obejcts themselves and the relationships to marking objects. however, iām suggesting a different use case which is where an existing marking definition was published with a mistake or needs a tweak to remain correctly defined. its a more common use case and likely to happen. right now we would force people to have to create a new marking definition and literally have to update all objects from the previous marking definition to the new one. thats a substantially more negative impact
-
in either case (whether you allow only create or modification) the recipient still has detect the change and then do something about it. with allowing modification on marking objects then there will be a lot less new STIX objects created vs if you create to create a new marking object you need to go and modify all the obejcts that used the prior marking definition too. The recipient would have process either case the same anyway and all we are doing is forcing a lot more noise over the wire to communicate something that can be communicated by a modification to the marking object, the recipient detects that change and then looks up in their view what has to be redone themselves (or not). There is no enforcement to begin with anyway. So we are making a decision at a system level that has a big impact on the system when products can take care of the issue in either scenario
from cti-stix2.
I can see an argument to support allowing markings to be revoked, but am against allowing them to otherwise be modified. Though I suppose "revoking" would require a new version anyway. So I guess I'm opposed to allowing revoking, too.
from cti-stix2.
from cti-stix2.
Maybe you can introduce a multi-member voting requirement before revoke's are granted.
from cti-stix2.
This was discussed at the working call on 2/13/18. The consensus on the call was to NOT make this change. The poll was:
For the change: 0
Against the change: 9 (Sarah Kelley, Chris Ricard, Mark Davidson, Richard Struse, Nicholas Hayden, Paul Patrick, Bret Jordan, Sean Barnum, Philip Royer)
Abstain: 1
from cti-stix2.
The call for objections ended COB 02 March with no objections received to the TC mailing list. QED, we are closing this issue.
from cti-stix2.
Related Issues (20)
- Add some normative text about when the lat/long on a Location object is not consistent with the other properties
- Do we need any text to give guidance to valid times when an Indicator is revoked HOT 1
- minor typos/errata for correction consideration
- Should Observed Data objects be referred to in sighting_of_ref property of Sightings HOT 1
- Link to Open Vocabs in Section 10 from property descriptions HOT 4
- Spec property decorations fail accessibility guidelines HOT 1
- definition and definition-type properties are deprecated with implications for STIX 2.2
- typos in participants names
- Better link for Shannon Entropy and inclusion as informative reference
- typo in header C.2.2
- Vocabulary/Enumeration Table Headers HOT 1
- Feedback about external references not being available on File SCOs HOT 1
- The UUIDv5 SCO ids should be checked to make sure they agree with the generate_id method in python-stix2
- the Industry sectors' vocab doesn't have "legal"
- Embedded references in SCOs HOT 3
- Predefined/Subtype extensions should be possible when defining a new STIX object extension definition, even with new SDOs
- ITU Feedback HOT 4
- Update Best Practices Guide HOT 1
- 6.12.2 HTTP Request Extension example is invalid: request_header must be a list of type string HOT 1
- trademark on website
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-stix2.