Matthias Samwald wrote:
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.
id.type certainly seems like a good idea for the actual URL of a specific representation, as anything else doesn't "Save as..." well (except perhaps web pages, where browsers are smart enough to propose the .html extension).
