[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Error in RM Schema
All- I found an error in one of the RM Schemas. In EDXL-RMRequestResource.xsd line 21-29 there is the following: <element name="Funding" minOccurs="0" maxOccurs="unbounded"> <complexType> <sequence> <!-- One(or both) of the FundCode and FundingInfo elements is required --> <element name="FundCode" type="rm:FundCodeType" minOccurs="0"/> <element name="FundingInfo" type="rm:FundingInfoType" minOccurs="0"/> </sequence> </complexType> </element> This differs from all the other schemas that explicitly declare Funding as type=”rm:FundingType”. The problem with this is that child elements of a Funding Section of a RequestResource Message will be in the urn:oasis:names:tc:emergency:EDXL:RM:1.0:msg instead of the urn:oasis:names:tc:emergency:EDXL:RM:1.0. I have reproduced this validation error in 3 different XML validation products (XMLSpy 2010, MSXML 2.0, and Oxygen)[Screenshot attached of the first]. It looks as though a special case was trying to be made for this particular message for requiring funding information. However, there is no way around the namespace collision, and I am unsure why this was done any different than the other messages, because Funding is optional. Proposed change: <element name="Funding" type="rm:FundingType" minOccurs="0" maxOccurs="unbounded" /> If we want to handle the one or both being required we should be doing that in the rm:FundingType Type. How can we make this change to the “official RM Schema file”? Don McGarry The MITRE Corp. Office: 315-838-2669 Cell: 703-595-9375 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]