[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti] versioning
I agree that it would cause a lot of confusion if anyone can revision an object. Also, I think anyone should be able to provide suggested revisions to any object.
More spitballing. Scenarios
scenario 1: Originator discovery of new information that results in revision/revocation
scenario 2: Non-originator references previously shared information that Then the Originator revises or revokes previously shared information based on non-originator feedback – and includes references to the non-originator’s input. This assumes that the originator is and remains the authoritative source. If the Originator does not maintain their own material in the face of a lot of input from others, then in some Darwinian fashion, someone else will take over as a new Originator of a new object, I guess. Pam Smith
JHU/APL
From: cti@lists.oasis-open.org <cti@lists.oasis-open.org> on behalf of Jason Keirstead <Jason.Keirstead@ca.ibm.com>
Sent: Monday, February 15, 2016 8:29 AM To: Patrick Maroney Cc: Jordan, Bret; cti@lists.oasis-open.org Subject: Re: [cti] versioning Question - who is "allowed" to revision an object? Can only the originator revision, or can anyone?
Although I suspect I'm banned from using the term Timestamp for at least a year ;-) ...Here's an interesting concept to consider:
Patrick Maroney Office: (856)983-0001 Cell: (609)841-5104 ![]() President Integrated Networking Technologies, Inc. PO Box 569 Marlton, NJ 08053 From: "cti@lists.oasis-open.org" <cti@lists.oasis-open.org> on behalf of Bret Jordan <bret.jordan@bluecoat.com> Date: Thursday, February 11, 2016 at 7:48 PM To: "cti@lists.oasis-open.org" <cti@lists.oasis-open.org> Subject: [cti] versioning What would people think about a versioning concept where each TLO had a "serial_number" field that was of type integer. And every object that gets created by a producer will start with serial_number "1". Then as they update the TLO, the producer will just incase the serial_number. I want to get the discussion started as I know some have very strong opinions on how it should work. But I also think, that with some good back and forth dialog, and some "coming to middle ground" we could solve this pretty quickly. Thanks, Bret Bret Jordan CISSP Director of Security Architecture and Standards | Office of the CTO Blue Coat Systems PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 F2C0 74F8 ACAE 7415 0050 "Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg." |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]