Issue 5792: CORBA-WSDL/SOAP: section 1.2.8.2 , 1.2.8.4 and 1.2.8.5                                                                                                                                                  (corbawsdl-ftf)
Source: Fujitsu (Mr. Tom Rutt, tom@coastin.com)
Nature: Uncategorized Issue
Severity: 
Summary: section 1.2.8.2 , 1.2.8.4 and 1.2.8.5 - In all the Example WSDL, the
target namespace in definitions and the namespace in import using URL
"http://tempuri.org/anExample/.." do not seem correct.


Proposed Resolution: fix the example after resolving the Type prefix FTF


issue on namespace and module name uniqueness.

Resolution: Fix the examples to use the correct target namespace url
Revised Text: In 1.2.8.2, 1.2.8.4, and 1.2.8.5, change:

“

targetNamespace="http://tempuri.org/anExample/definitions"

xmlns:tns="http://tempuri.org/anExample/definitions"

xmlns:xsd1="http://tempuri.org/anExample/schemas"

xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"

xmlns="http://schemas.xmlsoap.org/wsdl" >

<import

namespace="http://tempuri.org/anExample/schemas"

location="http://tempuri.org/anExample.xsd"/>

“

to:

“

targetNamespace=" http://www.omg.org/IDL-Mapped/"

xmlns:tns="http://www.omg.org/IDL-Mapped/"

xmlns:CORBA=http://www.omg.org/IDL-WSDL/1.0/

xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"

xmlns:wsdl="http://schemas.xmlsoap.org/wsdl" >

<import

namespace=" http://www.omg.org/IDL-WSDL/1.0/"/>

“


Actions taken:
December 17, 2002: received issue
November 6, 2003: closed issue
Discussion: 

End of Annotations:=====
Date: Tue, 17 Dec 2002 12:30:41 -0500 
From: Tom Rutt <tom@coastin.com> 
Reply-To: tom@coastin.com 
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) 
X-Accept-Language: en 
To: juergen@omg.org, issues@omg.org, 
   "corbawsdl-ftf@omg.org" <corbawsdl-ftf@omg.org> 
Subject: MARS and AB FTF issues for CORBA-WSDL/SOAP interworking 


Juergen, could you please file these as official issues for the FTF to
resolve.


Thank you:


Tom Rutt
corbawsdl FTF chair
---------------------
Initial FTF Issues on 02-10-12-draft-adopted-spec.PDF


FTF Issue 7
Source: AB review
section 1.2.8.2 , 1.2.8.4 and 1.2.8.5 - In all the Example WSDL, the
target namespace in definitions and the namespace in import using URL
"http://tempuri.org/anExample/.." do not seem correct.


Proposed Resolution: fix the example after resolving the Type prefix
FTF


issue on namespace and module name uniqueness.


Date: Tue, 18 Mar 2003 20:26:26 -0500 
From: Tom Rutt <tom@coastin.com> 
Reply-To: tom@coastin.com 
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 
X-Accept-Language: en-us, en 
To: "corbawsdl-ftf@omg.org" <corbawsdl-ftf@omg.org> 
Subject: Issue 5792 proposal 
X-OriginalArrivalTime: 19 Mar 2003 01:29:28.0031 (UTC) FILETIME=[FB9286F0:01C2EDB6] 


Issue 5792: CORBA-WSDL/SOAP: section 1.2.8.2 , 1.2.8.4 and 1.2.8.5 (corbawsdl-ftf)


Click here for this issue's archive.
Source: Fujitsu (Mr. Tom Rutt, tom@coastin.com)
Nature: Uncategorized Issue
Severity:
Summary:


section 1.2.8.2 , 1.2.8.4 and 1.2.8.5 - In all the Example WSDL, the


target namespace in definitions and the namespace in import using URL


"http://tempuri.org/anExample/.." do not seem correct.






Proposed Resolution: fix the example after resolving the Type prefix FTF


issue on namespace and module name uniqueness.



Proposed Resolution:  Fix the examples to use the correct target namespace url.
Proposed Revised Text:


In 1.2.8.2, 1.2.8.4, and 1.2.8.4, change:



targetNamespace="http://tempuri.org/anExample/definitions"


xmlns:tns="http://tempuri.org/anExample/definitions"


