OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [emergency] Error in RM Schema


Thanks Don,

This is a EM-Msg SC effort, so I am specifically copying that SC so we 
can set aside a moment to address this. Since we are now in the phase of 
individual tasks in SitReps, it shouldn't be a problem to make time for 
it in our next meeting Tuesday.

Cheers,
Rex

McGarry, Donald P. wrote:
> Yeah.  I think the problem was that the sample didn't have funding information.  So if examples were auto generated it wouldn't produce an error.  The errata was dated Dec of last year so I think we should be all set...
> Don McGarry
> The MITRE Corp.
> dmcgarry@mitre.org
> (315) 838-2669 Office
> (703) 595-9375 Cell
> Sent via Blackberry
>
> ----- Original Message -----
> From: Rex Brooks <rexb@starbourne.com>
> To: McGarry, Donald P.
> Cc: emergency@lists.oasis-open.org <emergency@lists.oasis-open.org>
> Sent: Fri Jul 23 20:41:55 2010
> Subject: Re: [emergency] Error in RM Schema
>
> Thanks Don,
>
> Odd we didn't catch this considering how many different validators we 
> worked against, however, it still needs to be fixed.
>
> As long as we are past six months from the last errata, we can do 
> another errata. I'll check on it.
>
> Cheers,
> Rex
>
> McGarry, Donald P. wrote:
>   
>> 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
>>
>> dmcgarry@mitre.org <mailto:dmcgarry@mitre.org>
>>
>>
>> ------------------------------------------------------------------------
>>
>> ------------------------------------------------------------------------
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS TC that
>> generates this mail.  Follow this link to all your TCs in OASIS at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
>>     
>
>   

-- 
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]