Subscribe to the XML Schema Development Blog in XML format

RSS 2.0
Atom 0.3

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.

To: Ken v

Posted 11/21/2014 10:47:44 AM

http://viajesestudiantesplaya.com/ftaeoyi/fjvqjudfvnavgxd.jtkwtkzgicoklhke Rob Harrington 11/21/2014 10:47:44 PM Received on Friday, 21 November 2014 21:48:11 UTC . . . Read full entry »

[ANN] XML Schema to SVG transform written in XQuery

Posted 9/1/2014 1:24:25 PM

I have developed XQuery code that transforms an XML Schema to an SVG representing that XSD. It is still a work in progress. I took the xsdvi project http://xsdvi.sourceforge.net/ that was written in Java and transformed it to an XQuery function module. It is available at https://github.com/lcahl . . . Read full entry »

[ANN] DocFlex/XML XSDDoc - XML Schema Documentation Generation Toolkit

Posted 7/26/2014 11:25:02 PM

Both a powerful multi-format XML schema (XSD) documentation generator with inclusion of XSD diagrams generated by XMLSpy or OxygenXML and a tool to create your own (custom) XSD documentation generators. ABOUT DOCFLEX/XML ================= DocFlex/XML is a Java-based software system for developmen . . . Read full entry »

[ANN] CodeSynthesis XSD 4.0.0 released, adds support for C++11

Posted 7/22/2014 1:00:43 PM

Hi, I am pleased to announce the release of CodeSynthesis XSD 4.0.0. XSD is an open source, cross-platform W3C XML Schema to C++ data binding compiler. Provided with a schema, it generates C++ classes that represent the given vocabulary as well as XML parsing and serialization code. You can then . . . Read full entry »

Rule Challenge 2014 - Submission Deadline Extension (June 18)

Posted 6/10/2014 5:27:51 PM