xmlns:xsd1="http://tempuri.org/anExample/schemas"


xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"


xmlns="http://schemas.xmlsoap.org/wsdl" >


<import


namespace="http://tempuri.org/anExample/schemas"


location="http://tempuri.org/anExample.xsd"/>



to:



targetNamespace=" http://www.omg.org/IDL-Mapped/"


xmlns:tns="http://www.omg.org/IDL-Mapped/"


xmlns:CORBA=http://www.omg.org/IDL-WSDL/1.0/


xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"


xmlns:wsdl="http://schemas.xmlsoap.org/wsdl" >


<import


namespace=" http://www.omg.org/IDL-WSDL/1.0/"/>





<The resulting examples need to be checked to see if they are correct given this change. This must be done before the final report is published>


Actions taken:
December 17, 2002: received issue




-- 
----------------------------------------------------
Tom Rutt                email: tom@coastin.com; trutt@fsw.fujitsu.com
Tel: +1 732 801 5744          Fax: +1 732 774 5133





Date: Wed, 02 Apr 2003 11:45:26 -0500 
From: Tom Rutt <tom@coastin.com> 
Reply-To: tom@coastin.com 
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 
X-Accept-Language: en-us, en 
To: "corbawsdl-ftf@omg.org" <corbawsdl-ftf@omg.org>, 
   iwasa 
 <kiwasa@jp.fujitsu.com> 
Subject: Vote impending for non controversial corbawsdl ftf issues 


So far the only issue which has had any discussion is ISSUE 5785.


The issue on examples (5792) depends on this issue resolution as well.


Thus I will send out a vote with the other proposed resolutions on this coming Monday.  Please look at the attached resolutions for wordsmithing
before the vote is sent out.


Please provided your comments on each proposal in a separate mail with the issue number in the title so it will get into the issues email archive.




TomRutt
FTF chair
-- 
----------------------------------------------------
Tom Rutt                email: tom@coastin.com; trutt@fsw.fujitsu.com
Tel: +1 732 801 5744          Fax: +1 732 774 5133



xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> 
Issue 5785: CORBA-WSDL/SOAP: Section 1.2.2.1 (corbawsdl-ftf)
Click here for this issue's archive.
Source: Fujitsu (Mr. Tom Rutt, tom@coastin.com)
Nature: Uncategorized Issue
Severity: 
Summary: 

Section 1.2.2.1 -
tns is a single namespace for all mapped IDL from the entire corba world. The module names for IDL across this vast namespace, need to be sufficiently qualified with pre-fixes (such as Type ID, or Pragma Prefix) to avoid module name collisions.
 
 
Proposed Resolution: FTF needs to determine appropriate prefixes or
namespaces to assure module name uniqueness in the generated WSDL

Discussion: 

The brute force approach is to use the scheme that is used for IDL form of repository ID for a Module.

 

Prefix the module name with the string from the pragma prefix IDL directive, usin g

(i.e. An OMG IDL pragma of the format:

#pragma prefi x 

)

 

Proposed Resolution:  The WSDL name for the IDL Module should be patterned after the IDL form for the repository ID for the Module.

 

