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 » Stylus Studio Technical Forum » Chameleon Schema?
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> - Stylus Studio - Registrar en o... (1)
-> + Stylus Studio - Registrar en o... (2)
-> + Can a pipeline send a file by ... (2)
-> + After Updateing WIN10 to WIN11... (12)
-> + Where do I add the custom java... (3)
-> + Where is the Diagram tab? (5)
-> + Applying XSLT to Word DOCX/XML (2)
-> - CSV conversion via ConvertToXM... (1)
-> + Text symbols in SS not same as... (4)
-> + Exposing xquery as webservice ... (6)
-> + Syntax Identifier (2)
-> + Saving a Converted XML as an X... (5)
-> + Output document cannot be pars... (4)
-> - Archiving output from conversi... (1)
-> + EDIFACT guideline from Stylus ... (3)
-> + CSV file putting all the data ... (5)
-> + Can't install Home version 64b... (5)
-> + presale - Can I covers this sc... (5)
-> + Problem with UNB (5)
-> + Splitting EDIFACT files pipeli... (4)
-- [1-20] [21-40] [41-60] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2016)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Nick LockeSubject: Chameleon Schema?
Author: Nick Locke
Date: 14 Sep 2007 05:45 AM
I have a set of XSDs organised for re-use (ie common types and elements declared once only, and then imports). My users are complaining at having to specify the many different namespaces in the instance documents - I understand their issues.

I have tried elementFormDefault="unqualified" on all of the schemas but then, at least when I use the Document Wizard to generate sample XML, I still get each schema in a separate namespace.

Next stop was to try a Chameleon approach. Now I get errors in the top level schema as soon as I remove targetNamespace:

file:///c:/xxxxx/XML/TypesXXXX-v1-00a.xsd:64,50: Schema Representation Constraint: Namespace 'http://types.XXXXX.org.uk' is referenced without <import> declaration

This seems to be because some of the simple types defined in the schema make reference (in base="XXXX") to a type defined earlier in the same schema document.

I'm not sure why removing targetNamespace breaks that, but the important thing is how to mend it.
Posttop
(Deleted User) Subject: Chameleon Schema?
Author: (Deleted User)
Date: 17 Sep 2007 11:24 AM
Hi Nick,
when you use the targetNamespace attribute in a schema, it means that at least all the global elements (i.e. the ones defined as direct child of the xsd:schema element) will be placed in that namespace; if you use elementFormDefault="qualified", also the locally defined elements will be in that namespace. If you decide that namespace handling has to be avoided, you should remove all the targetNamespace attributes from all the schemas, and change the xsd:import into xsd:include.

Hope this helps,
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-2016 All Rights Reserved.