Re: [search-ws] OASIS Web Services TC Strategy

["Ray Denenberg, Library of Congress" <rden@loc.gov>]

I think we can can get past this without modifying the charter though a clarification is probably warranted.  The intent was that we would not develop *external* APIs. Meaning that we were developing a protocol and APIs on top were out-of-scope.  Now were talking about splitting up the protocol (core spec, profiles, etc.) and we need to connectthe pieces.  Now we don't really have to call these connectors APIs, but if we do, we can call them "internal" APIs.

 

Does this sound reasonable?

 

Thanks.

 

--Ray

----- Original Message -----

From: Ashley Sanders

Cc: search-ws@lists.oasis-open.org

Sent: Friday, December 14, 2007 6:08 AM

Subject: Re: [search-ws] OASIS Web Services TC Strategy

Ray,

> We will develop a base, or core, specification - an abstract model from which
> serializations/profiles/bindings/extensions/specializations will be
> developed.

Just been looking over the group charter and it states:

   "development or standardisation of Abstract APIs is out of
    scope."

Are steps being taken to amend the charter?

Ashley.
--
Ashley Sanders               a.sanders@manchester.ac.uk
Copac http://copac.ac.uk A Mimas service funded by JISC

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php