Erratum to D16.1v0.2 - The Web Service Modeling Language WSML

13 July 2005

Copyright © 2005 DERI ®, All Rights Reserved. DERI liability, trademark, document use, and software licensing rules apply.

• In the second-last paragraph of Section 2.8, "module" should read "molecule".
• Table 8.1 in Chapter 8 contains the following errors:
  • The first line in the fourth row, second column now reads:
    ?x memberOf X and ?x[attribute_id hasValue ?y] implies ?y memberOf range_idlist.
    It should read: X[attribute_id impliesType range_idlist].
  • The first line in the fifth row, second column now reads:
    !- ?x memberOf X and ?x[attribute_id hasValue ?y] and naf ?y memberOf range_idlist.
    It should read: X [attribute_id ofType range_idlist}.
• Table 9.1 in Chapter 9 contains the following errors:
  • in row 15 of the table, "xsd#anyURI" should be replaced with "wsml#iri"
  • in row 16 of the table, "xsd#string" should be replaced with "wsml#string"
  • in row 17 of the table, "xsd#integer" should be replaced with "wsml#integer"
  • in row 18 of the table, "xsd#decimal" should be replaced with "wsml#decimal"
• In Table 9.1 in Chapter 9 the following bugs were fixed:
  1. the ones mentioned above
  2. the syntax of inverseOf
• In Table 9.2 in Chapter 9 the following bug was fixed:
  1. the syntax for variables in quantified expressions
• In the example at the end of Chapter 9 the following changes were done:
  1. no text in capability of web service- identifier as value of attribute name
  2. no text in interface of web service - identifier as value of attribute name

The above mentioned errors to Chapter 9 are fixed in wsml-xml-trans.html on cvs.deri.at.

• The XML Schema for WSML/XML needs updates (updated schemas available here!)
  1. syntax of WSMLVariable for sharedVariables and quantified expressions
  2. the cardinality of choreography and orchestration from required (1,1) to (0,1)

• The XML Schema for logical expressions has an error on molecules. The choice element allows per default exactly one child element, i.e. minOccurs = maxOccurs = 1 (done in the schema under erratum, as above)
• The XML Schema for logical expressions has an error on logExprType. The choice element allows per default exactly one logical expression element, i.e. minOccurs = maxOccurs = 1 (done in the schema under erratum, as above)

• inconsistencies between inline grammar and bnf, e.g. in ooMediator source (not fixed yet)

$Date: 2005/08/29 17:39:22 $