[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: Action item folloup / team meeting
<xsd:element
name="RequestAcceptedResponse">
<xsd:annotation>
<xsd:documentation
xml:lang="en">
Mapping of the same named interface in ebRS.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:attribute
name="xml:lang"
use="required" type="xsd:NMTOKEN"/>
</xsd:complexType>
</xsd:element>
I am unsure of what you are attempting to do here. You appear to be attempting to define an attribute within a complex type within RequestAcceptedResponse. I think xml:lang is reserved and is obviously not appropriate for what you are attempting to do.
Joel
I am copying you individually since I have no idea if you are registered with mailing list or not.
How about each of you posting to the list with an update of your action items. Note that each of us at least have the AI to comment of the Registry.xsd file (see attached).
I would like to have weekly RAWS team meetings from here on until we have a proposal on the table for the teams consideration. I would like the meeting to be as late as possible so help Chaemee who is in Korea. How is Mondays at 6-7pm US Eastern, starting today August 6th? Since most of you are in earlier time zones this may not be a burden. Please let me know.
Action Item Followup
----------------------
This is to follow-up on the action items from last meeting:
>-Review XSD file sent by Farrukh (All)
Have not heard back from any of you. Please share your thoughts. If you think it is OK say so. If you don't understand it say so.
>-Add namespace support to XSD file sent by Farrukh (John)
John, please send us an update on where things are at today with adding namespace support in the XSD file.
>-Send initial WSDL file to team (Farrukh)
The above AI was done 7/28
>-Scan spec for what changes will be needed and where. Write initial text
>where possible (e.g. support for multiple bindings under Architecture
>section) (Suresh)
Suresh, please send me an update on where things are at today
Thanks for your help.
--
Regards,
Farrukh
Farrukh Najmi wrote:
Team,I am concerned that no one has responded. We need to get engaged quickly. John any chance you could take #1 and #2? I could take #3 if no one else picks
up. I suspect Suresh and Dan are busy with security and query respectively and may have less bandwidth.Farrukh Najmi wrote:
> Team,
>
> I need to hear back from you on interest to work on following suggested sub-tasks this week:
>
> 1. Someone take Registry.wsdl and improve (Need basic WSDL skills)
> 2. Someone take RegistrySOAPBinding and improve (Need skills in WSDL
> SOAP binding)
> 3. Someone add support for ObjectManager (Need skills in WSDL Mime bindings)
>
> Pleas let me know by COB today so I can send final sub-task assignment for next 2 week.
>
> Farrukh Najmi wrote:
>
> > Team,
> >
> > As promised, attached are the initial WSDL files. They are far from
> > perfect and only address ObjectQueryManager. I have placed them under
> > source comtrol so that your changes can be merged easily. I have not
> > tested that they parse correctly.
> >
> > Registry.wsdl defines the abstract service definition
> > RegistrySOAPBinding.wsdl imports the abstract definition and then binds
> > it to a SOAP binding
> >
> > Note the style I have used for name spaces. This is a suggested style:
> >
> > http://<oasis base path/registry/<version>/.....
> >
> > Let me know what you think of the style. We need to be consistent in
> > Registry.dtd namespace (John's AI).
> >
> > I can see the following initial work items based on these files as a
> > start:
> >
> > 1. Someone take Registry.wsdl and improve (Need basic WSDL skills)
> > 2. Someone take RegistrySOAPBinding and improve (Need skills in WSDL
> > SOAP binding)
> > 3. Someone add support for ObjectManager (Need skills in WSDL Mime
> > bindings)
> > 4. All review and suggest improvement
> >
> > Let me know which work items interest you. If you already have a busy
> > load dont sign up for more.
> >
> > --
> > Regards,
> > Farrukh
> >
> > ------------------------------------------------------------------------
> > <?xml version="1.0"?>
> > <definitions name="ObjectQueryManager"
> >
> > <documentation>
> > $Header: /jse/ebxmlrr/misc/Registry.wsdl,v 1.1 2001/07/28 20:29:36 najmi Exp $
> > This is the the normative abstract WSDL service definition for the OASIS ebXML Registry services.
> > </documentation>
> >
> > targetNamespace="http://www.oasis-open.org/registry/1.1/Registry.wsdl"
> > xmlns:tns="http://www.oasis-open.org/registry/1.1/Registry.wsdl"
> > xmlns:xsd1="http://www.oasis-open.org/registry/1.1/schemas/Registry.xsd"
> > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
> > xmlns="http://schemas.xmlsoap.org/wsdl/">
> >
> > <import namespace="http://www.oasis-open.org/registry/1.1/schemas"
> > location="http://www.oasis-open.org/registry/1.1/schemas/Registry.xsd"/>
> >
> > <message name="GetRootClassificationNodesRequest">
> > <part name="GetRootClassificationNodesRequest" element="xsd1:GetRootClassificationNodesRequest"/>
> > </message>
> >
> > <message name="GetClassificationTreeRequest">
> > <part name="GetClassificationTreeRequest" element="xsd1:GetClassificationTreeRequest"/>
> > </message>
> >
> > <message name="GetClassifiedObjectsRequest">
> > <part name="GetClassifiedObjectsRequest" element="xsd1:GetClassifiedObjectsRequest"/>
> > </message>
> >
> > <message name="SubmitAdhocQueryRequest">
> > <part name="SubmitAdhocQueryRequest" element="xsd1:SubmitAdhocQueryRequest"/>
> > </message>
> >
> > <message name="GetContentsRequest">
> > <part name="GetContentsRequest" element="xsd1:GetContentsRequest"/>
> > </message>
> >
> > <message name="RegistryResponse">
> > <part name="RegistryResponse" element="xsd1:RegistryResponse"/>
> > </message>
> >
> > <portType name="ObjectQueryManagerPortType">
> > <operation name="getRootClassificationNodes">
> > <input message="tns:GetRootClassificationNodesRequest"/>
> > <output message="tns:RegistryResponse"/>
> > </operation>
> >
> > <operation name="getClassificationTree">
> > <input message="tns:GetClassificationTreeRequest"/>
> > <output message="tns:RegistryResponse"/>
> > </operation>
> >
> > <operation name="getClassifiedObjects">
> > <input message="tns:GetClassifiedObjectsRequest"/>
> > <output message="tns:RegistryResponse"/>
> > </operation>
> >
> > <operation name="submitAdhocQuery">
> > <input message="tns:SubmitAdhocQueryRequest"/>
> > <output message="tns:RegistryResponse"/>
> > </operation>
> >
> > <operation name="getContents">
> > <input message="tns:GetContentsRequest"/>
> > <output message="tns:RegistryResponse"/>
> > </operation>
> >
> > </portType>
> >
> > </definitions>
> >
> > ------------------------------------------------------------------------
> > <?xml version="1.0"?>
> > <definitions name="ObjectQueryManager"
> >
> > <documentation>
> > $Header: /jse/ebxmlrr/misc/RegistrySOAPBinding.wsdl,v 1.1 2001/07/28 20:29:37 najmi Exp $
> > This is the the normative concrete SOAP/HTTP binding for the OASIS ebXML Registry services.
> > </documentation>
> >
> > targetNamespace="http://www.oasis-open.org/registry/1.1/RegistrySOAPBinding.wsdl"
> > xmlns:tns="http://www.oasis-open.org/registry/1.1/RegistrySOAPBinding.wsdl"
> > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
> > xmlns="http://schemas.xmlsoap.org/wsdl/">
> >
> > <documentation>
> > Import the definition of the abstract OASIS ebXML Registry services
> > </documentation>
> > <import namespace="http://www.oasis-open.org/registry/1.1/definitions"
> > location="http://www.oasis-open.org/registry/1.1/Registry.wsdl"/>
> >
> > <documentation>
> > The SOAP bindings to the abstract services follow
> > </documentation>
> >
> > <binding name="ObjectQueryManagerSoapBinding" type="tns:ObjectQueryManagerPortType">
> > <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
> > <operation name="getRootClassificationNodes">
> > <soap:operation soapAction="http://www.oasis-open.org/registry/1.1/RegistrySOAPBinding/ObjectQueryManager/getRootClassificationNodes"/>
> > <input>
> > <soap:body use="literal"/>
> > </input>
> > <output>
> > <soap:body use="literal"/>
> > </output>
> > </operation>
> > </binding>
> >
> > <documentation>
> > The concrete services bound to the SOAP bidning follows
> > </documentation>
> >
> > <service name="ObjectQueryManager">
> > <documentation>The ObjectQueryManager service of OASIS ebXML registry version 1.1</documentation>
> > <port name="ObjectQueryManagerPort" binding="tns:ObjectQueryManagerSOAPBinding">
> > <soap:address location="http://www.oasis-open.org/registry/1.1/ObjectQueryManager"/>
> > </port>
> > </service>
> >
> > </definitions>
>
> --
> Regards,
> Farrukh--
Regards,
Farrukh
--
Regards,
Farrukh
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC