-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Term request: email address + phone number, postal address #130
Comments
From alanruttenberg@gmail.com on January 03, 2012 16:46:55 Added provision ID http://purl.obolibrary.org/obo/IAO_0000429 and editor note pointing to this thread. |
From stoec...@upenn.edu on January 03, 2012 18:59:03 I had not realized that there is such a mechanism as creating addresses with '+' on the fly. Given that, I agree with you completely.
On Tue, Jan 3, 2012 at 7:56 PM, Bjoern Peters bpeters@liai.org wrote:
There is a mechanism, but it is not necessarily CRID based - the gmail
For mail addresses I agree. For email addresses I'm not so sure. If I've taken the CRID case to mean there is a single database of some There's no question that email addresses have a somewhat organized way -Alan I'm having some doubts about the "about geographic location" axiom on
-- |
From stoec...@upenn.edu on January 04, 2012 13:29:16 From: Bill Hogan hoganwr@gmail.com Just to emphasize Alan's point, there is a huge difference between |
From stoec...@upenn.edu on January 04, 2012 13:52:57 I agree with Alan about inclusion of protocol in the definition of email address as it obviates the issue of spoofing since SMTP servers don't use header addresses according to the wikipedia link Alan provided. |
From stoec...@upenn.edu on August 13, 2012 10:02:18 At ICBO, I discussed phone number with Alan Ruttenberg along with email address and postal address as these seem to all be of the same type in some way. They share a communication objective but have different modalities (phone Summary: Term request: email address + phone number, postal address |
From alanruttenberg@gmail.com 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 stoeckrt@pcbi.upenn.edu
Date: Tue, Jan 3, 2012 at 6:15 PM
To: IAO Discuss information-ontology@googlegroups.com
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:
apologies if this has been discussed before but hard to search for in the discussion list.
Thanks
Chris
From: Alan Ruttenberg alanruttenberg@gmail.com
Date: Tue, Jan 3, 2012 at 7:20 PM
To: Chris Stoeckert stoeckrt@pcbi.upenn.edu
Cc: IAO Discuss information-ontology@googlegroups.com
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:alanruttenberg@gmail.com and we would then have assertions
< mailto:alanruttenberg@gmail.com > 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
The text was updated successfully, but these errors were encountered: