Sorry, I just say/saw (; to Evan) that I posted twice this morning. (01)
Leo Obrst wrote:
>
> FYI. Semantic Web Services standards, European efforts:
> e.g, Web Service Modeling Language (WSML) that formalizes the Web
> Service Modeling Ontology (WSMO). Also, Web Services Execution
> Environment (WSMX), one platform that uses these.
>
> -------- Original Message --------
> Subject: [seweb-list] CFP: 1st WSMO implementation workshop
> Date: Sat, 03 Jul 2004 07:11:19 +0200
> From: Holger Lausen <holger.lausen@xxxxxxxx>
> Organization: DERI
> To: holger.lausen@xxxxxxxx
>
> [This CFP is being posted to multiple lists; we apologize if you see
> it multiple times.]
>
> =======================================================================
> CALL FOR PARTICIPATION
> 1st WSMO IMPLEMENTATION WORKSHOP
>
> -----------------------------------------------------------------------
>
> http://www.wsmo.org/wiw/2004/
> 29th & 30th September 2004, Frankfurt
> =======================================================================
>
> SCOPE AND TOPICS
> ================
> Semantic Web Services are the next step in bringing the web to its full
> potential, after adding semantics to the static web. Web services can
> significantly increase the Web architecture's potential, by providing a
> way of automated program communication and discovery of services. This
> can be achieved by adding semantic annotations to the description of
> the component interfaces already available via standard technologies
> like WSDL, SOAP and UDDI.
>
> Recently, a new major initiative (WSMO)[1] has started in this area
> which has attracted a lot of attention. WSMO is an ontology for
> different aspects of Semantic Web Services aiming at solving the
> integration problem. The joint working groups around this initiative are
> developing a proper formalization language for semantic web services and
> providing (WSML)[2] and developing a reference implementation of WSMO
> (WSMX)[3].
>
> The objective of this workshop is to discuss different implementations
> related to WSMO, and to gain insight in problems related to implementing
> WSMO. We welcome papers on related topics and demonstrations of
> prototypes or deployed applications.
>
> TOPICS
> ======
>
> WSMO applications:
> - *WSMO runtime engine*
> Demonstrator that are able to handling all or parts of the tasks
> related to SWS at execution time (discovery, mediation, execution)
> - *WSMO reasoner*
> Reasoners and inference engines that provide support for particular
> constructs of WSML
> - *WSMO repository*
> Semantic enabled repositories that can store and retrieve elements of
> WSMO (Goals, Web Services, Mediator and Ontologies)
> - *WSMO editors*
> Editors that provide support for editing and browsing WSML
> descriptions.
>
> WSMO implementation process:
> - *WSMO interoperability in applications*
> This includes WSMO APIs architectures and design studies.
> - *WSMO compliance in legacy applications*
> Studies and Realization how WSMO applications can interoperate with
> existing legacy applications
> - *collaboration paths*
> Strategies on aligning different efforts and interoperability
> strategies.
> - *future plans*
>
> In the areas of (but not limited to these):
> - SWS Execution
> - SWS Discovery & Matchmaking
> - SWS Description
> - SWS Orchestration & Choreography
> - SWS Mediation
> - SWS Planning
>
> WORKSHOP FORMAT AND ATTENDANCE
> ==============================
>
> The program will occupy two days, and will include presentations of
> papers selected from the full papers category (see "Submissions" below).
> In some cases.
>
> There will be one invited speaker. Subject to time constraints, there
> may also be a panel of experts on a selected topic. Panels will be
> conducted in such a way as to encourage discussion with the audience.
>
> This workshop is open to all members of the SWS community. Please note
> that at least one author of each accepted submission must attend the
> workshop.
>
> Submission of a paper is not required for attendance at the workshop.
> However, in the event that the workshop cannot accommodate all who would
> like to participate, those who have submitted a paper (in any category)
> will be given priority for registration.
>
> SUBMISSIONS
> ===========
>
> All submissions should be formatted in Springer's LNCS style
> (www.springer.de/comp/lncs/authors.html), and sent by e-mail to
> holger.lausen@xxxxxxx
>
> Full papers will be peer-reviewed; position papers will receive no
> review.
>
> Accepted full papers will be scheduled for a presentation at the
> workshop, whereby we explicitly encourage the presentation of
> Demonstrators. In some cases, papers may be presented as part of themed
> discussion panels.
>
> We emphasize that a larger word count does not necessarily confer any
> greater likelihood of acceptance. In some cases -- such as papers
> describing early work on a project -- it is appropriate for papers to be
> considerably shorter than 15 pages. Naturally, however, figures that
> help the reader to quickly grasp the essence of complex material are
> strongly encouraged.
>
> Position statements are limited to 2 pages and should include some or
> all of the following:
>
> * introduction of the author(s)
> * brief description of your work (and possibly other work
> at your institution) related to Semantic Web services
> * tools or testbeds you have to offer to the community
> * discussion of what you view as the most challenging
> issues in Semantic Web Services and prospects for
> solving them
> * challenges, questions or issues that you'd like to see
> addressed at the workshop.
>
> IMPORTANT DATES
> ===============
>
> Submissions due: August 21, 2004
> Notification of acceptance: September 8, 2004
> Camera ready format due: September 25, 2004
>
> WORKSHOP ORGANIZERS
> ===================
> Eyal Oren, Holger Lausen
> Digital Enterprise Research Institute
> E-mail: eyal.oren@xxxxxxxx, holger.lausen@xxxxxxxx
>
> STEERING COMMITTEE
> =================
> Dieter Fensel, Christoph Bussler
> Digital Enterprise Research Institute
>
> PROGRAM COMMITTEE (to be confirmed)
> =================
> Michael Altenhofen, SAP AG, Germany
> Jürgen Angele, Ontoprise, Germany
> Steve Battle, Hewlett Packard, UK
> Richard Benjamins, iSOCO, Spain
> Alistair Duke, BT, UK
> Stefan Decker, Digital Enterprise Research Institute; I
> John Domingue, Open University, UK
> Sungkook Han, Wonkwang University, Korea
> Chris Priest, Hewlett Packard, UK
> Michael Kifer, University at Stony Brook, USA
> Atanas Kiryakov, OntoText, Bulgaria
> Enrico Motta, Open University, UK
> Bijan Parsia, University of Maryland, USA
> Marta Sabou, Vrije Universiteit, N
> Takahira Yamaguchi, Keio University, Japan
>
> [1] http://www.wsmo.org
> [2] http://www.wsmo.org/wsml
> [3] http://www.wsmo.org/wsmx
>
> --
> Holger Lausen
>
> Digital Enterprise Research Institute (DERI)
> http://www.deri.org//
>
> Tel: +43 512 27287814
> Email: holger.lausen@xxxxxxxx
> _______________________________________________
> seweb-list mailing list
> seweb-list@xxxxxxxxxxxxxxxxxxxxx
> http://informatik.uibk.ac.at:2081/mailman/listinfo/seweb-list
>
> _________________________________________________________________
> Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
> Subscribe/Unsubscribe/Config:
>http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
> Shared Files: http://ontolog.cim3.net/file/
> Community Wiki: http://ontolog.cim3.net/wiki/
> To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx
> (02)
--
_____________________________________________
Dr. Leo Obrst The MITRE Corporation, Information Semantics
lobrst@xxxxxxxxx Center for Innovative Computing & Informatics
Voice: 703-883-6770 7515 Colshire Drive, M/S H305
Fax: 703-883-1379 McLean, VA 22102-7508, USA (03)
lobrst.vcf
Description: Card for Leo Obrst
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Subscribe/Unsubscribe/Config:
http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx (01)
|