Apologies for cross-postings. Please send to interested colleagues. --------------------------------------------- 8th International Rule Challenge 2014 (http://2014.ruleml.org/challenge) part of the RuleML 2014 symposium held in conjunction with ECAI 2014, the 21st European Conference on Artifici . . . Read full entry »

Rule Challenge 2014 - Submission Deadline Extension (June 6)

Posted 5/27/2014 6:59:26 PM

Fwd: 4th RuleML Doctoral Consortium 2014 - Call for Papers

Posted 5/22/2014 11:54:13 AM

Call for Papers 4th RuleML Doctoral Consortium 2014, part of the RuleML'14 symposium held in conjunction with ECAI 2014, the 21st European Conference on Artificial Intelligence, Prague, Czech Republic, August 18 - 20, 2014 ============= About the Doctoral Consortium ================= The RuleML 20 . . . Read full entry »

[CfP] Rule Challenge 2014 Final Call for Papers

Posted 5/13/2014 1:16:11 PM

Apologies for cross-postings. Please send to interested colleagues. ---------------------------------------------------------------- Final Call for Papers 8th International Rule Challenge 2014 (http://2014.ruleml.org/challenge) part of the RuleML 2014 symposium held in conjunction with ECAI 2014, . . . Read full entry »

Re: request to enlist XmlPlus in the XSD-Tools list

Posted 4/12/2014 9:59:44 PM

On Wed, 2014-01-29 at 13:42 +0530, xmlplus custodians wrote: > Hi, > > Please add XmlPlus - xsd2cpp to the list here: > > http://www.w3.org/XML/Schema#Tools done, with apologies for taking so long - it turns out that the list is schema tools is curren . . . Read full entry »

RuleML 2014 - deadline extension

Posted 3/30/2014 2:26:37 PM

------------------------------------------------------------ --------------------- RuleML 2014 - 8th International Web Rule Symposium In conjunction with ECAI 2014 Prague, Czech Republic, August 18-20, 2014. http://2014.ruleml.org -------------------------------------------------------------------- . . . Read full entry »

RuleML 2014 - one week to abstract submission deadline

Posted 3/26/2014 12:06:17 AM

****** 1 WEEK TO ABSTRACT SUBMISSION DEADLINE ****** Apologies for cross-postings. Please send to interested colleagues. Call for Papers 8th International Web Rule Symposium (RuleML 2014) In conjunction with ECAI 2014, the 21st European Conference on Artificial Intelligence Prague, Czech Republic . . . Read full entry »

RuleML 2014: 2nd Call for Papers

Posted 2/20/2014 12:19:24 AM

2nd Call for Papers RuleML 2014 - 8th International Web Rule Symposium In conjunction with ECAI 2014, the 21st European Conference on Artificial Intelligence Prague, Czech Republic, August 18-20, 2014 http://2014.ruleml.org Special Issue =========== A selection of the best RuleML 2014 papers will . . . Read full entry »

Xml

Posted 2/3/2014 12:08:56 PM

text/xml attachment: oon_design.xml Received on Tuesday, 4 February 2014 12:53:25 UTC . . . Read full entry »

request to enlist XmlPlus in the XSD-Tools list

Posted 1/29/2014 1:42:14 PM

Hi, Please add XmlPlus - xsd2cpp to the list here: http://www.w3.org/XML/Schema#Tools The details follow: ------------------------------------------------------------------------------------------------------------------------------------------------------ Descrip . . . Read full entry »

[ann] oXygen XML Editor 15.2 adds support for XML Schema language version

Posted 1/24/2014 4:44:30 PM

Hello, I am happy to announce that version 15.2 of oXygen XML Editor is available from our website http://www.oxygenxml.com This new version implements support for working multiple XML Schema language versions, oXygen understanding now the vc:minVersion and vc:maxVersion attributes if these ar . . . Read full entry »

RuleML 2014 Call for Papers

Posted 12/8/2013 8:50:51 AM

** Apologies for cross-postings. Please send to interested colleagues. ** Call for Papers RuleML 2014 - 8th International Web Rule Symposium Prague, Czech Republic, August 18-20, 2014 http://2014.ruleml.org About RuleML 2014 ================= The annual International Web Rule Symposium (RuleML) i . . . Read full entry »

RuleML 2014 Call for Papers

Posted 12/6/2013 9:16:47 PM

Apologies for cross-postings. Please send to interested colleagues. Call for Papers RuleML 2014 - 8th International Web Rule Symposium Prague, Czech Republic, August 18-20, 2014 http://2014.ruleml.org About RuleML 2014 ================= The annual International Web Rule Symposium (RuleML) is the . . . Read full entry »

Re: XSD 1.1 assert and id()

Posted 11/18/2013 2:41:39 PM

Hello Michael, thanks for the clarification. Best, Maik Michael Kay schrieb: > XSD 1.1 states Part 1, Â§3.13.1): > > To check an assertion, an instance of the XPath 2.0 data model ([XDM]) is constructed, in which the element information item being Â·assessedÂ· is the (parentless) root . . . Read full entry »

Re: XSD 1.1 assert and id()

Posted 11/18/2013 12:36:39 PM

XSD 1.1 states Part 1, §3.13.1): To check an assertion, an instance of the XPath 2.0 data model ([XDM]) is constructed, in which the element information item being ·assessed· is the (parentless) root node and XPath Functions and Operators states (§15.5.2 fn:id): If $node, or the context item if . . . Read full entry »

XSD 1.1 assert and id()

Posted 11/18/2013 11:18:21 AM

Hello, I know that XSD 1.1 assert elements are restricted to descendent nodes of the content node that is asserted. It seems to me, that this rule does prevent the use of the id() function, since it could be used to access nodes out of scope. See the simple XSD below. I have a number of movies . . . Read full entry »

Altova XSD 1.1 announcement

Posted 11/2/2013 5:00:39 PM

It's good to see that Altova have now announced what we have suspected for some time, that they have developed an XML Schema 1.1 processor. They are claiming complete conformance with the spec: http://www.altova.com/whatsnew_missionkit.html Hopefully this will start to accelerate the rate of XSD . . . Read full entry »

Re: XML Schema language version

