Re: [cti] GeoLocation object

Looking at the rfc Paul provided it would appear it only supports lat/long not civic addresses.

 

I suggest if we are going to adopt a location mechanism that it supports both geo and civic capabilities as defined similar to or adopting
https://datatracker.ietf.org/doc/charter-ietf-geopriv/

 

Allan

 

From: 
"" <> on behalf of Dave Cridland <>

Date: Wednesday, September 7, 2016 at 5:14 AM

To: Paul Patrick <>

Cc: "" <>

Subject: Re: [cti] GeoLocation object

 

Perfect, that works for me.

 

On 7 Sep 2016 14:08, "Paul Patrick" <> wrote:

I’d go one step farther and just adopt RFC 7946 which is the standardization of GeoJSON specification from 2008.  For things like
 this, we should adopt the other standard and not try to create our own.

 

 

Paul Patrick

 

 

From:
<> on behalf of Jason Keirstead <>

Date: Wednesday, September 7, 2016 at 7:55 AM

To: Dave Cridland <>

Cc: "" <>

Subject: Re: [cti] GeoLocation object

 

There is also the GeoJSON standard which is used by a large number of products/projects

http://geojson.org/

It lets you define not just a discrete point, but also polygons which are good when you don't have precise locations.

-

Jason Keirstead

STSM, Product Architect, Security Intelligence, IBM Security Systems

www.ibm.com/security | 
www.securityintelligence.com

Without data, all you are is just another person with an opinion - Unknown 

Dave Cridland ---09/07/2016 01:48:49 PM---Folks, While
 we're discussing this, we might want to copy XMPP's GeoLoc object for

From: Dave Cridland <>

To: 

Date: 09/07/2016 01:48 PM

Subject: [cti] GeoLocation object

Sent by: <>

Folks, 

While we're discussing this, we might want to copy XMPP's GeoLoc object for this (after translating from XML to JSON):

https://xmpp.org/extensions/xep-0080.html

It's purely key/value as far as I remember, so should be easy to lift.

Dave.

 

This email and any attachments thereto may contain private, confidential, and/or privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments thereto) by others is
 strictly prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto.

---------------------------------------------------------------------

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