XML Schema-DEV is an open, un-moderated email list about XML Schema-releated development.
XMLSCHEMA-Dev was founded in March, 2000 by Gerald Oskoboiny, and is today hosted by
the World Wide Web consortium (W3C). The XML Schema Development Blog lets you
keep up to date with the latest news and buzz about XML Schema, a core XML technology used with
the most important XML technologies, including XSLT, XQuery and Web Services technologies.
Posted
4/28/2008 9:56:22 PM
I think, this is not possible in the current XSD language.
Though as a workaround, you can consider treating the attributes in
question as elements. Then you can use xs:choice instruction to get
the behaviour you are asking for.
for e.g., as following:
<xs:element name="Menuitem"&g
. . . Read full entry »
Posted
4/28/2008 4:58:14 PM
Manikandan,
In general, the answer is that XSD 1.0 spec doesn't support this type of constraints. However in your specific case (if you only have two attributes), you can enforce it using the following uniqueness constraint:
<xs:element name="Menuitem">
<xs:complexType&g
. . . Read full entry »
Posted
4/28/2008 2:46:19 PM
Manikandan,
In general, the answer is that XSD 1.0 spec doesn't support this type of constraints. However in your specific case (if you only have two attributes), you can enforce it using the following uniqueness constraint:
<xs:element name="Menuitem">
<xs:complexType&g
. . . Read full entry »
Posted
4/28/2008 2:32:54 PM
The short answer to your question is: enforcing the constraint that
occurrence of two attributes be mutually exclusive is not possible in XML
Schema 1.0, which is the current widely deployed version. Doing this will
be straightforward using the planned <assertion> feature of XSD 1.1 [1]
. . . Read full entry »
Posted
4/28/2008 1:01:46 PM
On 28/04/2008, Frank Merrow <fmerrow@qualcomm.com> wrote:
>
> At 12:20 AM 4/26/2008, Michael Kay wrote:
>
> Generally, that's not a good way of designing your XML, which explains why
> there is no w
. . . Read full entry »
Posted
4/28/2008 11:39:00 AM
As Mike and others have told you, the markup you're using is not in a
style that most XML users would consider idiomatic or best practice (I
think that's fair to say.) If you really want to use XSD, and if you know
at any given point in time what the set of legal element names is, it's
possib
. . . Read full entry »
Posted
4/28/2008 11:37:46 AM
Hi All,
Any updates on this question? I am in a kind of urgency and i am new bie
to XML schema.
Any help will be very much appreciated.
Thanks and Regards
Manikandan
________________________________
From: xmlschema-dev-request@w3.org [mailto:xmlschema-
. . . Read full entry »
Posted
4/28/2008 9:29:07 AM
At 06:47 PM 4/27/2008, you wrote:
>One solution to that kind of problem is to define an alternative
>format that can be described using XML Schema, and do your
>validation by transforming to the alternative format and validating
>that. Of course the problem is that any validation err
. . . Read full entry »
Posted
4/28/2008 3:09:09 AM
I doubt you'll find one schema that exercises all the possibilities (it
probably can't be done), but there is an extensive test suite for XML schema
at http://www.w3.org/XML/2004/xml-schema-test-suite/index.html
Unfortunately most of the schema documents are rather trivially small, but
if you ca
. . . Read full entry »
Posted
4/28/2008 2:47:09 AM
One solution to that kind of problem is to define an alternative format that
can be described using XML Schema, and do your validation by transforming to
the alternative format and validating that. Of course the problem is that
any validation error messages are one step removed from the original.
. . . Read full entry »
Posted
4/27/2008 11:23:27 PM
Thank you, Michael. I will look soon into this.
Michael Kay wrote:
> I doubt you'll find one schema that exercises all the possibilities (it
> probably can't be done), but there is an extensive test suite for XML schema
> at http://www.w3.org/XML/2004/xml-schema-test-suite/index.html
&
. . . Read full entry »
Posted
4/27/2008 10:43:05 PM
I am looking for any schema that has a set of all the possible tags and
attrributes with all combination. I need to use this for testing
purposes or an xsl transformation. I know there's a sample for "purchase
order" but that is not even close to perfect. It's missing a lot of tags
(
. . . Read full entry »
Posted
4/27/2008 5:50:13 PM
At 12:20 AM 4/26/2008, Michael Kay wrote:
>Generally, that's not a good way of designing your XML, which
>explains why there is no way of describing your design in XML
>Schema. It's best to use element and attribute names to denote
>types, and element or attribute values to contain i
. . . Read full entry »
Posted
4/27/2008 12:02:54 PM
> ______________________________________________
> From: Manikandan Thangavelu
> Sent: 27 April 2008 21:27
> To: 'xmlschema-dev-request@w3.org'
> Subject: XML schema help for an XML document
>
> Hi All,
>
> I am trying to d
. . . Read full entry »
Posted
4/26/2008 8:20:12 AM
Generally, that's not a good way of designing your XML, which explains why
there is no way of describing your design in XML Schema. It's best to use
element and attribute names to denote types, and element or attribute values
to contain instance data.
Michael Kay
http://www.saxonica.com/
____
. . . Read full entry »
Posted
4/25/2008 9:18:14 PM
Hi Marco,
Marco Faustinelli <marco_faustinelli@yahoo.com> writes:
> - If the XSD of the envelope defines the payload as
> <any namespace="##targetNamespace"> the validator expects to find
> inside elements
. . . Read full entry »
Posted
4/25/2008 1:45:17 PM
So I am writing my first Schema and a little lost.
The heart of the existing file I am trying to write a schema for
looks something like this:
<AI00020000 type='faq'>223</AI00020000>
<AI00020001
type='wiki'>Debugging_Problems_with_APS_Closing_Log_Files</AI00020001>
<A
. . . Read full entry »
Posted
4/24/2008 5:08:08 PM
So I am writing my first Schema and a little lost.
The heart of the existing file I am trying to write a schema for
looks something like this:
<AI00020000 type='faq'>223</AI00020000>
<AI00020001
type='wiki'>Debugging_Problems_with_APS_Closing_Log_Files</AI00020001>
<A
. . . Read full entry »
Posted
4/24/2008 12:39:46 AM
text/html attachment: stored
Received on Thursday, 24 April 2008 17:32:01 GMT
. . . Read full entry »
Posted
4/23/2008 5:38:57 PM
Ramkumar Menon wrote:
> Gurus,
>
> I had a question. Why is it that languages like XML Schema, XSLT etc
> allow only English in the element and attribute names ? I am not
> referring to the content, but the actual elements and attributes
> defined by the grammar.
> i.e.
. . . Read full entry »
Posted
4/23/2008 1:51:10 AM
text/html attachment: stored
Received on Thursday, 24 April 2008 17:31:56 GMT
. . . Read full entry »
Posted
4/22/2008 10:09:33 AM
Thank you everyone for all these ideas. I will look deeper into each
approach and report the results.
Daniel Marcus wrote:
> We have written an open source XSD->relational schema tool that we call XFT. It also generates java classes to support storing instance documents to the database
. . . Read full entry »
Posted
4/19/2008 10:27:01 AM
Ramkumar Menon wrote:
> Gurus,
>
> I had a question. Why is it that languages like XML Schema, XSLT etc
> allow only English in the element and attribute names ? I am not
> referring to the content, but the actual elements and attributes
> defined by the grammar.
> i.e.
. . . Read full entry »
Posted
4/18/2008 11:31:27 PM
This regex is legal according to the spec. However, many implementations of
XML Schema have taken shortcuts by using a regular expression library that
implements a different regex dialect (and XMLSpy is not the top scorer in
the conformance league table). You might find that value="(abc|bcd)?
. . . Read full entry »
Posted
4/18/2008 1:53:33 PM
Hello,
I think I'm making a mistake below--XMLSpy isn't accepting this simpleType.
For the following simpleType, I'm trying to say that widgetType may
have any of the three possible values:
1.) abc
2.) bcd
3.) ( an empty string )
<xs:simpleType name="widgetType">
<xs:res
. . . Read full entry »
Posted
4/18/2008 12:17:37 PM
Gurus,
I had a question. Why is it that languages like XML Schema, XSLT etc allow
only English in the element and attribute names ? I am not referring to the
content, but the actual elements and attributes defined by the grammar.
i.e. <schema>, <template>, <call-template>, <
. . . Read full entry »
Posted
4/16/2008 1:52:07 PM
Michael Kay wrote:
> Remember what UPA stands for: unique particle
> attribution. Every child element can be unambiguously
> associated with exactly one particle in the content
> model. If there are no child elements, this is trivially
> true.
Oh yes, I see my fault: I thought t
. . . Read full entry »
Posted
4/16/2008 1:14:41 PM
Hi
Considering the following schema:
<xs:group name="g1">
<xs:sequence>
<xs:element name="a" type="xs:int" minOccurs="0"/>
<xs:element name="b" type="xs:int" minOccurs="0"
. . . Read full entry »
Posted
4/16/2008 12:24:29 PM
Remember what UPA stands for: unique particle attribution. Every child
element can be unambiguously associated with exactly one particle in the
content model. If there are no child elements, this is trivially true.
Michael Kay
http://www.saxonica.com/
> -----Original Message-----
> From:
. . . Read full entry »
Posted
4/16/2008 11:53:41 AM
On 16 Apr 2008, at 05:52 , Florent Georges wrote:
>
> Michael Kay wrote:
>
>> Remember what UPA stands for: unique particle
>> attribution. Every child element can be unambiguously
>> associated with exactly one particle in the content
>> model. If there are no ch
. . . Read full entry »
Posted
4/8/2008 11:23:28 AM
Thanks Michael,
I was beginning to think that myself.
I've decided to ignore the the fact that the header tag must be first and
add all the children of <letter> to a group using <xsd:all>. The most
important constraint is that the "data" tags can appear only once and in any
. . . Read full entry »
Posted
4/7/2008 4:25:44 PM
Hi,
I'm currently having an issue with defining a schema for some existing XML
(i.e. the XML structure cannot change)
The structure looks like this:
<document>
<letter>
<header>...</header>
<data1>...</data1>
<data2>...</data2>
</letter
. . . Read full entry »
Posted
4/7/2008 10:15:10 AM
Hi David,
David Broker <davidb@warpedweb.net> writes:
> My problem is how to get the "DataBlock" tags to only repeat once.
> The above workds fine execpt that the tags can be repeated. I have
. . . Read full entry »
Posted
4/7/2008 9:30:36 AM
I don't think this can be done in XML Schema 1.0.
When you're trying to write a schema to describe an existing XML document
structure, it's often the case that not all the constraints can be
expressed.
Michael Kay
http://www.saxonica.com/
_____
From: xmlschema-dev-request@w&#
. . . Read full entry »
Posted
4/6/2008 8:51:57 PM
2.2.4.2 Type Alternative
A type-alternative component (type alternative for short) associates a type definition with a predicate. Type alternatives are used in conditional type assignment, in which the choice of ·governing type definition· <https://webmail.planet.nl/exchange/wilde825@plan
. . . Read full entry »
Posted
4/4/2008 9:43:04 PM
The next version of XML Schema will be numbered 1.1. It includes quite a few
new facilities, of which one, "Conditional Type Assignment" seems to
correspond to what you are looking for. Check the specification at
http://www.w3.org/TR/2007/WD-xmlschema11-1-20070830/
especially section
. . . Read full entry »
Posted
4/4/2008 6:35:03 PM
wilde825@planet.nl wrote:
Hi
> Is there anyone who can give me more information about the
> development of newer Schema version like 2.0? I'd need more support
> for checking co-relation (or how they call it) and using validat
. . . Read full entry »
Posted
4/4/2008 5:54:17 PM
>
> Thanks, did that replaced the old errata process ? In that
> case adding links to
> http://www.w3.org/2004/03/xmlschema-errata extracting the
> bugs associated to 1.0 Update would be nice.
The bugzilla database is the place for users (or WG members) to report
errors or is
. . . Read full entry »
Posted
4/4/2008 2:16:50 PM
Hello XML-Schema devvers,
Is there anyone who can give me more information about the development of newer Schema version like 2.0? I'd need more support for checking co-relation (or how they call it) and using validation based on attribute value. If XML Schema isn't being activily developed anymo
. . . Read full entry »
Posted
4/4/2008 2:09:57 PM
The working draft for the next version of XML Schema can be found at [1]
(for the structures draft) and [2] for datatypes. I believe that the
"assertions" mechanism gives the checking of "co-relations" that you seem
to need. I can't speak formally for the group on schedule
. . . Read full entry »
Posted
4/4/2008 11:37:43 AM
Daniel Veillard a écrit :
> For all the XSD-1.0 decimal derived types the lexical representation
> is defined using something like (e.g for byte):
>
> http://www.w3.org/TR/xmlschema-2/#byte
> "byte has a lexical representation consisting of an optional sign followed
>
. . . Read full entry »
Posted
4/4/2008 11:09:21 AM
On Fri, Apr 04, 2008 at 10:26:34AM +0800, Michael Kay wrote:
> I've put this on the WG agenda by means of a bugzilla entry
>
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=5625
>
> which you can track.
Thanks, did that replaced the old errata process ? In that case
adding link
. . . Read full entry »
Posted
4/4/2008 10:26:34 AM
I've put this on the WG agenda by means of a bugzilla entry
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5625
which you can track.
Michael Kay
http://www.saxonica.com/
> -----Original Message-----
> From: xmlschema-dev-request@w3.org
> [mail
. . . Read full entry »
Posted
4/3/2008 6:48:33 PM
> There are ways to specify in XML Schema whether elements
> should appear in a particular order or not (xs:sequence vs
> xs:all). What you are probably saying here is that if the
> schema says that elements can appear in any order, it does
> not mean that the actual order of el
. . . Read full entry »
Posted
4/3/2008 6:29:08 PM
Boris Kolpackov writes:
> There are ways to specify in XML Schema whether elements should appear
> in a particular order or not (xs:sequence vs xs:all).
I'm afraid that's not correct. Specifying "the sequence A, B, C" means
that only the elements A, B and C are allowed, and onl
. . . Read full entry »
Posted
4/3/2008 5:24:30 PM
> I need a database that reflects the structure of the standard schema.
Do you mean a relational database?
I don't think it's easy to automate this conversion. There's nothing in the
XSD for example that says whether the order of elements is significant; you
will need a more complex mapping
. . . Read full entry »
Posted
4/3/2008 1:47:00 PM
For all the XSD-1.0 decimal derived types the lexical representation
is defined using something like (e.g for byte):
http://www.w3.org/TR/xmlschema-2/#byte
"byte has a lexical representation consisting of an optional sign followed
by a finite-length sequence of decimal digits (#x3
. . . Read full entry »
Posted
4/3/2008 12:00:13 PM
Hi Michael,
Michael Kay <mike@saxonica.com> writes:
> There's nothing in the XSD for example that says whether the order
> of elements is significant;
There are ways to specify in XML Schema whether element
. . . Read full entry »
Posted
4/3/2008 11:51:02 AM
Hi,
Mansour Al Akeel <mansour.alakeel@gmail.com> writes:
> Is there a way that I can transform these xml sxhemas to database
> schema and use an orm mapping and/or xml binding to process the
> objects.
One approach would
. . . Read full entry »
Posted
4/3/2008 9:55:21 AM
We have written an open source XSD->relational schema tool that we call XFT. It also generates java classes to support storing instance documents to the database and querying via xpath. It's part of a neuroimaging database package available at http://www.xnat.org. I can't claim that it's comp
. . . Read full entry »
Posted
4/2/2008 1:55:34 PM
I am not sure if this is the correct place to ask for comments or advice
regarding this issue. If not, please advice me.
I need a database that reflects the structure of the standard schema.
There are lots of these well designed schemas at
http://xml.coverpages.org/xmlApplications.html (for ex
. . . Read full entry »
Posted
4/1/2008 11:27:15 AM
Some folks on this list might be interested in the new document of the
XML Schema Patterns for Databinding. Deadline for comments is April 30,
2008.
Philippe
-------- Forwarded Message --------
From: Yves Lafon <ylafon@w3.org>
Subject: "Basic X
. . . Read full entry »
Posted
3/30/2008 11:06:15 AM
Hello list-users,
I am searching for a CALS table model schema to implement it to my
schema in order not to write it by my own. Unfortunately I cannot find a
CALS schema. Doesn´t such a schema exist?
Thanls for helping me,
Andreas
Received on Sunday, 30 March 2008 09:06:48 GMT
. . . Read full entry »
Posted
3/30/2008 11:01:36 AM
It is valid, but it's not particularly useful (and the spec isn't particular
clear about it). The list as a whole must match one of the enumerated
values. If you want to restrict the set of tokens that can appear in the
list, you should define a type T that derives from NMTOKEN, and then define
a l
. . . Read full entry »
Posted
3/30/2008 2:03:40 AM
I came across a schema definition where the attribute type is defined as
<xs:simpleType name="someType">
<xs:restriction base="xs:NMTOKENS">
<!-- bunch of xs:enumeration elements -->
</xs:restriction>
</xs:simpleType>
I am not sure if
. . . Read full entry »
Posted
3/20/2008 9:18:56 AM
It's nice to see that XMLSpy is getting better at reporting errors in your
schema!
The value of schemaLocation is a sequence of pairs of URIs: first the
namespace URI, then the URI of a schema document for that namespace. I don't
know what you intended by supplying a list of three URIs, so I can'
. . . Read full entry »
Posted
3/19/2008 2:26:29 PM
Got your attention? Good :) , Thanks for looking
and thanks also for any assistance y'all can provide.
I use XMLSpy 2006 and my xml documents fail
validation because of the schemaLocation. The xml documents previously passed
validation when I used XMLSpy 2004. So obviously, either something w
. . . Read full entry »
Posted
3/18/2008 2:52:39 PM
On 18/03/2008, Michael Kay <mike@saxonica.com> wrote:
>
> > What's the best way to model "element with text content and
> > attributes"? For example:
> >
> > <foo bar=&qu
. . . Read full entry »
Posted
3/18/2008 12:06:33 PM
> What's the best way to model "element with text content and
> attributes"? For example:
>
> <foo bar="b" baz="b"> only text allowed </foo>
>
> I've used this before, but it seems bulky:
>
> <xs:complexType name="foo
. . . Read full entry »
Posted
3/18/2008 11:19:06 AM
On 18/03/2008, Michael Kay <mike@saxonica.com> wrote:
> If a complex type is empty, then no child elements are allowed. But if the
> mixed=true, then you are still allowed text nodes, comments, and processing
. . . Read full entry »
Posted
3/18/2008 8:56:26 AM
If a complex type is empty, then no child elements are allowed. But if the
mixed=true, then you are still allowed text nodes, comments, and processing
instructions as children; and even if mixed=false, you are still allowed
comments and processing instructions (and empty CDATA sections, I think). S
. . . Read full entry »
Posted
3/18/2008 4:27:48 AM
Hello,
In the case of mixed="true" I don't think that the text is of type xsd:string.
Shlomo.
-----Original Message-----
From: xmlschema-dev-request@w3.org on behalf of Andrew Welch
Sent: Tue 3/18/2008 1:19 PM
To: xmlschema-dev@w
. . . Read full entry »
Posted
3/18/2008 1:57:49 AM
Thank you.
Shlomo
-----Original Message-----
From: Michael Kay [mailto:mike@saxonica.com]
Sent: Tue 3/18/2008 10:56 AM
To: Shlomo Yona; xmlschema-dev@w3.org
Subject: RE: Empty c
. . . Read full entry »
Posted
3/18/2008 1:13:44 AM
Hello,
I have the following example test based on XML schema w3c test suite:
Instance:
<?xml version="1.0"?>
<root>test</root>
Schema:
<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:comp
. . . Read full entry »
Posted
3/14/2008 10:20:23 PM
Michael Kay writes:
> For some strange reason which I've never understood, local element
> declarations (i.e. <element name="x"/> within a complex type) default to
> being in no namespace, rather than defaulting to the target
> namespace of the
> schema.
How to tr
. . . Read full entry »
Posted
3/14/2008 9:27:25 PM
The easiest fix to this is to include elementFormDefault="qualified" in your
xs:schema attribute list. e.g.:
<xs:schema
elementFormDefault="qualified"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.foo.com"
xmln
. . . Read full entry »
Posted
3/14/2008 9:05:12 PM
For some strange reason which I've never understood, local element
declarations (i.e. <element name="x"/> within a complex type) default to
being in no namespace, rather than defaulting to the target namespace of the
schema. Most people change this default by adding
elementFormDe
. . . Read full entry »
Posted
3/14/2008 7:22:23 PM
> I need to use a targetNamespace (or is it an xmlns?) in my
> schema so that I can validate other files without having to
> add noNamespaceSchemaLocation to those files. Can someone
> help me understand the core issue here, and (especially) how
> to modify the file to accomplis
. . . Read full entry »
Posted
3/14/2008 1:34:50 PM
On Friday, March 14, 2008, at 12:24PM, "Michael Kay" <mike@saxonica.com> wrote:
>> I need to use a targetNamespace (or is it an xmlns?) in my
>> schema so that I can validate other files witho
. . . Read full entry »
Posted
3/14/2008 12:02:24 PM
The appended test case shows a simple schema that fails to validate (using oXygen/Xerces) when the targetNamespace is declared for the file. If I remove the targetNamespace, the file validates and works just fine.
I see that there are 'suggestions' on how to fix this, but I don't know exactly wha
. . . Read full entry »
Posted
3/14/2008 11:45:51 AM
On Friday, March 14, 2008, at 01:15AM, "Michael Kay" <mike@saxonica.com> wrote:
>Yes, you can do this. You just use
><xs:attribute ref="foo:msg"/>
>or
><xs:element ref="
. . . Read full entry »
Posted
3/14/2008 10:03:07 AM
Hi Gavin,
You need to define three schema files (one for each namespace and the main
one that is not associated with any namespace). Then in, for example, the
no-namespace schema, do:
<xs:element ref="bar:charlie"/>
or:
<xs:attribute ref="foo:msg"/>
. . . Read full entry »
Posted
3/13/2008 8:01:55 PM
How can I write a schema that requires an XML file to have a structure
like the following?
<root xmlns:foo="http://foo.com" xmlns:bar="http://bar.com">
<alpha>This is in the default namespace</alpha>
<bravo foo:msg="This namespaced attr
. . . Read full entry »
Posted
3/12/2008 9:00:22 AM
At 2008-03-11 13:30 -0400, I wrote:
>Note that the OASIS Code List Representation Technical Committee is
>offering a layered technique to extended and restricted code lists,
>complete with list-level, code-level and instance-level meta data
>specification and matching:
>
> g
. . . Read full entry »
Posted
3/12/2008 12:15:02 AM
>
> I spent the whole day with tinking and trying and now my head
> is totally empty. I have the following complexType which
> describes a listType for unordered and ordered lists:
It actually consists of a type which allows 1 to many unorderedlist elements
followed by 1 to many or
. . . Read full entry »
Posted
3/11/2008 9:30:37 PM
Hello schema-experts,
I spent the whole day with tinking and trying and now my head is totally
empty. I have the following complexType which describes a listType for
unordered and ordered lists:
<xs:complexType name="listType">
<xs:sequence>
<xs
. . . Read full entry »
Posted
3/11/2008 1:30:34 PM
Note that the OASIS Code List Representation Technical Committee is
offering a layered technique to extended and restricted code lists,
complete with list-level, code-level and instance-level meta data
specification and matching:
genericode 1.0 - lists of codes with list-level and code-leve
. . . Read full entry »
Posted
3/11/2008 10:11:08 AM
I know techniques for extensible enumerations in W3C XML Schema 1.0 have
been discussed on this list before (extensively), but I didn't find the
exact technique below, so I thought I'd post it here to get
feedback/comment.
Enumeration types (say, Enumerated_Type) are defined as xs:union betwee
. . . Read full entry »
Posted
3/11/2008 9:04:25 AM
In Schema 1.0 it's only possible if the two elements have different types,
and that's only possible if they appear in different contexts.
In Schema 1.1 this is easily done using conditional type assignment.
Michael Kay
http://www.saxonica.com/
_____
From: xmlschema-dev-request@
. . . Read full entry »
Posted
3/11/2008 8:58:16 AM
Creating xml instances may seem tedious to some. This is why I wanted to
add the ability to include numerous xml instances as a representative. It's
certainly on my wish list.
I like your ideas on the requirements of enums and min/maxOccurs. I'll put
this on my wish list as well.
Paul
. . . Read full entry »
Posted
3/10/2008 5:21:08 PM
> A full FAQ is available at http://www.xmlhelpline.com/tools (including a
section on how this relates to Schematron and other solutions). This is an
initial 1.0 release. I would love to continue to improve it if people find
it useful.
Other requirements for subsetting that I have often
. . . Read full entry »
Posted
3/10/2008 4:42:56 PM
Hi all,
I'm trying to figure if it's possible to have essentially several valid
attribute groups per element. For instance, if I have two types of
symbols,
<symbol type="a" a="val" b="val" c=123 />
<symbol type="b" x="val" y="
. . . Read full entry »
Posted
3/10/2008 1:07:23 PM
Greetings,
Have you ever had an Xml Schema that came from somewhere else (e.g. a
trading partner or a standards consortium) and wanted to reduce the bulk of
all the elements, attributes and types that you don't plan on implementing?
Perhaps you want to communicate a simpler version of the data
. . . Read full entry »
Posted
3/10/2008 9:48:02 AM
>
> I'm using the validator
> (http://www.w3.org/2001/03/webdata/xsv), and it's working
> great except for one thing. To illustrate, I've written a
> valid sample schema which, when uploaded, returns an error.
You might find Saxon's error message more helpful:
Error at xsd:al
. . . Read full entry »
Posted
3/10/2008 8:25:25 AM
Hi Chris,
Chris <jesdisciple@gmail.com> writes:
> <xsd:all>
> <xsd:element name="example" maxOccurs="2"/>
> </xsd:all>
The validator you are using is correct: elements within the 'a
. . . Read full entry »
Posted
3/9/2008 11:35:00 PM
Hello schema-users,
I have as I hope a very simple problem. Unfortunately not for me:
This is my complexType:
<xs:complexType name="chapterType">
<xs:sequence>
<xs:element name="title"/>
<xs:choice>
. . . Read full entry »
Posted
3/9/2008 6:52:14 PM
At 2008-03-09 23:35 +0100, Andreas Peter wrote:
>This is my complexType:
>
> <xs:complexType name="chapterType">
> <xs:sequence>
> <xs:element name="title"/>
> <xs:choice>
> <
. . . Read full entry »
Posted
3/9/2008 6:07:12 PM
Hello!
I'm using the validator (http://www.w3.org/2001/03/webdata/xsv), and it's
working great except for one thing. To illustrate, I've written a valid
sample schema which, when uploaded, returns an error. The source and
error follow.
<?xml version="1.0" encoding="iso-
. . . Read full entry »
Posted
3/7/2008 3:05:38 PM
Dear xml users,
*Thank you to report our news inside the schema tools page :
http://www.w3.org/XML/Schema#Tools
"EditiX XML Editor 2008 includes a visual schema W3C editor".
*
We are glad to announce the availability of EditiX XML Editor 2008 - Service
Pack 1 :
Download it at : http://w
. . . Read full entry »
Posted
2/29/2008 10:20:11 PM
Thanks David,
I mixed up xs:enumeration an xs:pattern :-(
Andreas
Quoting dmaze@us.ibm.com:
> Andreas Peter <info@minimag.de> wrote on 02/29/2008 04:00:34
. . . Read full entry »
Posted
2/29/2008 10:00:34 PM
Hello list users,
I have the following complexType:
<xs:complexType name="speccharType">
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="greek">
<xs:simpleType>
. . . Read full entry »
Posted
2/29/2008 4:14:23 PM
Andreas Peter <info@minimag.de> wrote on 02/29/2008 04:00:34 PM:
> <xs:element name="greek">
> <xs:simpleType>
> <xs:restriction base="xs
. . . Read full entry »
Posted
2/28/2008 5:12:45 PM
On 28/02/2008, Ben Liblit <liblit@cs.wisc.edu> wrote:
>
> > No, and a good thing too. Using defaults in the DTD to put elements in a
> > namespace that isn't visible to the casual reader of the XML instan
. . . Read full entry »
Posted
2/28/2008 11:01:34 AM
> No, and a good thing too. Using defaults in the DTD to put elements in a
> namespace that isn't visible to the casual reader of the XML instance is a
> source of immense frustration to people trying to process the XML,
OK, fair enough. The DTD namespace trick always seemed a bit fishy
. . . Read full entry »
Posted
2/28/2008 8:34:37 AM
> I've been able to do this
> in the past using DTDs by giving every HTML element a fixed
> xmlns="http://www.w3.org/1999/xhtml" attribute. This can be
> done easily by redefining an appropriate DTD element which
> modular XHTML offers as an extension point.
>
>
. . . Read full entry »
Posted
2/27/2008 8:58:48 PM
Hello Michael,
thanks for the reply. This is what I thought. So I have to define
elements with facets for each special character. Lot of work for me :-(
Thanks so far,
Andreas
Quoting Michael Kay <mike@saxonica.com
. . . Read full entry »
Posted
2/27/2008 7:31:45 PM
Hello Ken,
I have come to realize that it is always you who answers my silly
questions :-)
Okay, I understand. So I have to explain a liite more: I am writing a
schema for Word 2007 templates which should be validated against a
schema. My structure is clear so far. But the author should onl
. . . Read full entry »
Posted
2/27/2008 6:45:23 PM
> I have come to realize that it is always you who answers my
> silly questions :-) Okay, I understand. So I have to explain
> a liite more: I am writing a schema for Word 2007 templates
> which should be validated against a schema. My structure is
> clear so far. But the author
. . . Read full entry »
Posted
2/27/2008 4:38:28 PM
I am trying to formalize a family of documents which use a local, custom
structure at and near the document root, but which eventually use XHTML
block elements further down. For example:
<my:root
xmlns:my="http://example.com/my"
xmlns:html="http://www.w3.org/1999/xhtml
. . . Read full entry »
Posted
2/26/2008 8:35:57 PM
Hello list-users,
my problem is that I have a DTD including lots of entities for greek
characters, special characters and so on. I need them in my schema.
I´ve read that every entity must be written under schema as a separate
element. Is it possible, although DTDs are not xml syntax, to
r
. . . Read full entry »
Posted
2/26/2008 2:48:48 PM
At 2008-02-26 20:35 +0100, Andreas Peter wrote:
>my problem is that I have a DTD including lots of entities for greek
>characters, special characters and so on.
Those are used for resolving the text content of
the references made in your XML document.
>I need them in my schema.
A sche
. . . Read full entry »
Posted
2/19/2008 8:15:51 AM
The proposal is still on the table, I have no idea whether it's likely to
make it into Schema 1.1.
As far as Saxon is concerned, I'm trying to concentrate my attention on
implementing features as they are approved, and at present I'm resisting the
tendency to do extensions.
Michael Kay
>
. . . Read full entry »
Posted
2/18/2008 3:11:21 PM
Hello,
I have a need for overriding type definitions in one schema file by
other type definitions in another file. Not merely extending or
restricting, but actually replacing. For instance, I want to override a
type defined as a simpleType as a complexType.
I found several posts on this list me
. . . Read full entry »
Posted
2/18/2008 11:57:14 AM
Hi Noah,
On 15/02/2008, noah_mendelsohn@us.ibm.com <noah_mendelsohn@us.ibm.com> wrote:
> I think the point is that XML Schema has a uniform way of reflecting
. . . Read full entry »
Posted
2/17/2008 7:20:03 PM
Hello Pete,
that was exactly the solution for my problem.
Thanks so much,
Andreas
Pete Cordell schrieb:
>
> I'm not entirely sure I understand what you want, but you have
> probably forgotten that the patterns defined in XML schemas must match
> the entire thing they're matching,
. . . Read full entry »
Posted
2/17/2008 11:50:38 AM
Hello xmlschema-developers,
I am trying to right a schema for an unordered list where the first
character must be a dot, wave dash or simple a dash. But something is
not working :-(
This is my idea:
<xs:element name="lists">
<xs:complexType>
<xs:choice>
<xs:elem
. . . Read full entry »
Posted
2/17/2008 11:13:55 AM
I'm not entirely sure I understand what you want, but you have probably
forgotten that the patterns defined in XML schemas must match the entire
thing they're matching, not just fragments of it. Therefore, your patterns
need to be something like:
<xs:pattern value="~.*"/>
<
. . . Read full entry »
Posted
2/15/2008 5:53:08 PM
Dear xml users,
We are glad to announce the availability of EditiX 2008. EditiX is a
cross-platform (Windows, Mac OS X and Unix/Linux) and easy to use XML Editor
and XSLT Debugger designed to help web authors and application programmers
take advantage of the latest XML and XML-related technologie
. . . Read full entry »
Posted
2/15/2008 2:27:50 PM
I think the point is that XML Schema has a uniform way of reflecting
validation results, and the proposed xs:assertion mechanism uses that in a
consistent manner. Note that in many cases XSD validators are embedded in
other programs. Sometimes having a textual error message as in schematron
. . . Read full entry »
Posted
2/14/2008 6:21:52 PM
An xs:assert does seem to allow an xs:annotation. Does that help? I guess
it might help the developer, but you'd have to make assumptions about the
contents of the text before you displayed it to a regular user.
And if you're going to display messages embedded in the XML schema to a
user, wh
. . . Read full entry »
Posted
2/14/2008 5:44:19 PM
On 14/02/2008, Michael Kay <mike@saxonica.com> wrote:
> Given that XML Schema doesn't provide any facilities for customising error
> messages anywhere else (e.g. for failures to match the grammar of a complex
. . . Read full entry »
Posted
2/14/2008 5:10:15 PM
Given that XML Schema doesn't provide any facilities for customising error
messages anywhere else (e.g. for failures to match the grammar of a complex
type, failure to match a regular expression, key/keyref failures, etc) do
you think there is a good case to treat assertions differently? Or is it
. . . Read full entry »
Posted
2/14/2008 4:46:35 PM
What is the intended way to provide feedback when an assertion fails?
Given:
<xs:assert test="@min le @max"/>
How would you say "The min attribute must be less than or equal to the
max attribute" when the test fails?
I hope it's not:
<xs:assert test="
. . . Read full entry »
Posted
2/11/2008 9:35:38 PM
I think the problem here has very little to do with the key/keyref, and much
more to do with namespaces.
Unusually, you have not specified elementFormDefault="qualified" in your
first schema. This means that the locally-declared elements Subset1,
Subset2, and Element1 are in no namespac
. . . Read full entry »
Posted
2/11/2008 7:11:30 PM
[Newbie posting; I apologise in advance for any poor etiquette]
Before looking at the multi-file scenario, below is a sample XML Schema
describing the nested element structure. The key aspects of the schema
are:
- The "Superset" root element contains 2 "Subsets".
- The Subse
. . . Read full entry »
Posted
2/11/2008 4:05:00 PM
Sorry I'm late to this thread, finally got a moment to breathe.
This thread seems to lead toward what I have found to be the case with my
clients. Namely that the "ideal" is to use UML for a conceptual (and
business friendly) view of a canonical model. And XSD is the "ideal"
. . . Read full entry »
Posted
2/7/2008 3:27:23 PM
Hi,
I am pleased to announce the availability of CodeSynthesis XSD 3.1.0.
CodeSynthesis XSD is an open-source (GPL2 + proprietary license), cross-
platform W3C XML Schema to C++ data binding compiler. Provided with a
schema, it generates C++ classes that represent the given vocabulary as
well as
. . . Read full entry »
Posted
2/7/2008 1:49:27 PM
I'm 99% sure that it's intended to be legal. Schema Part 2 states the
intention clearly:
4.3.5 enumeration
[Definition:] enumeration constrains the
<http://www.w3.org/TR/xmlschema-2/#dt-value-space> .value space. to a
specified set of values.
There is however a minor bug in the spec; i
. . . Read full entry »
Posted
2/7/2008 10:22:11 AM
Original Message From: "dave"
> I would like to restrict the validation only to part
> of my XML schema. I do not want to validate anything
> under certain Element, say 'noValidation'. This
> element in turn contains an XML(which is WellFormed
> but not Valid) for which t
. . . Read full entry »
Posted
2/7/2008 9:45:26 AM
I'm not sure why you're asking on an XML Schema list.
I can't comment on XmlBeans, but you could do this either in XSLT or XQuery.
In my view XSLT works better than XQuery for this kind of transformation,
because of its built-in mechanism for doing a recursive descent of the tree,
applying rule
. . . Read full entry »
Posted
2/7/2008 1:09:41 AM
Hi,
When defining an enumeration-facet on a list, should we consider the
lexical-space or value-space of the value?
Is the following example legal?
Instance:
<root MyAtt="1.0 2.0"/>
Schema:
<?xml version="1.0" ?>
<xsd:schema xmlns:xsd="http
. . . Read full entry »
Posted
2/6/2008 7:56:31 PM
Am already using XmlBeans. I would need to see how I
can integrate VTD-XML with XMLBeans.
I agree with you that VTD-XML is an ideal match for
what I want to accomplish. I would still prefer if
XmlBeans offers anything on this line.
Thanks Jimmy.
dave
--- jimmy Zhang <jzhang@x�
. . . Read full entry »
Posted
2/6/2008 7:39:56 PM
For a given XML input, I would need to perform 'Search
and Replace' operation on Element/Attribute Tag names
and values. The resultant output is a transformed XML.
Since I would like to change both Tags and Values,
what is the best way to accomplish this? XSLT or
Xpath/XQuery or combination of bo
. . . Read full entry »
Posted
2/6/2008 3:59:29 PM
I would like to restrict the validation only to part
of my XML schema. I do not want to validate anything
under certain Element, say 'noValidation'. This
element in turn contains an XML(which is WellFormed
but not Valid) for which there is no schema for
whatever reason. But I would want to parse
. . . Read full entry »
Posted
2/4/2008 8:59:46 PM
The scenario described below seems to be quite REAL in large
organizations, where the Central Team is more interested in developing a
"common data model" reflecting the overall business of the enterprise,
but the Distributed Teams are more interested in developing the
"localized XML
. . . Read full entry »
Posted
2/3/2008 12:56:34 PM
> Another issue is that, if the same file is included multiple
> times via multiple paths (e.g. A includes B which includes C,
> and A also includes D which includes C), depending on the
> relative paths, the Schema validator won't always realise
> that "C" is the same
. . . Read full entry »
Posted
2/3/2008 12:22:15 PM
Hello List,
I am relatively new to XMLSchema. I am going to write a custom schema
for Word 2003/2007.
Currently I am working at the title hierarchy. My aim is to have a
schema which shows when a structural problem inside the document occurs.
This is what I want to realise:
Element titles can c
. . . Read full entry »
Posted
2/3/2008 12:06:59 PM
On Fri, 01 Feb 2008 18:28:46 -0000, Jack Lindsey <tuquenukem@hotmail.com>
wrote:
> I now need to define an approach to XML reuse in an organization that is
> typically the 800-pound gorilla in the room, rather
. . . Read full entry »
Posted
2/1/2008 1:28:46 PM
My experience strongly endorses Tony's themes here, but I resist the urge to indulge in war stories. This last post squarely addresses my current pre-occupation. So a couple of observations and questions.
Implementing in XSD should not impact your approach to modelling if you already have one.
. . . Read full entry »
Posted
1/31/2008 11:13:11 AM
I personally wouldn't prefer to use W3C XML Schemas directly when creating
a large set of Schemas which share type definitions. A couple of years
ago, I used IONA Artix Data Services (formerly C24 Integration Objects) to
create a type repository from which we designed and generated over 450
. . . Read full entry »
Posted
1/31/2008 12:02:24 AM
Designing in XML (e.g. W3C XML Schema) is an attractive option when you
(and/or your group) are only responsible for the messages that are sent
between systems. On the other hand, I know a number of large
organisations that are busy developing enterprise data models, at a level
above XML
. . . Read full entry »
Posted
1/30/2008 11:40:40 PM
On Wed, 30 Jan 2008 22:12:40 -0000, Michael Kay <mike@saxonica.com> wrote:
>> Nomenclature is a funny old thing. I would argue that you
>> don't access data via a logical model, you access it via a
>
. . . Read full entry »
Posted
1/30/2008 10:12:40 PM
> Nomenclature is a funny old thing. I would argue that you
> don't access data via a logical model, you access it via a
> physical model.
I'm afraid I was brought up on the notion that the logical model is what
programmers can see, the physical model is what's hidden from their sig
. . . Read full entry »
Posted
1/30/2008 9:07:28 PM
The main argument against using XSD for modelling is that it forces you to
make decisions which you don't really want to make at the modelling stage -
decisions about elements versus attributes, decisions about partitioning the
design into namespaces, decisions about whether A should restrict B or
. . . Read full entry »
Posted
1/30/2008 5:42:06 PM
Count me in as one of those "large organizations!" Is it ever
achievable? Any successful stories?
Given that as a goal (and constraint), will XSD still be a good (or
best) choice for message design?
Thanks,
Scott Tsao
Associate Technical Fellow
The Boeing Company
-----Origi
. . . Read full entry »
Posted
1/30/2008 5:33:20 PM
Thanks for pointing out those two bad practices of message design using
XML!
I would be very interested in some examples (if readily available), as
well as some general guidelines (good practices) in message design
(based on a common data model).
Please contact me directly if you prefer.
Tha
. . . Read full entry »
Posted
1/30/2008 5:28:18 PM
Michael Kay wrote:
> I'm afraid I was brought up on the notion that the logical model is what
> programmers can see, the physical model is what's hidden from their sight. I
> think that usage is very common in the database world. Of course, with XML,
> very little is hidden - until you
. . . Read full entry »
Posted
1/30/2008 3:10:53 PM
I was actually trying to focus my attention on the choice of XSD based
on this observation:
*
XML is a better approach for design and implementation at the
data interchange level, e.g., specifying the interface 'protocol'
between two systems (or applications). For example, in the SOA world,
XML
. . . Read full entry »
Posted
1/30/2008 1:15:50 PM
Michael Kay wrote:
>Scott Tsao wrote:
>> If these observations are correct, my next question would be: Is the
W3C XML Schema
>> the best choice on the market today for data modeling in the XML
world? (why or why not)
>
>I think there are two difficulties in using XML Schema
. . . Read full entry »
Posted
1/30/2008 11:46:56 AM
David,
I thought that it is about time that you might chime in :-)
I am not sure the REAL reasons why "XML Schema [XSD] is a definition
language, not a modeling language." It seems to me that a modeling
'language' (e.g., UML) provides a set of agreed-upon 'artifacts' for
human beings
. . . Read full entry »
Posted
1/30/2008 10:43:28 AM
> In fact, if you are just talking messages, there may be no
> defined 'application' data model at all (at least not an XML
> based one). Protocols such as VoIP and HTTP are generally
> defined mainly in terms of the messages that flow between nodes.
Sure (though VoIP and HTTP are
. . . Read full entry »
Posted
1/30/2008 9:59:14 AM
Original Message From "Michael Kay"...
>> If these observations are correct, my next question would be: Is the W3C
>> XML Schema the best choice on the market today for data modeling in the
>> XML
>> world? (why or why not)
>
> I think there are two diffi
. . . Read full entry »
Posted
1/30/2008 9:47:59 AM
Original Message From: "Tsao, Scott":
> If these observations are correct, my next question would be: Is the W3C
> XML Schema the best choice on the market today for data modeling in the
> XML world? (why or why not)
Given the caveat "on the market today", I think i
. . . Read full entry »
Posted
1/30/2008 9:17:19 AM
> If these observations are correct, my next question would be: Is the W3C
XML Schema the best choice on the market today for data modeling in the XML
world? (why or why not)
I think there are two difficulties in using XML Schema for modelling.
One is syntax - a model, by definition, capt
. . . Read full entry »
Posted
1/30/2008 9:06:28 AM
On Wed, 30 Jan 2008 04:33:28 -0000, Tsao, Scott <scott.tsao@boeing.com>
wrote:
> If these observations are correct, my next question would be: Is the W3C
> XML Schema the best choice on the market today for data modeli
. . . Read full entry »
Posted
1/30/2008 8:49:45 AM
On Tue, 29 Jan 2008 16:39:01 -0000, Bob Schloss <rschloss@us.ibm.com>
wrote:
> To ground this in some of the work my colleagues and I are doing at IBM
> Research, we have developed strategies so that XPath addressing c
. . . Read full entry »
Posted
1/29/2008 9:08:31 PM
Hi Mike. I clearly wasn't clear enough. I wasn't suggesting that
abstractions are forcibly technically-oriented. However, I was suggesting
that people with a technical mindset tend to create models with more
abstractions (i.e. data normalised into common superclasses) than do
people wit
. . . Read full entry »
Posted
1/29/2008 8:33:28 PM
First of all, I would like to thank those enthusiastic people who
quickly responded to my original inquiry.
I am taking the liberty to except from your replies the most useful
comments that seem to help me better understand the issues involved:
*
"These three concepts have been addresse
. . . Read full entry »
Posted
1/29/2008 3:58:00 PM
> So, what I should have said is that introducing "Person" as
> the common superclass of "Employer" and "Employee" is
> something you would normally do in the logical model, but you
> would only do that in the conceptual model if the business
> expe
. . . Read full entry »
Posted
1/29/2008 12:27:45 PM
On Tue, 29 Jan 2008 11:59:00 -0000, Michael Kay <mike@saxonica.com> wrote:
>> However, you
>> wouldn't normally expect to factor out "Person" as the common
>> superclass; that's the kind
. . . Read full entry »
Posted
1/29/2008 11:59:00 AM
Some interesting points here.
> An XML schema is a physical data model. It is physical
> because it includes significant amounts of information
> specific to a particular physical representation of the data,
> e.g. you have to worry about elements versus attributes in an
> XML
. . . Read full entry »
Posted
1/29/2008 11:39:01 AM
I haven't found it practical to draw rigid distinctions between logical
and physical models. In general, if low-cost hardware could provide all
the excellent response time, security etc. that we'd need without any
optimization of physical storage or physical transmission, the physical
model wo
. . . Read full entry »
Posted
1/29/2008 10:28:01 AM
An XML schema is a physical data model. It is physical because it
includes significant amounts of information specific to a particular
physical representation of the data, e.g. you have to worry about elements
versus attributes in an XML schema. By contrast, the equivalent UML
logical da
. . . Read full entry »
Posted
1/29/2008 10:13:48 AM
ST> I recently read an article A Few Thoughts on Data Modeling and Kids'
Soccer - An Interview with William G. Smith
<http://www.wilshireconferences.com/interviews/smith.htm> . In this article
Mr. Smith advocates a 3-schema architecture for data modeling, i.e.,
Conceptual, Logical, and P
. . . Read full entry »
Posted
1/29/2008 9:32:27 AM
Dear Scott,
This is an interesting point.
I understand that the 3-level of abstractions for modeling data, Conceptual,
Logical, and Physical are difference as follow:
Conceptual: the model at this level is platform-independent and also could
be logically modeled using any modeling technique, ERD,
. . . Read full entry »
Posted
1/28/2008 11:13:06 PM
Dear all!
I'm currently support for XSV into the next release of ValidatorBuddy
(http://www.spycomponents.com/ValidatorBuddy.htm) and started to do some
tests. Actually the integration uses the xsv.exe which comes with the
Windows installer (ValidatorBuddy also runs only on Windows).
I have a
. . . Read full entry »
Posted
1/28/2008 8:20:11 PM
I recently read an article A Few Thoughts on Data Modeling and Kids'
Soccer - An Interview with William G. Smith
<http://www.wilshireconferences.com/interviews/smith.htm> . In this
article Mr. Smith advocates a 3-schema architecture for data modeling,
i.e., Conceptual, Logical, and Physical
. . . Read full entry »
Posted
1/23/2008 1:29:22 PM
hello,
in our xml documents we use <Attachment> tag to specify, well,
attachments to these documents. something like:
<Doc>
<Title>xyz</Title>
....
<Attachment type="logo" format="url">http://some.url/logo.jpg</Attachment>
<Attachment ty
. . . Read full entry »
Posted
1/23/2008 10:23:08 AM
Hi,
Please let me know the case, i am giving the example here,
EX:
<staticroutes>
<ip ip="route1">
<via>192.168.55.1</via>
<via>192.168.55.1</via>
<mtu>5000</mtu>
<metric>5</metric>
. . . Read full entry »
Posted
1/23/2008 9:24:45 AM
I don't think this can be done without assertions, which is a new feature in
XSDL 1.1.
Michael Kay
http://www.saxonica.com/
> -----Original Message-----
> From: xmlschema-dev-request@w3.org
> [mailto:xmlschema-dev-request@w3&
. . . Read full entry »
Posted
1/23/2008 9:23:28 AM
This is the classic use case for "conditional type assignment" which is a
feature in XSDL 1.1.
With version 1.0, the only way to achieve it is by naming the attribute
xsi:type.
Michael Kay
http://www.saxonica.com/
> -----Original Message-----
> From: xmlschema-dev-request@
. . .
Cart
