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 » XSD validator errors
Conferences Close Tree View
+ Stylus Studio Feature Requests (1126)
+ Stylus Studio Technical Forum (13844)
+ Website Feedback (244)
- XSLT Help and Discussion (7447)
-> - TEMP directory question (1)
-> - [HELP] Template and namespace (1)
-> - The prefix "xsl" for element "... (1)
-> - Need help comparing dates in x... (1)
-> - trying to sort a list of artic... (1)
-> + Count unique values using XSLT (3)
-> + Dot "." vs. self::node() (2)
-> + Output from report and XSL do ... (2)
-> + XSL report (2)
-> + cannot see valid values in the... (2)
-> - sum function help (1)
-> + XSLT transformation problem (2)
-> + Flat To nested XML using Keys (3)
-> - XSLT Editor autocomplete funct... (1)
-> - Receiving an argument from a l... (1)
-> + Can't using the Xalan-J in Sty... (2)
-> + Need help testing to see if th... (2)
-> + Any good way to handle repeati... (2)
-> - Renaming child element name wh... (1)
-> + What to do to only how last 4 ... (2)
-> + Help to access an element with... (3)
-> - Multiplication for-each (1)
-> - XSL / X-Path query (1)
-> - Help in creating XSD (1)
-> + JAVASCRIPT Inside XSL (2)
-> + is at possible to create edita... (2)
-> + Grouping on Multiple Field (2)
-> + XSLT 1.0 Grouping Small change... (2)
-> + Revision bar based on the page... (2)
-> + xslt to rtf (2)
-> + XEP/FOP Error (3)
-> + XML to XML Transformation (3)
-> + This XSLT has stumped me.. (2)
-> + converting XML to EACOM format (2)
-> + Stylus with XSLT 1.0 + EXSLT T... (2)
-> + Xslt Mapper (2)
-> - xml to xsl (1)
-> - creating a website (1)
-> - XML to PDF using XML Publisher... (1)
-> - Replace nodes (1)
-> - New to XSLT, need help with a ... (1)
-> - Modify XSLT - Have List of Cha... (1)
-> - Replace nodes in one xml file ... (1)
-> - Alternate Row Colour (1)
-> - convert text to XML and then m... (1)
-> - CDATA to XML - work with trans... (1)
-> - XSL-fo and how to line feed th... (1)
-> + Houston we have a problem (2)
-> + XSL-FO PDF generation (2)
-> + StylusStudio - pick XSLT 1.0 b... (6)
-> - Stylus Studio 2010 debugging f... (1)
-> - Drop down menu List / Option M... (1)
-> - XML transformation using Java ... (1)
-> + i can't to find XSLT editor in... (2)
-> - Copy xml input as value of an ... (1)
-> - Remove Name space from the Tab... (1)
-> - CGI formatted URL with name/va... (1)
-> - Problem with counting (1)
-> + for-each loop is only returnin... (3)
-> - sort date but some dates may b... (1)
-> - Entity Conversion (1)
-> - How can I build an xml convert... (1)
-> + Little Help (2)
-> + how do I merge nodes to one sc... (2)
-> - beginner help xslt and xpath (1)
-> - Convert XML Feed to CSV/SQL/XL... (1)
-> - Working with text node. (1)
-> - No Topic (1)
-> - API for XSLT Converter for .NE... (1)
-> - Getting started (1)
-> + saxon sql extensions - mysql a... (2)
-> - How do I copy and create new e... (1)
-> + substring-before and sums (3)
-> + Parsing special characters in ... (2)
-> + Schema - Require attribute in ... (2)
-> - Edit existing XSL files when n... (1)
-> + How can I use one single XSLT ... (2)
-> - Default selection of value in ... (1)
-> - Problem with watermark in pdf ... (1)
-> + XSLT Parameter Values dialog n... (3)
-> + Value of File Name is not acce... (10)
-> - Need help with a complex table... (1)
-> - How to replace all nordic char... (1)
-> - XSLT java heap space error wit... (1)
-> - Table Overflow to next page (1)
-> - Using XSLT 2.0 to define custo... (1)
-> - "standalone" attribute and xs... (1)
-> + Standardizing IP addresses (2)
-> + Programmatically changing page... (6)
-> + Can Stylus generate XSLT if so... (5)
-> + Extraction based on NODE Name. (2)
-> + NO XSLT:WYSIWYG (2)
-> + determine condition at run tim... (2)
-> - How to reduce top margin in ev... (1)
-> + need help on xsl looping (4)
-> - Convert Symbol to Element (1)
-> + Separator -only- between field... (3)
-> + DocBook (9)
-> + First Occurance of Alphabet (2)
-> + XSL:Key and Document (2)
-- Previous [61-80] [81-100] [101-120] Next
+ XQuery Help and Discussion (1870)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (361)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Simon FrancisSubject: XSD validator errors
Author: Simon Francis
Date: 02 Feb 2006 06:12 PM
I'm using StylusValidator.exe to validate an xml document against a schema.

