Cart|
Home > Learn XML > XML Blogs > XMLSCHEMA-DEV Blog
Subscribe to the XML Schema Development Blog in XML format
The XML Schema Development Blog (XMLSchema-DEV Blog)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. Re: XML Schema 1.1 TutorialPosted 4/3/2013 8:15:23 PMOn Wed, Apr 3, 2013 at 7:10 PM, Maik Stührenberg < maik.stuehrenberg@uni-bielefeld.de> wrote: > > As far as I understand in this point you tutorial is not correct, since > competing . . . Read full entry » Re: XML Schema 1.1 TutorialPosted 4/3/2013 3:40:56 PMHello Ramkumar and Mukul, thanks for the tutorial and thanks for bringing this up again. However, I'm a bit puzzled, in Section 2. Extensibility and Versioning you state that, "Also considered legal is a competition between two wildcards. However, competition between two elements is still c . . . Read full entry » Re: XML Schema 1.1 TutorialPosted 4/3/2013 2:04:49 PMresponding very late to this post. Nice writeup. Regards, Mukul Gandhi Written from an android mobile On Wednesday, February 20, 2013, Ramkumar Menon <ramkumar.menon@gmail.com> wrote: > I wanted to share with everyone interested . . . Read full entry » Re: Add an attributePosted 4/1/2013 9:12:56 AMOn Apr 1, 2013, at 1:40 AM, Dave Pawson wrote: > Thanks Michael, fairly comprehensive answer. > Some comments in line. > > > On 31 March 2013 22:26, C. M. Sperberg-McQueen <cmsmcq@blackmesatech& . . . Read full entry » Re: Restriction errorPosted 4/1/2013 8:52:15 AMThanks Michael. I am using a 1.0 schema, but if you see the later post, I think this is one that MK noted as a bug in his validator as used in oXygen. regards On 1 April 2013 00:25, C. M. Sperberg-McQueen <cmsmcq@blackmesate . . . Read full entry » Re: Add an attributePosted 4/1/2013 8:40:23 AMThanks Michael, fairly comprehensive answer. Some comments in line. On 31 March 2013 22:26, C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> wrote: > > > I guess you mean &qu . . . Read full entry » Re: Restriction errorPosted 3/31/2013 5:25:36 PMOn Mar 20, 2013, at 8:06 AM, Dave Pawson wrote: > Note I'm the real newbie here Mike. > > On 20 March 2013 13:53, Michael Kay <mike@saxonica.com> wrote: >> A complex-type-with-simple-content is gene . . . Read full entry » Re: Redefinition of group, who's correctPosted 3/31/2013 4:27:56 PMOn Mar 25, 2013, at 2:49 AM, Pierre Attar wrote: > > > When trying to write this schema, my assumption was a little bit DTD like interpretation : the first defininition is the right one. That's true for entity and attribute declarations in DTDs, but not for element declarations (whi . . . Read full entry » Re: Redefinition of group, who's correctPosted 3/31/2013 4:22:31 PMOn Mar 20, 2013, at 11:56 AM, Pierre Attar wrote: > Hi, > > I have a problem using group redefinitions and validating both with XMLSpy (who complains) and Oxygen (who validates). > My question : who is correct ? Where a I wrong ? > > Note: my schema are a lot more complex but . . . Read full entry » Re: Add an attributePosted 3/31/2013 3:26:34 PMOn Mar 22, 2013, at 4:52 AM, Dave Pawson wrote: > Fixed, but the solution looks 'orrible. > Is it possible to make it tidier than this? > > regards ... confused. DaveP > > instance > <uaffect xmlns="http://www.dpawson.co.uk/ns#" xmlns:e="http://example.com . . . Read full entry » Re: Redefinition of group, who's correctPosted 3/25/2013 9:49:29 AMSorry I did not saw answers to questions because I had a problem with my mailer. In Oxygen, I'm using Saxon-EE : No errors. In XMLSpy, the message is : The schema doesn't appear to be valid by itself (as a part of another schema, it might still be OK). 'essai' is already declared in schema . . . Read full entry » Re: Add an attributePosted 3/22/2013 10:52:59 AMFixed, but the solution looks 'orrible. Is it possible to make it tidier than this? regards ... confused. DaveP instance <uaffect xmlns="http://www.dpawson.co.uk/ns#" xmlns:e="http://example.com"> <effect Type="a" TypeNotes="sss" e:dc="xx . . . Read full entry » Add an attributePosted 3/22/2013 10:02:06 AMI'm extending a schema. vsn 1.0 using oXygen, xerces parser main schema is in namespace ns1 I want to add an attribute group, all attributes in ns2 to give <a:element att1='x' b:att2='y'/> To keep it clean, I would like the attribute group to be defined in a second file and imported into th . . . Read full entry » Re: Redefinition of group, who's correctPosted 3/20/2013 9:59:12 PMIt has to be said that xs:redefine is underspecified in some respects. However, for this case the rule is fairly clear: Attribute group definitions and model group definitions must be supersets or subsets of their original definitions, either by including exactly one reference to themselves or . . . Read full entry » Re: Redefinition of group, who's correctPosted 3/20/2013 9:34:36 PMXMLSpy has a totally different interpretation of the schema 1.0 spec concerning xs:redefine. See e.g<http://lists.w3.org/Archives/Public/xmlschema-dev/2004Dec/0048.html> I have a had contact with Altova (the developers of XMLSpy) several times and their answer is something like "we are . . . Read full entry » RE: Redefinition of group, who's correctPosted 3/20/2013 8:49:13 PMSurprised there are people who still use XMLSpy. Are they not a dying breed? From: info@xml4pharma.com [mailto:info@xml4pharma.c&# . . . Read full entry » Re: Redefinition of group, who's correctPosted 3/20/2013 7:50:43 PMI tried your example in XMLBlueprint using Xerces2 and MSXML6: both XML processors say the schema is valid. However, in XMLSpy is get this error: "'essai' is already declared in schema document 'redefine.xd'. I don't know why XMLSpy is complaining. - Gerben Abbink Received on Wednesday, 20 . . . Read full entry » Re: Redefinition of group, who's correctPosted 3/20/2013 7:05:31 PMSince oXygen allows a choice of schema processors, it would be useful to say which one you selected (or to try more than one). It would also be useful to tell us what XMLSpy says is wrong - what is the error message? Michael Kay Saxonica On 20/03/2013 17:56, Pierre Attar wrote: > Hi, > & . . . Read full entry » Redefinition of group, who's correctPosted 3/20/2013 6:56:06 PMHi, I have a problem using group redefinitions and validating both with XMLSpy (who complains) and Oxygen (who validates). My question : who is correct ? Where a I wrong ? Note: my schema are a lot more complex but I try to make a sample (non realistic) in order to isolate my question. Here is . . . Read full entry » Re: Restriction errorPosted 3/20/2013 2:40:57 PMHi Dave, I cannot reproduce your error message in oXygen 14.2 (build 2013030817) with this schema: <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" xmlns:dc="http:/ . . . Read full entry » Re: Restriction errorPosted 3/20/2013 2:06:33 PMNote I'm the real newbie here Mike. On 20 March 2013 13:53, Michael Kay <mike@saxonica.com> wrote: > A complex-type-with-simple-content is generally defined by extension: think > of it as first defining the si . . . Read full entry » Re: Restriction errorPosted 3/20/2013 1:58:03 PMIgnore my previous response. It's probably this bug: https://saxonica.plan.io/issues/1698 which has been fixed in Saxon 9.4.0.7. Michael Kay Saxonica On 20/03/2013 13:03, Dave Pawson wrote: > Very new to xsd > > Schema part > <xs:complexType name="DCMIType"> > . . . Read full entry » Re: Restriction errorPosted 3/20/2013 1:53:56 PMA complex-type-with-simple-content is generally defined by extension: think of it as first defining the simple content of the element, then extending it to allow attributes. You can define a c-t-with-s-c as a restriction of another c-t-with-s-c, but that doesn't seem to be what you are doing he . . . Read full entry » Restriction errorPosted 3/20/2013 1:03:38 PMVery new to xsd Schema part <xs:complexType name="DCMIType"> <xs:simpleContent> <xs:restriction base="dc:SimpleLiteral"> <xs:simpleType> <<<<<<<<<<<<<<<<<<<<<<<<<&l . . . Read full entry » Re: TR: COSOLUCE : Urgent --> Problème de validation de schémaPosted 3/4/2013 11:58:01 PMOn Mon, Mar 04, 2013 at 08:18:18AM -0700, C. M. Sperberg-McQueen wrote: [...] > There are several measures you, or any software developer or user affected by > these issues can undertake. > > - You can and should set up and use some mechanism to allow the schema documents > in quest . . . Read full entry » AImWD-2013: Deadline extension and final CFPPosted 3/4/2013 3:17:49 PM---------------------------------------------------------------------- DEADLINE EXTENSION ---------------------------------------------------------------------- The paper submission deadline for AImWD-2013 has been extended to March 18, 2013. ------------------------------------------------------ . . . Read full entry » Re: TR: COSOLUCE : Urgent --> Problème de validation de schémaPosted 3/4/2013 3:07:46 PMIf my French is good enough, this message means there was an HTTP timeout fetching a resource. It's likely that the resource in question is http://www.w3.org/2001/xml.xsd. W3C has for the last year or two imposed an artificial delay on requests for common resources such as this, because its we . . . Read full entry » Re: TR: COSOLUCE : Urgent --> Problème de validation de schémaPosted 3/4/2013 8:18:18 AMThank you for your mail. (I regret that I am unable to respond in French; my apologies.) I wonder if the problem may be related to the measures W3C has undertaken to deal with the problem of excessive DTD and schema traffic [1, 2]. DTD and XSD resources change very slowly and can therefore be . . . Read full entry » TR: COSOLUCE : Urgent --> Problème de validation de schémaPosted 3/1/2013 1:08:04 PMMerci pour votre retour Voici la réponse de notre équipe réseau à ce sujet. Par la même occasion, pouvez-vous de votre côté tester la validation du schéma de ce fichier exemple (en pj) ? Encore merci Cordialement, [Julien Durand] Julien DURAND I Service Développement Techno . . . Read full entry » Re: Included <schema>Posted 2/27/2013 8:43:47 PMThanks George I join late this interesting discussion you initiated after our discussion on the problem of the *big* model S1000D+DITA. The presentation of that problem may give new inputs/thoughts to the discussion. The case is a model (schema) defining 1850 elements and 650 attributes. Such a . . . Read full entry » Re: Included <schema>Posted 2/27/2013 8:26:16 PMtext/html attachment: stored Received on Wednesday, 27 February 2013 19:26:45 GMT . . . Read full entry » Re: [ann] oXygen 14.2 comes with complete support for XML Schema 1.1Posted 2/27/2013 9:15:26 AMThank you David, We look forward to your feedback and we will be happy to offer oXygen licenses to XML Schema WG members that need one. We setup a webinar to cover the new XML Schema 1.1 support: https://www1.gotomeeting.com/register/167340249 This will be in three weeks from now, Wednesday, Mar . . . Read full entry » Re: Included <schema>Posted 2/26/2013 6:20:19 AMtext/html attachment: stored application/pdf attachment: Meta-models_S1000Dita.pdf application/octet-stream attachment: demoSample_14_-_POC_13.zip Received on Wednesday, 27 February 2013 06:53:00 GMT . . . Read full entry » RE: [ann] oXygen 14.2 comes with complete support for XML Schema 1.1Posted 2/21/2013 12:34:26 PMDear George: On behalf of the WG, thank you very much for the support in your fine product. I'll look forward to checking it out personally! Best regards, David Ezell (chair, Schema WG) -----Original Message----- From: George Cristian Bina [mailto:george@oxyge&# . . . Read full entry » XML Schema 1.1 TutorialPosted 2/19/2013 2:30:12 PMI wanted to share with everyone interested this tutorial on XML Schema 1.1 a while back, describing various new XML Schema 1.1 features with examples. https://blogs.oracle.com/rammenon/entry/xml_schema_11_what_you_need_to regards, Ram Received on Tuesday, 19 February 2013 22:30:39 GMT . . . Read full entry » Re: Can root name in DOCTYPE be a XSD-validity thing?Posted 2/18/2013 4:59:47 AMC. M. Sperberg-McQueen, Fri, 15 Feb 2013 08:15:39 -0700: > Just one slightly pedantic footnote: Great! :-) > On Feb 15, 2013, at 4:00 AM, Leif Halvard Silli wrote: > >> A doctype such as >> <!DOCTYPE TheDocumentElement SYSTEM "ID" [<!--bla, bla--&g . . . Read full entry » Re: Can root name in DOCTYPE be a XSD-validity thing?Posted 2/17/2013 11:33:32 PMOn Mon, 2013-02-18 at 04:59 +0100, Leif Halvard Silli wrote: > [...] > > Right. And as such, it is a very flexible system since it allows any > element to serve as root. What about XSD in this regard? Perhaps XSD > âhard codesâ which elements can serve as root element? Some i . . . Read full entry » Re: Can root name in DOCTYPE be a XSD-validity thing?Posted 2/17/2013 11:13:24 PMOn 2/17/2013 10:59 PM, Leif Halvard Silli wrote: > Right. And as such, it is a very flexible system since it allows any > element to serve as root. What about XSD in this regard? Perhaps XSD > âhard codesâ which elements can serve as root element? Nope. Actually, XSD doesn't provide . . . Read full entry » Re: Can root name in DOCTYPE be a XSD-validity thing?Posted 2/15/2013 12:00:26 PMC. M. Sperberg-McQueen, Thu, 14 Feb 2013 12:12:14 -0700: > On Feb 13, 2013, at 11:13 PM, Leif Halvard Silli wrote: >> Can a XSD-based processor validate that a XHTML5 document contains the >> HTML5 DOCTYPE type declaration? ⦠>> Note: The HTML5 DOCTYPE *declarati . . . Read full entry » Re: Can root name in DOCTYPE be a XSD-validity thing?Posted 2/15/2013 8:15:39 AMJust one slightly pedantic footnote: On Feb 15, 2013, at 4:00 AM, Leif Halvard Silli wrote: > A doctype such as > <!DOCTYPE TheDocumentElement SYSTEM "ID" [<!--bla, bla-->] > > allows to verify > > a) that the DOCTYPE declaration is internally valid, > . . . Read full entry » [ann] oXygen 14.2 comes with complete support for XML Schema 1.1Posted 2/14/2013 4:58:05 PMHi all, I am happy to announce that oXygen XML Editor 14.2 and oXygen XML Developer 14.2 are available from our website http://www.oxygenxml.com One of the major additions in version 14.2 is that oXygen finalizes its support for XML Schema 1.1. We also created a short video demo to cover this . . . Read full entry » Re: Can root name in DOCTYPE be a XSD-validity thing?Posted 2/14/2013 12:12:14 PMOn Feb 13, 2013, at 11:13 PM, Leif Halvard Silli wrote: > Hello schema devs. > > Can a XSD-based processor validate that a XHTML5 document contains the > HTML5 DOCTYPE type declaration? And can it do so without resorting > hacks? Can it be expressed in the XSD-language itself, . . . Read full entry » Re: Included <schema>Posted 2/14/2013 11:41:23 AMOn Feb 13, 2013, at 6:09 AM, Michael Kay wrote: > > On 13/02/2013 08:10, George Cristian Bina wrote: >> Thanks Henry, >> >> Regarding the lazy component construction my understanding of that was that during the schema creation when a module is read it may contain referen . . . Read full entry » Can root name in DOCTYPE be a XSD-validity thing?Posted 2/14/2013 7:13:35 AMHello schema devs. Can a XSD-based processor validate that a XHTML5 document contains the HTML5 DOCTYPE type declaration? And can it do so without resorting hacks? Can it be expressed in the XSD-language itself, or must the processor performa an initial 'DTD-mode' check? Note: The HTML . . . Read full entry » Re: Included <schema>Posted 2/13/2013 1:09:49 PMOn 13/02/2013 08:10, George Cristian Bina wrote: > Thanks Henry, > > Regarding the lazy component construction my understanding of that was > that during the schema creation when a module is read it may contain > references that cannot be be resolved at that time but they should . . . Read full entry » Re: Included <schema>Posted 2/13/2013 11:52:58 AMGeorge Cristian Bina writes: > Regarding the lazy component construction my understanding of that was > that during the schema creation when a module is read it may contain > references that cannot be be resolved at that time but they should > still be resolved when all the modules are . . . Read full entry » Re: Included <schema>Posted 2/13/2013 10:28:47 AMThanks Mike, Sometimes I know that I know something but I do not know how I got that knowledge and trying to get the relevant part of the spec if usually difficult. Probably a FAQ for XML Schema will help a lot, similar to what Dave Pawson did for XSLT. Best Regards, George -- George Cristian . . . Read full entry » Re: Included <schema>Posted 2/13/2013 10:10:56 AMThanks Henry, Regarding the lazy component construction my understanding of that was that during the schema creation when a module is read it may contain references that cannot be be resolved at that time but they should still be resolved when all the modules are read. This seems to be also wha . . . Read full entry » Re: Included <schema>Posted 2/12/2013 8:36:54 PMOn 12/02/2013 09:48, George Cristian Bina wrote: > Hello, > > I always thought that an included schema document may refer to > components that are defined in the including <schema> even if they are > not directly reachable if we start from the included schema. Yes, this is t . . . Read full entry » Re: Included <schema>Posted 2/12/2013 7:21:38 PMOn Tue, Feb 12, 2013 at 4:37 PM, George Cristian Bina <george@oxygenxml.com>wrote: > Yes, it is clear that m.xsd is invalid if we validate it standalone. I would like it to be believed like this. Henry T . . . Read full entry » Re: Included <schema>Posted 2/12/2013 4:28:43 PMHi George, The XSD 1.1 spec at the same place mentions only this, <quote> 1.2 It resolves to a <schema> element information item in a well-formed information set. </quote> The 1.1 spec doesn't say "which in turn corresponds to a valid schema." I think, with an XS . . . Read full entry » Re: Included <schema>Posted 2/12/2013 1:56:09 PMMukul Gandhi writes: > Hi George, > The XSD 1.1 spec at the same place mentions only this, > > <quote> > 1.2 It resolves to a <schema> element information item in a well-formed > information set. > </quote> > > The 1.1 spec doesn't say "which . . . Read full entry » Re: Included <schema>Posted 2/12/2013 1:07:12 PMHi Mukul, Thanks Mukul for pointing out that this part is removed in XML Schema 1.1. Yes, it is clear that m.xsd is invalid if we validate it standalone. The problem I have is if m.xsd should be considered invalid according to XML Schema 1.0 also when we start from test.xsd. Best Regards, Geor . . . Read full entry » Included <schema>Posted 2/12/2013 11:48:00 AMHello, I always thought that an included schema document may refer to components that are defined in the including <schema> even if they are not directly reachable if we start from the included schema. More clearly the following sample should be valid: test.xsd <xs:schema xmlns:xs=&qu . . . Read full entry » Re: Included <schema>Posted 2/12/2013 11:04:23 AMGeorge Cristian Bina writes: > I always thought that an included schema document may refer to > components that are defined in the including <schema> even if they are > not directly reachable if we start from the included schema. True, IMO. > Now, the spec says in http://www.w3 . . . Read full entry » [xmlschema-dev] <none>Posted 2/12/2013 4:06:10 AMHello! http://www.assuremag.com/gzb/wo4uw8esuk4x7vxxg0ssdb7tdvuxbg0/53fimapfi67no8o2f7wnh9k8i2mzq?4151h2x6blzk4ziqbgbiey1gu Received on Tuesday, 12 February 2013 12:06:43 GMT . . . Read full entry » My Brutal Experience...............................!!! Help Needed!!!Posted 2/9/2013 12:50:46 AMI really hope you get this fast. I could not inform anyone about our trip, because it was impromptu. we had to be in Philippines for a program. The program was successful, but our journey has turned sour. we misplaced our wallet and cell phone on our way back to the hotel we lodge in after we w . . . Read full entry » Re: keyref to a key in a different scopePosted 1/14/2013 9:45:16 PMHi George, As a workaround, with XSD 1.1 we can write an assertion on the complexType of element "parent" as follows: <xs:assert test="every $tst in test satisfies $tst/@ref = child/element/@id"/> This kind of simulates the keyref you've written. On Mon, Jan 14, 201 . . . Read full entry » Re: keyref to a key in a different scopePosted 1/14/2013 5:47:07 PMThank you Michael and Henry! Can you think of a real usecase for this? I encountered this in a user schema but I think that they had a different expectation from those constraints. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http . . . Read full entry » Re: keyref to a key in a different scopePosted 1/14/2013 3:57:09 PMOn 14/01/2013 15:47, George Cristian Bina wrote: > Thank you Michael and Henry! > Can you think of a real usecase for this? I don't think I've ever encountered a real use case for referential integrity that can't be satisfied by putting the key and the keyref declaration on the same elemen . . . Read full entry » keyref to a key in a different scopePosted 1/14/2013 3:16:20 PMHi all, I have problems identifying the relevant parts of the XML Schema spec that apply to the following example. There is a key defined on the "child" element selecting the "element/@id" attribute and a key reference defined on the "parent" element that specifies . . . Read full entry » Re: keyref to a key in a different scopePosted 1/14/2013 2:23:54 PMOn 14/01/2013 13:16, George Cristian Bina wrote: > Hi all, > > I have problems identifying the relevant parts of the XML Schema spec > that apply to the following example. You're not the only one. This bit of the spec is horrendous. I generally advise users against doing this. Fir . . . Read full entry » Re: keyref to a key in a different scopePosted 1/14/2013 1:59:00 PMGeorge Cristian Bina writes: > <xs:element name="child" maxOccurs="unbounded"> > <xs:complexType> > <xs:sequence maxOccurs="unbounded"> > <xs:element name="element"> > . . . Read full entry » Re: Simple node type with attributePosted 1/5/2013 5:49:54 PMOf course. This is known (clumsily) as a complex type with simple content, and a typical example is: <xs:element name="test"> <xs:annotation> <xs:documentation> ... </xs:documentation> </xs:annot . . . Read full entry » Simple node type with attributePosted 1/4/2013 4:40:36 PMHi, is possible to declare scheme for simple node type with attribute ? <ACTLOGLINE xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <ACTLOGLINE> <DTTIMESTAMP xsi:type="x . . . Read full entry » CFP: 2nd International Workshop on Artificial Intelligence meets the Web of Data (AImWD-2013)Posted 12/24/2012 4:40:50 PM**** Apologies for cross-posting **** **** Please, acknowledge this message to your colleagues **** ---------------------------------------------------------------------- CALL FOR PAPERS 2nd International Workshop on Artificial Intelligence meets the Web of Data (AImWD-2013) co-located with the . . . Read full entry » The datatypes schema has the XML declaration positioned after the DOCTYPE, it should occur before the DOCTYPEPosted 12/22/2012 6:38:49 PMHi Folks, In the datatypes schema: http://www.w3.org/TR/xmlschema-2/#schema the XML declaration is positioned after the DOCTYPE declaration. I believe that is incorrect. I believe that it should be positioned before the DOCTYPE declaration. /Roger Received on Saturday, 22 December 2012 18:39 . . . Read full entry » A practical example of why mixed="true" would be positioned on a complexContent element and not its parent complexType element?Posted 12/22/2012 4:38:03 PMHi Folks, This is a complexType with mixed content: <xs:complexType name="C1" mixed="true"> <xs:complexContent> ... </xs:complexContent> </xs:complexType> This is also a complexType with mixed content: <xs:c . . . Read full entry » Re: Equivalent ways to declare an element with string content and an attributePosted 12/18/2012 3:16:00 PM>Those are two equivalent ways of declaring an element with string content and an attribute. Careful! You are using the word "equivalent" to mean that if an instance is valid under one schema then it is valid under the other, and vice versa. But schemas are not just about validati . . . Read full entry » Equivalent ways to declare an element with string content and an attributePosted 12/18/2012 12:41:58 PMHi Folks, Suppose that you want to create a <comment> element. Its content is string data and it has an attribute, xml:lang. Here is a sample instance: <comment xml:lang="en">This is a comment</comment> One way to declare the <comment> element is as a comp . . . Read full entry » ANN: Updated XML Schema 1.1 TutorialPosted 12/14/2012 9:16:25 PMHi Folks, In the last two weeks I have twice taught a 3-day class on XML Schema 1.1 In the process of teaching the classes I discovered a way to present the material in a way that makes it *much* easier to learn the material -- using lots of intuitive diagrams. I am excited about this approach. . . . Read full entry » Re: A practical use case for a fixed ID attribute?Posted 12/10/2012 2:52:39 PMOn Dec 8, 2012, at 5:56 AM, Costello, Roger L. wrote: > Hi Folks, > > In XML Schema 1.1 it is possible to declare an attribute of type ID and fix its value. For example: > > <attribute name="instructor" type="ID" fixed="Professor-Johnson" /> &g . . . Read full entry » Re: A practical use case for a fixed ID attribute?Posted 12/9/2012 12:56:20 PMOrthogonality is important in language design. You shouldn't impose restrictions just because you think something isn't useful. Is it useful to be able to write $x+0, or $x*1? Probably not, but it would be wrong to have a rule that prevents it. So preventing use of "fixed" for one par . . . Read full entry » Re: A practical use case for a fixed ID attribute?Posted 12/8/2012 2:23:26 PMOn Sat, 2012-12-08 at 12:56 +0000, Costello, Roger L. wrote: > Hi Folks, > > In XML Schema 1.1 it is possible to declare an attribute of type ID > and fix its value. It was/is possible to do this with a DTD, too. It's useful e.g. for a version attribute <!ATTLIST sock-weaving-pa . . . Read full entry » A practical use case for a fixed ID attribute?Posted 12/8/2012 12:56:09 PMHi Folks, In XML Schema 1.1 it is possible to declare an attribute of type ID and fix its value. For example: <attribute name="instructor" type="ID" fixed="Professor-Johnson" /> Yesterday I showed that example to my class and they challenged me on the usefulne . . . Read full entry » Re: A practical use case for a fixed ID attribute? (UNCLASSIFIED)Posted 12/8/2012 9:46:46 AMClassification: UNCLASSIFIED Roger, A schema can be written to specify a subset to an existing grammar specified by either an instance or separate schema. In this case a larger structure may already be defined. For the sake of argument lets say XHTML. You need to supply a model for a form that . . . Read full entry » Re: A practical use case for a fixed ID attribute?Posted 12/8/2012 8:24:39 AMAt 2012-12-08 12:56 +0000, Costello, Roger L. wrote: >In XML Schema 1.1 it is possible to declare an attribute of type ID >and fix its value. For example: > ><attribute name="instructor" type="ID" fixed="Professor-Johnson" /> > >Yesterday I sho . . . Read full entry » Re: The <xs:assert> element cannot use inheritable attributes?Posted 12/7/2012 10:16:30 AMInherited attributes are a very limited feature. They were introduced to meet a very specific use case related to xml:lang. xml:lang is related to internationalization, and anything related to internationalization in W3C is highly political, which means that you often end up with technical fea . . . Read full entry » The <xs:assert> element cannot use inheritable attributes?Posted 12/7/2012 9:45:16 AMHi Folks, It is my understanding that <xs:assert> elements cannot use inheritable attributes (that is, the xpath expression in the <xs:assert> element's @test attribute cannot reference attributes declared with inheritable="true"). Only <xs:alternative> elements ca . . . Read full entry » Re: Test suite?Posted 12/3/2012 6:05:13 PMI have sent a copy of Saxon's test driver off-list. Michael Kay Saxonica On 03/12/2012 16:56, Casey Jordan wrote: > Thanks Michael, > > Do you know if there is a Java test runner for this suite available > somewhere. I see the format is fairly easy to work with, but I don't > . . . Read full entry » Re: Determining what facets can operate on what datatype.Posted 12/3/2012 5:05:11 PMAwesome, exactly what I was looking for. Thanks! On Mon, Dec 3, 2012 at 5:00 PM, C. M. Sperberg-McQueen < cmsmcq@blackmesatech.com> wrote: > > On Dec 3, 2012, at 2:18 PM, Casey . . . Read full entry » Re: Test suite?Posted 12/3/2012 4:44:23 PMOn 03/12/2012 16:27, Casey Jordan wrote: > I should note that I did find the XML schema 1.0 tests here: > http://www.w3.org/XML/2004/xml-schema-test-suite/index.html#releases > > If there are the most up to date resources then I will use them. > That page needs updating (and we ne . . . Read full entry » Re: Determining what facets can operate on what datatype.Posted 12/3/2012 4:30:39 PMAnd in the same vein, the definition for enumeration, indicates to me that it accepts any type, even user defined ones: "*enumeration* does not impose an order relation on the value space<http://www.w3.org/TR/2001/PR-xmlschema-2-20010330/#dt-value-space> it creates; the value of the ord . . . Read full entry » Determining what facets can operate on what datatype.Posted 12/3/2012 4:18:20 PMAs I dig deeper into the spec I am finding it hard to easily determine what facets are compatible with what datatypes. For instance, the definition of length: "For string and datatypes derived from string, length is measured in units of characters as defined in [XML 1.0 (Second Edition)]. For . . . Read full entry » Re: Determining what facets can operate on what datatype.Posted 12/3/2012 3:00:26 PMOn Dec 3, 2012, at 2:18 PM, Casey Jordan wrote: > As I dig deeper into the spec I am finding it hard to easily determine what facets are compatible with what datatypes. For instance, the definition of length: > > "For string and datatypes derived from string, length is measured in . . . Read full entry » Re: Test suite?Posted 12/3/2012 11:56:42 AMThanks Michael, Do you know if there is a Java test runner for this suite available somewhere. I see the format is fairly easy to work with, but I don't want to re-invent the wheel if I don't have to. Thanks, Casey On Mon, Dec 3, 2012 at 11:44 AM, Michael Kay <mike@sax . . . Read full entry » Re: Test suite?Posted 12/3/2012 11:27:17 AMI should note that I did find the XML schema 1.0 tests here: http://www.w3.org/XML/2004/xml-schema-test-suite/index.html#releases If there are the most up to date resources then I will use them. Thanks, Casey On Mon, Dec 3, 2012 at 11:22 AM, Casey Jordan <casey.jordan@jo� . . . Read full entry » Test suite?Posted 12/3/2012 11:22:26 AMIs there an available test suite for XML Schema 1.1? I am developing a java application and it would be great to be able to test my schema code against a standard resource. Thanks, Casey -- -- Casey Jordan easyDITA a product of Jorsek LLC "CaseyDJordan" on LinkedIn, Twitter & Fac . . . Read full entry » No declaration for "restriction" in the DTD for XML Schema 1.1Posted 12/2/2012 1:34:00 PMHi Folks, Appendix I in the Structures specification has the DTD for XML Schema [1]. I see the declaration for the "extension" element. I don't see the declaration for the "restriction" element. Is that a mistake or am I simply overlooking it? /Roger [1] http://www.w3.org/ . . . Read full entry » Re: No declaration for "restriction" in the DTD for XML Schema 1.1Posted 12/2/2012 12:42:56 PMOn Dec 2, 2012, at 6:34 AM, Costello, Roger L. wrote: > Hi Folks, > > Appendix I in the Structures specification has the DTD for XML Schema [1]. > > I see the declaration for the "extension" element. > > I don't see the declaration for the "restriction" . . . Read full entry » Re: xsd validation bug in scxml? cvc-complex-type.2.4.bPosted 11/24/2012 10:06:19 PMThis is what Saxon has to say about the schema at http://www.w3.org/2011/04/SCXML/scxml.xsd Error on line 281 of scxml-module-core.xsd: Error in complex type scxml.if.type: Ambiguous content model, element <Q{.../scxml}cancel> appears in its own right, and also matches an <xs:any& . . . Read full entry » Re: xsd validation bug in scxml? cvc-complex-type.2.4.bPosted 11/24/2012 9:42:58 PMThe xsd is the scxml official one. I have copied in local and fixed like I said because the error is with the Eclipse xsd validator. Thanks a lot. El 24/11/2012 20:35, "Henry S. Thompson" <ht@inf.ed.ac.uk> . . . Read full entry » Re: xsd validation bug in scxml? cvc-complex-type.2.4.bPosted 11/24/2012 8:44:42 PMht writes: > Fix your schema, and the problem will go away. I should have added, that the _comment_ against the definition of the group called scxml.extra.content, which says "group allowing elements from other namespaces" is at odds with the actual wildcard which appears in it, n . . . Read full entry » Re: xsd validation bug in scxml? cvc-complex-type.2.4.bPosted 11/24/2012 8:35:28 PMYour problem is probably that arising because your schema is invalid per XML Schema 1.0 (it's full of violations of the Unique Particle Attribution constraint, informally known as the "no non-determinism constraint"), http://www.w3.org/2011/04/SCXML/scxml-module-core.xsd:257:2: Invali . . . Read full entry » xsd validation bug in scxml? cvc-complex-type.2.4.bPosted 11/24/2012 1:45:12 PMHi, I'm validating a scxml and getting a validation error which I don't think it is. The xml extract is: <scxml xmlns="http://www.w3.org/2005/07/scxml" xmlns:a=" http://www.nosolojava.com/android.scxml" xmlns:xmpp="http://www.nosolojava.com/xmpp.scxml" ver . . . Read full entry » Re: Does anyone have a transform to change comments into annotations in an existing schema?Posted 11/21/2012 4:37:31 PMOn Wed, Nov 21, 2012 at 4:14 PM, Loren Cahlander <loren.cahlander@gmail.com> wrote: > Thanks! I will try that. > Just noted my stylesheet was too simplistic as the comments precede the element they relate to in the example u g . . . Read full entry » Re: Does anyone have a transform to change comments into annotations in an existing schema?Posted 11/21/2012 4:03:14 PMOn Wed, Nov 21, 2012 at 4:01 PM, Ihe Onwuka <ihe.onwuka@gmail.com> wrote: > On Wed, Nov 21, 2012 at 3:45 PM, Loren Cahlander > <loren.cahlander@gmail.com> wrote: & . . . Read full entry » Re: Does anyone have a transform to change comments into annotations in an existing schema?Posted 11/21/2012 4:01:50 PMOn Wed, Nov 21, 2012 at 3:45 PM, Loren Cahlander <loren.cahlander@gmail.com> wrote: > I am looking to transform comments that precede an element and make those > comments as an annotation for that element. > > for example: . . . Read full entry » Re: Does anyone have a transform to change comments into annotations in an existing schema?Posted 11/21/2012 3:00:30 PMAt 2012-11-21 13:10 -0600, Loren Cahlander wrote: >That fixed it. I have added some additional code including calling >normalize-space() to strip leading and trailing spaces from the comments. Because of the repetition you have, you may find the (not yet checked for typos) version of your . . . Read full entry » Re: Does anyone have a transform to change comments into annotations in an existing schema?Posted 11/21/2012 2:11:03 PMThanks! On Nov 21, 2012, at 2:00 PM, "G. Ken Holman" <gkholman@CraneSoftwrights.com> wrote: > At 2012-11-21 13:10 -0600, Loren Cahlander wrote: >> . . . Read full entry » Re: Does anyone have a transform to change comments into annotations in an existing schema?Posted 11/21/2012 1:10:36 PMThat fixed it. I have added some additional code including calling normalize-space() to strip leading and trailing spaces from the comments. <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs= . . . Read full entry » Re: Does anyone have a transform to change comments into annotations in an existing schema?Posted 11/21/2012 12:58:38 PMAt 2012-11-21 11:10 -0600, Loren Cahlander wrote: >The current contents of the xs:element were not copied when the >annotation was added. Yep! You're right! There is one line missing. I hope the stylesheet below helps. That's what I get for throwing something together without testing . . . Read full entry » Re: Does anyone have a transform to change comments into annotations in an existing schema?Posted 11/21/2012 11:10:19 AMThe current contents of the xs:element were not copied when the annotation was added. On Nov 21, 2012, at 10:09 AM, G. Ken Holman <gkholman@cranesoftwrights.com> wrot . . . Read full entry » Re: Does anyone have a transform to change comments into annotations in an existing schema?Posted 11/21/2012 11:09:52 AMSomething similar to the following should work for you: <?xml version="1.0" encoding="US-ASCII"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" version= . . . Read full entry » Re: Does anyone have a transform to change comments into annotations in an existing schema?Posted 11/21/2012 10:14:29 AMThanks! I will try that. On Nov 21, 2012, at 10:03 AM, Ihe Onwuka <ihe.onwuka@gmail.com> wrote: > On Wed, Nov 21, 2012 at 4:01 PM, Ihe Onwuka <ihe.onwuka@gmail.com& . . . Read full entry » Does anyone have a transform to change comments into annotations in an existing schema?Posted 11/21/2012 9:45:13 AMI am looking to transform comments that precede an element and make those comments as an annotation for that element. for example: <!-- Information about foo --> <xs:element name="foo-group"> . . . </xs:element> to <xs:element name="foo-group"> <x . . . Read full entry » Re: Restrict <CRLF> to the value \r\n ... the instance is <CRLF>\r\n</CRLF> ... error on validation -- why?Posted 10/24/2012 4:15:19 PMOn Oct 24, 2012, at 7:32 AM, Michael Kay wrote: > The Xerces parser is reporting the value of the "value" attribute to > Saxon as two spaces. (The debugger also shows a private field > indicating that the unnormalized value of the attribute is > "&CR;&LF;" . . . Read full entry » RE: Restrict <CRLF> to the value \r\n ... the instance is <CRLF>\r\n</CRLF> ... error on validation -- why?Posted 10/24/2012 3:03:35 PMWith this example you also have to consider the XML processor's handling of end-of-line characters in the instance document. http://www.w3.org/TR/REC-xml/#sec-line-ends Pete Geraghty From: Sandy Gao [mailto:sandygao@ca.ibm.co&# . . . Read full entry » Re: Restrict <CRLF> to the value \r\n ... the instance is <CRLF>\r\n</CRLF> ... error on validation -- why?Posted 10/24/2012 2:32:29 PMThe Xerces parser is reporting the value of the "value" attribute to Saxon as two spaces. (The debugger also shows a private field indicating that the unnormalized value of the attribute is "& CR;& LF;" without the spaces. So it's XML attribute value normalization th . . . Read full entry » Restrict <CRLF> to the value \r\n ... the instance is <CRLF>\r\n</CRLF> ... error on validation -- why?Posted 10/24/2012 12:55:10 PMHello Folks, The following schema declares two ENTITIES, one for carriage return and one for line feed. And then it restricts the value of the <CRLF> element by referencing those ENTITIES. ------------------------------------------------- CRLF.xsd --------------------------- . . . Read full entry » Re: Restrict <CRLF> to the value \r\n ... the instance is <CRLF>\r\n</CRLF> ... error on validation -- why?Posted 10/24/2012 9:53:27 AM> So it's XML attribute value normalization that's to blame. Yes. See section 3.3.3 in the XML spec, especially the example at the end of that section. http://www.w3.org/TR/REC-xml/#AVNormalize Thanks, Sandy Gao IBM Canada (1-905) 413-3255 T/L 313-3255 sandygao@ca. . . . Read full entry » Re: Three equivalent ways to specify an unconstrained data type ... are there others?Posted 10/21/2012 5:35:19 PMThe three types have the same value space, but they are not equivalent in other ways. For example, an element of type xs:NCName can appear in the substitution group of E1 but not of E2. Michael Kay Saxonica On 20/10/2012 13:04, Costello, Roger L. wrote: > Hi Folks, > > Below are declar . . . Read full entry » [Summary] Equivalent ways to specify an unconstrained data typePosted 10/21/2012 11:28:29 AMThanks Ken and Mukul. Great! Recap: Below are 5 equivalent ways to specify an unconstrained string. All of these forms, except the form using mixed content, can be used with the other data types as well. Thus there are 4 equivalent ways to create an unconstrained integer, 4 equivalent ways to cre . . . Read full entry » Re: Three equivalent ways to specify an unconstrained data type ... are there others?Posted 10/21/2012 9:48:35 AMThis is possibly one more way, <xs:simpleType name="t-unconstrained-string"> <xs:union memberTypes="xs:string"/> </xs:simpleType> On Sat, Oct 20, 2012 at 5:34 PM, Costello, Roger L. <costello@mitre.or . . . Read full entry » Re: Three equivalent ways to specify an unconstrained data type ... are there others?Posted 10/20/2012 4:19:58 PMG. Ken Holman wrote: > Just a simple 3-line batch file that invokes one batch file for > each of the three processors That's what I guessed, but just in case there was more... > XJParse for Xerces At least I learned something, I didn't know XJParse ;-) Thanks, -- Florent George . . . Read full entry » Re: Three equivalent ways to specify an unconstrained data type ... are there others?Posted 10/20/2012 4:03:08 PMG. Ken Holman wrote: Hi, > t:\ftemp>w3cschema roger.xsd roger.xml I find that part particularly interesting ;-) Is "w3cschema" a script of your own, or a kind of standard bundle that can be downloaded to validate a schema and an instance with different processors? Regards . . . Read full entry » Re: Three equivalent ways to specify an unconstrained data type ... are there others?Posted 10/20/2012 12:07:59 PMAt 2012-10-20 16:03 +0100, Florent Georges wrote: >G. Ken Holman wrote: > > > Hi, > > t:\ftemp>w3cschema roger.xsd roger.xml > > I find that part particularly interesting ;-) Is "w3cschema" a > script of your own, or a kind of standard bundle that can b . . . Read full entry » Three equivalent ways to specify an unconstrained data type ... are there others?Posted 10/20/2012 12:04:19 PMHi Folks, Below are declarations of three elements, E1, E2, and E3. All three elements have the same data type: an unconstrained string. All other data types (boolean, integer, etc.) can be similarly specified. Thus there are 3 ways to specify the same thing for every built-in data type. Can you . . . Read full entry » XML Schema ChecklistPosted 10/20/2012 11:19:37 AMHi Folks, Before publishing your XML Schemas, check that they contains these 4 things: 1. xml:lang 2. xml:id 3. pattern facets 4. user-defined entities More ... http://www.xfront.com/XML-Schema-Checklist.pdf Comments welcome. /Roger Received on Saturday, 20 October 2012 11:20:05 GMT . . . Read full entry » Re: Three equivalent ways to specify an unconstrained data type ... are there others?Posted 10/20/2012 10:16:16 AMAt 2012-10-20 12:04 +0000, Costello, Roger L. wrote: >Hi Folks, > >Below are declarations of three elements, E1, E2, and E3. All three >elements have the same data type: an unconstrained string. All other >data types (boolean, integer, etc.) can be similarly specified. Thus >th . . . Read full entry » Re: XML Schema ChecklistPosted 10/20/2012 7:55:45 AMAll XML Schemas should also be properly annotated: <xsd:annotation> <xsd:documentation>This version adds the ability to specify the URI to an XML Schema for parameters and return values</xsd:documentation> </xsd:annotation> It is very helpful to anyone looking at an XM . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/18/2012 8:27:18 PMOriginal Message From: "C. M. Sperberg-McQueen" > If you don't see that the counter implementation you propose can > be regarded as an implementation of the FSA I described, I don't > think I know how to help you. I think I can claim Godwin's on that!!! I think again we have a . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/18/2012 5:45:14 PMOriginal Message From: "C. M. Sperberg-McQueen" > On Oct 18, 2012, at 9:05 AM, Pete Cordell wrote: >> Original Message From: "C. M. Sperberg-McQueen" >> >>> - While enumerating 24! or 120! disjuncts in a large regular expression >>> or content mo . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/18/2012 4:15:05 PMMichael, I'm sure that you prove mathematically, if you put your mind to it, that a Turing machine (or even a Java compiler...) is a conformant XML Schema processor. But there are users out there who have practical problems to solve, and I'm trying to help them... Michael Kay On 18/10/2012 14 . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/18/2012 4:05:25 PMOriginal Message From: "C. M. Sperberg-McQueen" > - While enumerating 24! or 120! disjuncts in a large regular expression > or content model whose top-level operator is choice may > exceed current engineering capacity, it is not beyond the wit of > human beings or the memory . . . Read full entry » Re: union is not a union, it's a sequencePosted 10/18/2012 2:15:19 PMWell, you have defined two value spaces: strings consisting entirely of printable characters, and strings consisting entirely of whitespace characters. The union of those two value spaces is (strings that consist entirely of printable characters or entirely of whitespace characters). A string t . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/18/2012 1:03:42 PMOn Thu, 2012-10-18 at 09:48 +0100, Michael Kay wrote: > In practice, enumerating the different permutations to permit all > possible orderings of 24 elements, some of which can be repeated, is > impossible on the kind of computers that are available for purchase > today, whatever th . . . Read full entry » union is not a union, it's a sequencePosted 10/18/2012 12:44:42 PMHi Folks, Proposition: A union of member types does not produce a union, it produces a sequence of member types. Proof: <xs:simpleType name="white-space-characters"> <xs:annotation> <xs:documentation> The . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/18/2012 11:17:48 AMOn Oct 18, 2012, at 10:45 AM, Pete Cordell wrote: > Original Message From: "C. M. Sperberg-McQueen" >> On Oct 18, 2012, at 9:05 AM, Pete Cordell wrote: >>> Original Message From: "C. M. Sperberg-McQueen" >>> >>>> - While enumerating 24! . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/18/2012 10:50:21 AMOn Oct 18, 2012, at 9:15 AM, Michael Kay wrote: > Michael, I'm sure that you prove mathematically, if you put your mind to it, that a Turing machine (or even a Java compiler...) is a conformant XML Schema processor. But there are users out there who have practical problems to solve, and I'm tr . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/18/2012 10:03:03 AMOn Oct 18, 2012, at 9:05 AM, Pete Cordell wrote: > Original Message From: "C. M. Sperberg-McQueen" > >> - While enumerating 24! or 120! disjuncts in a large regular expression >> or content model whose top-level operator is choice may >> exceed current engineeri . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/18/2012 9:48:37 AM>I agree that it is often difficult, and the result is almost never easy to read and understand. But I do not believe it is ever impossible. Depends whether your definition of "impossible" is a mathematical definition or an engineering definition. In practice, enumerating the diff . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/18/2012 7:30:08 AMOn Oct 18, 2012, at 2:48 AM, Michael Kay wrote: > >I agree that it is often difficult, and the result is almost never easy to read and understand. But I do not believe it is ever impossible. > > Depends whether your definition of "impossible" is a mathematical definition or . . . Read full entry » Re: What is the namespace for XSD1.1?Posted 10/17/2012 10:12:46 PMFred, It's the same namespace as 1.0, so that (almost) all 1.0 schemas continue to be good 1.1 schemas. The "1.1 mode" is not turned on by using a different namespace. You'll likely need to configure the schema process (e.g. set a property) to achieve that. Thanks, Sandy Gao IBM Canad . . . Read full entry » Re: What is the namespace for XSD1.1?Posted 10/17/2012 10:12:43 PMThe namespace is unchanged. New processors will recognize the new features, and old ones won't. In general, XSD 1.0 schemas are also XSD 1.1 schemas. Noah On 10/17/2012 9:19 PM, Fred Li wrote: > Hi experts, > > I appreciate all the answers you provided to my question about the use > . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/17/2012 8:51:36 PMOn Oct 17, 2012, at 8:39 AM, George Cristian Bina wrote: > Expression every possible permutation does not generally work as you will get a lot of errors from the unique particle attribution rule that will not allow you to say for example > (a, b, x) | (a, b, y) > forcing you to write &g . . . Read full entry » Re: XSD 1.1: not okay to have an xs:assert at the attribute level?Posted 10/17/2012 6:39:49 PMSorry for the delay in responding to this. It's a Saxon bug which I have logged at https://saxonica.plan.io/issues/1637 and a patch will be in the next maintenance release. I am adding the test case to the W3C XSD 1.1 test suite. Michael Kay Saxonica On 23/09/2012 12:55, Costello, Roger L. w . . . Read full entry » What is the namespace for XSD1.1?Posted 10/17/2012 6:19:12 PMHi experts, I appreciate all the answers you provided to my question about the use of order indicators in the XSD file, and I am happy to know that there is no maxOccurs restrictions on "all" in XSD1.1, so the problem I mentioned is not a problem any more with XSD1.1. Now my question is . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/17/2012 5:39:44 PMExpression every possible permutation does not generally work as you will get a lot of errors from the unique particle attribution rule that will not allow you to say for example (a, b, x) | (a, b, y) forcing you to write (a, b, (x | y)) instead. However, for a complex model getting the right . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/17/2012 4:33:29 PMAh yes, I was looking at the restrictions on xs:all cardinality itself, not the elements within it. Panic over!!! Thanks. So in summary, for XSD 1.1 you can do: <xs:all> <xs:element ref="a" minOccurs="0" maxOccurs="unbounded"/> <xs:element r . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/17/2012 4:18:24 PMAt 2012-10-16 15:13 -0700, Fred Li wrote: >Hi XML experts, > >I have a problem about the use of order indicators in the creation of >XML schema (.xsd file). As I learned from W3School >(http://www.w3schools.com/schema/schema_complex_indicators.asp), we >have 3 order indicators in . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/17/2012 4:16:33 PMOK, some of the restrictions were lifted but not all. Essentially, you still can't mix all/sequence/choice in the same content model. So if you use xs:all, it has to be at the top level and can itself only occur once. But the element and wildcard particles within xs:all can now have arbitrary m . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/17/2012 4:04:17 PMOriginal Message From: "Michael Kay" > On 17/10/2012 15:35, Pete Cordell wrote: >> Can't believe they didn't fix the restrictions on xs:all in XSD >> 1.1!!!!!! :-( >> > They did. I'm looking at: http://www.w3.org/TR/xmlschema11-1/#declare-contentModel It says: . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/17/2012 3:46:41 PMOn 17/10/2012 15:35, Pete Cordell wrote: > Can't believe they didn't fix the restrictions on xs:all in XSD > 1.1!!!!!! :-( > They did. Michael Kay Saxonica Received on Wednesday, 17 October 2012 14:47:12 GMT . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/17/2012 3:45:49 PMOn 16/10/2012 23:13, Fred Li wrote: > Hi XML experts, > > I have a problem about the use of order indicators in the creation of > XML schema (.xsd file). As I learned from W3School > (http://www.w3schools.com/schema/schema_complex_indicators.asp), we > have 3 order indicators in . . . Read full entry » Re: Order indicators in the .xsd filePosted 10/17/2012 3:35:46 PMCan't believe they didn't fix the restrictions on xs:all in XSD 1.1!!!!!! :-( Pete Cordell Codalogic Ltd Twitter: http://twitter.com/petecordell Interface XML to C++ the easy way using C++ XML data binding to convert XSD schemas to C++ classes. Visit http://codalogic.com/lmx/ or http://www.xml2cp . . . Read full entry » Re: "Unsafe" union?Posted 10/16/2012 3:15:17 PMThe principle of type safety is the rule that if X is substitutable for Y (i.e. an instance of type X can be supplied where an instance of type Y is expected), then every valid instance of X must be a valid instance of Y. if you define a union type U as union of xs:date and xs:dateTime, then x . . . Read full entry » Order indicators in the .xsd filePosted 10/16/2012 3:13:51 PMHi XML experts, I have a problem about the use of order indicators in the creation of XML schema (.xsd file). As I learned from W3School (http://www.w3schools.com/schema/schema_complex_indicators.asp), we have 3 order indicators in the XML Schema language: All - the child elements can appear in . . . Read full entry » "Unsafe" union?Posted 10/16/2012 11:08:07 AMHi Folks, The XPath 3.0 specification has this statement: The current (second) edition of XML Schema 1.0 contains an error in respect of the substitutability of a union type by one of its members: it fails to recognize that this is unsafe if the union is derived by restric . . . Read full entry » Here's how to empower instance document authors to create their own root elementPosted 10/14/2012 12:59:49 PMHi Folks, It is not necessary to declare a root element in your XML Schema. You can empower instance document authors to create their own root element. Here's how: 1. In the XML Schema create a complexType for the root element, but don't declare a root element. 2. Instance document authors creat . . . Read full entry » Re: Here's how to empower instance document authors to create their own root elementPosted 10/14/2012 12:35:19 PMOn 10/14/2012 8:59 AM, Costello, Roger L. wrote: > It is not necessary to declare a root element in your XML Schema. You can empower instance document authors to create their own root element. Right, or you can explicitly declare several root elements, and let your users use any one as a root . . . Read full entry » Re: Element name replacementPosted 10/12/2012 3:09:17 PMAn XML Schema can tell you that your document is invalid, but there is nothing in XSD that helps you repair it when it isn't. For HTML there are tools such as HTMLTidy that attempt to do this: see http://tidy.sourceforge.net Michael Kay Saxonica On 12/10/2012 10:10, salma.siddiqa wrote: > H . . . Read full entry » Re: Request for schema namespace 1.1Posted 10/12/2012 3:07:08 PMPlease tell us exactly what you did and exactly what error you got, and then we can tell you exactly what you did wrong. Michael Kay Saxonica On 11/10/2012 23:17, Srividya Chilakamarri wrote: > Hi, > > I have a scenario as you guys answered > http://lists.w3.org/Archives/Public/xmlsc . . . Read full entry » Element name replacementPosted 10/12/2012 2:40:42 PMHi, I am new to XSD, I went through your blog would you kindly help me. I want to generate an xsd which will validate an xml. The xml file is the html converted file and hence has html tags I want to validate the tag Hierarchy Eg: if the <p> tag has <div> tags within it then replace the . . . Read full entry » Request for schema namespace 1.1Posted 10/11/2012 3:17:05 PMHi, I have a scenario as you guys answered http://lists.w3.org/Archives/Public/xmlschema-dev/2010Jan/0029.html I would like to validate my xml schema against my xml document. What are the namespaces that I need to use as it throws a message * http://www.w3.org/2001/XMLSchema">* to use o . . . Read full entry » Re: Treatement of whitespace in enumerationsPosted 10/8/2012 5:11:03 PMwrt this question, you recently wrote on xsl-list that you further had a schema declaration as follows: <xsd:element name="propertySubType" type="PropertySubTypeList"/> <xsd:simpleType name="PropertySubTypeList"> <xsd:list itemType="PropertySub . . . Read full entry » Re: Treatement of whitespace in enumerationsPosted 10/8/2012 10:45:01 AMThe error is probably in the part of the code that you haven't shown us. Can you reduce it to a complete but minimal working example? Michael Kay Saxonica On 06/10/2012 14:31, Ihe Onwuka wrote: > I have an restriction by enumeration as follows > > <xsd:simpleType name="PropertyS . . . Read full entry » Treatement of whitespace in enumerationsPosted 10/6/2012 2:31:16 PMI have an restriction by enumeration as follows <xsd:simpleType name="PropertySubType"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="Cold Store"/> <xsd:enumeration value="Data Centre"/> . . . Read full entry » [ANN] Definitive XML Schema, 2nd edition has been releasedPosted 9/26/2012 1:41:52 PMHello all, Just wanted to let you know that the second edition of my book Definitive XML Schema was released last week. It was updated to cover all XML Schema 1.1 features. Because I thought it might take some time for people to transition over to 1.1, and because some readers may just want to k . . . Read full entry » Re: XSD 1.1: not okay to have an xs:assert at the attribute level?Posted 9/24/2012 6:07:58 PM>I have never had to co-locate the namespace declaration like this. Should this be considered a bug in the XML Schema validator that I am using? Sorry for the delay in responding. Yes, I think it's a Saxon bug. The specs may not be 100% definitive on the point, but it's normal practice whe . . . Read full entry » RE: XSD 1.1: not okay to have an xs:assert at the attribute level?Posted 9/24/2012 4:30:15 PM> Do you still get those errors if you copy the namespace declaration > for 'xsd' onto the Rule element? Ah! When I move the namespace declaration to the Rule element: <Test > <Rule xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="xsd:element" /> . . . Read full entry » Re: XSD 1.1: not okay to have an xs:assert at the attribute level?Posted 9/24/2012 9:11:20 AMHi Roger, I was using Xerces. If you model the schema little differently, it can be more correct than what I posted last. Here's the modified schema design that I would propose, for this use case: New XML document: <Test xsdNs="http://www.w3.org/2001/XMLSchema"> <Rule na . . . Read full entry » Re: XSD 1.1: not okay to have an xs:assert at the attribute level?Posted 9/23/2012 10:29:14 PMHi Roger, The following <assert>, <xsd:assert test="QName('http://www.w3.org/2001/XMLSchema', string(@name)) eq xsd:QName('xsd:element')"/> seems to give me the result that you want. On Sun, Sep 23, 2012 at 9:03 PM, Costello, Roger L. <costello@mi . . . Read full entry » RE: XSD 1.1: not okay to have an xs:assert at the attribute level?Posted 9/23/2012 9:39:49 PM> <xsd:assert test="QName('http://www.w3.org/2001/XMLSchema', > string(@name)) eq xsd:QName('xsd:element')"/> Nice work Mukul. You used XERCES, right? I tried that with SAXON and got errors. So either XERCES is accepting as valid something that it shouldn't . . . Read full entry » Re: XSD 1.1: not okay to have an xs:assert at the attribute level?Posted 9/23/2012 8:41:59 PMHi Roger, I observe following results with Xerces XSD 1.1 validator: I get a 'false' <assert> result, with the way you've specified the first variant of your assertion (i.e, an <assert> failure similar to Saxon. but not the namespace prefix error). When I change the assertion to fo . . . Read full entry » Re: XSD 1.1: not okay to have an xs:assert at the attribute level?Posted 9/23/2012 3:54:54 PMOn Sep 23, 2012, at 5:55 AM, Costello, Roger L. wrote: > ... > > I validated the XML document using SAXON 9.4 and got these two errors: > > (1) Namespace prefix {xsd} has not been declared > > (2) Element Rule does not satisfy assertion @name eq xsd:QName('xsd:element' . . . Read full entry » RE: XSD 1.1: not okay to have an xs:assert at the attribute level?Posted 9/23/2012 3:33:13 PMHello Mukul, > <xsd:assert test="string(@name) eq 'xsd:element'" /> That's a good idea, but the value of @name is not a string, it is a QName. Thus, I should be able to change the namespace prefix: <xsd:assert test="string(@name) eq 'xs:element'" . . . Read full entry » XSD 1.1: not okay to have an xs:assert at the attribute level?Posted 9/23/2012 11:55:32 AMHello Folks, For this XML document: <Test xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <Rule name="xsd:element" /> </Test> I want an xs:assert element to test that the name attribute has the QName value xsd:element I placed the xs:assert inside the ele . . . Read full entry » Re: Fascinating XPath and XSD 1.1 assert problemPosted 9/20/2012 10:04:55 PMHi Roger, Here are the results that I observe with Xerces's XSD 1.1 validator, a) When I run your below sample as it is, I get an assertion failure with this additional message, XPTY0004 - Value does not match a required type Although, this is part of the Xerces proprietary <assert> err . . . Read full entry » Re: Fascinating XPath and XSD 1.1 assert problemPosted 9/20/2012 2:12:51 PMOn Sep 20, 2012, at 7:33 AM, Costello, Roger L. wrote: > ... > Now suppose that in the XML Schema @units is declared to be fixed: > > <xs:attribute name="units" type="xs:string" fixed="feet" /> > > Although the XML instance document . . . Read full entry » Fascinating XPath and XSD 1.1 assert problemPosted 9/20/2012 1:33:58 PMHello Folks, I have stumbled upon a fascinating problem (I didn't recognize fully the problem until Michael Kay explained it to me). Consider the following XML document. There are two <Attitude> elements; they have a mandatory "reference" attribute and an optional "units" . . . Read full entry » Re: Access to Schema API informationPosted 9/18/2012 10:30:48 AM[Sorry for earlier no-comment reply!] Michael Kay writes: > On 22/05/2012 11:06, Henry S. Thompson wrote: >> Michael Kay writes: >> >>> I have been implementing a Saxon extension that exposes the Schema >>> Component Model to XSLT and XQuery applications >> . . . Read full entry » Re: Access to Schema API informationPosted 9/18/2012 10:26:34 AMMichael Kay writes: > On 22/05/2012 11:06, Henry S. Thompson wrote: >> Michael Kay writes: >> >>> I have been implementing a Saxon extension that exposes the Schema >>> Component Model to XSLT and XQuery applications >> Using functions is cool, but did you co . . . Read full entry » Re: 2000-01-01+13:00 and 1999-12-31-11:00 are equal?Posted 9/17/2012 10:26:19 PMOriginal Message From: "Costello, Roger L." > In the XSD 1.1 data types specification it says this in the discussion of > the "date" data type: > > Some date values with different time zone offsets > that were identical in the 1.0 version of this > sp . . . Read full entry » 2000-01-01+13:00 and 1999-12-31â??11:00 are equal? %ž‚|è ; l°Í ‚|h& É‚|Ì . ð ; ´¯Í %ž‚| & À . & & ¤°Í z§‚|& É‚|Ì . È . È . À . È . 8 `° D¯Í øëË#L°Í à€‚|¸÷' àÇ‚|(°Í ¨& `§ˆ| Ÿ l°Í ¸È‚|È¢u! & P œ¯Í à€‚| & É‚|€ & Ä¯Í 0 à€Ô¯Í ÿÿÿÿÜ°Í à€‚|Ђ|ÿÿÿÿÉ‚|öλw & ûλwÌ . È . È . ¨°Í qdFsL±Í tl¼w¸°Í ÿÿÿÿL±Í PÖƒ P º±Í èpdôèpdÖƒP ºP º±Í NTžpP ºà(ö\±Í Í?žp @žpNGrd1 8P ºà(ö ±Í ˆ2£p¸·Í Mÿ¢p@žpÿÿÿÿ @žpW*žp 1Â,²Í eæpdà±Í ÛØ[]¬±Í d²Í 1 ²Í @žp à(öÐMªÐ±Í 1Â>)žp,²Í h܃ÐMªà(öì±Í èpdôèpd¨Üƒ à(öü±Í Tžpà(ö,²Í ²Í {Tžp h²Í éNžpà(ö éØ¡p èÂÍ À6 èÂÍ À'ö¬ÅÍ ¤ÃÍ 8 ¶Í É¢p ˆ Î ˆ žp Š¢p / i n c l u d e / m e g a b a n n e r D e f a u l t . a s p à²Í @ !ˆ Í Ì´Í ö } ³Í ¾[ 4³Í Ì´Í ! } ³Í üµÍ ! } # D 5 ?  <³Í I g n oPosted 9/17/2012 7:31:29 PMHi Folks, In the XSD 1.1 data types specification it says this in the discussion of the "date" data type: Some date values with different time zone offsets that were identical in the 1.0 version of this specification, such as 2000-01-01+13:00 and 1999-12-31â1 . . . Read full entry » Re: 2000-01-01+13:00 and 1999-12-31−11 :00 are equal?Posted 9/17/2012 4:45:23 PMAt 2012-09-17 19:31 +0000, Costello, Roger L. wrote: >Hi Folks, > >In the XSD 1.1 data types specification it says >this in the discussion of the "date" data type: > > Some date values with different time zone offsets > that were identical in the 1.0 version . . . Read full entry » Short tutorial on restricting complexTypes that have mixed contentPosted 9/16/2012 6:41:59 PMHi Folks, I've discovered that you can do some really powerful things by creating a base type that is a complexType with mixed content. So I created a short tutorial which shows the various ways to restrict a complexType that has mixed content: http://www.xfront.com/restricting-complexTypes-that . . . Read full entry » Re: sml schema regular expression performancePosted 9/14/2012 8:48:25 PMFirst-character optimization is all about finding a place in the string where it's worth attempting a match. As such, it doesn't apply to XSD regular expressions, because there is only one place you are allowed to attempt a match - namely, at the beginning of the string. Michael Kay Saxonica O . . . Read full entry » RE: sml schema regular expression performancePosted 9/14/2012 7:09:18 PMThank you, Michael for very detailed answer. Still would like to know about performance. XSD schema does defines its own flavor http://www.regular-expressions.info/xml.html and the statement is Compared with other regular expression flavors<http://www.regular-expressions.info/refflavors.html> . . . Read full entry » Re: sml schema regular expression performancePosted 9/14/2012 6:11:27 PMI don't understand what you are saying. XML Schema is a specification, not an implementation. The regex language it defines has no differences from other popular regex languages that would make it less efficient. The decision to anchor regexes by default has nothing to do with efficiency or p . . . Read full entry » RE: sml schema regular expression performancePosted 9/14/2012 3:52:19 PMOn Fri, 2012-09-14 at 19:09 +0000, Armishev, Sergey wrote: > The arguments against XML schema regular expression performance that I > cited is that such flavor can't use "first character optimization" . > Somebody can compare this "first character optimization" versus . . . Read full entry » sml schema regular expression performancePosted 9/11/2012 10:03:58 PMHi, XML schema experts. I have question regarding Regular Expression performance. I received the opinion that XML schema using very inefficient engine. Below is a statement. Is it TRUE or FALSE and WHY when it comes to regex, XSD has one thing VERY WRONG: anchoring regexes is NOT a way to make t . . . Read full entry » Re: If I have a 1.1 schema and remove the 1.1 specific stuff, will I then have a 1.0 schema?Posted 9/5/2012 5:11:32 PMOn 05/09/2012 16:17, Costello, Roger L. wrote: > Hi Folks, > > Suppose that I have a 1.1 schema. > > If I remove all the 1.1 specific stuff (assert, alternative, openContent, etc.) will the resulting document be a 1.0 compliant schema? > > /Roger > > I don't think you ca . . . Read full entry » If I have a 1.1 schema and remove the 1.1 specific stuff, will I then have a 1.0 schema?Posted 9/5/2012 3:17:04 PMHi Folks, Suppose that I have a 1.1 schema. If I remove all the 1.1 specific stuff (assert, alternative, openContent, etc.) will the resulting document be a 1.0 compliant schema? /Roger Received on Wednesday, 5 September 2012 15:17:35 GMT . . . Read full entry » [ XML Schema 1.1 Quiz ] What's the data type of an element that does not specify a type and is a member of multiple substitution groups?Posted 8/29/2012 3:09:28 PMFolks, Hello, In XML Schema 1.1 you can declare an element to be substitutable for multiple elements, e.g., <element name="Example" substitutionGroup="A B C" ...> Recall that in XML Schema 1.0 if you declared an element and didn't provide a type, then it inherits t . . . Read full entry » Re: XML testsPosted 8/28/2012 11:10:29 AMLooks like you need a content model which is choice( sequence(newelement, element1), sequence(element1, element2, element3) ) Michael Kay Saxonica On 28/08/2012 09:44, stuart shepherd wrote: > I have a schema which validates my XML files very well, but I've > recently added a new o . . . Read full entry » XML testsPosted 8/28/2012 9:44:59 AMI have a schema which validates my XML files very well, but I've recently added a new optional element to a previous defined element, and I would like to know if there is a way to test that if an element is present then only certain other elements can be present. i.e old element, can have element . . . Read full entry » Re: What is the type of an element with a fixed value?Posted 8/28/2012 12:07:41 AMThe presence of a fixed value does not affect the type, which is determined in the usual way based on the type attribute or equivalent. In your examples there is no type attribute so the type is xs:anyType. The fixed value must of course be valid against the type, though if it isn't, this is co . . . Read full entry » What is the type of an element with a fixed value?Posted 8/27/2012 9:35:51 PMHi Folks, What is the type of Foo? <element name="Foo" fixed="Hello World" /> Is it: (a) xs:string (b) xs:anyType What is the type of Bar? <element name="Bar" fixed="93" /> Is it: (a) xs:string (b) xs:decimal (c) xs:anyType / . . . Read full entry » Re: What is the type of an element with a fixed value?Posted 8/27/2012 6:11:36 PMOn Aug 27, 2012, at 3:35 PM, Costello, Roger L. wrote: > Hi Folks, > > What is the type of Foo? > > <element name="Foo" fixed="Hello World" /> > > Is it: > > (a) xs:string > (b) xs:anyType > > > What is the type of Bar? > . . . Read full entry » RE: Is this the complete list of ways to create recursion in XML Schemas?Posted 8/25/2012 9:12:02 PMThanks Liam. > Recursion via substitution groups Here is an example of circular substitutionGroups: <xsd:element name="Subway" substitutionGroup="Metro" type="xsd:string" /> <xsd:element name="Metro" substitutionGroup="Subway& . . . Read full entry » Re: Is this the complete list of ways to create recursion in XML Schemas?Posted 8/25/2012 3:24:20 PMOn Sat, 2012-08-25 at 15:10 +0000, Costello, Roger L. wrote: > Hi Folks, > Is that the complete list? Are there any other ways to create > recursion in XML Schemas? Some others: Indirect recursion - element A contains B which can contain A... Recursion via substitution groups Co-occur . . . Read full entry » Is this the complete list of ways to create recursion in XML Schemas?Posted 8/25/2012 3:10:18 PMHi Folks, One way to create recursion in XML Schemas is with a recursive element reference, e.g., <xsd:element name="Section" type="SectionType" /> <xsd:complexType name="SectionType"> <xsd:sequence> <xsd:element . . . Read full entry » RE: XML Schema quiz on default valuesPosted 8/24/2012 10:48:40 PMAnother use case is archiving. In many cases XML documents will be archived without their schemas. This is not generally a problem as long as default and fixed values are not used. That is one reason why some sets of naming and design rules discourage (or forbid) the use of these features. Paul . . . Read full entry » Re: XML Schema quiz on default valuesPosted 8/24/2012 6:03:37 PMOriginal Message From: "Daniel Dui" > My experience is that a user that sees the default feature in XML schema > expects that the default value is the value that an optional element > "takes" when it's not included in the instance document. > > You might think it . . . Read full entry » Re: XML Schema quiz on default valuesPosted 8/24/2012 5:16:25 PMMy experience is that a user that sees the default feature in XML schema expects that the default value is the value that an optional element "takes" when it's not included in the instance document. You might think it's naive, but that's the reality for many C++/Java/C# developers who ne . . . Read full entry » RE: XML Schema quiz on default valuesPosted 8/24/2012 1:36:02 PMHello Daniel, > this [default values] is definitely a dark corner of the specs. I agree. Hopefully this discussion has shed some light on it. /Roger From: Daniel Dui [mailto:daniel.dui@gmail.com] Sent: Friday, August 24, 2012 8:33 . . . Read full entry » Re: XML Schema quiz on default valuesPosted 8/24/2012 1:33:11 PMRoger et al., thanks for the clarification. I have used XML Schema for a long time and this is definitely a dark corner of the specs. I always warn people about using default values and often recommend not using them. This non-obvious defaulting behavior looks to me like another reason why many s . . . Read full entry » Re: XML Schema quiz on default valuesPosted 8/24/2012 11:48:03 AMHello Daniel, Suppose Title is declared like this: <xs:element name="Title" type="xs:string" default="Hello World" /> Note that a default value ("Hello World") is specified. Now suppose we have this empty Title element in an instance document: . . . Read full entry » Re: XML Schema quiz on default valuesPosted 8/24/2012 11:21:42 AMOn Aug 24, 2012, at 11:03 AM, Pete Cordell wrote: > Original Message From: "Daniel Dui" > >> My experience is that a user that sees the default feature in XML schema >> expects that the default value is the value that an optional element >> "takes" whe . . . Read full entry » |
PURCHASE STYLUS STUDIO ONLINE TODAY!!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! 
Learn XQuery in 10 Minutes!Say goodbye to 10-minute abs, and say Hello to "Learn XQuery in Ten Minutes!", the world's fastest and easiest XQuery primer, now available for free! Why Pay More for XML Tools?With Stylus Studio® X14 XML Enterprise Suite, you get the most comprehensive XML tool suite at one incredibly low price. Value: it's just one of many reasons why smart XML developers are choosing Stylus Studio! |
XML PRODUCTIVITY THROUGH INNOVATION ™
Prev: "XQuery Talk Blog"
Next: "EDI-List Blog"
