# Re: URN Resolution Paths Considered Harmful

Fisher Mark (FisherM@is3.indy.tce.com)
Mon, 10 Jul 95 11:06:00 PDT

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Larry Masinter: "Re: URN Resolution Security and Privacy Issues"
- Previous message: Fisher Mark: "Re: URN Resolution Paths Considered Harmful"
- Maybe in reply to: Fisher Mark: "URN Resolution Paths Considered Harmful"
- Next in thread: Mark Madsen: "Re: URN Resolution Paths Considered Harmful"
- Reply: Mark Madsen: "Re: URN Resolution Paths Considered Harmful"

Because:
1) URN resolution services are just a database system; and
2) The most successful database technology so far (relational databases)
does not include the resolution path in the query, but leaves up to the
resolver;
I think that we should follow the direction of other database systems by not
encoding the resolution path into the URN.
======================================================================
Mark Fisher Thomson Consumer Electronics
fisherm@indy.tce.com Indianapolis, IN

- Next message: Larry Masinter: "Re: URN Resolution Security and Privacy Issues"
- Previous message: Fisher Mark: "Re: URN Resolution Paths Considered Harmful"
- Maybe in reply to: Fisher Mark: "URN Resolution Paths Considered Harmful"
- Next in thread: Mark Madsen: "Re: URN Resolution Paths Considered Harmful"
- Reply: Mark Madsen: "Re: URN Resolution Paths Considered Harmful"