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
11/18/2009 5:03:52 PM
(If the maintainer of http://www.w3.org/XML/Schema#Tools would be so
kind as to add the link to PyXB's home page, I'd appreciate it. Thanks.)
PyXB version 1.0.0 is now available from SourceForge at:
http://sourceforge.net/projects/pyxb/
PyXB (Python XML Schema Bindings; "pixbee") is
. . . Read full entry »
Posted
11/18/2009 3:29:49 PM
Hi Folks,
In XSD 1.1 vendors are allowed to extend the language with additional (vendor-unique) datatypes and facets.
Example: In some countries the decimal point symbol is the comma; so a vendor may provide a new decimal datatype and a new facet for specifying the decimal point symbol:
<xs
. . . Read full entry »
Posted
11/11/2009 3:02:12 PM
Thanks Henry. Just done.
As I know the WG is not looking for extra work I thought I'd post to the
public list so that members have a low procedure way to object to the
comment if I've really missed the point! That said, I think it's a simple
and useful change to make.
Thanks again,
Pete.
--
. . . Read full entry »
Posted
11/11/2009 9:40:29 AM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Requests for changes to the spec should go to
www-xml-schema-comments@w3.org or into Buzilla -- they may get
overlooked if they are only sent here.
I'd suggest you reduce the length of your requested new names,
. . . Read full entry »
Posted
11/10/2009 5:57:56 PM
In "Schema Representation Constraint: Override Constraints and Semantics",
is there any chance that:
- D1 could be changed to Doverridden and
- D2 could be changed to Doverriding?
Then:
2 One of the following must be true:
2.1 D2 has a targetNamespace [attribute], and its ·actual valu
. . . Read full entry »
Posted
11/7/2009 2:24:52 PM
Thank you all for your valuable feedback. I think Henry put it most
succintly:
"The spec doesn't provide a mechanism by which a schema can constrain the
document element of schema-valid documents."
That's what I was wanting to know. I apologise if I used confusing
terminology in trying
. . . Read full entry »
Posted
11/7/2009 10:25:13 AM
> (b) make sure your processor distinguishes between elements
> with [validity]=invalid and those with [validity]=notKnown
> (again, how you do this is between you and your processor,
> and out of scope for the XSD spec); and
You might like to note that Saxon's
. . . Read full entry »
Posted
11/6/2009 7:35:27 PM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The spec doesn't provide a mechanism by which a schema can constrain
the document element of schema-valid documents.
It _does_ provide license for conformant processors to do
schema-validity assessment with such a constraint in place [1].
Different p
. . . Read full entry »
Posted
11/6/2009 5:35:19 PM
On 5 Nov 2009, at 23:58 , kennardconsulting wrote:
>
> I'm generating a bunch of XML Schemas that look roughly like:
>
> <xs:schema ...>
> <xs:element name="foo"/>
> <xs:element name="bar"/>
> </xs:schema>
>
> You can see t
. . . Read full entry »
Posted
11/6/2009 2:30:11 PM
I'm not quite sure what you are asking. Are you trying to restrict how
your schema can be extended, or are you trying to restrict what is
allowed in an instance document?
Perhaps you have a conceptual misunderstanding? Note that
<xs:schema ...>
<xs:element name="foo"/&
. . . Read full entry »
Posted
11/5/2009 10:58:55 PM
Hi guys,
I'm generating a bunch of XML Schemas that look roughly like:
<xs:schema ...>
<xs:element name="foo"/>
<xs:element name="bar"/>
</xs:schema>
You can see the actual ones http://metawidget.org/xsd here . My question
is, this schema allows
. . . Read full entry »
Posted
10/29/2009 3:38:25 PM
Altova is pleased to announce general availability version 2010 of its
MissionKit XML, database, and UML tools. v2010 is our MOST WANTED
release and includes over 70 new customer-requested features. Just a few
of these include:
* Support for WSDL 2.0, JSON, and SysML technologies
* New styles
. . . Read full entry »
Posted
10/26/2009 2:52:05 PM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Florent Georges writes:
> Henry S. Thompson wrote:
>
>> Without going into tedious and confidential details about
>> personalities and working group discussions, suffice it to say
>> that the design we have was the only one tha
. . . Read full entry »
Posted
10/26/2009 2:20:39 PM
Henry S. Thompson wrote:
Hi,
> Without going into tedious and confidential details about
> personalities and working group discussions, suffice it to say
> that the design we have was the only one that included both
> possibilities which the WG could reach consensus on.
Yes, but
. . . Read full entry »
Posted
10/26/2009 11:56:14 AM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael Kay writes:
> Yes. I've never heard an adequate explanation of why this extraordinary
> decision was made, but in practice everyone changes the default by using
> elementFormDefault="qualified".
At the time the spec. was wr
. . . Read full entry »
Posted
10/26/2009 11:22:14 AM
Henry Thompson writes:
> That was part of the compromise.
Stated differently: you can infer that there were a significant number of
people involved who strongly took the opposite position from yours, and
the default you see was in deference to their views of what the community
needed. As
. . . Read full entry »
Posted
10/25/2009 10:39:37 PM
Michael Kay wrote:
Hi,
> > I thought the element 'b' was defined in the target
> > namespace, but it seems it has to be in no namespace.
> Just as if you didn't use redefine, your local element
> declaration will only be in the target namespace if you specify
> elementForm
. . . Read full entry »
Posted
10/25/2009 6:51:17 PM
> I thought the element 'b' was defined in the target namespace, but it
seems it has to be in no namespace.
Just as if you didn't use redefine, your local element declaration will only
be in the target namespace if you specify elementFormDefault="qualified" on
your xs:schema element.
. . . Read full entry »
Posted
10/25/2009 6:05:41 PM
Hi,
I have a schema document that redefines a complex type as
following:
<xs:redefine schemaLocation="redefine.xsd">
<xs:complexType name="root">
<xs:complexContent>
<xs:extension base="tns:root">
. . . Read full entry »
Posted
10/22/2009 10:18:39 AM
Very well. Thank you, Michael and Michael.
On 10/22/2009 4:08 AM, Michael Kay wrote:
>> How will the prefix in the ref attribute in the
>> attributeGroup element be handled? If D2' is the result of
>> applying the xs:override transform, and D2' contains an
>> element i
. . . Read full entry »
Posted
10/22/2009 9:08:12 AM
>
> How will the prefix in the ref attribute in the
> attributeGroup element be handled? If D2' is the result of
> applying the xs:override transform, and D2' contains an
> element information item that is identical to the one for the
> <attributeGroup>, I expect it wi
. . . Read full entry »
Posted
10/21/2009 6:11:48 PM
On 21 Oct 2009, at 15:22 , Kevin Braun wrote:
> Here's an XSD 1.1 <override> question.
> Suppose I have:
> <schema ... xmlns:qrs="uri:example.com">
> <override ...>
> <complexType name="SomeType">
> <attributeGroup ref
. . . Read full entry »
Posted
10/21/2009 5:22:02 PM
Hi,
Here's an XSD 1.1 <override> question.
Suppose I have:
<schema ... xmlns:qrs="uri:example.com">
<override ...>
<complexType name="SomeType">
<attributeGroup ref="qrs:abc"/>
</complexType>
</override>
. . . Read full entry »
Posted
10/20/2009 10:33:32 PM
Hi Scott,
Trang can generate XML Schema from a set of XML files
http://code.google.com/p/jing-trang/
Best Regards,
George
--
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
Tsao, Scott wrote:
> I am wondering if there are good
. . . Read full entry »
Posted
10/20/2009 10:51:47 AM
Hello.
I downloaded the XSV validator and am a novice user I think because from the hours I have spent looking for set up instructions, I cannot find them. Can you provide the steps I need to follow to set up my validator?
Janell Craig
Business Analyst
Oakland Schools<http://oakland.k12.mi.us
. . . Read full entry »
Posted
10/20/2009 9:26:40 AM
I've had good results on this using Stylus Studio. It works from a single
instance document, but you can always combine multiple instances into one
before you start. There is some control over the design patterns it uses,
but I generally find the default settings are quite usable. Of course you
hav
. . . Read full entry »
Posted
10/20/2009 9:07:09 AM
My good advice: don't.
or at least, do not expect too much of it.
If you do, you will still need to do a lot of manual work afterwoods improving your schema.
For example, if some attributes are enumerated, how do you know that ? And if you do, how are you sure you have all possible values in your
. . . Read full entry »
Posted
10/19/2009 6:06:26 PM
I am wondering if there are good tools that would enable (auto) generation of XML schema from multiple instances of sample XML document.
It seems to me that one should be able to specify certain parameters for the resulting schema, e.g., the design pattern [1] to be followed.
Any comments or sugg
. . . Read full entry »
Posted
10/19/2009 5:22:12 PM
Hi, Michael
Would it be something like this?
<xs:attribute name="attribute_id" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:assert test="@attribute_id=Attributes/Attribute/@id or
@attribut
. . . Read full entry »
Posted
10/19/2009 4:57:10 PM
This looks correct (from visual inspection).
To run it you will need Saxon 9.2 or the development version of Xerces (I
can't speak for Xerces). Most schema tools do not yet support XSD 1.1, and
both these two are incomplete implementations.
You don't need to change the xs:schema element in orde
. . . Read full entry »
Posted
10/19/2009 11:06:23 AM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael Kay writes:
>> ... I think this probably means that I would have to augment my
>> list of schema document abstraction to actually make it a
>> list of (schemadoc, targetNamespace) pairs,
>
> That's precisely what I
. . . Read full entry »
Posted
10/19/2009 11:02:27 AM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael Kay writes:
> Note that dcterms-elem.xsd is reachable from vac.xsd via one route that
> contain a "redefines" step, and by another route that omits this step (but
> which does contain a different redefines step). This is whe
. . . Read full entry »
Posted
10/18/2009 11:27:50 PM
I don't think this can be done in XSD 1.0
It can be done in XSD 1.1, of course, using assertions.
Regards,
Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay
> -----Original Message-----
> From: xmlschema-dev-request@w3.org
>
. . . Read full entry »
Posted
10/18/2009 3:31:44 AM
Hi
I have an xml schema which restricts the Indexes/Tag/@attribute_id values to
the ones are defined in the parent element's Attributes/Attribute/@id. Is
there a way to extend this and enable one (or more) different static values
for example "id"?
There are more Indexes/Tag and Attribute
. . . Read full entry »
Posted
10/16/2009 10:22:09 PM
> -----Original Message-----
> From: noah_mendelsohn@us.ibm.com [mailto:noah_mendelsohn@us.ibm.com]
> Sent: 16 October 2009 21:35
> To: Michael Kay
>
. . . Read full entry »
Posted
10/16/2009 9:11:58 PM
> While my
> ACSOOD proposal remains very incomplete and has a variety of
> problems, I think it does more or less signal my thinking
> about questions like this [1].
>
Yes. It's close the the way I think about it. It appears to handle a chain
of redefinition (A redefines B, B
. . . Read full entry »
Posted
10/16/2009 5:57:20 PM
Michael Kay writes:
> Perhaps you just let it be caught by the general ban on duplicate
> components.
That was the idea.
> But unless you're careful about the wording, that ban also
> catches you out on a linear chain of redefinitions.
I'm pretty sure that's handled OK. Specificall
. . . Read full entry »
Posted
10/16/2009 4:35:06 PM
Michal Kay writes;
> It's not clear what answers it gives for more complex
> redefinition graphs.
Well, it's been a long time since I've looked at it. I guess I assume
that all redefinition graphs are in fact trees, I.e. each redefine can
redefine only one thing, and ultimately there is
. . . Read full entry »
Posted
10/16/2009 2:59:13 PM
Michael Kay writes:
> Because the common components have been copied into three different
> namespaces, a redefine occurring in one namespace does not
> affect copies of
> the component in a different namespace. That's Saxon's interpretation,
> anyway. You could take the view that
. . . Read full entry »
Posted
10/16/2009 2:29:34 PM
> Hmmm -- let's leave redefine aside, as we've agreed to differ
> on that before, but I'm surprised you recommend against
> chameleon include. I find it hugely useful (for those little
> bits that you use all the time but aren't worth putting in a
> namespace) and am not aware o
. . . Read full entry »
Posted
10/12/2009 9:04:47 PM
> Hmmm -- let's leave redefine aside, as we've agreed to differ
> on that before, but I'm surprised you recommend against
> chameleon include. I find it hugely useful (for those little
> bits that you use all the time but aren't worth putting in a
> namespace) and am not aware o
. . . Read full entry »
Posted
10/12/2009 8:38:15 PM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael Kay writes:
> I suspect, but without testing(!) that the strategy can be extended to
> xs:redefine as follows:
>
> (a) if redefinition for a namespace is required, create a new schema
> document with that targetNamespace that in
. . . Read full entry »
Posted
10/12/2009 6:02:10 PM
On 12 Oct 2009, at 11:00 , Costello, Roger L. wrote:
>
> Hi Folks,
>
> Below are two ways to declare a <Book> element.
>
> Both versions use <all>, to permit the elements within <Book> to
> occur in any order.
>
> The first version uses an unbounded
. . . Read full entry »
Posted
10/12/2009 5:48:09 PM
I agree with all of this, but it leaves the question of xs:redefine.
I suspect, but without testing(!) that the strategy can be extended to
xs:redefine as follows:
(a) if redefinition for a namespace is required, create a new schema
document with that targetNamespace that invokes the (previous)
. . . Read full entry »
Posted
10/12/2009 4:39:33 PM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Stimulated in equal measure by this thread, and a request from the XML
Security WG [0], I came up with my personal 'best practice' guideline
for schema document design for multi-namespace schemas. I include the
core bit below -- for the full context a
. . . Read full entry »
Posted
10/12/2009 1:00:39 PM
Hi Folks,
Below are two ways to declare a <Book> element.
Both versions use <all>, to permit the elements within <Book> to occur in any order.
The first version uses an unbounded <any>. The second version uses interleaved open content.
Are these two versions identica
. . . Read full entry »
Posted
10/9/2009 11:05:50 AM
Hi Pete,
Good point. That sounds like a good idea.
Cheers for that,
Andy
-----Original Message-----
From: xmlschema-dev-request@w3.org [mailto:xmlschema-dev-request@w3.org] On Behalf Of Pete Cordell
Sent: 09 Octob
. . . Read full entry »
Posted
10/9/2009 10:35:50 AM
Hi Pete,
Thanks for that but I thought about it and although I wanted d to appear before e or f, it is possible to submit an xml file with none of these fields populated so I left it in there.
Cheers,
Andy
-----Original Message-----
From: Pete Cordell [mailto:petexmldev@co
. . . Read full entry »
Posted
10/9/2009 10:02:46 AM
Hi Andy,
In that case it might be more aesthetic to move the minOccurs to the outer
xsd:choice so you get:
<xsd:choice minOccurs="0" maxOccurs="unbounded">
Pete.
----- Original Message -----
From: "Neill, Andrew" <andy.neill@sie
. . . Read full entry »
Posted
10/9/2009 9:32:39 AM
Hi Andy,
That's great. Actually, I don't know whether you noticed already, but
looking at it again, I don't think the minOccurs="0" on the xsd:sequence is
required.
HTH,
Pete.
----- Original Message -----
From: "Neill, Andrew" <andy.neill@sie
. . . Read full entry »
Posted
10/8/2009 1:06:47 PM
Hi Andy,
You can have a first any of a, b, c any number of times and then follow
them optionally with d followed by any of a, b, c, e, f any number of times:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
. . . Read full entry »
Posted
10/8/2009 12:12:26 PM
Hi George,
Thanks for that. I have been looking at this schema too long and missed that.
Thanks for your help.
Andy
-----Original Message-----
From: George Cristian Bina [mailto:george@oxygenxml.com]
Sent: 08 Oc
. . . Read full entry »
Posted
10/8/2009 12:11:11 PM
Hi Pete,
That works. I don't know how I missed that.
Many Thanks,
Andy
-----Original Message-----
From: Pete Cordell [mailto:petexmldev@codalogic.com]
Sent: 08 October 2009 11:07
To: Neill, Andrew; xmlschema-dev
. . . Read full entry »
Posted
10/8/2009 11:07:01 AM
Hi Andy,
Does something like the following work?
...
<xsd:choice maxOccurs="unbounded">
<xsd:element ref="a" minOccurs="0"/>
<xsd:element ref="b" minOccurs="0"/>
<xsd:element ref="c" minOccurs="
. . . Read full entry »
Posted
10/8/2009 9:24:59 AM
Excellent, thanks!
On 10/6/2009 6:40 PM, C. M. Sperberg-McQueen wrote:
>
> On 6 Oct 2009, at 14:45 , Kevin Braun wrote:
>
>> Hello,
>>
>>
>> Can anyone explain the following comment from the "changes since" in
>> XSD 1.1?
>>
>> "Wh
. . . Read full entry »
Posted
10/7/2009 6:10:30 PM
Can anyone help with this XSD please? It doesnt seem to work?
Essentially i want to ensure that if "E" or "F" are populated then "D" is populated before them. The rest of the elements can appear in any order and any amount of times.
<?xml version="1.0" en
. . . Read full entry »
Posted
10/6/2009 4:45:50 PM
Hello,
Can anyone explain the following comment from the "changes since" in XSD
1.1?
"When an |xsi:type| attribute appears on an element, and has a QName as
its value, but the QName does not resolve to a known type definition,
processors are now required to "fall back"
. . . Read full entry »
Posted
10/6/2009 4:40:46 PM
On 6 Oct 2009, at 14:45 , Kevin Braun wrote:
> Hello,
>
>
> Can anyone explain the following comment from the "changes since" in
> XSD 1.1?
>
> "When an |xsi:type| attribute appears on an element, and has a QName
> as its value, but the QName does not re
. . . Read full entry »
Posted
10/5/2009 12:57:12 PM
Michael - you've asked for feedback about whether redefine should be
deprecated. I believe it should.
I believe that the primary purpose for which schemas are written is an
attempt to facilitate automated data exchange between computer systems.
Features which in practice provide an "impe
. . . Read full entry »
Posted
10/3/2009 5:11:12 PM
> > So JSON may be a good alternative.
>
> I would never discourage you from looking for the best
> language to meet your needs, and JSON is in many respects
> simpler than XML. That said, keep in mind that JSON is
> fundamentally aimed at what we informally call "dat
. . . Read full entry »
Posted
10/3/2009 12:30:48 PM
Michael Kay writes:
> When XML was first conceived, I think most people expected it to be used
> primarily for documents (I had heard people talking about using SGML for
> data in the 1980s, and I thought they were nuts). It's
> interesting to review
> why XML proved successful as
. . . Read full entry »
Posted
10/3/2009 12:13:54 PM
In our extension schemas, we only use "redefine" to ADD extra attributes and
elements (in a separate namespace), not to change or remove any existing
ones.
One of my positive surprises with the way we implemented it, is that a XML
data binding like XMLBeans had no problem at all worki
. . . Read full entry »
Posted
10/3/2009 11:18:38 AM
Jozef Aerts writes:
> So JSON may be a good alternative.
I would never discourage you from looking for the best language to meet
your needs, and JSON is in many respects simpler than XML. That said,
keep in mind that JSON is fundamentally aimed at what we informally call
"data",
. . . Read full entry »
Posted
10/3/2009 11:09:56 AM
Hi Noah,
IMHO both xs:redefine and xs:complexType restriction should be
eliminated. With respect to the increasingly important area of XML data
binding for programming languages, redefine and complexType restriction
are generally ignored for the simple reason that they have no equivalent
in te
. . . Read full entry »
Posted
10/2/2009 11:43:49 PM
While I think many of your criticisms of xs:redefine and complex type
restriction and indeed xs:override are valid, I personally don't accept the
premise that XSD should be constrained or influenced by the data typing
paradigms of conventional programming languages. XML and XSD are first and
formo
. . . Read full entry »
Posted
10/2/2009 11:57:54 AM
Hi,
In 3.16.6.2 Derivation Valid (Restriction, Simple)
(http://www.w3.org/TR/xmlschema11-1/#cos-st-restricts), step 3.1.2.3
says: "Each type definition in D.{member type definitions}
<http://www.w3.org/TR/xmlschema11-1/#std-member_type_definitions> is
validly ·derived· <http://www.w3
. . . Read full entry »
Posted
10/2/2009 9:19:21 AM
Thanks Michael,
About the justification you are mentioning: that is exactly what our standard is about: allowing companies (but also the FDA) to add extra elements and attributes in a separate namespace.
The whole discussion is a trigger for us to move to XML-Schema 1.1 earlier than we envisaged.
. . . Read full entry »
Posted
10/1/2009 11:53:20 PM
Just for the record (though it only really confirms the point that there are
differing interpretations), I implemented the XSD 1.0 specification without
the benefit of knowing anything about the intent of the WG beyond what was
written in the spec, and I came to the conclusion that there was only o
. . . Read full entry »
Posted
10/1/2009 11:44:17 PM
> I am strongly for depreciating redefine (as well as inheritance by
> restriction, while we are at it ;-)).
I wouldn't like to see that deprecated, but as a matter of good practice,
once people adopt XSD 1.1 I shall probably be advising them always to do
restriction of complex content mode
. . . Read full entry »
Posted
10/1/2009 5:57:05 PM
Hi,
noah_mendelsohn@us.ibm.com <noah_mendelsohn@us.ibm.com> writes:
> because we believe that <redefine> has seen widespread use,
I have a completely o
. . . Read full entry »
Posted
10/1/2009 11:54:04 AM
Just the sort of feedback we need, thank you! It's quite possible that my
intuition on this is wrong.
Noah
--------------------------------------
Noah Mendelsohn
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------
Boris Kolpackov
. . . Read full entry »
Posted
9/30/2009 1:07:19 PM
Hi all,
I'm looking at 3.4.2.3.3 Mapping Rules for Content Type Property of
Complex Content.
The branch under 6.1 is the only case that allows the type being defined
to pick up the openContent of the base type. However, whenever 5.2
applies (the wildcard element is based on the schema's
defa
. . . Read full entry »
Posted
9/29/2009 3:47:32 PM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
XMLSchema at XML4Pharma writes:
> Our extension mechanism is based on the "import" and "redefine"
> elements of XML-Schema.
> [see] http://www.altova.com/forum/default.aspx?g=posts&m=1000005665
> We now want to es
. . . Read full entry »
Posted
9/29/2009 2:13:35 PM
2009/9/29 XMLSchema at XML4Pharma <XMLSchema@xml4pharma.com>:
> We, the CDISC XML-Tech Governance Team (and other CDISC teams) have
> developed a number of extensible standards for exchange of clini
. . . Read full entry »
Posted
9/29/2009 1:24:13 PM
We, the CDISC XML-Tech Governance Team (and other CDISC teams) have developed a number of extensible standards for exchange of clinical data and for submitting information to the regulatory authorities (FDA).
CDISC is a Standardization Organization active in the healthcare world.
Our extension me
. . . Read full entry »
Posted
9/29/2009 12:57:14 PM
I strongly urge you to read Michael Sperberg-McQueen's note carefully.
While, as noted below, some of my preferences for resolving ambiguities
happen to be different from his, I believe that his email very accurately
and carefully summarizes the state of play on this issue. Let me just
quote a
. . . Read full entry »
Posted
9/29/2009 11:07:20 AM
Hi,
Some time ago we have a similar problem in a project with one schema per
"concept" aproach project, we create almost 3500 schema-s. (GEL-XML ).
The XML-Spy validator is so different (so good) to other parsers, so you
have o create (readable) schema-s for all parsers implementation
. . . Read full entry »
Posted
9/29/2009 9:57:53 AM
On 29 Sep 2009, at 05:24 , XMLSchema at XML4Pharma wrote:
> We, the CDISC XML-Tech Governance Team (and other CDISC teams) have
> developed a number of extensible standards for exchange of clinical
> data and for submitting information to the regulatory authorities
> (FDA).
>
. . . Read full entry »
Posted
9/22/2009 2:44:04 PM
Ian, and everyone:
I chewed over this whole tempest through a leisurely, solo lunch.
And as I masticated, I considered the original directive given to
DARPA deep in the bowels of the Pentagon around the time that I was
born,
from which all of this (and a great deal more) has resulted.
. . . Read full entry »
Posted
9/8/2009 3:59:16 PM
Henry,
Long time no chat, hope all your pipes are clear and no ciphers!
I am sitting here at home, on extended sick leave, and I feel like I am
the only audience to a horror movie, the only one who happens to be privy
to a host of disparate pieces of arcane information which, taken all
. . . Read full entry »
Posted
9/7/2009 12:13:30 PM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
XML4Pharma writes:
> [positive about XML Schema 1.1]
Thanks for the encouraging words!
> Speaking about MS parsers. Is there any news there about future
> support by Microsoft for XML-Schema 1.1? E.g. are there any .Net
> validating pars
. . . Read full entry »
Posted
9/5/2009 11:25:18 PM
Hello Roger,
As usual, a brilliant description from you, as shared at the URL
given by you :) I'll be reading the presentation you wrote, in the
next few days, and may post any thoughts I might have.
I would like to share, that Apache Xerces-J is also working on XML
Schema 1.1 implementation. I
. . . Read full entry »
Posted
9/5/2009 8:51:16 PM
Excellent stuff !
I have passed it to the other team members of our CDISC "XML Governance
Team" (CDISC provides XML-based standards for use in clinical research).
Together with the information that Apache Xerces-J is working on an
implementation, this might mean that we move all our sc
. . . Read full entry »
Posted
9/5/2009 10:38:42 AM
Hi Folks,
I created a tutorial, for managers, on XML Schema 1.1.
Its purpose is to give an overview of the new features of XML Schema 1.1, without getting into its syntax, and to show how the new features can benefit a business.
http://www.xfront.com/xml-schema-1-1/xml-schema-1-1-for-managers.
. . . Read full entry »
Posted
9/4/2009 11:51:11 AM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tsao, Scott writes:
> Henry,
>
> Thanks for the confirmation!
>
> Is this the document you were referring to as far as W3C TAG's strong
> recommendation is concerned:
> http://www.w3.org/2001/tag/doc/URNsAndRegistries-50 ?
Yes,
. . . Read full entry »
Posted
9/3/2009 4:39:45 PM
Henry,
Thanks for the confirmation!
Is this the document you were referring to as far as W3C TAG's strong
recommendation is concerned:
http://www.w3.org/2001/tag/doc/URNsAndRegistries-50 ?
Scott
-----Original Message-----
From: Henry S. Thompson [mailto:ht@inf.�
. . . Read full entry »
Posted
9/3/2009 10:00:45 AM
> Simon Cox writes:
>> A processors will maintain a cache of schema component definitions and
>> declarations and associate it with a namespace.
Ah I can see where the confusion would come from : ) and why it then
seemed to make sense (or be a requirement in fact) to change the
name
. . . Read full entry »
Posted
9/3/2009 9:10:56 AM
Andrew says 'Unless they also changed the prefix between versions,
looking at snippets of markup you would still be none the wiser'. From
the perspective of automated processing of XML this is beside the point.
A program processing XML does not look at snippets of markup (and anyway
the prefix is
. . . Read full entry »
Posted
9/2/2009 8:08:59 PM
Also forwarded to the list as this is likely to be of general interest.
-----Original Message-----
From: Simon Cox [mailto:simon.cox@j...]
Sent: Wednesday, 2 September 2009 20:06
To: 'noah_mendelsohn@us.ibm.com'
Cc: 'Andrew Welch
. . . Read full entry »
Posted
9/2/2009 7:34:30 PM
No - its not merely the identity issue.
It’s the processing issue.
A processors will maintain a cache of schema component definitions and
declarations and associate it with a namespace.
The processing rules in the XML Schema spec do not require that a processor
load the schema fresh if a
. . . Read full entry »
Posted
9/2/2009 7:24:54 PM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
C. M. Sperberg-McQueen writes:
> The meaning of some identifiers is given in a way that
> guarantees permanence of the meaning assigned.
I'm very interested in examples of this for identifiers useable on the
web, particularly ones which partici
. . . Read full entry »
Posted
9/2/2009 7:03:07 PM
I agree with Michael.
The fact that there is no general URN resolution service (besides reading
the relevant RFCs) is highly inconvenient and pragmatically it is a killer.
But the fact that URN assignment is onerous (much much much more onerous
than URL creation) is not necessarily a bad thing.
. . . Read full entry »
Posted
9/2/2009 6:17:56 PM
2009/9/2 Simon Cox <simon.cox@j...>:
> Andrew Welch wrote
>> use a version attribute to distinguish the versions
>
> Where?
Typically on the root element, but it could go anywhere that's suitable.
> The issue was that elements with the same name were defined differently i
. . . Read full entry »
Posted
9/2/2009 6:03:51 PM
Andrew Welch wrote
> use a version attribute to distinguish the versions
Where?
The issue was that elements with the same name were defined differently in
both GML 2.0 and GML 3.0,
But they had the same target namespace. The differences were subtle -
technical rather than conceptual - but
. . . Read full entry »
Posted
9/2/2009 5:22:06 PM
In some situations it is good to include dates or version numbers in
namespace names.
For example, if your maintenance/governance arrangement expects new
versions, and particularly if the new versions are not compatible with older
versions.
Geography Markup Language from OGC made the mistake of k
. . . Read full entry »
Posted
9/2/2009 4:53:48 PM
2009/9/2 Simon Cox <simon.cox@j...>:
> In some situations it is good to include dates or version numbers in
> namespace names.
> For example, if your maintenance/governance arrangement expects new
> versions, and particularly if the new versions are not compatible with older
>
. . . Read full entry »
Posted
9/2/2009 4:40:35 PM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
C. M. Sperberg-McQueen writes:
> The record would not be complete without someone observing
> that it also has the disadvantage that if the domain name
> registration for [your committee] ever lapses, there is no
> guarantee that the new o
. . . Read full entry »
Posted
9/2/2009 3:46:25 PM
2009/9/2 <noah_mendelsohn@us.ibm.com>:
> Hi, Scott. Further endorsing the advice that Henry and Eliot have given
> you, I suggest you might be interested in the TAG's finding that
> specifically encourages you to prov
. . . Read full entry »
Posted
9/2/2009 10:53:09 AM
On 2 Sep 2009, at 09:40 , Henry S. Thompson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> C. M. Sperberg-McQueen writes:
>
>> The record would not be complete without someone observing
>> that it also has the disadvantage that if the domain name
>>
. . . Read full entry »
Posted
9/2/2009 10:39:38 AM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tsao, Scott writes:
> Thanks very much for your suggestions!
>
> Is http: URI that same as URL?
Many people use 'URL' to mean 'URI using the http: scheme', yes.
> And, is the use of them for namespace names (in lieu of URN)
> recommen
. . . Read full entry »
Posted
9/2/2009 10:06:30 AM
Hi, Scott. Further endorsing the advice that Henry and Eliot have given
you, I suggest you might be interested in the TAG's finding that
specifically encourages you to provide useful information that can be
retrieved using the namespace URI. See [1].
Noah
[1] http://www.w3.org/2001/tag/doc/n
. . . Read full entry »
Posted
9/2/2009 9:04:26 AM
On 2 Sep 2009, at 03:39 , Henry S. Thompson wrote:
>
> Tsao, Scott writes:
>
>> ...
>
>> And, is the use of them for namespace names (in lieu of URN)
>> recommended by standards organizations such as W3C and OASIS?
>
> Absolutely. OASIS have backed off using U
. . . Read full entry »
Posted
9/2/2009 8:12:53 AM
On 9/2/09 4:39 AM, "Henry S. Thompson" <ht@inf.ed.ac.uk> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Tsao, Scott writes:
...
>> The committee (we are participating in
. . . Read full entry »
Posted
9/1/2009 11:05:05 AM
Thanks very much for your suggestions!
Is http: URI that same as URL? And, is the use of them for namespace names (in lieu of URN) recommended by standards organizations such as W3C and OASIS?
The committee (we are participating in) seems to think that we should register a formal URN namespace
. . . Read full entry »
Posted
8/31/2009 11:21:34 AM
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
G. Ken Holman writes:
> I regret that the OASIS policy at the release of UBL was URN-based and
> not URL-based, but such was the case at the time.
Just to endorse the implication here: use http: URIs, and put
_something_ at that URI, even if it
. . . Read full entry »
Posted
8/28/2009 9:37:01 PM
At 2009-08-28 15:34 -0700, Tsao, Scott wrote:
>We are trying to decide on a namespace URI for an XML schema under
>development by a standards committee in the aerospace industry.
>
>Are there best practices that we could follow? For example, the
>choice between URL and URN, case s
. . . Read full entry »
Posted
8/28/2009 3:34:55 PM
We are trying to decide on a namespace URI for an XML schema under development by a standards committee in the aerospace industry.
Are there best practices that we could follow? For example, the choice between URL and URN, case sensitivity, unique components in the name, and incorporation of RDD
. . . Read full entry »
Posted
8/28/2009 3:13:31 PM
Else just use elements.
Why does XML have the choice of element or attribute, anyway ;-)
--------------------------------------------------------
Simon Cox
European Commission, Joint Research Centre,
Institute for Environment and Sustainability,
Spatial Data Infrastructures Unit, TP 262
Via
. . . Read full entry »
Posted
8/28/2009 1:37:35 PM
Hi Folks,
I am creating a new tutorial:
XML Schema 1.1 for Managers.
I am trying to describe how the new features in XML Schema 1.1 provide a benefit at the business level, not just the IT level.
I start my tutorial with a discussion of assertions. It's easy to see how assertions can bene
. . . Read full entry »
Posted
8/28/2009 11:22:24 AM
It's a well-known limitation of XSD 1.0 that you can't do this.
It's easy in XSD 1.1, but most processors don't support that yet. (Saxon
does support a sufficient subset, however).
Regards,
Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay
Received on Friday, 28 August 2009
. . . Read full entry »
Posted
8/28/2009 10:58:04 AM
At 2009-08-28 15:13 +0200, Simon Cox wrote:
>Else just use elements.
>Why does XML have the choice of element or attribute, anyway ;-)
Of course you can coerce any attribute value into an element, but I
like having the distinction between containment and attachment. Thus
there is no probl
. . . Read full entry »
Posted
8/28/2009 10:48:29 AM
So basically you're telling me that I don't have to repeat all
attributes from attributeGroup in restriction and it is sufficient to
just list the changed ones, that is the 'label' attribute in my case?
<xsd:complexType name="parentWithReqLabelAttr">
<xsd:complexContent>
. . . Read full entry »
Posted
8/28/2009 10:05:16 AM
> So basically you're telling me that I don't have to repeat
> all attributes from attributeGroup in restriction and it is
> sufficient to just list the changed ones, that is the 'label'
> attribute in my case?
>
> <xsd:complexType name="parentWithReqLabelAttr">
. . . Read full entry »
Posted
8/26/2009 6:20:01 PM
I wish to create an XML document in which one of its elements must be
defined with one of two known attributes, but not both.
For example, I would like to define a "socketHandler" element as follows:
<xs:element name="socketHandler">
<xs:complexType>
. . . Read full entry »
Posted
8/26/2009 10:04:41 AM
On 26 Aug 2009, at 02:06 , Michael Kay wrote:
>
> There's an assymetry here between attributes and child elements. For
> the
> content model (child elements), when you restrict a type you have to
> restate
> all the parts of the content model that you want to inherit. For
. . . Read full entry »
Posted
8/26/2009 9:22:53 AM
OK, so let's say we get rid off this repeating of content model
declaration using named model group, see below.
There's still one place I'd like to fix - the enumeration of all
attributes from 'attributes' attributeGroup inside the
'parentWithReqLabelAttr' type declaration.
<xsd:attributeGroup
. . . Read full entry »
Posted
8/26/2009 9:06:28 AM
There's an assymetry here between attributes and child elements. For the
content model (child elements), when you restrict a type you have to restate
all the parts of the content model that you want to inherit. For attributes,
you only have to list the things that have changed - any other attribut
. . . Read full entry »
Posted
8/25/2009 3:20:29 PM
The key point is that because your document uses elements from two
namespaces, an instance document with no namespace prefixes at all is
invalid. The 'no prefix' can only be used by one namespace, not both.
--------------------------------------------------------
Simon Cox
European Commission,
. . . Read full entry »
Posted
8/25/2009 2:18:22 PM
The Libray and Book elements are declared in different namespaces.
The instance document has to distinguish between the namespaces in use
somehow.
So one of them must have a prefix to achieve this.
--------------------------------------------------------
Simon Cox
European Commission, Joint
. . . Read full entry »
Posted
8/25/2009 2:13:56 PM
>
>
> I know - i can handle this XML with any prefix. Its depend on
> the declaration in the header (xlmns).
>
> But,
>
> XML without any prefix will failed in validation . I want to
> have the option to not have prefix at all and i dont know how
> can i do this
. . . Read full entry »
Posted
8/25/2009 1:31:03 PM
>
> I dont want any prefix. and i dont know how to get rid the n1 prefix.
>
As I said before (I can only repeat myself)
(a) you should be able to handle the document whatever prefixes it uses - if
not, there is something wrong with your application
(b) to find out whether you can ge
. . . Read full entry »
Posted
8/25/2009 1:11:41 PM
If you omit the target namespace, you are giving up using namespaces,
which are used to help avoid naming conflicts.
These resources might help you:
http://www.w3.org/TR/xmlschema-0/#NS
http://www.amazon.com/gp/product/0130655678
Kevin
(I earlier CC'd xmlschema-dev-request instead of xmlschema-de
. . . Read full entry »
Posted
8/25/2009 12:31:43 PM
The instance document is valid against your schema. I don't know whether the
Altova tool gives you any choice over the use of namespace prefixes, you
will have to consult the Altova documentation or support. But any user of
this XML document shouldn't care about the allocation of prefixes - it's
on
. . . Read full entry »
Posted
8/25/2009 11:01:39 AM
>
> i have two schemas A,B.
> B import A.
Actually, you have one schema made up from two schema documents.
> Both of them defined as unqualified element, but the xml that
> generated from B has n1: as a prefix for the root elements.
> Is there a way to have no prefix at all
. . . Read full entry »
Posted
8/25/2009 9:36:16 AM
It sounds like you're looking for an instance more like:
<Library xmlns="http://www.library.org">
<test xmlns="">
<Title>XSLT 2.0 Programmer's Reference</Title>
</test>
</Library>
That doesn't use any namespace prefixes, but puts the
. . . Read full entry »
Posted
8/25/2009 9:13:17 AM
I think what you may be trying to say is that despite the fact that you
are using elemFormDefault="unqualified", your elements are qualified.
Global elements belong to the target namespace; the elemFormDefault only
applies to local elements (ie, within a complex type). If you don't
. . . Read full entry »
Posted
8/25/2009 6:46:20 AM
Almost.
I want instance like you attach,but in your instance you have xmlns in the
test element.
Remove it and your instance is not valid.
And i dont want prefix at all. clean xml.
David Maze wrote:
>
> It sounds like you're looking for an instance more like:
>
> <Library xml
. . . Read full entry »
Posted
8/25/2009 5:49:25 AM
Last one - (Thank you!!!!!)
I know - i can handle this XML with any prefix. Its depend on the
declaration in the header (xlmns).
But,
XML without any prefix will failed in validation . I want to have the option
to not have prefix at all and i dont know how can i do this either by
chanigng the
. . . Read full entry »
Posted
8/25/2009 5:18:19 AM
The instance is valid , but the instance is create with prefix "n1", but i
dont want prefix!!!!
remove the prefix 'n1' from the instance and change
'xmlns:n1="http://www.library.org" to '''xmlns="http://www.library.org"
will cause to invalid instance.
I dont want a
. . . Read full entry »
Posted
8/25/2009 3:55:57 AM
Attached files as ZIP
Avihaimar wrote:
>
> Exampel : lib.xsd import book.xsd (both with unqualified)
>
> ------ LIB -------
> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
> xmlns="http://www.library.org" xmlns:b="http://www.book.org&
. . . Read full entry »
Posted
8/25/2009 3:53:51 AM
Exampel : lib.xsd import book.xsd (both with unqualified)
------ LIB -------
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.library.org" xmlns:b="http://www.book.org"
targetNamespace="http://www.library.org" elementFormDefaul
. . . Read full entry »
Posted
8/24/2009 1:34:39 PM
Hey,
i have two schemas A,B.
B import A.
Both of them defined as unqualified element, but the xml that generated from
B has n1: as a prefix for the root elements.
Is there a way to have no prefix at all?
Thank you
--
View this message in context: http://www.nabble.com/Unqualified-elment---b
. . . Read full entry »
Posted
8/24/2009 1:34:39 PM
Hey,
i have two schemas A,B.
B import A.
Both of them defined as unqualified element, but the xml that generated from
B has n1: as a prefix for the root elements.
Is there a way to have no prefix at all?
Thank you
--
View this message in context: http://www.nabble.com/Unqualified-elment---b
. . . Read full entry »
Posted
8/21/2009 5:48:36 PM
Michael Kay wrote:
>> The following is my xml for which I require to write the xsd schema
>>
>> <type>
>> <foo/>
>> <bar/>
>> </type>
>>
>> In the above xml for type element the following conditions
>> should be satisfie
. . . Read full entry »
Posted
8/21/2009 10:35:47 AM
>
> The following is my xml for which I require to write the xsd schema
>
> <type>
> <foo/>
> <bar/>
> </type>
>
> In the above xml for type element the following conditions
> should be satisfied 1] Atleast one element either foo or bar
>
. . . Read full entry »
Posted
8/20/2009 1:01:05 PM
Hi,
The following is my xml for which I require to write the xsd schema
<type>
<foo/>
<bar/>
</type>
In the above xml for type element the following conditions should be
satisfied
1] Atleast one element either foo or bar must be present
2] foo or bar can have a maximum o
. . . Read full entry »
Posted
8/17/2009 3:07:39 PM
I feared it was so :-)
But it is then more than a little bit awkward - as I have to add a new
complexType that restricts the complexType 'parent' and then within it
I have to repeat all the stuff declared the 'parent' and its parent
types (by extension) etc., and eventually I have to use the new
c
. . . Read full entry »
Posted
8/17/2009 2:28:28 PM
> But it is then more than a little bit awkward - as I have to
> add a new complexType that restricts the complexType 'parent'
> and then within it I have to repeat all the stuff declared
> the 'parent' and its parent types (by extension) etc.
Yes, that's a particularly nasty featur
. . . Read full entry »
Posted
8/16/2009 12:59:30 PM
You can do this, but only in an <xs:restriction>, not in an <xs:extension>
Regards,
Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay
> -----Original Message-----
> From: xmlschema-dev-request@w3.org
> [mailto:xm
. . . Read full entry »
Posted
8/14/2009 2:41:59 PM
Hello all,
my question follows, I am using XML Schema 1.0.
I have an attributeGroup with an optional attribute. This
attributeGroup is used in declaration of complexType. Another
complexType is then an extension of that complexType. Please see my
sample code below.
I would like to declare the att
. . . Read full entry »
Posted
8/14/2009 10:32:37 AM
Thanks, very much Mike for the answers. This has helped me.
On Fri, Aug 14, 2009 at 7:45 AM, Michael Kay<mike@saxonica.com> wrote:
>> Â Â I have following questions about inheritable attributes,
>> in X
. . . Read full entry »
Posted
8/14/2009 3:15:19 AM
> I have following questions about inheritable attributes,
> in XML Schema 1.1.
Good questions, and I had to do some careful reading to find the answers.
>
> 1. supposing there is an attribute declaration, like following:
>
> (a global declaration, and child of xs:schema e
. . . Read full entry »
Posted
8/13/2009 10:09:37 AM
Hi all,
I have following questions about inheritable attributes, in XML Schema 1.1.
1. supposing there is an attribute declaration, like following:
(a global declaration, and child of xs:schema element)
<xs:attribute name="TEST_ATTR" type="xs:integer" />
then, can I
. . . Read full entry »
Posted
8/12/2009 4:46:34 PM
On 12 Aug 2009, at 11:29 , Costello, Roger L. wrote:
>
> Here's what the XML Schema 1.1 specification says:
>
> The <redefine> construct is *deprecated*
Quite correct. While some may wish it were not so, the
current spec does deprecate the 'redefine' construct,
just as it
. . . Read full entry »
Posted
8/12/2009 4:30:51 PM
>From slide 24:
"Example: in XSD 1.0 the below instance document is invalid because the
<Title> element matches both the explicit element declaration and the
<any/> wildcard. In XSD 1.1, the instance is valid."
Not quite right. In XSD 1.0, the >>schema<< i
. . . Read full entry »
Posted
8/12/2009 3:11:36 PM
Thanks again Noah. Great suggestion! See slide 24:
http://www.xfront.com/xml-schema-1-1/xml-schema-1-1.ppt
/Roger
> -----Original Message-----
> From: noah_mendelsohn@us.ibm.com [mailto:noah_mendelsohn@us
. . . Read full entry »
Posted
8/12/2009 2:40:43 PM
Suggestion:
I think the changes to support non-deterministic content models involving
<any> is a big deal, and it would be good to highlight that in the 5
minute intro along with the syntax changes to <any>
Use case is:
You have a content model like:
<sequence>
. . . Read full entry »
Posted
8/12/2009 1:50:59 PM
Thanks Noah, Dave, Eliot,
I changed the slides (slide 25 and slide 253) about <redefine> to say:
The XML Schema working group is considering
deprecating the <redefine> element.
Noah, I also changed slide 50 per your suggestion:
http://www.xfront.com/xml-schema-1-1/xml-schema
. . . Read full entry »
Posted
8/12/2009 1:03:19 PM
First, taking the opportunity... Roger, thanks very much for this tutorial. I can't speak for the WG, but as chair, I deeply appreciate it!
Now on to the question of deprecating redefine...
I believe that Noah is right, that given the "priority feedback" nature of the plan to deprecat
. . . Read full entry »
Posted
8/12/2009 1:03:12 PM
Roger Costello writes:
> Here's what the XML Schema 1.1 specification says:
>
> The <redefine> construct is *deprecated*
I acknowledged that. Immediately below the text you quote, it says:
"Editorial Note: Priority Feedback Request
"The Working Group requests feedb
. . . Read full entry »
Posted
8/12/2009 11:29:44 AM
Here's what the XML Schema 1.1 specification says:
The <redefine> construct is *deprecated*
/Roger
> -----Original Message-----
> From: Eliot Kimber [mailto:ekimber@reallysi.com]
> Sent: Wednesday,
. . . Read full entry »
Posted
8/12/2009 11:19:57 AM
Slide 50:
"If I had placed the assertion on the <Para> element my XPath expression
would need to "look up" to the <Document> element (parent). That's not
allowed. It's an error, in fact."
Nope, it's not an error, at least not in the eyes of a schema processor.
I
. . . Read full entry »
Posted
8/12/2009 11:14:24 AM
Overall, I think this is excellent, and much improved from the first
version. One quibble, though reasonable people might disagree with my
position on this:
You say on Slide 25 that <redefine> is deprecated, but that is followed in
the CR draft with a feedback request asking the communit
. . . Read full entry »
Posted
8/12/2009 10:26:29 AM
On 8/12/09 10:14 AM, "noah_mendelsohn@us.ibm.com"
<noah_mendelsohn@us.ibm.com> wrote:
> Overall, I think this is excellent, and much improved from th
. . . Read full entry »
Posted
8/8/2009 1:27:50 PM
Hi Folks,
Here are the updates I made to the XML Schema 1.1 Tutorial:
1. I received many excellent comments and
incorporated them.
2. I created 20 lab exercises. I recommend
working the exercises as you read through
the tutorial.
Here is the updated tutorial:
. . . Read full entry »
Posted
8/6/2009 6:30:03 PM
Firstly, you're off-topic for this list - your question has nothing to do
with XML Schema.
There's nothing wrong with your XLink syntax if you can find an XLink
processor to process it. Don't expect a plain XML parser to do anything with
it. In practice, XLink processors are thin on the ground. Y
. . . Read full entry »
Posted
8/6/2009 12:30:31 PM
I am looking for the way
to drop external XML fragments into an XML instance file.
I think that this used to work:
<gmd:contact xlink:show="embed"
xlink:href="http://asdd.ga.gov.au/asdd/profileinfo/GAOpenDaySeries.xml#GADetails"/>
The documentation that I can find, su
. . . Read full entry »
Posted
8/6/2009 11:30:28 AM
On 6 Aug 2009, at 10:30 , John.Tucker wrote:
> I am looking for the way
> to drop external XML fragments into an XML instance file.
>
> I think that this used to work:
>
> <gmd:contact xlink:show="embed"
>
> xlink:href="http://asdd.ga.gov.au/asdd/profilei
. . . Read full entry »
Posted
8/5/2009 1:06:41 PM
FYI
Hi,
I am new to Xquery, could anyone tell me what is the jar file required for
using xquery and a sample program to get the xml data using xquery.
Thanks in Advance
Sri
Received on Wednesday, 5 August 2009 11:43:43 GMT
. . . Read full entry »
Posted
8/5/2009 9:34:49 AM
Sri,
What platform (machine, operating system, Java version) do you intend
to run on? As far as I know, Java by itself does not come automatically
with support for XQuery.
IBM is now having a series of releases of an open beta of XQuery
support with a special API allowing Java cod
. . . Read full entry »
Posted
8/4/2009 3:19:48 PM
Hi,
I am new to xpath, I am using xpath to get the data dynamically from soap
response.
Soap Response:
<soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<ns1:getClosestPaymentCenterResponse xmlns:ns1="http://test.com">
<ns1:
. . . Read full entry »
Posted
7/30/2009 5:46:37 PM
> >
> > Are these equivalent:
> >
> > 2009-07-29T24:00:00-6:00
> > 2009-07-30T00:00:00-6:00
> >
They are two different lexical representations of the same xs:dateTime
value. (Just as "1" and "true" are different lexical representat
. . . Read full entry »
Posted
7/30/2009 5:31:15 PM
2009/7/30 Costello, Roger L. <costello@mitre.org>:
>
> Hi Folks,
>
> Are these equivalent:
>
> 2009-07-29T24:00:00-6:00
> 2009-07-30T00:00:00-6:00
>
> /Roger
>
xs:dateTime('2009-07-29T24:00:00') eq
. . . Read full entry »
Posted
7/30/2009 2:10:31 PM
> 108 shows an xsd:alternative element with an inline simple type
> definition. This is not strictly speaking illegal or
> impossible, but since the element in question is being handled with
> conditional type
> assignment it will typically have attributes, and if it has any
&g
. . . Read full entry »
Posted
7/30/2009 1:00:57 PM
D.2.2 discusses the lexical space:
/hourFrag/ ::= ([|01|] /digit/
<http://www.w3.org/TR/xmlschema11-2/#nt-digit>) | ('|2|' [|0-3|])
On 7/30/2009 12:46 PM, Michael Kay wrote:
>
>
>>> Are these equivalent:
>>>
>>> 2009-07-29T24:00:00-6:00
>>&g
. . . Read full entry »
Posted
7/30/2009 12:23:09 PM
24 isn't a valid hour (see part 2, D.2.1)
On 7/30/2009 12:10 PM, Costello, Roger L. wrote:
> Hi Folks,
>
> Are these equivalent:
>
> 2009-07-29T24:00:00-6:00
> 2009-07-30T00:00:00-6:00
>
> /Roger
>
>
Received on Thursday, 30 July 2009 16:24:32 GMT
. . . Read full entry »
Posted
7/30/2009 12:10:06 PM
Hi Folks,
Are these equivalent:
2009-07-29T24:00:00-6:00
2009-07-30T00:00:00-6:00
/Roger
Received on Thursday, 30 July 2009 16:10:44 GMT
. . . Read full entry »
Posted
7/30/2009 8:32:32 AM
Hi Michael,
See inlined comments.
> 15 says "defaultAttributes is used to specify a set of
> attributes that apply to every complexType in the schema."
>
> Not quite. Like the default open content, the default
> attributes apply to every complex type declared in the
&
. . . Read full entry »
Posted
7/29/2009 11:03:57 PM
>
> I think it would be more accurate to say:]
>
> "A XSD 1.0 Schema Document with one targetNamespace could
> not restrict a type using ^^ elements from another
> targetNamespace. In XML Schema 1.1, you can do this, by
> adding a targetNamespace attribute to each s
. . . Read full entry »
Posted
7/29/2009 7:15:18 PM
On 29 Jul 2009, at 17:01 , Costello, Roger L. wrote:
> ...
>
>
>> I noticed that precisionDecimal doesn't seem to have made it into
>> the hierarchy diagram on slide 263--nor have the new duration- and
>> dateTime-derived datatypes.
>
>
> I used the hierarchy ch
. . . Read full entry »
Posted
7/29/2009 7:01:14 PM
Hi Dave,
See inline comments.
> At 4:21 PM -0400 2009-07-29, noah_mendelsohn@us.ibm.com wrote:
> >Dave:
> >
> >Not sure if you saw this. Are Roger's sample precisions on slide 28
> >actually correct?
. . . Read full entry »
Posted
7/29/2009 6:40:22 PM
Ah, I added the "s" but I as I reread it I see that you are correct. Thanks. Fixed and uploaded.
/Roger
> -----Original Message-----
> From: noah_mendelsohn@us.ibm.com [mailto:noah_mendelsohn@us�
. . . Read full entry »
Posted
7/29/2009 6:40:02 PM
Looks fine to me, except for one grammar error:
to each such "foreign" elements and attributes in the restriction -> to
each such "foreign" element and attribute in the restriction
(each is singular)
Noah
--------------------------------------
Noah Mendelsohn
IBM Corpor
. . . Read full entry »
Posted
7/29/2009 6:23:45 PM
Thanks Noah and Michael. I made the suggested changes. See slides 27-28:
http://www.xfront.com/xml-schema-1-1/xml-schema-1-1.ppt
/Roger
> -----Original Message-----
> From: noah_mendelsohn@us.ibm.com [mailto:noah_mendelsohn
. . . Read full entry »
Posted
7/29/2009 6:21:23 PM
At 4:21 PM -0400 2009-07-29, noah_mendelsohn@us.ibm.com wrote:
>Dave:
>
>Not sure if you saw this. Are Roger's sample precisions on slide 28
>actually correct? His draft says:
>
><length>3.00</length>
. . . Read full entry »
Posted
7/29/2009 4:21:28 PM
Dave:
Not sure if you saw this. Are Roger's sample precisions on slide 28
actually correct? His draft says:
<length>3.00</length> <!-- value is 3, precision is 2 -->
<length>3.0</length> <!-- value is 3, precision is 1 -->
<length>3</length>
. . . Read full entry »
Posted
7/29/2009 4:03:34 PM
On Slide 27, you say:
"With XML Schema 1.0 you could not restrict a type defined in another
schema. In XML Schema 1.1 you can by adding a targetNamespace attribute to
each element and attribute in the restriction"
I think it would be more accurate to say:]
"A XSD 1.0 Schema Doc
. . . Read full entry »
Posted
7/28/2009 10:31:29 PM
On 27 Jul 2009, at 11:01 , Pete Cordell wrote:
> In XSD 1.1 section 2.2 it says:
>
> Note: At the abstract level, there is no requirement that the
> components of a schema share a ·target namespace·. Any schema for
> use in ·assessment· of documents containing names from more t
. . . Read full entry »
Posted
7/27/2009 4:01:40 PM
In XSD 1.1 section 2.2 it says:
Note: At the abstract level, there is no requirement that the components of
a schema share a ·target namespace·. Any schema for use in ·assessment· of
documents containing names from more than one namespace will of necessity
include components with different ·tar
. . . Read full entry »
Posted
7/24/2009 2:16:38 PM
Hi Folks,
I updated my XML Schema 1.1 Tutorial:
http://www.xfront.com/xml-schema-1-1/xml-schema-1-1.ppt
Here are the changes:
1. At the beginning I added a "5 minute intro" section that quickly covers all of the new capabilities in XML Schema 1.1
2. I completely revised the section
. . . Read full entry »
Posted
7/23/2009 1:25:46 PM
I have configured a base object and have extended the object. I am know
trying to set certain base elements from within the extended object.
Received on Friday, 24 July 2009 21:44:38 GMT
. . . Read full entry »
Posted
7/23/2009 9:44:21 AM
Although the lexical space of integer is a subset of the lexical space of
string, integer is not derived by string by restriction. This decision has
been controversial, but there are those who feel that declaring something as
a string conveys something about the intended use of the type which is no
. . . Read full entry »
Posted
7/22/2009 8:01:27 PM
> Doesn't this achieve the same result (I simply omitted the
> third alternative):
>
> <element name="template">
> <alternative test="@name" type="xslt:named-template"/>
> <alternative test="@match" type
. . . Read full entry »
Posted
7/22/2009 6:08:42 PM
Hi Roger,
I think, xs:error is an useful facility. Basically, if an element
or an attribute has a type xs:error, then that element or attribute
becomes invalid during validation process.
xs:error has an empty lexical and value space. It just designates,
that something is invalid.
We can utilize
. . . Read full entry »
Posted
7/22/2009 2:14:35 PM
Hi Roger,
It's said in the XML Schema 1.1, spec that xs:error is mainly
useful in "conditional type alternative" (CTA) definitions.
As far as I know, xs:error is a special type which is present
implicity in all 1.1 Schemas. If the xs:error type get's applied to
anything (like, element
. . . Read full entry »
Posted
7/22/2009 1:57:55 PM
Hi Michael,
> A schema for XSLT, for example, might enforce a rule that
> XSLT templates must have either a name or a match attribute
> by declaring the xsd:template element thus:
>
> <element name="template">
> <alternative test="@name"
. . . Read full entry »
Posted
7/22/2009 1:00:43 PM
Hello,
I have a simple XML file:
<?xml version="1.0" standalone="yes"?>
<mytext xml:space="preserve">the text</mytext>
I have a complex type that manages the xml:space attribute. The xsd
looks like this:
<?xml version="1.0"?>
<xs:s
. . . Read full entry »
Posted
7/22/2009 11:51:01 AM
On 22 Jul 2009, at 05:37 , Costello, Roger L. wrote:
>
> Hi Mukul,
>
> Yesterday I was talking with a colleague and I described to him
> Conditional Type Alternative (CTA) and then xs:error. He was puzzled
> about xs:error. He couldn't see a legitimate (nonredundant) use case
. . . Read full entry »
Posted
7/22/2009 11:40:21 AM
On 21 Jul 2009, at 13:56 , Costello, Roger L. wrote:
>
>
> Can you provide an example that illustrates the usefulness of
> xs:error?
>
You might want to examine the work of Fabio Vitali, Paolo
Marinelli, and Claudio Sacerdoti Coen on SchemaPath, which
provided the initial impetu
. . . Read full entry »
Posted
7/22/2009 7:37:58 AM
Hi Mukul,
Yesterday I was talking with a colleague and I described to him Conditional Type Alternative (CTA) and then xs:error. He was puzzled about xs:error. He couldn't see a legitimate (nonredundant) use case for it. As I got to thinking about it, I agreed with him.
For example, if the kind
. . . Read full entry »
Posted
7/21/2009 3:56:59 PM
Hi Folks,
Consider this usage of xs:error:
<xs:element name="Publication" type="PublicationType">
<xs:alternative test="@kind eq 'magazine'" type="MagazineType" />
<xs:alternative test="@kind eq 'book'" type="
. . . Read full entry »
Posted
7/21/2009 9:33:22 AM
I think CMSMcQ must have got out of bed the wrong side this morning - his
note contains the answer, but it's so buried in ramblings and musings that
you might have trouble finding it!
The problem this facility is solving is the use case where you want to
customize an industry-standard schema such
. . . Read full entry »
Posted
7/20/2009 8:58:12 PM
On 20 Jul 2009, at 17:42 , Costello, Roger L. wrote:
>
> Hi Folks,
>
> In XSD 1.1 a schema can have multiple targetNamespaces. Presumably
> this capability was introduced to solve a problem. What problem is
> it solving?
>
Pedantic note: I think you must mean that a sch
. . . Read full entry »
Posted
7/20/2009 8:51:17 PM
On 20 Jul 2009, at 17:42 , Costello, Roger L. wrote:
>
> Hi Folks,
>
> In XSD 1.1 a schema can have multiple targetNamespaces.
Not in general, no. In some fairly tightly constrained
situations, it's possible to write declarations that
generate components in a namespace other than th
. . . Read full entry »
Posted
7/20/2009 8:08:04 PM
If I remember correctly, there was a concern expressed by some users about
an inability in XSD 1.0 to succeed in restricting certain complex types
when the content models involved more than one namespace. I don't think I
can reproduce an example offhand, but I'm fairly sure that was the
origin
. . . Read full entry »
Posted
7/20/2009 8:06:29 PM
Yes, that looks great to me, except for another typo I made in my email
that you missed:
When you want to optimize something like business rules for a
particular document type, or for a major subsection of a document, than I
think -> THEN I think
--------------------------------------
No
. . . Read full entry »
Posted
7/20/2009 7:42:05 PM
Hi Folks,
In XSD 1.1 a schema can have multiple targetNamespaces. Presumably this capability was introduced to solve a problem. What problem is it solving?
/Roger
Received on Monday, 20 July 2009 23:42:42 GMT
. . . Read full entry »
Posted
7/20/2009 7:37:47 PM
Thanks again Noah.
I recast the slide as illustrating different use cases (and corrected my mistake of "assertions on elements").
Please let me know if this is reasonable (slide 28):
http://www.xfront.com/xml-schema-1-1/xml-schema-1-1.ppt
/Roger
> -----Original Message-----
>
. . . Read full entry »
Posted
7/20/2009 5:19:38 PM
Thank you for taking these concerns to heart.
p 28: Well, it's all up to you, but I still think you are conflating types
with elements on slide 28, and in a tutorial that seems unfortunate. My
mail showed an example with two elements, <width> and <height>. Also, I
think calling i
. . . Read full entry »
Posted
7/18/2009 5:00:19 PM
Call for Submissions
3rd International Rules Challenge
at
RuleML-2009
co-located with the Business Rules Forum
November 5-7 2009, Las Vegas, Nevada, USA
http://2009.ruleml.org/challenge
. . . Read full entry »
Cart
Prev: "XQuery Talk Blog"
Next: "EDI-List Blog"
