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

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep message

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

Subject: Meeting reminder and agenda for telecon June 10th

This is a reminder and the agenda for our telecon Thursday, June 10th,
from 1:30-3:30.  

Call in information is below (I have called the conference center and
verified the call-in information!) 

USA domestic toll free number: 1-866-235-8350
International number: 206-655-2988
Pass code: 669014#
Here is the phone number for the operator if you have any problems:
206-655-2254. 

Agenda:
	1. Minute taker
 
	2. Approval of minutes from last meeting

	3. eGov report

	4. WSRP report
 
	5. SCM subcommittee report

	6. cc Review subcommittee report

	7. Specs status

	8. Interface Change proposal
 <<[regrep] Proposed revision to HTTP interface for version 3>> 
	9. Interop demo opportunities
  <<[regrep] FW: [chairs]  Interop Demo Opportunities>> 
	10. Update on Publishing Web Services
  <<Re: [regrep] [Paper on Federated Registries] Re: [Fwd: Semantic Web
Services Architecture Committee Requirements   Document]>> 
	11. Survey discussion
  <<RepositoryQuestionaireRE.pdf>> 
	12. Other issues/items
 
	13. Next meeting

Please let me know if there are additional items for the agenda. 


Kathryn Breininger
CENTRAL Project Manager
Emerging Technologies
Boeing Library Services

425-965-0182 phone
425-237-3491 fax
kathryn.r.breininger@boeing.com
--- Begin Message --- 
Team,

Per my AI from last meeting I have created an uploaded a document 
describing proposed changes to the RS spec for 3.0 in the area of HTTP 
interface. In particular a new File Path based URL is included in the 
proposal as the main item for TC review prior to tomorrows meeting.

The document may be downloaded at:

http://www.oasis-open.org/apps/org/workgroup/regrep/download.php/7173/httpInterfaceChangeProposal.pdf

Kathryn would it be possible to set aside about 15 min in tomorrows meeting to do a WebEx based demo of the proposed File Path based URL feature? Is so I will setup WebEx and send details. 

Please be advised that (sadly) WebEx only seems to work on Windows Explorer. You  
should visit http://www.webex.com/dailydemo/index.php to test your browser setup prior to the meeting. 

Thanks.

-- 
Regards,
Farrukh



To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php.
--- End Message ---
--- Begin Message --- 
We have several opportunities for Interop Demos this year.  We need to let OASIS know in which ones we would be interested in demonstrating by June 15th.  Comments?
 
Kathryn
-----Original Message-----
From: Dee Schur [mailto:dee.schur@oasis-open.org] 
Sent: Wednesday, June 02, 2004 5:18 AM
To: chairs@lists.oasis-open.org
Cc: Dee Schur (Dee Schur); Jane Harnad; Carol Geyer (Carol Geyer)
Subject: [chairs] Interop Demo Opportunities



Dear TC chairs,

The Consortium is making plans now for an exciting fall/winter with some great opportunities for OASIS InterOps. These public interoperability demonstrations showcase multi-vendor implementations of approved OASIS work. Usually hosted in connection with a conference or trade show, OASIS InterOps are official Consortium activities, endorsed by one or more OASIS TCs, and mutually supported by OASIS staff and OASIS InterOp participants. 


Staff will provide assistance in promoting and organizing these events, but the real energy (and scripts) comes from the TC leadership and members.  TC participants demonstrate the usefulness of a spec, and its practical availability across a range of vendor platforms.  

Prior InterOps have generated tremendous energy and strong trade press for the work product.  Public InterOp events are an excellent opportunity to demonstrate real, shippable standards-based solutions for e-business problems.     

Several conference organizers are interested in featuring OASIS InterOps, they include: 


1) Delphi (4-7 Oct, BPX 2004)
2) OASIS Open Standards Days (4-8 Oct.)
3) Gartner (15-17 Nov, Applications Integration and Web Services Summit)
4) IDEAlliance (XML 2004, 16-18 Nov) <http://www.xmlconference.org/xmlusa/>
5) RSA (23-27 Feb) <http://2004.rsaconference.com/us/c4p/>
  



If your TC has an approved OASIS Committee Draft or OASIS Standard, or expects to be at that stage prior to these events, we encourage you to consider conducting a multi-member InterOp.  However, in order to make arrangements, we need to hear from you by June 15. If there is another conference at which you'd like to demonstrate, please let us know. We are ready to work with you to coordinate logistics, participation, and promotion.

