RE: [regrep] Proposal for a ebXML Regrep subcommittee

["David RR Webber \(XML\)" <david@drrw.info>]

Farrukh,

 

Agree with the edit - for some reason my original text garbled that - your text is really what I was driving at!

 

Thanks, DW

"The way to be is to do" - Confucius (551-472 B.C.)

-------- Original Message --------
Subject: Re: [regrep] Proposal for a ebXML Regrep subcommittee
From: "Farrukh S. Najmi" <farrukh@wellfleetsoftware.com>
Date: Thu, December 14, 2006 11:11 am
To: "Breininger, Kathryn R" <kathryn.r.breininger@boeing.com>
Cc: ebXML Regrep <regrep@lists.oasis-open.org>,  david@drrw.info

+1 on the idea of a REST Subcommittee to operate under the ebXML
Registry TC.
Thank you David for this valuable proposal.

I would like to propose one small change to the proposed deliverables:

Current:

- Detailed Technical proposal on REST-based Interfacing. This will
incorporated into the specs as spec content once approved.

Proposed Replacement:

- Detailed technical specification for a REST-based interface to ebXML Registry. We can decide later whether this will be incorporated into the a future version of core ebRS spec or whether it will remain a separate spec in our spec bundle.

Thanks.


Breininger, Kathryn R wrote:
> There has been a proposal for a REST Subcommittee to operate under the
> ebXML Registry TC. Please see the draft charter below.  I will add this
> item to our agenda for our next meeting, which is scheduled for December
> 21, at 8:00 am Pacific Time.  In the meantime, please review and discuss
> on the list.
>
> Proposal for REST interface development SC for ebXML Registry.
>
> In keeping with the TC Charter focus on developing future versions of
> the OASIS ebXML Registry Specifications with consideration of related
> technologies adopted by other forums - the REST sub-committee will
> develop a specification document to allow implementers to develop a
> complimentary optional REST-based interface for Registry. This will
> not replace the existing interface - but augment the access methods
> that Registry can support based on the existing RIM and APIs. The SC
> will first formalize the scope and use cases to be addressed using
> REST-based interfacing and then develop formal mechanisms and
> specification details to implement that. This will be tailored to
> ensure focus on rapidly attainable results. The goal will be to
> support a limited common set of use cases, rather than an extended set.
> One particular use case will be to support development of AJAX-based
> user interfaces for registry. If REST is determined to be poorly suited
> to support a particular interface mechanism then that will be simply
> documented and noted. Later work may then optionally address this when
> better understanding and practical experience provide better insights.
>
>
> Deliverables for the SC:
> - Slide Presentation: Includes, Use cases, Requirements, Motivations,
> Assumptions and Overview of Technical proposal.
> - Detailed Technical proposal on REST-based Interfacing. This will
> incorporated into the specs as spec content once approved.
> - Paper on "REST-based interfacing using the ebXML Registry". Venue for
> submission of paper will be determined later.
>
> Kathryn
>
> Kathryn Breininger
> CENTRAL Project Manager
> Emerging Technologies
> Boeing Library Services
>
> 425-965-0182 phone
> 425-237-3491 fax
> kathryn.r.breininger@boeing.com
>
>  
>> How was your service? Please click link below.......
>> http://socal.web.boeing.com/ssglibsurvey/
>>
>>
>>    


--
Regards,
Farrukh

Web: http://www.wellfleetsoftware.com