Posted 10/11/2013 10:14:20 AM

Dear Michael, If the document specifies only vc:minVersion="1.0" on the schema root element then we will need to use an XML Schema 1.1 processor and this matches the result of the provided algorithm. Why we need to use an XML Schema 1.1 processor in this case? minVersion="1.0&qu . . . Read full entry »

Re: XML Schema language version

Posted 10/10/2013 6:26:27 PM

On Oct 10, 2013, at 5:49 AM, Loren Cahlander wrote: > I fully agree. Max means less than or equal, not less than. > > The example in http://www.w3.org/2007/XMLSchema-versioning/ matches the general understaning of max. It also matches the initial description of the vc:* namespace, b . . . Read full entry »

Re: XML Schema language version

Posted 10/10/2013 6:21:19 PM

On Oct 10, 2013, at 4:35 AM, Timothy W. Cook wrote: > Thanks for this addition to oXygen. > The maxVersion issue needs to be fixed in the specs. I think everyone agrees that the current definition is just non-sensical. Well, no. The initial draft of the vc:* namespace had inclusive sem . . . Read full entry »

Re: XML Schema language version

Posted 10/10/2013 6:12:54 PM

On Oct 10, 2013, at 2:19 AM, George Cristian Bina wrote: > Thanks Mike for this suggestion! > > We will implement this algorithm in oXygen: > > if (there are vc:minVersion or vc:maxVersion attributes on the schema root element) then { > if (version 1.1 is accepted) > the . . . Read full entry »

Re: XML Schema language version

Posted 10/10/2013 11:19:48 AM

Thanks Mike for this suggestion! We will implement this algorithm in oXygen: if (there are vc:minVersion or vc:maxVersion attributes on the schema root element) then { if (version 1.1 is accepted) then (use XML Schema version 1.1) else if (version 1.0 is accepted) then (use XML Schema ve . . . Read full entry »

Re: XML Schema language version

Posted 10/10/2013 9:58:23 AM

Yes, the exclusive nature is a bit of a pain. I would use values like max=1.0001 or max=1.1001. Michael Kay Saxonica On 10 Oct 2013, at 09:19, George Cristian Bina wrote: > Thanks Mike for this suggestion! > > We will implement this algorithm in oXygen: > > if (there are vc:minV . . . Read full entry »

Re: XML Schema language version

Posted 10/10/2013 7:49:09 AM

I fully agree. Max means less than or equal, not less than. The example in http://www.w3.org/2007/XMLSchema-versioning/ matches the general understaning of max. The second value in the example should have been min and not max. Schema authors can use this to provide alternative formulations of s . . . Read full entry »

Re: XML Schema language version

Posted 10/10/2013 7:35:40 AM

Thanks for this addition to oXygen. The maxVersion issue needs to be fixed in the specs. I think everyone agrees that the current definition is just non-sensical. On Thu, Oct 10, 2013 at 5:19 AM, George Cristian Bina <george@oxygenxml . . . Read full entry »

Re: XML Schema language version

Posted 10/3/2013 10:40:37 AM

The document at http://www.w3.org/2007/XMLSchema-versioning/ needs to be updated. There are typos, "How it workds." The example in that section is wrong. The example in http://www.w3.org/TR/xmlschema11-1/#cip is much better. Sent from my iPad > On Oct 3, 2013, at 10:00 AM, " . . . Read full entry »

Re: XML Schema language version

Posted 10/3/2013 9:34:49 AM

Hi, I just want to mention that vc:maxVersion="1.1" would lead to an empty schema document for a 1.1 processor (see http://www.w3.org/TR/xmlschema11-1/#cip) : "If V is less than the value of vc:minVersion, or if V is greater than or equal to the value of vc:maxVersion, then the ele . . . Read full entry »

Re: XML Schema language version

Posted 10/3/2013 8:00:30 AM

On Oct 3, 2013, at 3:34 AM, XML Dev wrote: > Hi, > > I just want to mention that vc:maxVersion="1.1" would lead to an empty schema document for a 1.1 processor (see http://www.w3.org/TR/xmlschema11-1/#cip) : > > "If V is less than the value of vc:minVersion, or if . . . Read full entry »

Re: XML Schema language version

Posted 10/3/2013 6:19:15 AM

On Wed, Oct 2, 2013 at 9:47 PM, C. M. Sperberg-McQueen < cmsmcq@blackmesatech.com> wrote: > > But since the 1.1 spec already defines both minVersion and > maxVersion, and since . . . Read full entry »

Re: XML Schema language version

Posted 10/2/2013 9:12:17 PM

I think it would be a creative but perfectly reasonable interpretation of the XSD 1.1 specification to advise users to set vc:minVersion="1.0" or vc:minVersion="1.1" or vc:maxVersion="1.0" on the xs:schema element to indicate whether they expect to use a 1.0 processor . . . Read full entry »

Re: XML Schema language version

Posted 10/2/2013 8:22:09 PM

vc:minVersion="1.1" is a great solution for marking them as 1.1 required. Is there a need for a vc:maxVersion? --Tim On Wed, Oct 2, 2013 at 5:12 PM, Michael Kay <mike@saxonica.com> wrote: > I think i . . . Read full entry »

Re: XML Schema language version

Posted 10/2/2013 6:47:13 PM

On Oct 2, 2013, at 5:22 PM, Timothy W. Cook wrote: > vc:minVersion="1.1" is a great solution for marking them as 1.1 required. Is there a need for a vc:maxVersion? Probably less of a need, if (as I suggested in another mail) vc:minVersion="1.0" is taken by editing environ . . . Read full entry »

Re: XML Schema language version

Posted 10/2/2013 2:38:09 PM

On Oct 2, 2013, at 2:12 PM, Michael Kay wrote: > I think it would be a creative but perfectly reasonable interpretation of the XSD 1.1 specification to advise users to set vc:minVersion="1.0" or vc:minVersion="1.1" or vc:maxVersion="1.0" on the xs:schema element t . . . Read full entry »

Re: XML Schema language version

Posted 10/2/2013 1:55:34 PM

On Sep 26, 2013, at 2:58 AM, George Cristian Bina wrote: > Hi all, > > We introduced XML Schema 1.1 support in oXygen some time ago. As there is no way to specify the version of the XML Schema language we added an application option that controls what version is in use. By default XML S . . . Read full entry »

XML Schema language version

Posted 9/26/2013 11:58:22 AM

Hi all, We introduced XML Schema 1.1 support in oXygen some time ago. As there is no way to specify the version of the XML Schema language we added an application option that controls what version is in use. By default XML Schema 1.1 is selected and we show a notification to the user informing . . . Read full entry »

Re: Context Sensitive Element Definitions in W3C XSD Schema?

Posted 8/26/2013 8:45:23 AM

Yes, very non-intuitive. XSD 1.1 allows a targetNamespace attribute on a local xs:element, but only under very restricted circumstances. I argued for removing all restrictions and allowing it anywhere, but others wanted to keep a stronger relationship between schema modules and namespaces, so I di . . . Read full entry »

Re: XML Schema 1.1 Tutorial

Posted 4/3/2013 8:15:23 PM

On 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 Tutorial

Posted 4/3/2013 3:40:56 PM

Hello 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 Tutorial

Posted 4/3/2013 2:04:49 PM

responding 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 attribute

Posted 4/1/2013 9:12:56 AM

On 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 error

Posted 4/1/2013 8:52:15 AM

Thanks 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 attribute

Posted 4/1/2013 8:40:23 AM

Thanks 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 error

Posted 3/31/2013 5:25:36 PM

On 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 correct

Posted 3/31/2013 4:27:56 PM

On 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 correct

Posted 3/31/2013 4:22:31 PM

On 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 attribute

Posted 3/31/2013 3:26:34 PM

On 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 correct

Posted 3/25/2013 9:49:29 AM

Sorry 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 attribute

Posted 3/22/2013 10:52:59 AM

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"> <effect Type="a" TypeNotes="sss" e:dc="xx . . . Read full entry »

Add an attribute

Posted 3/22/2013 10:02:06 AM

I'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 correct

Posted 3/20/2013 9:59:12 PM

It 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 correct

Posted 3/20/2013 9:34:36 PM

XMLSpy 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 correct

Posted 3/20/2013 8:49:13 PM

Surprised 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 correct

Posted 3/20/2013 7:50:43 PM

I 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 correct

Posted 3/20/2013 7:05:31 PM

Since 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 correct

Posted 3/20/2013 6:56:06 PM

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 I try to make a sample (non realistic) in order to isolate my question. Here is . . . Read full entry »

Re: Restriction error

Posted 3/20/2013 2:40:57 PM

Hi 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 error

Posted 3/20/2013 2:06:33 PM

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 generally defined by extension: think > of it as first defining the si . . . Read full entry »

Re: Restriction error

Posted 3/20/2013 1:58:03 PM

Ignore 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 error

Posted 3/20/2013 1:53:56 PM

A 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 error

Posted 3/20/2013 1:03:38 PM

Very 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éma

Posted 3/4/2013 11:58:01 PM

On 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 CFP

Posted 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éma

Posted 3/4/2013 3:07:46 PM

If 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éma

Posted 3/4/2013 8:18:18 AM

Thank 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éma

Posted 3/1/2013 1:08:04 PM

Merci 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 PM

Thanks 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 PM

text/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.1

Posted 2/27/2013 9:15:26 AM

Thank 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 AM

text/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.1

Posted 2/21/2013 12:34:26 PM

Dear 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 Tutorial

Posted 2/19/2013 2:30:12 PM

I 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 AM

C. 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 PM

On 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 PM

On 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 PM

C. 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 AM

Just one slightly pedantic footnote: On Feb 15, 2013, at 4:00 AM, Leif Halvard Silli wrote: > A doctype such as > <!DOCTYPE TheDocumentElement SYSTEM "ID" [] > > 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.1

Posted 2/14/2013 4:58:05 PM

Hi 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 PM

On 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 AM

On 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 AM

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, 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 PM

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 > 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 AM

George 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 AM

Thanks 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 AM

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 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 PM

On 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 PM

On 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 PM

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 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 PM

Mukul 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 PM

Hi 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 AM

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. 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 AM

George 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 AM

Hello!            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 AM

I 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 scope

Posted 1/14/2013 9:45:16 PM

Hi 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 scope

Posted 1/14/2013 5:47:07 PM

Thank 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 scope

Posted 1/14/2013 3:57:09 PM

On 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 scope

Posted 1/14/2013 3:16:20 PM

Hi 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 scope

Posted 1/14/2013 2:23:54 PM

On 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 scope

Posted 1/14/2013 1:59:00 PM

George 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 attribute

Posted 1/5/2013 5:49:54 PM

Of 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 attribute

Posted 1/4/2013 4:40:36 PM

Hi, 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 DOCTYPE

Posted 12/22/2012 6:38:49 PM

Hi 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 PM

Hi 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 attribute

Posted 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 attribute

Posted 12/18/2012 12:41:58 PM

Hi 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 Tutorial

Posted 12/14/2012 9:16:25 PM

Hi 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 PM

On 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 PM

Orthogonality 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 PM

On 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 PM

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" /> 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 AM

Classification: 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 AM

At 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 AM

Inherited 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 AM

Hi 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 PM

I 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 PM

Awesome, 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 PM

On 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 PM

And 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 PM

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 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 PM

On 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 AM

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 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 AM

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. 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 AM

Is 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.1

Posted 12/2/2012 1:34:00 PM

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" 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.1

Posted 12/2/2012 12:42:56 PM

On 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.b

Posted 11/24/2012 10:06:19 PM

This 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.b

Posted 11/24/2012 9:42:58 PM

The 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.b

Posted 11/24/2012 8:44:42 PM

ht 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.b

Posted 11/24/2012 8:35:28 PM

Your 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.b

Posted 11/24/2012 1:45:12 PM

Hi, 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 PM

On 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 PM

On 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 PM

On 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 PM

At 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 PM

Thanks! 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 PM

That 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 PM

At 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 AM

The 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 AM

Something 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 AM

Thanks! 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 AM

I am looking to transform comments that precede an element and make those comments as an annotation for that element. for example:  <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 PM

On 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 PM

With 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 PM

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;" 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 PM

Hello 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 PM

The 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 type

Posted 10/21/2012 11:28:29 AM

Thanks 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 AM

This 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 PM

G. 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 PM

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 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 PM

At 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 PM

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 there are 3 ways to specify the same thing for every built-in data type. Can you . . . Read full entry »

XML Schema Checklist

Posted 10/20/2012 11:19:37 AM

Hi 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 AM

At 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 Checklist

Posted 10/20/2012 7:55:45 AM

All 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 file

Posted 10/18/2012 8:27:18 PM

Original 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 file

Posted 10/18/2012 5:45:14 PM

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! or 120! disjuncts in a large regular expression >>> or content mo . . . Read full entry »

Re: Order indicators in the .xsd file

Posted 10/18/2012 4:15:05 PM

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 trying to help them... Michael Kay On 18/10/2012 14 . . . Read full entry »

Re: Order indicators in the .xsd file

Posted 10/18/2012 4:05:25 PM

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 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 sequence

Posted 10/18/2012 2:15:19 PM

Well, 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 file

Posted 10/18/2012 1:03:42 PM

On 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 sequence

Posted 10/18/2012 12:44:42 PM

Hi 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 file

Posted 10/18/2012 11:17:48 AM

On 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 file

Posted 10/18/2012 10:50:21 AM

On 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 file

Posted 10/18/2012 10:03:03 AM

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 model whose top-level operator is choice may >> exceed current engineeri . . . Read full entry »

Re: Order indicators in the .xsd file

Posted 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 file

Posted 10/18/2012 7:30:08 AM

On 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 PM

Fred, 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 PM

The 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 file

Posted 10/17/2012 8:51:36 PM

On 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 PM

Sorry 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 PM

Hi 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 file

Posted 10/17/2012 5:39:44 PM

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 (a, b, (x | y)) instead. However, for a complex model getting the right . . . Read full entry »

Re: Order indicators in the .xsd file

Posted 10/17/2012 4:33:29 PM

Ah 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 file

Posted 10/17/2012 4:18:24 PM

At 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 file

Posted 10/17/2012 4:16:33 PM

OK, 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 file

Posted 10/17/2012 4:04:17 PM

Original 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 file

Posted 10/17/2012 3:46:41 PM

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. Michael Kay Saxonica Received on Wednesday, 17 October 2012 14:47:12 GMT . . . Read full entry »

Re: Order indicators in the .xsd file

Posted 10/17/2012 3:45:49 PM

On 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 file

Posted 10/17/2012 3:35:46 PM

Can'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 PM

The 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 file

Posted 10/16/2012 3:13:51 PM

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 the XML Schema language: All - the child elements can appear in . . . Read full entry »

"Unsafe" union?

Posted 10/16/2012 11:08:07 AM

Hi 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 element

Posted 10/14/2012 12:59:49 PM

Hi 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 element

Posted 10/14/2012 12:35:19 PM

On 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 replacement

Posted 10/12/2012 3:09:17 PM

An 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.1

Posted 10/12/2012 3:07:08 PM

Please 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 replacement

Posted 10/12/2012 2:40:42 PM

Hi, 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.1

Posted 10/11/2012 3:17:05 PM

Hi, 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 enumerations

Posted 10/8/2012 5:11:03 PM

wrt 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 enumerations

Posted 10/8/2012 10:45:01 AM

The 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 enumerations

Posted 10/6/2012 2:31:16 PM

I 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 released

Posted 9/26/2012 1:41:52 PM

Hello 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 »

Download a 15 Day Free Trial Now >

See What's New in Stylus Studio® X16 XML >

Buy Stylus Studio Now >

Stylus Most Wanted

PURCHASE STYLUS STUDIO ONLINE TODAY!!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Amazon.com Widgets

Attend a Live Webinar This Week!

Learn about Stylus Studio's unique features and benefits in just under an hour. Register for the Stylus Studio QuickStart Training WebCast!

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 EDITOR

The XML Schema Development Blog (XMLSchema-DEV Blog)

Posted 11/21/2014 10:47:44 AM

Posted 9/1/2014 1:24:25 PM

Posted 7/26/2014 11:25:02 PM

Posted 7/22/2014 1:00:43 PM

Posted 6/10/2014 5:27:51 PM

Posted 5/27/2014 6:59:26 PM

Posted 5/22/2014 11:54:13 AM

Posted 5/13/2014 1:16:11 PM

Posted 4/12/2014 9:59:44 PM

Posted 3/30/2014 2:26:37 PM

Posted 3/26/2014 12:06:17 AM

Posted 2/20/2014 12:19:24 AM

Posted 2/3/2014 12:08:56 PM

Posted 1/29/2014 1:42:14 PM

Posted 1/24/2014 4:44:30 PM

Posted 12/8/2013 8:50:51 AM

Posted 12/6/2013 9:16:47 PM

Posted 11/18/2013 2:41:39 PM

Posted 11/18/2013 12:36:39 PM

Posted 11/18/2013 11:18:21 AM

Posted 11/2/2013 5:00:39 PM

Posted 10/11/2013 10:14:20 AM

Posted 10/10/2013 6:26:27 PM

Posted 10/10/2013 6:21:19 PM

Posted 10/10/2013 6:12:54 PM

Posted 10/10/2013 11:19:48 AM

Posted 10/10/2013 9:58:23 AM

Posted 10/10/2013 7:49:09 AM

Posted 10/10/2013 7:35:40 AM

Posted 10/3/2013 10:40:37 AM

Posted 10/3/2013 9:34:49 AM

Posted 10/3/2013 8:00:30 AM

Posted 10/3/2013 6:19:15 AM

Posted 10/2/2013 9:12:17 PM

Posted 10/2/2013 8:22:09 PM

Posted 10/2/2013 6:47:13 PM

Posted 10/2/2013 2:38:09 PM

Posted 10/2/2013 1:55:34 PM

Posted 9/26/2013 11:58:22 AM

Posted 8/26/2013 8:45:23 AM

Posted 4/3/2013 8:15:23 PM

Posted 4/3/2013 3:40:56 PM

Posted 4/3/2013 2:04:49 PM

Posted 4/1/2013 9:12:56 AM

Posted 4/1/2013 8:52:15 AM

Posted 4/1/2013 8:40:23 AM

Posted 3/31/2013 5:25:36 PM

Posted 3/31/2013 4:27:56 PM

Posted 3/31/2013 4:22:31 PM

Posted 3/31/2013 3:26:34 PM

Posted 3/25/2013 9:49:29 AM

Posted 3/22/2013 10:52:59 AM

Posted 3/22/2013 10:02:06 AM

Posted 3/20/2013 9:59:12 PM

Posted 3/20/2013 9:34:36 PM

Posted 3/20/2013 8:49:13 PM

Posted 3/20/2013 7:50:43 PM

Posted 3/20/2013 7:05:31 PM

Posted 3/20/2013 6:56:06 PM

Posted 3/20/2013 2:40:57 PM

Posted 3/20/2013 2:06:33 PM

Posted 3/20/2013 1:58:03 PM

Posted 3/20/2013 1:53:56 PM

Posted 3/20/2013 1:03:38 PM

Posted 3/4/2013 11:58:01 PM

Posted 3/4/2013 3:17:49 PM

Posted 3/4/2013 3:07:46 PM

Posted 3/4/2013 8:18:18 AM

Posted 3/1/2013 1:08:04 PM

Posted 2/27/2013 8:43:47 PM

Posted 2/27/2013 8:26:16 PM

Posted 2/27/2013 9:15:26 AM

Posted 2/26/2013 6:20:19 AM

Posted 2/21/2013 12:34:26 PM