(closed) Last Call (20070410) Issues List of SAWSDL

This is the issues list for the 20070410 Last Call Working Draft of the Semantic Annotations for WSDL and XML Schema specification. This list is closed, all issues were resolved and the specification proceeded to Proposed Recommendation.

See also the issues list for SAWSDL issues not pertaining to any LC-or-later publication, the closed last call issues list for the 20060928 Last Call working draft, and the CR issues list for Candidate Recommendation 20070126 issues.

Comments on these issues should be sent to public-ws-semann@w3.org.

Summary of Active Issues
Summary of Resolved but not (yet) Implemented Issues
Summary of Implemented but not (yet) Closed Issues
Detailed Issue List
Table Legend

Summary of Active Issues

ID	Class	Title	Raised By
none

Summary of Resolved but not (yet) Implemented Issues

ID	Class	Title	Raised By
none

Summary of Implemented but not (yet) Closed Issues

ID	Class	Title	Raised By
none

Detailed Issue List

ID	Title	Class	Status	Raised By
1	Propagation of annotation in schema components unclear	Editorial	Closed	Jonathan Marsh
Description: I confess I am not completely sure what this means. The first paragraph appears to be limited to the annotation of the Schema component model, and therefore irrelevant to WSDL-XSLT, which only exposes WSDL components. However, I do wonder whether "defined with" is precise enough. For example, does this include derivation by extension and restriction? Are there any ambiguities when substitution or model groups are used? I find the second paragraph is a bit ambiguous. It says the {model reference} property that corresponds to a top-level simple type (and therefore corresponds to a WSDL Type Definition component), but it says the property is to appear upon a WSDL Element Declaration component. Is this just a typo? Should it instead say WSDL Type Definition component? [email]
Resolution: The intention was to allow propagation of model references and schema mappings from global type definitions to global element and attribute declarations, both in schema and in WSDL (only elements apply to WSDL), this will be clarified in the specification. [meeting minutes] [email to commenter] no disagreement voiced in the following thread

Propagation of annotation in schema components unclear

Editorial

Closed

Jonathan Marsh

Description:

I confess I am not completely sure what this means.

The first paragraph appears to be limited to the annotation of the Schema
component model, and therefore irrelevant to WSDL-XSLT, which only exposes
WSDL components.  However, I do wonder whether "defined with" is precise
enough.  For example, does this include derivation by extension and
restriction?  Are there any ambiguities when substitution or model groups
are used?

I find the second paragraph is a bit ambiguous.  It says the {model
reference} property that corresponds to a top-level simple type (and
therefore corresponds to a WSDL Type Definition component), but it says the
property is to appear upon a WSDL Element Declaration component.  Is this
just a typo?  Should it instead say WSDL Type Definition component?

[email]

Resolution:

The intention was to allow propagation of model references and schema mappings from global type definitions to global element and attribute declarations, both in schema and in WSDL (only elements apply to WSDL), this will be clarified in the specification.

[meeting minutes]

[email to commenter]

no disagreement voiced in the following thread

Table Legend

ID: Issue number
Title: Short title/name of the issue
Class: Design or Editorial
Status: One of: Active, Resolved (not yet implemented), Implemented (not yet responded), Responded, Closed
Raised by: Person who raised the issue
Description: Description of issue, possibly including link to origin of issue
Resolution: Short description of resolution, possibly including link to a more elaborate description

Maintained by Jacek Kopecky
$Date: 2007/08/22 17:03:02 $

Copyright © 2007 W3C^® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.