# Normalized Email object

**URL:** <https://forum.openreferral.org/t/normalized-email-object/741>\
**Category:** Technical\
**Created:** [September 17, 2025, 5:16pm UTC](https://forum.openreferral.org/t/normalized-email-object/741 "2025-09-17T17:16:08Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![skyleryoung](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openreferral.org/skyleryoung/32/212_2.png) [@skyleryoung](https://forum.openreferral.org/u/skyleryoung)\
**Post date:** [October 15, 2025, 10:49pm UTC](https://forum.openreferral.org/t/normalized-email-object/741/3 "2025-10-15T22:49:09Z")

</div>

I think the use cases for this are weaker than they were for, say, phones, so I’ll just put that out there. Email is used much less frequently as a primary means of contact for services (at least for most of my clients). However, to the extent that it’s started coming up more frequently, it prompted me to wonder why our contact methods aren’t handled in a standardized way. Email would seem to be the last one that’s not normalized at the tabular level.

I really love having the phone and URL tables broken out separately, because it provides the opportunity to include descriptions, types, and other useful meta info that can be used to improve the experience in user facing solutions like our Resource Directory.

Is that an adequate use-case? 🙂

I wouldn’t say that adding an email object is a major impetus for speeding up our next major release, but I definitely think we should include it _in_ our next major release when that’s ready.

---

_[View the full topic](https://forum.openreferral.org/t/normalized-email-object/741)._