[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: FW: xNAL schemas
CIQ TC, FYI. Regards, Ram Ram Kumar General Manager - Software R&D and Architecture MSI Business Systems Suite 204A, 244 Beecroft Road Epping, NSW 2121, AUSTRALIA Direct: +61-2-9815 0226 Mobile: +61-412 758 025 Fax: +61-2-98150200 URL: www.msi.com.au -----Original Message----- From: Paul Spencer [mailto:paul.spencer@boynings.co.uk] Sent: Tuesday, August 24, 2004 7:11 PM To: Ram Kumar Subject: xNAL schemas Hi Ram, As you know, we are using the xNAL schemas in the OASIS Election Markup Language. I think I have come across a problem. In EML, we have several different types of addresses. We have given each of these its own data type. In some national versions, these are cast to different data types, but in the International version, they are all xal:AddressDetails: <xs:complexType name="MailingAddressStructure"> <xs:complexContent> <xs:extension base="xal:AddressDetails"/> </xs:complexContent> </xs:complexType> <xs:complexType name="PhysicalAddressStructure"> <xs:complexContent> <xs:extension base="xal:AddressDetails"/> </xs:complexContent> etc. xal:AddressDetails has two optional items (xal:PostalServiceElements and an xs:choice) followed by an optional xs:any namespace="##other". I believe that, unless the target namespace of the containing schema is the xAL namespace, this makes the schema non-deterministic since, say, the xal:PostalServiceElements element could be part of either the branch with its name or the xs:any branch. Unfortunately, schema processors are notoriously bad at detecting non-deterministic schemas, so this is difficult to test. Do you have any comments? It could be that I have read this wrongly. Regards Paul Spencer Director Boynings Consulting Ltd http://www.boynings.co.uk
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]