# Standard representation of asset ownership vs token

**URL:** https://forums.counterparty.io/t/standard-representation-of-asset-ownership-vs-token/6435
**Category:** Counterparty
**Created:** [October 6, 2022, 4:31am UTC](https://forums.counterparty.io/t/standard-representation-of-asset-ownership-vs-token/6435 "2022-10-06T04:31:52Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![JPJA](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/jpja/32/1324_2.png) [@JPJA](https://forums.counterparty.io/u/JPJA)
#### Post date: [October 6, 2022, 4:31am UTC](https://forums.counterparty.io/t/standard-representation-of-asset-ownership-vs-token/6435/1 "2022-10-06T04:31:52Z")

</div>

If you have a token of, say MYTOKEN, we refer to it with capitalized letters. We’re lucky to have this standard as it makes XCP tokens stand out across crypto.

Since there is a unique “mytoken” asset ownership independent of the MYTOKEN tokens, I wonder how best to reference it in the least confusing way?

One way could be to use lowercase with a domain extension, e.g.  
mytoken.xcp  
or  
mytoken.btc

Perhaps @ would be better?  
mytoken@xcp  
or  
mytoken@btc

Then, of course, there are subasset owneships:  
mytoken.subasset@xcp  
or  
mytoken.subasset@btc

Since subasset are case-sensitive, it could make sense to apply a soft rule that only low caps are allowed for aliases. That’s how namecoin domain works. On the protocol all three are allowed; `d/bitcoin`, `d/Bitcoin`, `d/BITCOIN` but only `d/bitcoin` is a standard .bit domain.

This is only brainstorming from me at this point. Curious to hear what you think.