Issue 4207: Naming of RepresentationType                                                                                                                                                                            (pki-ftf)
Source: DSTC (Mr. Simon Gibson, gibson@dstc.edu.au)
Nature: Clarification
Severity: Minor
Summary: The name "RepresentationType" would indicate that the type is a definition of a particular representation type, when in fact is a structure carrying a particular set of encoded information. For clarity this type should be renaming to something like "EncodedInformation".

Resolution: see above
Revised Text: 
Actions taken:
February 19, 2001: received issue
July 5, 2002: closed issue
Discussion: 
Simple name change (PKI.idl). From 

    struct RepresentationType { 
        EncodingType encoding_type; 
        Opaque date; 
    }; 
  

To 
    struct EncodedData { 
        EncodingType encoding_type; 
        Opaque data; 
    }; 

End of Annotations:=====
From: webmaster@omg.org
Message-Id: <200102190044.f1J0ieF11743@emerald.omg.org>
Date: 18 Feb 2001 20:46:21 -0500
To: <juergen@omg.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Issue/Bug Report
Content-Type: Text/html; charset=windows-1252
X-UIDL: V=kd9Ck@!!,?Oe9Y[Ee9



Name: Simon Gibson 
Company: DSTC 
mailFrom: gibson@dstc.edu.au 
Notification: No 
Specification: Public Key Infrastructure 
Section: 2.2 
FormalNumber: dtc/2001-02-01 
Version: 1 
RevisionDate: 02/02/2000 
Page: 2-3 
Nature: Clarification 
Severity: Minor 
HTTP User Agent: Mozilla/4.75 [en] (X11; U; SunOS 5.8 sun4u) 


Description

The name "RepresentationType" would indicate that the type is a
definition of a particular representation type, when in fact is a
structure carrying a particular set of encoded information. For
clarity this type should be renaming to something like
"EncodedInformation".


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: Request Vote Issues #4205 #4206 #4207
Mime-Version: 1.0
Date: Wed, 27 Jun 2001 14:24:19 +1000
From: Simon Gibson <gibson@dstc.qut.edu.au>
Content-Type: text/plain; charset=us-ascii
X-UIDL: 3ho!!iCjd9R?C!!LI$!!

This is issue # 4205	Simon Gibson gibson@dstc.edu.au

Specification of EncodingType

Section 2 "PKI Interface" does not define EncodingType. There is a an 
introduction to this is section 1, and details in the IDL, however,
for 
completeness - EncodingType should be declared under section 2,
probably 
following the definition of Opaque.

---------------------------------------
Proposed Solution

Add the following to Section 2 after 2.2.1 Opaque.

"The EncodingType is a type used to describe the method of encoding
used
to encode the original PKI structure to an Opaque type. The general
case 
will be ASN.1 DER (Distinguished Encoding Rules)."



This is issue # 4206		 Simon Gibson gibson@dstc.edu.au

Specification of CertificateType

Section 2 "PKI Interface" does not define CertificateType. For 
completeness
CertificateType should be declared under section 2, probably following
the 
definition of EncodingType (see issue B).

------------------------------
Proposed Solution

Add the following to Section 2

"The CertificateType is a type describing the actual type of
certificate 
represented in the Opaque data. This will in the general case most
likely
be an X509 Version 3 Certificate." 




This is issue # 4207 Simon Gibson gibson@dstc.edu.au

Naming of RepresentationType

The name "RepresentationType" would indicate that the type is a
definition 
of a particular representation type, when in fact is a structure
carrying 
a
particular set of encoded information. For clarity this type should be 
renaming to something like "EncodedInformation".
-------------------------------
Proposed Solution

Leave RepresentationType unchanged.


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 <gibson@dstc.qut.edu.au>
Content-Type: text/plain; charset=us-ascii
X-UIDL: Y<nd9)=(!!K3$!!)KGe9

Hi Everyone,

As promised here are some more issues to be voted on. In essence these
issues relate to changing the way in which a certificate etc are
represented. In the original specification we used anys so that a
valuetype could be used later on, well this gets rid of anys and
replaces with simple valuetypes.

Simon

-----------------------------

Issue 4207: Naming of RepresentationType (pki-ftf)

Click here for this issue's archive.
Source: DSTC (Mr. Simon Gibson, gibson@dstc.edu.au)
Nature: Clarification
Severity: Minor
Summary: The name "RepresentationType" would indicate that the type is
a
definition of a particular representation type, when in
fact is a structure carrying a particular set of encoded
information. For
clarity this type should be renaming to something like
"EncodedInformation".

Proposed Resolution:

Simple name change From

    struct RepresentationType {
        EncodingType encoding_type;
        Opaque date;
    };


To
    struct EncodedData {
        EncodingType encoding_type;
        Opaque data;
    };
-----------------------------
Y/N/Abstain |                |
---------------------------------------------------------------------------


Issue 4191: use of "any" (pki-ftf)

Source: DSTC (Mr. Simon Gibson, gibson@dstc.edu.au)
Nature: Uncategorized Issue
Severity:
Summary: The use of "any" rather than a union to handle the
representation_type in structures for Certificates, CRLs etc.
Sections
2.2.3-7
Proposed Resolution:

Change structs to valuetypes to the following:

From
    struct Certificate {
        CertificateType certificate_type;
        any representation_type;
    };
To
    valuetype Certificate {
        private CertificateType certificate_type;
        private EncodedData data;
    };
-------------------------------------------------------
From
    struct CRL {
        CRLType crl_type;
        any representation_type;
    };
To
    valuetype  CRL {
        private CRLType crl_type;
        private EncodedData data;
    };
-------------------------------------------------------
From
    struct CertificateRequest {
        CertificateRequestType cert_request_type;
        any representation_type;
    };
To
    valuetype CertificateRequest {
        private CertificateRequestType cert_request_type;
        private EncodedData data;
    };
-------------------------------------------------------
From
    struct Continue {
        ContinueType continue_type;
        any representation_type;
    };
To
    valuetype Continue {
        private ContinueType continue_type;
        private EncodedData data;
    };
-------------------------------------------------------
From
    struct CertRevocation {
        CertRevocationType cert_rev_type;
        any representation_type;
    };
To
    valuetype CertRevocation {
        private CertRevocationType cert_rev_type;
        private EncodedData data;
    };
-------------------------------------------------------
From
    struct KeyRecResponse {
        KeyRecoveryType key_recovery;
       any representation_type;
    };
To
    valuetype KeyRecResponse {
        private KeyRecoveryType key_recovery;
        private EncodedData data;
    };
-------------------------------------------------------
    struct CertificateStatusRequest {
     CertificateStatusRequestType type;
       any representation_type;
    };
To
    valuetype CertificateStatusRequest {
        private CertificateStatusRequestType type;
        private EncodedData data;
    };
-------------------------------------------------------
From
    struct CertificateStatusResponse {
        CertificateStatusResponseType type;
       any representation_type;
    };
To
    valuetype CertificateStatusResponse {
        private CertificateStatusResponseType type;
        private EncodedData data;
    };
-------------------------------------------------------

Revised Text:
Actions taken:
February 5, 2001: received issue


-----------------------------
Y/N/Abstain |                |
---------------------------------------------------------------------------



Issue 4192: Replace the term "local value object type" as used in 2.2 
(pki-ftf)

Click here for this issue's archive.
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 "valuetype". Sections 2.2.3-7
Proposed Resolution:

Change the incorrect term to "valuetype" in text in Sections 2.2.3-7.

Revised Text:
Actions taken:
February 5, 2001: received issue
-----------------------------
Y/N/Abstain |                |
---------------------------------------------------------------------------