> I sort of regret the commons/type/source/id structure I chose for > our PURLs; doing commons/source/type/id would have been better, I > think, and commons/source/id.type is not terrible.
"+1"
I would actually prefer the "commons/source/id.type" pattern, if it can be implemented with the current purl.org system. It is more intuitive to most developers/users and it brings the elements of the URI into a nice hierarchical order.
- Matthias
|