Hi -
I have been quiet for a while :-) So, jumping back in with both feet.
Scanning the spreadsheet and checking out items such as Contact and Incident
Location and COuntry, I would really encourage this group to look at the
work done in the IETF and NENA for Next Generation 911. Would be nice to use
the same encodings, terms and definitions, and so forth. These two groups
along with the OGC have spent years working on various location elements for
standards for use in the EM community. A number of these are now mandatory
to implement in the i3 NG 911 architecture.
Check out:
http://datatracker.ietf.org/wg/geopriv/ for a list of IETF location related
RFCs and in progress documents. Please note, for example, that CISCO has
already implemented the DHCP location conveyance option in their new
generation routers.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/7_1_2/ccmfeat/fsgeoloc.html#wpxref24864
While a binary encoding, the geometry content model is consistent with ISO
19107 and GML. There are tools for mapping the DHCP location encoding into
GML.
A bit harder to get to the NENA documents as you need to be a registered
NENA use. That said, NENA NG 911 is using the Location Object as defined by
the IETF. They are also using vcard for contact information.
Any questions, please let me know.
Cheers
Carl
Original Message -----
From: