RE: Distinguishing between types of address (locn)

Hi Makx,

I know, Lawyers like to argue :) , but for XML repositories like ADMS[1] and StratML[2,3] the physical address is conceptual, I think.  By this I mean that all "physical address synonyms" are dereferenced to the name space located @loopback = 127.0.0.1.  The territories and coverage areas defined in that name space are another matter.

For StratML and Emergency Management, we (Russ Ruggiero and I) turned the chore of keeping track of territorial coverage to OASIS Common Alert Protocol (CAP 1.1 or 1.2).  We reuse the "area" element.  The reason is that US Government Warnings and Alerts as well as Weather Warnings or Alerts are in CAP format.  These feeds provide a ready source of detail for geophysical data, which in turn requires hardware resources beyond the reach of us normal folk and in the US these services are in the Public Domain[4] + free of charge.  Examples CAP "area" are here[5,6,7].

The "AlertPlace" module has an XSD schema.  This schema can be integrated easily into any of the StratML formats including (ISO 17469), ANSI/AIIM 22:2011, and the ISO configuration of  ANSI/AIIM 22:2011 still in the ISO process.

Here is an example Server Root (close your eyes and dream of Open Linked Data @localhost)
http://www.rustprivacy.org/2015/stratml/value-added


[1] https://joinup.ec.europa.eu/asset/adms/description
[2] http://www.stratml.us
[3] http://stratmlworld.com/
[4] Commercial opportunities are a political expedient.  Sorry.  Thanks to Pope Francis for keeping the politicians busy this morning so they do not have to hear this.
[5] http://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.html
[6] http://www.fema.gov/common-alerting-protocol
[7] http://alerts.weather.gov/



--------------------------------------------
On Thu, 9/24/15, Makx Dekkers <mail@makxdekkers.com> wrote:

 Subject: RE: Distinguishing between types of address (locn)
 To: "'Pano Maria'" <pano.maria@taxonic.com>
 Cc: public-locadd@w3.org
 Date: Thursday, September 24, 2015, 5:25 AM
 
 All,
 
 > 
 > > I think this is
 what you should do. Unless the two sites correspond to
 > > the same site.
 >
 
 > I don't follow. I do mean that
 they are one and the same site.
 > Say I
 have an organization O with site S1. And S1 has a
 registration address
 > Ar1 and a postal
 address Ap1. Would I then have to model an additional
 > instance S1'
 >
 representing the same site just to express the different
 addresses?
 > 
 
 I don't understand how one site (=physical
 location) can have two different addresses, one the
 registration address and one the postal address.
 Or is the issue that an *organisation* can have
 a postal address that is different from the registration
 address? If that is the issue, I'd argue that two
 different addresses are associated with different physical
 locations. E.g. the physical location of a post office box
 is at the post office, not at the location where the
 organisation has its office.
 
 Makx.

Received on Thursday, 24 September 2015 16:05:35 UTC