- From: Holger Lausen <holger.lausen@deri.org>
- Date: Mon, 08 May 2006 20:58:02 +0200
- To: SAWSDL WG <public-ws-semann@w3.org>
- Message-ID: <445F94BA.8020107@deri.org>
Hi, When creating a complete file set [1] out of the current po scenario I have detected a mistake in the current xslt examples, respectively in the methodology to extend complex types with schema mappings. (Please correct me if I am wrong since I am relative new to xsd/xslt&Co...) A schema mapping is explained as attribute of a complex type, a typical example (from the appendix) is: <complexType name="POAddress" sawsdl:schemaMapping="http://example.org/examples/POAddress.xq" sawsdl:modelReference="POOntology#Address"> A snippet of the given xslt is: <xsl:template match="/"> <POOntology:Address rdf:ID="Address1"> <POOntology:has_Receiver rdf:datatype="xs:string"> <xsl:value-of select="POAddress/recepientInstName"/> [...] To my understanding the xpath statement in the xslt select statement needs the tag name occurring in the actual xml message. However this tag name is dependent on the xsd element name and not xml complex type name. See [2] for an example how it could work. For me this has two concussions: (1) the schemaMapping attribute should be on the xs:element level (2) the main spec should not (or only in the appendix) include details on the possible mapping languages, since that would get two complex (and distracts from the core). best Holger [1] http://www.w3.org/2002/ws/sawsdl/spec/po/ [2] http://www.w3.org/2002/ws/sawsdl/spec/po/schemamapping-poaddress.xsl -- Holger Lausen Digital Enterprise Research Institute (DERI) http://www.deri.org/ Tel: +43 512 5076464 Email: holger.lausen@deri.org
Received on Monday, 8 May 2006 18:58:26 UTC