# We need a normalized \`url\` table in the pattern of the \`phone\` table

**URL:** <https://forum.openreferral.org/t/we-need-a-normalized-url-table-in-the-pattern-of-the-phone-table/431>\
**Category:** Technical\
**Tags:** datastructure\
**Created:** [September 14, 2023, 4:25pm UTC](https://forum.openreferral.org/t/we-need-a-normalized-url-table-in-the-pattern-of-the-phone-table/431 "2023-09-14T16:25:13Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [September 14, 2023, 4:52pm UTC](https://forum.openreferral.org/t/we-need-a-normalized-url-table-in-the-pattern-of-the-phone-table/431/4 "2023-09-14T16:52:07Z")

</div>

@devin I agree wholeheartedly that `attribute` would be much more useful with a `description` field included.

@bloom thanks for the reference. I forgot that I was involved in that Github issues thread as well. I don’t see any recent activity there though. It _does_ seem like a normalized table would be generally well received, based on that thread. What’s it take to promote that recommendation?

---

_[View the full topic](https://forum.openreferral.org/t/we-need-a-normalized-url-table-in-the-pattern-of-the-phone-table/431)._