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

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-comment message

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


Subject: EDXL-RM additional issues....?


All,

 

One of our new software developers came across some EDXL-RM issues that I’m not if they have been addressed yet. However, I am passing his information along to get added or noted for feedback and reply.

 

 

 

For example, there are some inconsistencies in the use of namespaces between the documentation and examples. For importing and displaying, I am ignoring namespaces, since we don't really care as long as the XML validates correctly and the actual node name is correct. But for producing a new message, it would be nice to be a little more definitive, since we don't know how strict a receiving organization will be. Part of it may be my limited understanding of namespace syntax in an Xml document. For example, There is a LocationType element defined on page 127 of the EDLX-RM standard. LocationType specifies an Address element of type xal:AddressType. The example on page 59 shows it being used in the ScheduleInformation element. The syntax is:

 

<rm:Address>

<xal:Country></ xal:Country>

...

</rm:Address>

 

I assumed that the "rm" was used since <Address> was resource metadata for <Location>. But then if you look at page 126 where AddressType is used in the <AdditionalContactInformation> element, it uses the syntax:

 

<xal:Address>

<xal:Country></ xal:Country>

...

</xal:Address>

 

And then if you look further on page 126, the <PartyName> element uses the "xnl" namespace, but <Addresses> and <ContactNumbers> use "xpil". It states at the top of page 126 that PartyType is in the "xpil" namespace, so I don't know if these are typos, or if I just don't have a good understanding of how to cascade namespaces.

 

On top of that, some of the example Xml that I downloaded from their website are missing required elements, but have additional elements that don't appear in the standard. As for these, I just ignore the extra elements, and go strictly by what it says in the standard.

 

Overall, it seems like the documentation is a little immature.

 

 

 

Thanks,

 

Timothy D. Gilmore | SAIC

Senior Test Engineer | ILPSG | NIMS SC | NIMS STEP

phone: 606.274.2063 | fax: 606.274.2012

mobile: 606.219.7882 | email: gilmoret@us.saic.com  

P Please consider the environment before printing this email.

 



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