XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
search
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Home » Boards » Stylus Studio Developer Network » XSLT Help and Discussion » transform XML Schema value or lexical space?
Conferences Close Tree View
+ Stylus Studio Feature Requests (1123)
+ Stylus Studio Technical Forum (13809)
+ Website Feedback (243)
- XSLT Help and Discussion (7447)
-> + Sorting Help Needed (3)
-> + XSLT help with linking (2)
-> + selecting data into node set b... (2)
-> + Watch and Variable in Debug no... (4)
-> + Transforming XML to XML - grou... (2)
-> + Saxon 9.0 B support in debug m... (2)
-> + Repeating element question (2)
-> + Newly Purchased Version Not La... (2)
-> + xsl:include not finding file (5)
-> + JAXP and XSLT 2.0 / XPATH 2.0 (2)
-> + ASP:DropDownList trigger in Xs... (2)
-> + Auto-Skip empty values (2)
-> + retrieving a javascript functi... (2)
-> + need help (2)
-> + html tag ignored (2)
-> + Quick reply needed (8)
-> + xslt to remove namespaces but ... (2)
-> - Using a WSDL definition in an ... (1)
-> + XSL logic issue for simple inp... (6)
-> + Regarding XML namespace prefix... (4)
-> + Mapper reoganizes itself. (8)
-> + XSL Substring Removal (2)
-> + Regarding XSLT logic for a sim... (3)
-> + XSLT Transform documentation (2)
-> + XSLT stack trace in case of er... (3)
-> + No New Line (2)
-> - No New Line (1)
-> + howto loop through a sequence (2)
-> + xml and xsl and whitespace in... (2)
-> + XSL Date formatting (4)
-> + XSL to XSL Mapping using custo... (4)
-> + flat xml to nested xml comvers... (4)
-> + Including schema in scenario (2)
-> + DTDs and traversing (2)
-> + Help with transformation (2)
-> + Problem running XSLT against X... (2)
-> + Carriage return in the output (5)
-> + Generating XSLT to match a sch... (3)
-> + WYSIWYG editor (2)
-> + Grouping without For-Each (3)
-> + output XML using XSLT (8)
-> + Help configuring Xalan-j proce... (8)
-> + Convert Existing HTML pages to... (2)
-> + Generating Transformation - XS... (4)
-> + DOCTYPE public and system info... (2)
-> + Using EXSLT str:tokenize funct... (5)
-> + Where can I get a special char... (3)
-> + XSLT vs XQuery (2)
-> + Using Variables. How to use a ... (4)
-> + XSL incremental count - (5)
-> + thought I was being clever but... (2)
-> - Need help with FO:Table-row (1)
-> + Need help with FO:Table-row (3)
-> + Create mapping based on destin... (5)
-> + Finding a missing parameter (2)
-> + looping an element (5)
-> + Generate an XSLT from an XML f... (2)
-> + Easiest way to split many docu... (7)
-> + how to get xsl:copy-of to appe... (5)
-> + Recursive XSLT Templates (7)
-> + Selecting nodes (help please) (2)
-> + if string = null stop it from... (2)
-> + Display top n items from categ... (3)
-> + Retain input values (2)
-> + XML data import with XSL Style... (4)
-> + Entities with the stylesheet (3)
-> + How can I make a subset Schema... (5)
-> + How to map XML to XML with a m... (2)
-> + displaying specific html when ... (3)
-> + table and cell borders (8)
-> + Grouping Problem (3)
-> + Error while running an XSL wit... (4)
-> + images in XSL Reports. (2)
-> + XSLT Preview on syntax error l... (6)
-> + Mapping Alternatives (2)
-> + how to load image in xsl (2)
-> + XSLT page breaks (2)
-> + Need help on Processing two xm... (7)
-> + Parse text from XML, remember ... (10)
-> + Grouping on lookup values. (3)
-> - How do find get parent group w... (1)
-> + How do find get parent group w... (7)
-> + Problem With XSL-FO page break... (6)
-> + Alternate row color (9)
-> + display a label once and only ... (2)
-> + Date Sequence (8)
-> + XLS:FO line break problem (7)
-> + Problem with prefixes (2)
-> + Copy-of and namespace Hell (2)
-> + Simple custom xslt extension (2)
-> + Brain Teaser (4)
-> + Adding a simple DOCTYPE using ... (4)
-> + html get actual value (3)
-> + WYSIWYG (4)
-> - Need help in tranforming one X... (1)
-> + Problems with for-each and a t... (2)
-> + Element Loop (3)
-> + can anyone implement 'if then ... (2)
-> + stylus xml publisher and xpath (4)
-> + how to print only cdata value/... (4)
-- Previous [661-680] [681-700] [701-720] Next
+ XQuery Help and Discussion (1861)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (361)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Hans-Peter KüchlerSubject: transform XML Schema value or lexical space?
Author: Hans-Peter Küchler
Date: 31 Oct 2001 06:38 AM
Hi,
I'm using XML Schema for defining element types. Should a XSL transformation use the lexical space (as stylus do) or the value space of a XML document for the transformation? Lexical and value space are defined in "XML Schema Part 2: Datatypes". I think it should use the value space for transformation not the lexical space!

