Term request: email address + phone number, postal address

[zhengj2007]

From [email protected] on January 03, 2012 19:23:03

From: https://groups.google.com/group/information-ontology/browse_thread/thread/cb03fa62269dd995 Subject: [IAO] email address

From: Chris Stoeckert [email protected] Date: Tue, Jan 3, 2012 at 6:15 PM To: IAO Discuss [email protected]

Hi (and Happy New Year) I have multiple use cases that require specification on an email address. 'postal address' (IAO_0000422) is actually quite close (defined as: A textual entity that is used as directive to deliver something to a person, or organization) however it is logically defined as 'is about' some 'geographical location' which does not fit. I propose:

1. adjusting the textual definition of postal address to reflect its dependency on geographical location.
2. addition of the term 'email address' with a definition such as " A textual entity that is used as directive to deliver something electronically to a person, or organization." For differentia from 'postal address', we need to indicate what 'email address' is about but I don't think we have something appropriate for an electronic account (not really a device).

apologies if this has been discussed before but hard to search for in the discussion list. Thanks Chris

---

From: Alan Ruttenberg [email protected] Date: Tue, Jan 3, 2012 at 7:20 PM To: Chris Stoeckert [email protected] Cc: IAO Discuss [email protected]

Clearly a mixed message here. The reason that the textual definition doesn't mention geographical location is that there are postal addresses that are not geographically fixed, for example addresses on warships. I would say it is loosely about geographical location in that eventually it is a material entity that is delivered somewhere specifically located (to a site, perhaps). So the text should be adjusted, but with a mind to not confuse postal address with names for geographic location such as longitude and latitude coordinates. We probably should include something about email addresses used as intended, and for other uses. Legitimate uses are as identifiers for persons and organizations, such as when used as a login, and to record provenance, as when used in the "From:" field. Illegitimate uses are, for example, spoofing From: addresses by spammers. I think that the definition of email address should make reference to the protocols that define delivery, something along the lines of delivering information to a mailbox by certain protocols. The protocols are well documented on the wikipedia page: http://en.wikipedia.org/wiki/Email_address In addition, since there is a standard for email address URIs, these should be used for instances. I.e. the URI for my gmail box would be: mailto:[email protected] and we would then have assertions

< mailto:[email protected] > instanceOf(i.e. rdf:type) <iao:email address> (whatever the id is)

etc. Protege lets you explicitly set the URI of a term. I'm going to add an issue once I send this email, and copy the conversation (or leave pointers) there. If you agree with the strategy and want to have a go at a definition, please add it to the issue thread?

Original issue: http://code.google.com/p/information-artifact-ontology/issues/detail?id=130