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 (1192)
+ Stylus Studio Technical Forum (14621)
+ Website Feedback (249)
- XSLT Help and Discussion (7625)
-> + First time to Stylus Studio 20... (3)
-> + xsl:if test statement result t... (4)
-> + XSLT for dynamic target fields (4)
-> + Remove duplicates (2)
-> + XML-XSL grouping issue while d... (2)
-> + Two XML files. Two Tables. One... (3)
-> + Saxon 9.3 with XSLV (2)
-> - How do I remove the text strin... (1)
-> + Xpath of each element (3)
-> + Attributes - required vs optio... (2)
-> + XML schema to XML schema with ... (2)
-> + how to preserve the & in X... (2)
-> + how to use variables within (2)
-> + need help in XSLT programming (3)
-> + XSLT Mapper Option... Where i... (3)
-> - Selecting element based on att... (1)
-> + replace question (2)
-> - select other node based on one... (1)
-> - XSLT question... (1)
-> - Mapper and XSL (1)
-> - Copying XML as is with one cha... (1)
-> - Help with XSLT (1)
-> - XSL repeat the parent node for... (1)
-> - xls to xml (1)
-> - Stylus support non-backreferen... (1)
-> - Assigning records to existing ... (1)
-> + xsl:for-each and key() (2)
-> + tags containing a: (2)
-> - Create a namespace in output f... (1)
-> - XML Converters problem on UNIX (1)
-> - Copy XML Based on IF Condition... (1)
-> - csv counting dependencies (1)
-> + For extension function, could ... (2)
-> - XML XSLT Transformation (1)
-> + Transform XSD to another XSD (3)
-> - New to Stylus (1)
-> + my enterprise install doesn't ... (2)
-> - Replace line in XML (1)
-> - 5010 HIPAA - Example EDI files... (1)
-> - Display table in two columns f... (1)
-> + java.lang.RuntimeException (4)
-> + Select Value-Of Qualified Elem... (2)
-> + Validating different sets of r... (2)
-> + Passing complete source docume... (2)
-> - XSLT to sort XML per schema (1)
-> - XSL to select the group of row... (1)
-> + first ancestor of a type (2)
-> - Column Width Adjustment (1)
-> + XSLT breakpoint being ignored ... (6)
-> - Creating a tab delimited file (1)
-> - Invalid characters in xml (1)
-> + Creating XSLT File Based on XS... (2)
-> - Unable to filter InputStream f... (1)
-> + finding a list of values (7)
-> - 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)
-- Previous [61-80] [81-100] [101-120] Next
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ 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-2016 All Rights Reserved.