[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [External] [cti-stix] Re: [EXT] [cti-stix] Location, latitude/longitude, and precision
So what is the problem this would actually solve? I understand the use case of specifying a human-readable location (“Dallas, Texas, USA”, “1600 Pennsylvania Ave, Washington, DC”, etc.) but I don’t quite understand
what lat/long is used for in this context. From: <cti-stix@lists.oasis-open.org> on behalf of Bret Jordan <Bret_Jordan@symantec.com> Since we do not yet really know what we need here, I would propose that we add this field at a later time. I fully understand the problem we think we are trying to solve, but I am not sure we have identified the best solution. It would
be nice if we had a bunch of real-world problems in products that were driving this. Further, if you are uncertain about a location you should NOT be using lat/long to represent the location. You should be using one of the other properties like region, country, city, administrative_area, etc. Those are the named non-precise
ways of doing location. Bret
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. ______________________________________________________________________________________ www.accenture.com |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]