This document has a couple of attributes from a different name space.

The validator is throwing an error saying that these attributes should be unqaulified however I can't seem to get my schema document to make then unqualified.


XML

<annotation id="ANNTG-FISH!1-ACT-NZL-PUB-Y.1977-28~ANNT.!1" xpb:anchor="id(ACT-NZL-PUB-Y.1977-28~BDY~PT.1~S.3)" xpb:position="below" xmlns:xpb="http://www.brookers.co.nz/namespace/xpb/1.0">



SCHEMA

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xpb="http://www.brookers.co.nz/namespace/xpb/1.0"
elementFormDefault="qualified"
attributeFormDefault="unqualified">


...

<xsd:element name="annotation">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="editorial-note" minOccurs="0"/>
<xsd:element ref="synopsis" minOccurs="0"/>
<xsd:element ref="cross-references" minOccurs="0"/>
<xsd:element ref="commentary" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="id"/>
<xsd:attribute name="anchor" form="unqualified" use="required"/>
<xsd:attribute name="position" form="unqualified" default="below">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="before"/>
<xsd:enumeration value="after"/>
<xsd:enumeration value="below"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>

...


STYLUSVALIDATOR.EXE

file:///c:/vault/common/content/dtd-conversion/updates/sgml/fisheries-law/ANNTG-FISH!1-ACT-NZL-PUB-Y.1977-28.converted.xml:1,362: Attribute 'anchor' should be un-qualified
file:///c:/vault/common/content/dtd-conversion/updates/sgml/fisheries-law/ANNTG-FISH!1-ACT-NZL-PUB-Y.1977-28.converted.xml:1,362: Attribute 'position' should be un-qualified
file:///c:/vault/common/content/dtd-conversion/updates/sgml/fisheries-law/ANNTG-FISH!1-ACT-NZL-PUB-Y.1977-28.converted.xml:1,3211: Attribute 'anchor' should be un-qualified
file:///c:/vault/common/content/dtd-conversion/updates/sgml/fisheries-law/ANNTG-FISH!1-ACT-NZL-PUB-Y.1977-28.converted.xml:1,3211: Attribute 'position' should be un-qualified
file:///c:/vault/common/content/dtd-conversion/updates/sgml/fisheries-law/ANNTG-FISH!1-ACT-NZL-PUB-Y.1977-28.converted.xml:1,4720: Attribute 'anchor' should be un-qualified
file:///c:/vault/common/content/dtd-conversion/updates/sgml/fisheries-law/ANNTG-FISH!1-ACT-NZL-PUB-Y.1977-28.converted.xml:1,4720: Attribute 'position' should be un-qualified
Validation FAILED
Postnext
Tony LavinioSubject: XSD validator errors
Author: Tony Lavinio
Date: 02 Feb 2006 10:56 PM
You've said that anchor and position should be unqualified, which
means in no namespace, and then you've forced them into a namespace
with the xpb: prefix - which means they've been qualified.

Either remove the xpb: prefix, or make them qualified so that they
will belong in the namespace of the schema and the document.
Postnext
Simon FrancisSubject: XSD validator errors
Author: Simon Francis
Date: 06 Feb 2006 04:25 PM
Thanks for the info

