search

airsalliance / airs-xml

Automatically exported from code.google.com/p/airs-xml
Creative Commons Zero v1.0 Universal
3 stars 2 forks source link

any top-level element can have any other as a child #47

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Can this be expanded so that the Agency, Site, ServiceSite (and Service if we 
can bring that into the schema) elements can have any of the other top-level 
element as a child? This would remove a lot of assumptions built into the 
schema about what can and cannot be in the Agency, Site and ServiceSite 
elements. 

For example, some clients want to put GeographicAreaServed information at the 
Site level, rather than the ServiceSite level. 

Anything that is prohibited by the AIRS standards should not be allowed (e.g. 
taxonomy assignments at the Site level), but otherwise it should be allowed in 
the schema. 

This might also illuminate new areas of the AIRS standards and style guide that 
should be better defined....e.g. perhaps GeographicAreaServed should not be 
allowed at the Site level - but that should first be incorporated into the AIRS 
standards and only then reflected in the AIRS XML Schema.

Original issue reported on code.google.com by e...@ejahn.net on 17 Feb 2012 at 3:08