2002/ws/desc/wsdl20 wsdl20-rdf.html,1.14,1.15

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

Modified Files:
	wsdl20-rdf.html 
Log Message:
editorial tweaks

Index: wsdl20-rdf.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-rdf.html,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -d -r1.14 -r1.15
*** wsdl20-rdf.html	2 Feb 2006 13:21:06 -0000	1.14
--- wsdl20-rdf.html	2 Feb 2006 15:25:57 -0000	1.15
***************
*** 159,163 ****
  <p>Web Services Description Language is defined in XML, because XML is the
  standard format for exchange of structured information. The use of XML brings
! great interoperability in for WSDL generators and parsers, and the use of XML
  Schema makes the structure of WSDL well constrained, yet extensible. On the
  other hand, XML vocabularies in general don't have clear composition rules,
--- 159,163 ----
  <p>Web Services Description Language is defined in XML, because XML is the
  standard format for exchange of structured information. The use of XML brings
! better interoperability to WSDL generators and parsers, and the use of XML
  Schema makes the structure of WSDL well constrained, yet extensible. On the
  other hand, XML vocabularies in general don't have clear composition rules,
***************
*** 172,177 ****
  elements in WSDL service element. Equally, a WSDL description can be combined
  with a policy by adding the WSDL description as part of the policy. While the
! result should be similar (WSDL combined with policy is the same as policy
! combined with WSDL, right?), they are in fact very different for the
  processing software, and a policy in WSDL cannot easily be used by software
  that doesn't know WSDL.</p>
--- 172,176 ----
  elements in WSDL service element. Equally, a WSDL description can be combined
  with a policy by adding the WSDL description as part of the policy. While the
! results should be similar (WSDL with policy information), they are in fact very different for the
  processing software, and a policy in WSDL cannot easily be used by software
  that doesn't know WSDL.</p>
***************
*** 182,193 ****
  whose graph structure together with the use of URIs for identifying nodes
  makes it very easy for different documents to be brought together. If a WSDL
! document describes about a Web service, a policy document attaches
  constraints to the service and a general description specifies the author of
  the service, all this information can be merged and the resulting document
! will contain all the three kinds of information assigned to the single
  service.</p>
  
  <p>The main objective of this specification is to present a standard RDF
! vocabulary equivalent to WSDL 2, so that all WSDL 2 documents can be
  transformed into RDF and merged with other Semantic Web data.</p>
  
--- 181,192 ----
  whose graph structure together with the use of URIs for identifying nodes
  makes it very easy for different documents to be brought together. If a WSDL
! document describes a Web service, a policy document attaches
  constraints to the service and a general description specifies the author of
  the service, all this information can be merged and the resulting document
! will contain all the three kinds of information associated with the single
  service.</p>
  
  <p>The main objective of this specification is to present a standard RDF
! vocabulary equivalent to WSDL 2, so that WSDL 2 documents can be
  transformed into RDF and merged with other Semantic Web data.</p>
  
***************
*** 200,204 ****
  <h3 id="overview">1.1 Organization of this specification</h3>
  
! <p>This specification is split into five main parts &mdash; three sections and two
  appendices:</p>
  
--- 199,203 ----
  <h3 id="overview">1.1 Organization of this specification</h3>
  
! <p>This remainder of this specification is split into two sections and two
  appendices:</p>
  
***************
*** 222,231 ****
  component model defined in <a href="#todo">WSDL2 Core</a>. While the text in
  this section may imply how the components might be mapped to their RDF
! representation, such implications are not intended to be normative; for the
! formal normative mappings, see <a href="#mappingtables">Appendix B</a>.</p>
  
  <p>This section may also briefly touch on some differences between the OWL
  ontology and the component model, but for the full account and
! rationalization of these differences see <a href="#modelingdiffs">section
  3</a>.</p>
  
--- 221,231 ----
  component model defined in <a href="#todo">WSDL2 Core</a>. While the text in
  this section may imply how the components might be mapped to their RDF
! representation, such implications are not intended to be normative, as this
! section aims to be a verbose explanation of the mapping. For the formal
! normative mappings, see <a href="#mappingtables">Appendix B</a>.</p>
  
  <p>This section may also briefly touch on some differences between the OWL
  ontology and the component model, but for the full account and
! rationales of these differences see <a href="#modelingdiffs">section
  3</a>.</p>
  
***************
*** 233,237 ****
  href="#todo">WSDL2 Core</a> are described in <a href="#core">section 2.1</a>.
  All these components are extensible, so <a href="#extensions">section 2.2</a>
! describes how features, properties and extensions are mapped to RDF. The
  following sections, from 2.3 to 2.7, describe the ontological equivalents for
  the various adjuncts specified in <a href="#todo">WSDL2 Adjuncts</a>.</p>
--- 233,237 ----
  href="#todo">WSDL2 Core</a> are described in <a href="#core">section 2.1</a>.
  All these components are extensible, so <a href="#extensions">section 2.2</a>
! describes how extensions are mapped to RDF. The
  following sections, from 2.3 to 2.7, describe the ontological equivalents for
  the various adjuncts specified in <a href="#todo">WSDL2 Adjuncts</a>.</p>
***************
*** 257,261 ****
  subsections. This means that every interface, binding and service described
  by WSDL will be mapped to a single instance in the RDF representation, linked
! from the instance mapped from the top-level description component.</p>
  
  <p>All the components in WSDL can contain documentation. Such documentation
--- 257,261 ----
  subsections. This means that every interface, binding and service described
  by WSDL will be mapped to a single instance in the RDF representation, linked
! from the instance mapped from the top-level Description component.</p>
  
  <p>All the components in WSDL can contain documentation. Such documentation

Received on Thursday, 2 February 2006 15:26:16 UTC