URN's aren't ideal - maybe we can define standard fields for URC's, but
URN's are more designed to work like this:
URN:URC::DNS-hostname:host IP number:
I.e. you give a resource a URN, and then you can change its physical
location without breaking links to it.
URN's could have keywords as part of the name, but it isn't as flexible
as what Mark (and others out here :) want. Now, Universal Resource
Containers describe meta-information about objects, and (in the proposal)
will be resolved and cached around the net much like DNS is now (they
also provide the URN->URL resolution). Having some standard vrml-related
metainformation fields (like keywords) in there might not be a bad idea.
This is how local caching should work, and is one solution to the
Your slick hype/tripe/wipedisk/zipped/zippy/whine/online/sign.on.the.ish/oil
pill/roadkill/grease.slick/neat.trick is great for what it is. -- Wired Fan #3
email@example.com firstname.lastname@example.org http://www.hotwired.com/Staff/brian/