Dear Paul and Alexey, thanks for your remarks. We are pleased to work with you to fix all the issues still remaining in the current urn:lex version.
As regards the quoted issue on names or queries, the urn:lex draft actually talks about names. As pointed out by Alexey, any reference to queries is meant to clarify the principles of the resolution process for urn:lex, moreover the section “resolution” is expected in the draft template. As regards Paul’s remarks on the possibility to arrive at different forms of urn:lex starting from document metadata, this is actually meant to facilitate interoperability. A typical example is the possibility to create equivalent urn:lex names in different languages. Moreover, the addressed flexibility is also meant to cope with promoting interoperability when, for example, it is necessary to link legal resources from incomplete textual citations. In this case the suggested behavior of the resolution system can facilitate the discovery of the target resource. For the other issues raised, we will analyse them in details and get back to you soon. Best regards Pierluigi and Enrico --------------------------------------------------------- Enrico Francesconi ITTIG - CNR Institute of Legal Information Theory and Techniques Italian National Research Council Via de' Barucci 20 50127 Florence Italy Tel: +39-055-4399-665 Fax: +39-055-4399-605 email: [email protected] --------------------------------------------------------- > On 14 set 2017, at 19:04, Paul Kyzivat <[email protected]> wrote: > > Hi Alexey, > > On 9/14/17 12:25 PM, Alexey Melnikov wrote: >> Hi Paul, >> I am not an author, but let me disagree with one of your reported issues: >>> On 14 Sep 2017, at 16:45, Paul Kyzivat <[email protected]> wrote: >>> >>> (2) MAJOR: Name or query? >>> >>> A URN is by definition a *name*. Some parts of this document do focus on >>> the lex URN as a name. But the document also proposes using the lex URN as >>> a *query*. The following text from section 2 highlights this: >>> >>> "To cope with possible incomplete or inaccurate uniform names, >>> the implementation of a catalogue, based on a relational- >>> database, able to associate a URN to related URLs, is >>> suggested, as it will lead to a higher flexibility in the >>> resolution process. A resolver can provide names normalization, >>> completion of inaccurate or incomplete names, and finally their >>> resolution in network locations (see Section 8.2 and 8.3 for >>> characteristics and behaviour of a catalogue for resolution)." >>> >>> This behavior is inconsistent with the intent of URNs. >> I think the document is only talking about names. Association with URLs is >> the result of URN resolution process, which is a part of URN architecture. >> If this is not clear, I think it should be clarified (if authors agree that >> this is the intent). > > I found it very difficult to sort out what was fundamental and normative > regarding the URN from the parts that are aspirational about resolution and > use. Hence my recommendation that this document be split. Such a split may > well resolve this issue for me. > > I only pointed to this one place, but there are other places that express an > intention that it be possible to "guess" or recreate a lex URN based on > metadata about the document. That only makes sense if then intent is that the > resulting URN be resolvable to the document. But there are so many elements > to chosen and used or not for a given document that reasonable people are > likely to arrive at different forms of the URN. That ties in to the quote > above. > > Thanks, > Paul _______________________________________________ Gen-art mailing list [email protected] https://www.ietf.org/mailman/listinfo/gen-art
