Help with how we should address ordinals in our new protocol, WTTP

[nickjuntilla]

We are designing a new protocol and we would like some help from the ordinals community how you would like your assets represented. The protocol name is WTTP, Web Three Transfer Protocol, which is designed to address blockchain assets on various chains and display them in the browser. You can see the source code here:

WTTP

The issue we're currently working with is how we should address ordinals to display in our tools, including a new browser. When viewed in our browser these links can be pasted in the search bar or used as anchor links inline in-page.

After reading the page you have here, it seems we have 4 options for addressing ordinals.

1. ord:6fb976ab49dcec017f1e201e84395983204ae1a7c2abf7ced0a85d692e442799i0 -- This may work for in-page links, but will present us with some issues in the browser url bar because it's lacking // and it appears you may not have meant it to be used as a protocol by itself.
2. ord://6fb976ab49dcec017f1e201e84395983204ae1a7c2abf7ced0a85d692e442799i0 -- This is not standard to your specification and we wouldn't want to just add it.
3. wttp://ord:6fb976ab49dcec017f1e201e84395983204ae1a7c2abf7ced0a85d692e442799i0 -- This would add a protocol, be easy to implement and match your format.
4. wttp://6fb976ab49dcec017f1e201e84395983204ae1a7c2abf7ced0a85d692e442799i0:bitcoin -- This is closer to how we address assets on other chains like Ethereum. i.e. wttp://.:/, but diverges from your specification.

Thank you for any input

[raphjaph]

We have some documentation on URIs here: https://docs.ordinals.com/inscriptions/uris.html

[nickjuntilla]

I referenced that in my question. In our use case it's not clear from that documentation.

[raphjaph]

I think @casey might have some thoughts on this especially on ord: vs ord://.

[casey]

I would try ord:6fb976ab49dcec017f1e201e84395983204ae1a7c2abf7ced0a85d692e442799i0, and then if you run into practical difficulties with it do ord://6fb976ab49dcec017f1e201e84395983204ae1a7c2abf7ced0a85d692e442799i0. ord:// is not correct for some pretty nitpicky technical reasons (doesn't refer to a heirarchical resource) but ultimately doesn't matter.