You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by "John Kaputin (JIRA)" <ji...@apache.org> on 2007/01/12 17:44:27 UTC
[jira] Commented: (WODEN-102) Resolve Errors in W3C Test
SparqlQuerySimplified-1G
[ https://issues.apache.org/jira/browse/WODEN-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464244 ]
John Kaputin commented on WODEN-102:
------------------------------------
The problem is that Woden attempts to filter out the schemas that are *referenceable* by the WSDL 2.0 document (i.e. they are inlined or imported directly within the wsdl:types element) and uses only those schemas to create the ElementDeclarations and TypeDefinitions in the Component model. However, *referenceability* is a document-centric concept that cannot be applied to the Component model because we can't tell in the Component model which documents particular WSDL or Schema components originated from (so we can't really say that an ElementDeclaration or TypeDefinition is referenceable by the WSDL components....we'd have to say by *which* WSDL components).
As per the discussion on the WSDL 2.0 mailing list [1], the correct approach is to extract the global elements and types from ALL schemas accessible within the document model, regardless of whether their namespaces are *referenceable*, and add them to the Component model as ElementDeclarations and TypeDefinitions. ALL schemas include not only those inlined or imported directly within a wsdl:types element but also any schema trees imported by those schemas. And they include the schemas from any wsdl:imported or wsdl:included schemas as well.
If a component model was changed so that a WSDL component referred to an element or type that was not referenceable by it in the underlying infoset, then if the component model is serialized or converted back to the element model, an xs:import of the schema namespace should be added to the relevant description's wsdl:types element to make those schema components referenceable by that document. However, we can leave this functionality until we deal with WSDL updates and editing in general (current focus up to M7 has been on reading/parsing only).
[1] http://lists.w3.org/Archives/Public/www-ws-desc/2007Jan/0078.html
> Resolve Errors in W3C Test SparqlQuerySimplified-1G
> ---------------------------------------------------
>
> Key: WODEN-102
> URL: https://issues.apache.org/jira/browse/WODEN-102
> Project: Woden
> Issue Type: Bug
> Components: Parser
> Affects Versions: M7
> Reporter: Arthur Ryman
> Assigned To: John Kaputin
> Fix For: M7
>
>
> There are 69 errors reported. [1]
> [1] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/results/Woden/SparqlQuerySimplified-1G/sparql-protocol-query.results.xml?content-type=application/xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org