W3C home > Mailing lists > Public > public-ws-desc-eds@w3.org > May 2007

2002/ws/desc/wsdl20 wsdl20-rdf.html,1.43,1.44

From: Jacek Kopecky via cvs-syncmail <cvsmail@w3.org>
Date: Sun, 20 May 2007 15:41:07 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <E1HpnWt-0003YS-9O@lionel-hutz.w3.org>

Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv13640

Modified Files:
	wsdl20-rdf.html 
Log Message:
adding conformance, implementation statements

Index: wsdl20-rdf.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-rdf.html,v
retrieving revision 1.43
retrieving revision 1.44
diff -C 2 -d -r1.43 -r1.44
*** wsdl20-rdf.html	20 May 2007 14:17:29 -0000	1.43
--- wsdl20-rdf.html	20 May 2007 15:41:04 -0000	1.44
***************
*** 46,52 ****
  </dl>
  
! <!-- todo proof-read -->
! 
! <!-- todo 
  The group has not defined who and what will implement this specification.
  
--- 46,50 ----
  </dl>
  
! <!-- todo  done, now respond
  The group has not defined who and what will implement this specification.
  
***************
*** 61,65 ****
  -->
  
! <!-- todo
  295: the RDF mapping document uses no capitalized RFC 2119 keywords, it
  only repeats (in lowercase) the restrictions from WSDL itself. However,
--- 59,63 ----
  -->
  
! <!-- todo done, now respond
  295: the RDF mapping document uses no capitalized RFC 2119 keywords, it
  only repeats (in lowercase) the restrictions from WSDL itself. However,
***************
*** 158,161 ****
--- 156,160 ----
  &nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#naming-conventions">Naming and Notation Conventions</a><br />
  &nbsp;&nbsp;&nbsp;&nbsp;1.2 <a href="#overview">Organization of this specification</a><br />
+ &nbsp;&nbsp;&nbsp;&nbsp;1.3 <a href="#conformance">Conformance</a><br />
  2. <a href="#ontology">WSDL Ontology</a><br />
  &nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#core">Core WSDL Components</a><br />
***************
*** 232,236 ****
  href="#rdf">RDF</a>]) and OWL ([<a href="#owl">OWL</a>])
  vocabulary to express WSDL&nbsp;2.0, so that WSDL&nbsp;2.0 documents can be
! transformed into RDF and merged with other Semantic Web data.</p>
  
  <p>Note: the readers of this document are expected to have an understanding of
--- 231,240 ----
  href="#rdf">RDF</a>]) and OWL ([<a href="#owl">OWL</a>])
  vocabulary to express WSDL&nbsp;2.0, so that WSDL&nbsp;2.0 documents can be
! transformed into RDF and merged with other Semantic Web data. This
! specification can be implemented as a standalone tool, as part of a tool
! that generates WSDL descriptions (outputting the RDF form in parallel to the
! XML form), or as part of a tool that processes RDF data, enabling the ability
! to read WSDL documents as RDF input.
! </p>
  
  <p>Note: the readers of this document are expected to have an understanding of
***************
*** 333,336 ****
--- 337,367 ----
  </ul>
  
+ 
+ <h3 id="conformance">1.3 Conformance</h3>
+ 
+ <p>This document defines a mapping from valid WSDL 2.0 documents (interpreted
+ as the corresponding component model), into sets of RDF statements. A
+ conforming mapping processor must follow all the mappings specified in the
+ mapping tables in <a href="#ontology">Section&nbsp;2</a> of this document, to the extent of its
+ understanding of the optional WSDL extensions. A WSDL processor that
+ does not support the SOAP binding, for example, may not implement any
+ mappings specified in <a href="#soapbinding">Section&nbsp;2.6</a>.</p>
+ 
+ <p>This specification does not mandate a particular form of generated unique
+ identifiers; while the example in <a href="#example">Section&nbsp;3</a> uses
+ the urn:uuid: scheme, this is not required by this specification. Therefore,
+ the RDF mapping of a single WSDL document may differ in these generated
+ identifiers when created by different tools, or even when created by the same
+ tool at different times.</p>
+ 
+ <p>While this RDF mapping does not (and cannot) handle WSDL extensions in
+ general (apart from those predefined by the WSDL 2.0 specifications),
+ implementations of the RDF mapping may support other WSDL extensions and
+ enhance the resulting RDF graph with the appropriate statements. An RDF
+ mapping implementation conforms to this specification if it produces all the
+ statements mandated by the mapping tables herein; it may produce additional
+ statements as well.</p>
+ 
+ 
  <h2 id="ontology">2. WSDL Ontology</h2>
  
***************
*** 357,363 ****
  Adjuncts</a>].</p>
  
- <!-- todo sprinkle the contents of this section with examples and colorful
- figures, and have a full example in section 3? -->
- 
  <h3 id="core">2.1 Core WSDL Components</h3>
  
--- 388,391 ----
Received on Sunday, 20 May 2007 15:41:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 20 May 2007 15:41:10 GMT