Hans-Peter Küchler
Postnext
Alberto MassariSubject: Re: transform XML Schema value or lexical space?
Author: Alberto Massari
Date: 31 Oct 2001 10:30 AM
At 06:46 AM 10/31/2001 -0500, you wrote:
>From: "Hans-Peter Küchler"
>
>Hi,
>I'm using XML Schema for defining element types. Should a XSL
>transformation use the lexical space (as stylus do) or the value space of=
>a XML document for the transformation? Lexical and value space are defined=
>in "XML Schema Part 2: Datatypes". I think it should use the value space
>for transformation not the lexical space!

Stylus simply implements the XSLT 1.0 specs, that don't distinguish between=
value and lexical spaces; being based upon XML 1.0, XSLT has a limited
number of supported datatypes (string, boolean, number, node-set).
So, if you need to test if "100" and "100.0" are two entries in the lexical=
space for the same entry in the value space, you can do it by comparing
number("100") with number("100.0"); but if you want to compare/manipulate
user-defined datatypes, you need to write your own extension functions.

Summarizing, what you need is going to be addressed by XSLT 2.0 (see
http://www.w3.org/TR/xslt20req paragraph 2.3), that is currently in the
Working Draft status.

Alberto
Postnext
Hans-Peter KüchlerSubject: Re: transform XML Schema value or lexical space?
Author: Hans-Peter Küchler
Date: 31 Oct 2001 12:09 PM
Yes, XSLT 2.0 paragraph 2.3 could eventually interpreted this way but there is no explicit distinction between lexical and value space. Only the preface of 2.3 refers to "matching and constructing... based on... typed elements and attributes". The specific MUSTs don't say anything about lexical/value space or canonical lexical representation, they will use the type for ordering, grouping, formatting... And it is not only the named type of an element, also the restrictions (pattern, whiteSpace..) of unnamed types refer to value space.
Hans-Peter Küchler
Posttop
Alberto MassariSubject: Re: transform XML Schema value or lexical space?
Author: Alberto Massari
Date: 31 Oct 2001 12:21 PM
At 12:16 PM 10/31/2001 -0500, you wrote:
>From: "Hans-Peter Küchler"
>
>Yes, XSLT 2.0 paragraph 2.3 could eventually interpreted this way but
>there is no explicit distinction between lexical and value space. Only the=
>preface of 2.3 refers to "matching and constructing... based on... typed
>elements and attributes". The specific MUSTs don't say anything about
>lexical/value space or canonical lexical representation, they will use the=
>type for ordering, grouping, formatting... And it is not only the named
>type of an element, also the restrictions (pattern, whiteSpace..) of
>unnamed types refer to value space.

Keep in mind that this document is just the list of the requirements that
the XSLT 2.0 specs will need to address/include; it's not a detailed
description of how things will work. In my opinion, the reference to
matching and sorting datatypes clearly refers to the need for XSLT 2.0 to
work inside the value space; but we will have to wait for the first draft
to have a definite answer.

Alberto
   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2011 All Rights Reserved.