<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 5, 2019, at 7:11 PM, Eric Seidel <<a href="mailto:eric@seidel.io" class="">eric@seidel.io</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">My main concern is that I'd like us to be consistent in how we disambiguate namespaces. If we want to use `data`, we should use it everywhere (synonyms are fine by me as long as they are also consistent). This would means we'd need to revise the fixity proposal I linked to above.<span class="Apple-converted-space"> </span></span></div></blockquote></div><br class=""><div class="">Yes, I should have included this in my email. If we decide to go in this direction, I would want to be consistent. This would include updating the fixity proposal (which is, I believe, still unimplemented) and expanding -XExplicitNamespaces to include `data`. Eventually, we would deprecate the use of `pattern` in import/export lists and then remove that feature. I suppose all this would necessitate yet another proposal.... but I do think the wider community (not just this list) should weigh in. However, before doing so, I'd be curious for more feedback from this group as a test-bed.</div><div class=""><br class=""></div><div class="">Richard</div></body></html>