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


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-msg message

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

Subject: RE: [emergency-msg] Confusion about RM location elements

I agree with Gary – that’ll work.


As an additional piece of info regarding location, attached are the guidelines Carl provided to us in May.  I can’t remember whether we reviewed / considered this when making decisions on location.  I’ll admit I have not taken the time recently to review this.






From: Aymond, Patti [mailto:Patti.Aymond@iem.com]
Sent: Tuesday, January 30, 2007 2:29 PM
To: Karen Robinson; emergency-msg@lists.oasis-open.org
Subject: RE: [emergency-msg] Confusion about RM location elements




The structure of these elements haven’t been finalized, so the discrepancies persist.


You’re message caused me to pause and look seriously at the structure of these elements for the first time. I’ve never really stopped to “think” about what these structures should be. After taking a fresh look at this, I have a few suggestions for all of you to consider. I’ve attached is a suggestion on the structure of the ContactInformation and  Location elements. A few key points are listed below:


1)       I suggest that we eliminate the “CIQInformation” element as a complex structure. We can add a single sub-element to the ContactInformation element (e.g. OtherContactInfo) of type ciq:xcil that can contain any of the CIQ name, address, or other “party” information data.

2)       The LocationType structure would include the three conditional elements: LocationDescription (xsd:string), Address (ciq:xal), and TargetArea (geo-oasis:where).


Let me know what you think. If everyone agrees, I will clean up the document before releasing a new version with Rex’s updated ERMs.




Patti Iles Aymond, PhD
Senior Scientist, Research & Development
Innovative Emergency Management, Inc.
Managing Risk in a Complex World

8555 United Plaza Blvd.   Suite 100
Baton Rouge, LA 70809
(225) 952-8228 (phone)
(225) 952-8122 (fax)

From: Karen Robinson [mailto:Karen.Robinson@nicta.com.au]
Sent: Tuesday, January 30, 2007 12:00 AM
To: emergency-msg@lists.oasis-open.org
Subject: [emergency-msg] Confusion about RM location elements



Dear all,


I’m in the process of updating the RM message schemas and examples, and checking consistency with the latest version of the matrix and data dictionary.  I’m confused about the location elements.  The data dictionary lists the sub-elements of Location as being:


-          LocationDescription

-          ExplicitAddress (with sub-elements ExplicitAddressScheme & ExplicitAddressValue – both strings)

-          TargetArea (with sub-elements Circle, Polygon, Country, Subdivision, LocCodeUN – all strings)


However, I was previously under the impression that we were using a combination of CIQ addresses and the OASIS GML profile?  The CommonTypes schema lists the following as the sub-elements of Location:


-          Description

-          CIQInformation (with sub-elements Party and Address – probably only Address is needed in this context)

-          geo-oasis:where (with sub-elements Point, LineString, Polygon & Envelope)


Could somebody please clarify for me the latest decision about these elements?  In my opinion, if we are using CIQ for addresses in the ContactInformation package, we should stick with CIQ addresses for Location, for the sake of consistency.  Also, representing circles, polygons, etc. with strings does not seem like a good solution.  The alternative is to use the OASIS GML profile – however this has errors in it and does not seem to have been updated for a while (does anyone know what is happening with this?).






This email and any attachments may be confidential. They may contain legally
privileged information or copyright material. You should not read, copy,
use or disclose them without authorisation. If you are not an intended
recipient, please contact us at once by return email and then delete both
messages. We do not accept liability in connection with computer virus,
data corruption, delay, interruption, unauthorised access or unauthorised
amendment. This notice should not be removed.

No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.17.15/659 - Release Date: 1/30/2007 9:31 AM

No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.17.15/659 - Release Date: 1/30/2007 9:31 AM


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