I've tried changing the default forms and correcting the anchor and position attribute, form="qualified", however the validator is still producing the following error. What else am I doing wrong here?

file:///c:/vault/common/content/dtd-conversion/updates/sgml/fisheries-law/ANNTG-
FISH!1-ACT-NZL-PUB-Y.1977-28.converted.xml:2,169: Attribute 'anchor' should be un-qualified
file:///c:/vault/common/content/dtd-conversion/updates/sgml/fisheries-law/ANNTG-
FISH!1-ACT-NZL-PUB-Y.1977-28.converted.xml:4,2527: Attribute 'anchor' should be un-qualified
file:///c:/vault/common/content/dtd-conversion/updates/sgml/fisheries-law/ANNTG-
FISH!1-ACT-NZL-PUB-Y.1977-28.converted.xml:6,1159: Attribute 'anchor' should be un-qualified
Validation FAILED


<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xpb="http://www.brookers.co.nz/namespace/xpb/1.0"
elementFormDefault="unqualified"
attributeFormDefault="unqualified">

...
<xsd:attribute name="anchor" form="qualified" use="required"/>
<xsd:attribute name="position" form="qualified" default="below">
...
Postnext
Tony LavinioSubject: XSD validator errors
Author: Tony Lavinio
Date: 07 Feb 2006 09:37 AM
Why do you want the elements unqualified but their attributes
qualified?
The simplest case would be to make the attributes unqualified,
and just drop the xpb: prefix. This is generally the way things
are done.
You can't have the elements come from a schema with no target
namespace and their attributes come from the same schema with
a target namespace.
Postnext
Simon FrancisSubject: XSD validator errors
Author: Simon Francis
Date: 07 Feb 2006 05:14 PM
Unfortunately they're legacy production system attributes which can't be changed.

I beleive that the xpb namespace has been used on this attribute because its not part of the content and its inserted and used by the production system, it isn't output.

Could you please tell me what would I need to change to create a valid schema given that changing the namespaces isn't an option?
Posttop
Minollo I.Subject: XSD validator errors
Author: Minollo I.
Date: 08 Feb 2006 03:56 PM
Simon,
top level definitions always belong to the target namespace declared in the schema. Your schema doesn't seem to define any target namespace, that implies that the <annotation> element and it attributes must live in the default namespace, no matter if marked as qualified or unqualified.

In your case, you either change the schema to define...
<xsd:schema ... targetNamespace="http://www.brookers.co.nz/namespace/xpb/1.0"
xmlns="http://www.brookers.co.nz/namespace/xpb/1.0">

...and then you use:
<xpb:annotation id="ANNTG-FISH!1-ACT-NZL-PUB-Y.1977-28~ANNT.!1"
xpb:anchor="id(ACT-NZL-PUB-Y.1977-28~BDY~PT.1~S.3)" xpb:position="below" xmlns:xpb="http://www.brookers.co.nz/namespace/xpb/1.0">...

...or you define xmlns to be the same namespace as xpb and then use <annotation>

In alternative, if <annotation> and @anchor and @position do need to live in different namespaces, then you need to split the schema in two, one definining items in the xpb namespace:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.brookers.co.nz/namespace/xpb/1.0" xmlns="http://www.brookers.co.nz/namespace/xpb/1.0">
<xsd:attribute name="anchor"/>
<xsd:attribute name="position" default="below">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="before"/>
<xsd:enumeration value="after"/>
<xsd:enumeration value="below"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:schema>

...and one definining items in the default namespace and referencing the first one:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xpb="http://www.brookers.co.nz/namespace/xpb/1.0" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xsd:import schemaLocation="file:///x:/attributes.xsd" namespace="http://www.brookers.co.nz/namespace/xpb/1.0"/>
<xsd:element name="annotation">
<xsd:complexType>
<xsd:attribute name="id"/>
<xsd:attribute use="required" ref="xpb:anchor"/>
<xsd:attribute default="below" ref="xpb:position"/>
</xsd:complexType>
</xsd:element>
</xsd:schema>

Hope this helps,
Minollo
   
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.