Issue 4192: Replace the term "local value object type" as used in 2.2 (pki-ftf) Source: DSTC (Mr. Simon Gibson, gibson@dstc.edu.au) Nature: Uncategorized Issue Severity: Summary: The term "local value object type" used in 2.2 should probably be replaced by "value type". Sections 2.2.3-7 Resolution: Change the incorrect term to "valuetype" in text in Sections 2.2.3-7. Revised Text: Actions taken: February 5, 2001: received issue July 5, 2002: closed issue Discussion: End of Annotations:===== From: webmaster@omg.org Message-Id: <200102060209.f16292r18891@emerald.omg.org> Date: 05 Feb 2001 22:10:15 -0500 To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Issue/Bug Report Content-Type: Text/html; charset=windows-1252 X-UIDL: -?'!!ZW:e9P11e97E1e9 Name: Simon Gibson Company: DSTC mailFrom: gibson@dstc.edu.au Notification: No Specification: Public Key Infrastructure Section: 2.2.3-7 FormalNumber: dtc/2001-02-01 Version: 1 RevisionDate: 02/01/2001 Page: 2-2,2-4 Nature: Revision Severity: Minor HTTP User Agent: Mozilla/4.75 [en] (X11; U; SunOS 5.8 sun4u) Description The term "local value object type" used in 2.2 should probably be replaced by "value type". Sections 2.2.3-7 X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: pmclaughlin@baltimore.com (Patrick McLaughlin), polar@adiron.com (Polar Humenn), gjarboe@promia.com (Gene Garboe), cwbinko@trcinc.com (Bill Binko), mcconnell@osm.net (Stephen McConnell), dflinn@iona.com (Don Flinn), Ronald.Monzillo@east.sun.com (Ron Monzillo), gibson@dstc.edu.au (Simon Gibson), christopher_milsom@hp.com (Christopher Milsom) cc: pki-ftf@emerald.omg.org Subject: PKI FTF issue # 4192 Mime-Version: 1.0 Date: Thu, 15 Feb 2001 08:48:28 +1000 From: Simon Gibson Content-Type: text/plain; charset=us-ascii X-UIDL: Ko$!!KG6!!X*#e9J1ad9 This is issue # 4192 Simon Gibson gibson@dstc.edu.au Replace the term "local value object type" as used in 2.2 The term "local value object type" used in 2.2 should probably be replaced by "value type". Sections 2.2.3-7 ------------------------------------ Proposed Solution Replace all occurrences of "local value object type" with "value type" throughout document for accuracy and consistency. X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: pmclaughlin@baltimore.com (Patrick McLaughlin), polar@adiron.com (Polar Humenn), gjarboe@promia.com (Gene Garboe), cwbinko@trcinc.com (Bill Binko), mcconnell@osm.net (Stephen McConnell), dflinn@iona.com (Don Flinn), Ronald.Monzillo@east.sun.com (Ron Monzillo), gibson@dstc.edu.au (Simon Gibson), christopher_milsom@hp.com (Christopher Milsom) cc: pki-ftf@emerald.omg.org Subject: PKI FTF Request Vote on Issue #4192 Mime-Version: 1.0 Date: Tue, 26 Jun 2001 09:41:39 +1000 From: Simon Gibson Content-Type: text/plain; charset=us-ascii X-UIDL: cQm!!>^A!!0g;!!ip~e9 This is issue # 4192 Simon Gibson gibson@dstc.edu.au Replace the term "local value object type" as used in 2.2 The term "local value object type" used in 2.2 should probably be replaced by "value type". Sections 2.2.3-7 ------------------------------------ Proposed Solution Replace all occurrences of "local value object type" with "value type" throughout document for accuracy and consistency. From: "Stephen McConnell" To: "Simon Gibson" Cc: "Patrick McLaughlin" , "Gene Garboe" , "Bill Binko" , "Don Flinn" , "Ron Monzillo" , "Simon Gibson" , "Christopher Milsom" Subject: Feedback on the draft PKI FTF document Date: Wed, 1 Aug 2001 18:18:12 +0200 Message-ID: <000401c11aa5$8faefb20$0a01a8c0@osm.net> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <200107130559.f6D5xVm01732@thunder.dstc.qut.edu.au> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0001_01C11AB6.531D8C60" X-UIDL: /Yjd9l`id9?C@!!E)9e9 Hi everyone: I'm happy with most of the changes Simon has proposed. I do however have a problem with the resolution (no action) against 4192. I have attached the PDF file from Simon with annotations from myself. The annotations mainly concern (a) some suggestions on improving the text, and (b) recommendation of changes to properly resolve issue 4192 through rationalisation of the definition of several data-structures by changing from structs to valuetypes and tightening up some definitions. The changes I've proposed would make things simpler to implement, provide a higher level of type safety (by eliminating variable anys), and provide a sounder framework for future specification evolution, and last but not least, provide an easier mechanism for vendor enhancements. Please keep in mind that changing stuct definitions to valuetype is well within the scope of the FTF. I believe that this should be addressed now before the spec gets cast in stone. If the change to valuetypes is not carried out, we will be stuck with non-extendable structs and extra lines of code validating datatypes contained in anys. As such, could you all take a look at the notes and let me know what you think. Cheers, Steve. Stephen J. McConnell, OSM sarl digital products for a global economy http://www.osm.net mailto:mcconnell@osm.net Simon Gibson wrote: > Hi There, > > Well I haven't heard too much comment from people on the list. I > understand we are all busy and this is a bit of a context switch > so I have gone ahead and made changes to the document in relation > to all the changes I have proposed. So it may be easier to see > exactly what I mean by reading it in context as a whole document. > The doc has changebars and strikethroughs indicating changes. > > This document reflects the solutions I have proposed for issues > summarised as: > > #4190 - Raises clauses left out > #4192 - Use of any (No Changes) > #4192 - Change of "local value object type" to valuetype > #4193 - PKIStatus constants > #4194 - Transaction ID description > #4195 - RequestManager lifetimes > #4196 - Exception descriptions > #4197 - Asynchronous messaging > #4205 - EncodingType description > #4206 - CertificateType description > #4207 - ReqpresentationType name (No Changes) > > There has also been some discussion between myself and Stephen McConnell > with regard to using a valuetype for a Certificate. Stephen is going to > propose a basic valuetype that can be added to this specification. The > intention would be that that this be extended to create a more > encompassing set of operations for X509 V3 certs. This extension will be > done most likely through the RFP process. > > Look forward to hearing from you. > > Simon > [] pki_book.osm.pdf X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: pmclaughlin@baltimore.com (Patrick McLaughlin), polar@adiron.com (Polar Humenn), gjarboe@promia.com (Gene Garboe), cwbinko@trcinc.com (Bill Binko), mcconnell@osm.net (Stephen McConnell), Ronald.Monzillo@east.sun.com (Ron Monzillo), gibson@dstc.edu.au (Simon Gibson), christopher_milsom@hp.com (Christopher Milsom), IBalabine@iona.com (Igor Balabine) cc: pki-ftf@omg.org Subject: Vote on issues 4207, 4191, 4192 Mime-Version: 1.0 Date: Wed, 07 Nov 2001 11:34:39 +1000 From: Simon Gibson Content-Type: text/plain; charset=us-ascii X-UIDL: Y