Re: [urn] Feedback on draft-ietf-urnbis-rfc2141bis-urn-16

[Julian Reschke <[e-mail]>]

On 2017-01-10 07:28, Hakala, Juha E wrote:
> ...
> Yes, different namespaces definitely support different resolution services. In the ISSN namespace it is possible to request metadata about the identified periodical, or locations from which it can be found. But it is usually not possible to request all volumes and issues of a periodical.
>
> Identified resources also have an impact on resolution services. Dublin Core metadata record as an identified resource allows some services (including migration to another metadata format), large research datasets some others, such as extraction of selected variables.
>
> One aspect which is missing from Julian's suggestion above is that applications with which we manage resources also support different services. There are certain things an integrated library system can do for an electronic book, and then some other services only a digital preservation system can supply for the same book. Taken together, the different system with which organizations manage their digital collections will support a wide variety of services which can be requested using q- and r-components. Syntax and semantics of these components will evolve over time to reflect new functionalities supported by digital asset management systems in production.
> ...

My proposal was just to remove the (IMHO) confusing and unnecessary 
mention of RFC 3986... Yes, there may be other things to change -- this 
is why we're doing a Last Call, right?

Best regards, Julian