//Standardization of Iotas Tangle by OMG Consortium moving forward

Standardization of Iotas Tangle by OMG Consortium moving forward

OMG Consortium released the Technical Meeting Agenda for their meeting 24th to 26th September 2018:​https://ift.tt/2MopUtB Infos on OMG, see here:https://ift.tt/2NvKnBp CEO Richard Soley is on the Supervisory Board of Iota:https://ift.tt/2Mn6Rjn of Richard Soley:https://ift.tt/2NAceAq on used Acronyms from:https://ift.tt/2Mn6Snr For Comment (RFC): An alternative to the Technology Adoption Process allowing an OMG member to request OMG adoption of an uncontentious specification without requiring a Request for Proposals to be issued.Technology Adoption Process: Defined by the P&P, the Technology Adoption Process has a number of steps. Check the definitions of italicized terms for details not repeated here.(1) Optionally, a TF may issue an RFI. The information gathered via an RFI may be used to generate zero, one, or more RFPs.(2) The TF writes an RFP and votes to recommend that its Parent Body issue it.(3) The AB certifies that the RFP is consistent with MDA and with all previously adopted OMG technology.(4) The Parent Body votes, which formally issues the RFP.(5) On or before the deadline specified in the RFP, submitting companies respond with LOIs. Submitting companies must be either Contributing Members (for any RFP), or Platform Members (for RFPs issued by the PTC), or Domain Members (for RFPs issued by the DTC).(6) On or before the next deadline, submitting companies submit Initial Submissions which are presented to the TF at one of its regularly scheduled meetings.(7) On or before the next deadline, submitting companies submit Revised Submissions which are presented to the TF at one of its regularly scheduled meetings. The Revised Submission deadline may be extended, and this step repeated, one or several times.(8) The TF evaluates the technology described in the submissions and, typically, recommends one to its Parent Body for adoption.(9) The AB certifies that the technology complies with the MDA and is consistent with previously adopted OMG technology.(10) The TF’s parent TC votes by email or FAX to recommend adoption of the technology to the BoD.(11) The BoD Business Committee certifies, based on surveys of the submitters’ plans to market commercial implementations of the technology, that an implementation will be available within a year.(12) The BoD votes to make the technology an Adopted Specification.(13) An FTF conducts the first maintenance revision of the technology.(14) The FTF report is certified by the AB and recommended by its parent TC, and at least one submitter actually makes an implementation commercially available.(15) A vote of the BoD makes the technology an Available Specification. NOTE: The RFC process provides an alternative to steps 1 through 8.[formatted for readability]

OMG Consortium released the Technical Meeting Agenda for their meeting 24th to 26th September 2018:

https://i.redd.it/5g5dil90usl11.jpg

PDF:

https://www.omg.org/events/ottawa-18/agendas/FDTF.pdf

For Infos on OMG, see here:

https://www.omg.org/about/

OMGs CEO Richard Soley is on the Supervisory Board of Iota:

https://blog.iota.org/welcome-richard-soley-to-the-iota-foundation-eb61e015187d?gi=448c003f525d

Bio of Richard Soley:

https://www.omg.org/~soley/bio.html

Informations on used Acronyms from:

https://www.omg.org/gettingstarted/terms_and_acronyms.htm#R

Request For Comment (RFC): An alternative to the Technology Adoption Process allowing an OMG member to request OMG adoption of an uncontentious specification without requiring a Request for Proposals to be issued.

Technology Adoption Process: Defined by the P&P, the Technology Adoption Process has a number of steps. Check the definitions of italicized terms for details not repeated here.

(1) Optionally, a TF may issue an RFI. The information gathered via an RFI may be used to generate zero, one, or more RFPs.

(2) The TF writes an RFP and votes to recommend that its Parent Body issue it.

(3) The AB certifies that the RFP is consistent with MDA and with all previously adopted OMG technology.

(4) The Parent Body votes, which formally issues the RFP.

(5) On or before the deadline specified in the RFP, submitting companies respond with LOIs. Submitting companies must be either Contributing Members (for any RFP), or Platform Members (for RFPs issued by the PTC), or Domain Members (for RFPs issued by the DTC).

(6) On or before the next deadline, submitting companies submit Initial Submissions which are presented to the TF at one of its regularly scheduled meetings.

(7) On or before the next deadline, submitting companies submit Revised Submissions which are presented to the TF at one of its regularly scheduled meetings. The Revised Submission deadline may be extended, and this step repeated, one or several times.

(8) The TF evaluates the technology described in the submissions and, typically, recommends one to its Parent Body for adoption.

(9) The AB certifies that the technology complies with the MDA and is consistent with previously adopted OMG technology.

(10) The TF's parent TC votes by email or FAX to recommend adoption of the technology to the BoD.

(11) The BoD Business Committee certifies, based on surveys of the submitters' plans to market commercial implementations of the technology, that an implementation will be available within a year.

(12) The BoD votes to make the technology an Adopted Specification.

(13) An FTF conducts the first maintenance revision of the technology.

(14) The FTF report is certified by the AB and recommended by its parent TC, and at least one submitter actually makes an implementation commercially available.

(15) A vote of the BoD makes the technology an Available Specification. NOTE: The RFC process provides an alternative to steps 1 through 8.

[formatted for readability]