> Dick Hardt scripsit: > > > To elaborate, anything starting with dix:/ would be reserved for > > identifiers in the DIX standard. eg. dix:/core#1 > > Anyone with a domain name can define their own. eg. dix://acm.org/foobar > > It looks like the tag: URI scheme would be appropriate: it's used for > identifying > rather than locating, and anyone with a domain name or email address > can assign one.
Indeed, if it's important to have the URIs not be dereferenceable, tags URIs (RFC 4151, which I co-wrote) are a fine choice. On the other hand, it's often very useful to provide information about the identified thing, via URI dereference, so I strongly recommend using an HTTP one, even though it can feel like like a strange approach. -- sandro _______________________________________________ dix mailing list [email protected] https://www1.ietf.org/mailman/listinfo/dix