Clearly, conferences organizers want OASIS InterOps because they recognize the quality of the work of OASIS TCs and the growing market power of open standards. Your diligence and efforts to advance open standards are much appreciated. 

Regards,

 

Dee Schur
--- End Message ---
--- Begin Message --- 
Thanks for sharing Joe.

This reminds me of the need for doing an update on the Publishing Web 
Services TN to add details on how to publish QoS attributes for Web 
Services and how to use those QoS attributes for Service discovery. Our 
existing specs handle this use case already but the details need to be 
spelled out.

I propose we add this to our next TC meeting's agenda. Thanks.

-- 
Regards,
Farrukh



Chiusano Joseph wrote:

>FYI: I sent the e-mail below to the SCM subcomittee, then noticed one of
>the citations [1] which was a paper on "Discovery of Web Services in a
>Federated Registry Environment" - so I thought it might be of interest
>to the full TC. Includes references to both UDDI and ebXML Registry.
>
>This University of Georgia (US) paper discusses the METEOR-S Web Service
>Discovery Infrastructure[2][3], which provides an ontology based
>infrastructure to provide access to registries divided based on business
>domains and grouped into federations. It also discusses how Web Service 
>discovery is carried out within a federation.
>
>[1] http://lsdis.cs.uga.edu/Library/download/MWSDI-ICWS04-final.pdf
>[2] http://lsdis.cs.uga.edu/proj/meteor/mwsdi.html
>[3] http://lsdis.cs.uga.edu/Projects/METEOR-S/index.php
>
>Joe
>
>Joseph Chiusano wrote:
>  
>
>>Just announced: The Semantic Web Services Initiative (SWSI) has released
>>architecture requirements for Semantic Web Services. Highlights are
>>included below - including service lifecycle and ontology management.
>>
>>[1] http://www.daml.org/services/swsa/swsa-requirements.html
>>
>>Thanks,
>>Joe
>>
>>HIGHLIGHTS:
>>
>>(1) Semantic Web Services are viewed as a way to extend the capabilities
>>of web services in the direction of dynamic interoperability, thereby
>>making it possible for clients to successfully utilize web services
>>without prior arrangements between people that are realized in rigid
>>software protocols, and immutable ontologies or meta-data.
>>
>>(2) The functions addressed by the Semantic Web Services Architecture
>>will include:
>>
>>* Dynamic Service Discovery: The capability for a software agent to
>>identify candidate services for particular objectives; includes
>>candidate service matchmaking and brokering functions.
>>
>>* Service Selection and Composition: The capability to dynamically
>>select and compose services to achieve some objective; includes failure
>>recovery and compensation mechanisms, as well as choreography
>>interpretation and execution. Also includes ontology translation
>>services.
>>
>>* Negotiation and Contracting: Ability for two agents to mutually
>>formulate a shared agreement in terms of performance to be provided;
>>includes dispute resolution and compliance.
>>
>>* Semantic Web Community Support Services: Capabilities associated with
>>sharing semantic descriptions, ontologies, ontology mappings, and
>>service catalogs within and across communities, and managing these items
>>as well.
>>
>>* Semantic Web Service Lifecycle and Resource Management Services:
>>Capability to management the lifecycle of Semantic Web Services.
>>
>>* Other: Includes QoS requirements (time, cost, reliabilty, operational
>>metrics, etc.), and the capability to discover a service based on these
>>factors.
>>
>>-------- Original Message --------
>>Subject: Semantic Web Services Architecture Committee Requirements
>>Document
>>Resent-Date: Thu,  3 Jun 2004 11:28:16 -0400 (EDT)
>>Resent-From: public-sws-ig@w3.org
>>Date: Thu, 03 Jun 2004 11:28:06 -0400
>>From: Mark Burstein <burstein@bbn.com>
>>To: public-sws-ig@w3.org
>>
>>The Architecture Committee of the Semantic Web Services Initiative
>>(SWSI)
>>has spent the last few
>>months putting together an overview of the functional requirements that
>>a
>>comprehensive approach to architectures for semantic web services should
>>include.  While different communities will need more or
>>less of some of the features covered, we felt it was worthwhile to try
>>to
>>take a longer term view in this exercise.
>>
>>The document is available for review and comment from the SWSA committee
>>home page at
>>http://www.daml.org/services/swsa/
>>
>>The document itself is located at
>>
>>http://www.daml.org/services/swsa/swsa-requirements.html
>>
>>Comments can be sent to public-sws-ig or to me personally at the address
>>below.
>>    
>>
>
>  
>




To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php.
--- End Message ---

RepositoryQuestionaireRE.pdf

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