Append the pragma prefix (if present, in front of the module name.  If the module definition has no corresponding pragma prefix directive, the prefix string shall be empty.

 

If pragma prefixes are not used, there could be collisions.  If such collisions were detected in the mapped WSDL document, they could be resolved by the addition of an appropriate pragma prefix to one of the IDL module definitions.

 

Need to fix all examples to use this pragma prefix in module name prefixes


Proposed Revised Text: 

Remove the following text from th e row of the table in 1.2.2.1

(There are still some issues to be addressed at the FTF stage around how we should map repository IDs into namespaces, so it is likely that some sort of concatenation of namespace and ID will occur).

 

Also, in section 1.2.4 Modules:

Change

IDL modules are represented in WSDL as prefixes to the names contained in the module. These prefixes are concatenated using  a as a separator. For example, an entit y in a modul e will have the nam e in WSDL.

 

to the following:

IDL modules are represented in WSDL as module name prefixes to the names contained in the module.  The module prefix to use shall be the pragma prefix associated with to the IDL module definition (or the empty string if there is no pragma prefix directive) concatenated.to the module name, using  a as a separator.

 

These module prefixes are concatenated using  a as a separator. For example, an entit y in a modul e with pragma prefi x  will have the nam e in WSDL.   If there were no pragma prefix directive, the same IDL entit y in modul e would have the nam e in WSDL.

 

Fix all examples to append the pragma prefix before the module name (at least pu t before the module name, if there is no pragma prefix in the IDL example).  <this needs to be done before the final report is sent in>
Actions taken:
December 17, 2002: received issue

 

xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> 
Issue 5786: CORBA-WSDL/SOAP: Section 1.2.3 (corbawsdl-ftf)
Click here for this issue's archive.
Source: Fujitsu (Mr. Tom Rutt, tom@coastin.com)
Nature: Uncategorized Issue
Severity: 
Summary: 

Section 1.2.3 - need to have appropriate text to describe the nature of
the source "hint".  Examples might be included, using filenames.
 
 
Proposed Resolution: FTF should determine appropriate text.
 

Discussion:  The nature of the hint can remain an implementation specific matter.   

Resolution:  Close issue with no revision.
Revised Text:   None
Actions taken:
December 17, 2002: received issue

 

xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> 
Issue 5787: Section 1.2.3 repository id inconsistency (corbawsdl-ftf)
Click here for this issue's archive.
Source: Fujitsu (Mr. Tom Rutt, tom@coastin.com)
Nature: Uncategorized Issue
Severity: 
Summary: 

Section 1.2.3 - there is an inconsistency, in that the documentation
schema for the repository ID does not include the version of the mapping,
 
 
as included in the URL source documentation schema.
Knowing what version of the IDL to WSDL mapping produced the WSDL is
important for gateway design.
 
 
Proposed Resolution: add mapping version to the respositoryID
documentation schema.

Discussion:  This is a bug.  There is also two typographical errors in the schema for IDL source

Proposed Resolution:  Add mapping version to the repositoryID documentation schema
Proposed Revised Text: 

In section 1.2.3, schema for IDLsource:  change:

     <xsd:documentation>IDL/WSDL Mapping Info</xs:documentation>

to

      <xsd:documentation>IDL/WSDL Mapping Info</xsd:documentation>

 

also , in the same schema change:

<xsd:element name="version"> type="xsd:string" minOccurs="1" maxOccurs="1"/>

to

<xsd:element name="version" type="xsd:string" minOccurs="1" maxOccurs="1"/>

 

also, in the example text after the first schema, change (to match the schema name for the complex type): 

<wsdl:documentation>

  <CORBA:MappingInfo>

     <CORBA:source>IDL Source</CORBA:source>

     <CORBA:version>1.0</CORBA:version>

  </CORBA:MappingInfo>

</wsdl:documentation>

to:

<wsdl:documentation>

  <CORBA:SourceIDL>

    <CORBA:source>IDL Source</CORBA:source>

    <CORBA:version>1.0</CORBA:version>

  </CORBA:MappingInfo>

</wsdl:documentation>

 

also, change the following text for the repositoryID form schema and example from:

<?xml version="1.0" encoding="UTF-8"?>

<xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema targetNamespace=http://www.omg.org/IDL-MAPPED elementFormDefault="qualified" attributeFormDefault="unqualified">

<xsd:element name="repositoryID" typ=exsd:strign minoccurs=0 maxoccurs=1/>

</xsd:schema>

 

The generated WSDL will then use this schema to indicate the mapping information as shown in the following example:

 

<CORBA:repositoryID> repository-id  </CORBA:repositoryID>

to the following:

<?xml version="1.0" encoding="UTF-8"?>

<xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema targetNamespace=http://www.omg.org/IDL-MAPPED elementFormDefault="qualified" attributeFormDefault="unqualified">

    <xsd:element name="SourceRepositoryID" minoccurs=0>

        <xsd:annotation>

                <xsd:documentation>IDL Mapped Repository ID </xsd:documentation>

        </xsd:annotation>

       <xsd:complexType>

           <xsd:sequence>

                <xsd:element name="repositoryID" type="xsd:string" minOccurs="1" maxOccurs="1"/>

               <xsd:element name="version" type="xsd:string" minOccurs="1" maxOccurs="1"/>

           </xsd:sequence>

        </xsd:complexType>

    </xsd:element>

</xsd:schema>

 

The generated WSDL will then use this schema to indicate the mapping information as shown in the following example:

 

<wsdl:documentation>

  <CORBA:SourceRepositoryID>

     <CORBA:repositoryID> repositoryIDtext </CORBA:repositoryID>

    <CORBA:version>1.0</CORBA:version>

  </CORBA:SourceRepositoryID>

</wsdl:documentation>

Actions taken:
December 17, 2002: received issue

 

xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> 
Issue 5788: CORBA-WSDL/SOAP: section 1.2.4 (corbawsdl-ftf)
Click here for this issue's archive.
Source: Fujitsu (Mr. Tom Rutt, tom@coastin.com)
Nature: Uncategorized Issue
Severity: 
Summary: 

section 1.2.4 - The sentence "The most significant is that XML flattens
the constructed namespace to a single targeted namespace when an XML
schema is imported." does not seem quite correct. Avoiding a large
number of files for the wsdl processor to deal with is a major reason
cited by the submitters.
 
 
Proposed Solution: Replace the offending sentence, with: "Having a
separate namespace for each imported module results in a large number of
files for the WSDL processor to deal with when constructing a gateway."

Proposed Resolution:  Agree to editorial fix. 
Proposed Revised Text:  In section 1.2.4 change:

The most significant is that XML flattens the constructed namespace to a single targeted namespace when an XML schema is imported.

to:

Having a separate namespace for each imported module results in a large number of files for the WSDL processor to deal with when constructing a gateway.

Actions taken:
December 17, 2002: received issue

 

xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> 
Issue 5790: CORBA-WSDL/SOAP: Section 1.2.7.10 (corbawsdl-ftf)
Click here for this issue's archive.
Source: Fujitsu (Mr. Tom Rutt, tom@coastin.com)
Nature: Uncategorized Issue
Severity: 
Summary: 

Section 1.2.7.10 -
Only public state members are mapped. Since use of the Dynamic Any api
allows access to both the private and public members, this restriction 
was challenged by the AB revieweras unwarranted.
Also the sentence "For example, DII/DSI bridges will be unable to
process value types." is not justified.
 
 
The dynamic ANY api can be used to access value type state members in a
DII/DSI based gateway.
If private state cannot be represented, an input value type parameter
which has private state will not be mapped to the IDL server.
 
 
Proposed Solution:
Delete offending sentence about dynamic gateways.
Unless the private member restriction can be justified, change the spec
to map both private and public value type state members.

Discussion:   Since the dynamic ANY api can be used to access all value type state members in a DII/DSI gateway, the restriction to not mapping private state members needs to be removed.

Proposed Resolution:   Remove the restriction of not mapping Private state members.
Proposed Revised Text: 

In 1.2.7.10:

Remove the following text from the first sentence: 

 

 

Change:

Basic valuetypes are mapped to structs, as noted above. Private fields are ignored. For example, consider the following:

// IDL

valuetype sampleX {

   public short a;

   private long b;

}

The private fiel d is ignored, so this maps to:

<complexType name="sampleX">

    <xsd:sequence>

        <xsd:element  name="a" type="xsd:short" maxOccurs="1" minOccurs="1"/>

    </xsd:sequence>

to the following:

Basic valuetypes are mapped to structs, as noted above. Both Public and Private fields are mapped. For example, consider the following:

// IDL

valuetype sampleX {

   public short a;

   private long b;

}

 

This maps to:

<complexType name="sampleX">

    <xsd:sequence>

        <xsd:element  name="a" type="xsd:short" maxOccurs="1" minOccurs="1"/>

        <xsd:element  name="b" type="xsd:int" maxOccurs="1" minOccurs="1"/>

    </xsd:sequence>

Actions taken:
December 18, 2002: received issue

 

xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> 
Issue 5791: CORBA-WSDL/SOAP: Section 1.2.7.10.3 (corbawsdl-ftf)
Click here for this issue's archive.
Source: Fujitsu (Mr. Tom Rutt, tom@coastin.com)
Nature: Uncategorized Issue
Severity: 
Summary: 

Section 1.2.7.10.3 - need to represent value type in IDL sequence as an
IdRef/value choice.
 
 
Proposed Resolution:
fix spec to use the idRef/Value choice for sequence.

Discussion:  Agree to bug fix.  Also need resolve editorial problems pointed out in bold by the reviewer in  ptc/3-01-14.

Proposed Resolution: include IDL sequence including a value type in the mapping algorithm generation of the IdRef/value choice type.
Proposed Revised Text: 

In 1.2.7.10 change:

Mapping of value types as struct or value type members

 

IDL value types can have recursive definitions, allowing complex structures, such as graphs, to be represented. This occurs whenever a value type has a state member that is the same type as its containing value type. Such cycles in an instance graph can b e though a series of value types, which contain member
 

Due to its complexity, support at run time for mapping shared value types is a separate, optional, conformance point for this specification. 

 

Whenever an IDL struct or an IDL value type includes a member that is a value type, the corresponding sequence element for the value type member must be mapped to an xsd:choice element, containing

either:

    an element which is an that valuetype or, [Reviewer: Please clarify]

    an element which is a reference to a value type instance included in the same XML document.

to the following:

Mapping of value types as struct or value type members

 

IDL value types can have recursive definitions, allowing complex structures, such as graphs, to be represented. This occurs whenever a value type has a state member that is the same type as its containing value type. Such cycles in an instance graph can be s of eac h through a series of value types, which contain member
 

Due to its complexity, support at run time for mapping shared value types is a separate, optional, conformance point for this specification. 

 

Whenever an IDL struct, sequence, or value type includes a member that is a value type, the corresponding sequence element for the value type member must be mapped to an xsd:choice element, containing

either:

    an element which is a value of that valuetype or, 

    an element which is a reference to a value type instance included in the same XML document.

Actions taken:
December 17, 2002: received issue

 

xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> 
Issue 5792: CORBA-WSDL/SOAP: section 1.2.8.2 , 1.2.8.4 and 1.2.8.5 (corbawsdl-ftf)
Click here for this issue's archive.
Source: Fujitsu (Mr. Tom Rutt, tom@coastin.com)
Nature: Uncategorized Issue
Severity: 
Summary: 

section 1.2.8.2 , 1.2.8.4 and 1.2.8.5 - In all the Example WSDL, the
target namespace in definitions and the namespace in import using URL
"http://tempuri.org/anExample/.." do not seem correct.
 
 
Proposed Resolution: fix the example after resolving the Type prefix FTF
issue on namespace and module name uniqueness.

Proposed Resolution:  Fix the examples to use the correct target namespace url.
Proposed Revised Text:   

In 1.2.8.2, 1.2.8.4, and 1.2.8.4, change:

targetNamespace="http://tempuri.org/anExample/definitions"

xmlns:tns="http://tempuri.org/anExample/definitions"

xmlns:xsd1="http://tempuri.org/anExample/schemas"

xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"

xmlns="http://schemas.xmlsoap.org/wsdl" >

<import

namespace="http://tempuri.org/anExample/schemas"

location="http://tempuri.org/anExample.xsd"/>

to:

targetNamespace=" http://www.omg.org/IDL-Mapped/"

xmlns:tns="http://www.omg.org/IDL-Mapped/"

xmlns:CORBA=http://www.omg.org/IDL-WSDL/1.0/

xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"

xmlns:wsdl="http://schemas.xmlsoap.org/wsdl" >

<import

namespace=" http://www.omg.org/IDL-WSDL/1.0/"/>

 

<The resulting examples need to be checked to see if they are correct given this change. This must be done before the final report is published>

Actions taken:
December 17, 2002: received issue

 

Issue 5793: CORBA-WSDL/SOAP: Section 1.2.7.4 (corbawsdl-ftf)
Click here for this issue's archive.
Source: Fujitsu (Mr. Tom Rutt, tom@coastin.com)
Nature: Uncategorized Issue
Severity: 
Summary: 
The mapping does not state what value should be used for the default case.



Proposed Resolution:
Add text stating that any valid value for the discriminant, other than
those used in the union definition, can be inserted for the default case.


Resolution: Accept proposal from source
Revised Text: In section 1.2.7.4 , add the following new paragraph after the existing first paragraph:

Actions taken:
December 18, 2002: received issues of each otherother