OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

regrep-raws message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: Suggested Modifications to RSS and RIM


Thanks for the "Suggested Modifications to RSS and RIM ". It was well written
and easy to follow. Some additional thoughts follow:

Note I changed the subject to give this issue a separate thread.

Line 19:

>RegistryClient binds to the WSDL implementation files, and invokes the call
using SOAP 1.2  (XMLP when that standard becomes >Candidate Recommendation).

Should this be SOAP 1.1/attachments since 1.2 is not yet stable and not
supported by WSDL?

Line 23:

>The actor of this use case is RegistryClient. RegistryClient discovers a set
of WSDL specifications by accessing a public (no prior >CPA required to
interact), or a private (a valid CPA required to interact) registry.

I am not sure the distinction you make on CPA required is valid. Lets discuss
this further in meeting today.

Line 28:

>Subsequently, RegistryClient invokes the services. The request/response modes
supported by the RegistryClient are as described in >Sec 6.4.1 of [ebRS].

I think only synchronous request/response mode should be supported for the
initial RAWS use case.

Line 31:

>2 Changes to RSS[ebRS]

I would recommend also adding the following:

1. Reformat “Registry Architecture” chapter 6, to use web service as its
basis. Present ebXML MSG and async mode as advanced capabilities (may be
deferred to an appendix).
2. Define mapping between UML and SOAP services in updated appendix B
3. Downplay or eliminate RegistryService interface. Focus on the ObjectManager
and ObjectQueryManager
4. Reformat chapter 7, 8 to recast in term of web services

The effect of above indeed would be more work than we ideally want. However,
it will also help address understandability of the spec, something I believe
is important to adoption.


"Damodaran, Suresh" wrote:

> I am attaching my first take on RSS and RIM.
> I have tried to describe our use case, so please
> take a look at it. We can discuss it today, if you like.
> Regards,
> -Suresh
> -----Original Message-----
> From: Farrukh Najmi [mailto:Farrukh.Najmi@Sun.COM]
> Sent: Monday, August 06, 2001 11:39 AM
> To: regrep-raws@lists.oasis-open.org
> Cc: Chaemee Kim; John Evdemon
> Subject: RAWS Meting Reminder: Latest files attached)
> Team,
> Based on input received it seems that the 6-7pm US Eastern time is
> agreeable to most of us. Us East Coasters will grin and bear it :-)
> So we will meet each Monday from 6-7pm US Eastern starting tonight. Let
> me know if any of you are able to host the con calls for future weeks,
> and we will share the responsibility based on a agreed upon schedule.
> Here are the details for todays meeting:
> Agenda:
> --------
> -Discuss tactical plan
> -Report on Action Items from last meeting
> -Discuss latest WSDL and schema
> -Discuss issues related to attachments
> Logistics
> ---------
> Date: August 6, 2001
> Time: 6-7pm US Eastern
> US Toll free: 888-422-7116
> Intl Dial: 650-250-1218 (Sorry this is not toll free)
> The files for review are attached and also available at:
>     http://groups.yahoo.com/group/ebxmlrr-raws/files/
> I have yet to hear from John and Chaemee so I am continuing to CC them
> separately.
> --
> Regards,
> Farrukh
>   ------------------------------------------------------------------------
>                                 Name: ebXML-RSS-RIM-Changes.doc
>    ebXML-RSS-RIM-Changes.doc    Type: WINWORD File (application/msword)
>                             Encoding: base64
org:Sun Microsystems;Java Software
adr:;;1 Network Dr. MS BUR02-302;Burlington;MA;01803-0902;USA
fn:Farrukh Najmi

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC