- From: Mark Feblowitz <mfeblowitz@frictionless.com>
- Date: Mon, 19 Nov 2001 09:28:02 -0500
- To: "'Kanaskie, Kurt A (Kurt)'" <kkanaskie@lucent.com>, "'ht@cogsci.ed.ac.uk'" <ht@cogsci.ed.ac.uk>
- Cc: "Xmlschema-Dev (E-mail)" <xmlschema-dev@w3.org>
Henry apologized for the obscure message, said that the xml contains the detail, and said he'd fix the stylesheet to reflect the meaning of the "None." Mark ---------------------------------------------------------------------------- ---- Mark Feblowitz [t] 617.715.7231 Frictionless Commerce Incorporated [f] 617.495.0188 XML Architect [e] mfeblowitz@frictionless.com 400 Technology Square, 9th Floor Cambridge, MA 02139 www.frictionless.com -----Original Message----- From: Kanaskie, Kurt A (Kurt) [mailto:kkanaskie@lucent.com] Sent: Monday, November 19, 2001 9:25 AM To: Mark Feblowitz; 'ht@cogsci.ed.ac.uk' Cc: Xmlschema-Dev (E-mail) Subject: RE: Interesting XSV message Right, This is the same thing I discovered in the Spec that you cant reduce the minOccurs value in a restriction. Nice to see XSV is catching these aspects of the Spec. ________________________________________________________________ Kurt Kanaskie Lucent Technologies kkanaskie@lucent.com (610) 778-1069 -----Original Message----- From: Mark Feblowitz [mailto:mfeblowitz@frictionless.com] Sent: Friday, November 16, 2001 5:50 PM To: 'ht@cogsci.ed.ac.uk' Cc: Xmlschema-Dev (E-mail) Subject: Interesting XSV message In using today's build of XSV 1.4, I got the following message: file:/OAGIS/BODs/ProcessPurchaseOrder.xsd:19:3: Invalid: Content model of None not actually a restriction of base type BusinessObjectDocument: a {http://www.openapplications.org/OAGIS}:DataArea element at node 1 of this model can't be matched by any edge leaving node 1 of the base Base model: This model: I guessed (correctly) that the base type BusinessObjectDocument had a content model requiring an ApplicationArea element (minOccurs="1") but that the element ProcessPurchaseOrder (incorrectly reported as "None" in the error message), incorrectly changed the minOccurs to "0". In spite of the somewhat confusing error report, XSV now looks to catch an improper restriction in cardinality. Mark ---------------------------------------------------------------------------- ---- Mark Feblowitz [t] 617.715.7231 Frictionless Commerce Incorporated [f] 617.495.0188 XML Architect [e] mfeblowitz@frictionless.com 400 Technology Square, 9th Floor Cambridge, MA 02139 www.frictionless.com
Received on Monday, 19 November 2001 09:28:33 UTC