How much of this proposal, and of other similar proposals, can be handled by the asset description field? (Not much space is needed to store a URL.).I love namespaces, etc., but I want to keep the protocol-level as simple and as stupid as possible. We could do this sort of thing is Counterwallet and BootleXCP themselves, for example.
Extremely good point and porqupine has also communicated the same to me.
We would only need a naming convention on how to format the asset description field. The rest can be up to the client side to parse it.
As long as there was some defacto which was perhaps outlined by the Counterparty team but not necessarily enforced, then everyone would be a happy camper.
Eg Lets just use the tilde as a delimiting character in the description. Field 1 = namespace, field 2 = description, field 3 = url
It needs to be a new long asset name field that is enforced by the protocol for long names. A description will not work because users can put anything in there.