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

"Svensson, Lars" <L.Svensson@dnb.de> Wed, 11 January 2017 08:42 UTC

Return-Path: <L.Svensson@dnb.de>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22797129A8A for <urn@ietfa.amsl.com>; Wed, 11 Jan 2017 00:42:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level:
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-3.199] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m-Wlo1HZ_-8l for <urn@ietfa.amsl.com>; Wed, 11 Jan 2017 00:42:16 -0800 (PST)
Received: from mail.dnb.de (prodfix-out0.dnb.de [193.175.100.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 935B51294A9 for <urn@ietf.org>; Wed, 11 Jan 2017 00:42:16 -0800 (PST)
Received: from smg1.ad.ddb.de (unknown [10.69.63.232]) by mail.dnb.de (Postfix) with ESMTP id 2F7164455D08; Wed, 11 Jan 2017 09:42:14 +0100 (CET)
X-AuditID: 0a453fe7-171ff70000000f1b-68-5875efe2bd8a
Received: from dnbf-ex1.AD.DDB.DE (dnbf-ex1.ad.ddb.de [10.69.63.245]) by smg1.ad.ddb.de (DNB Symantec Messaging Gateway) with SMTP id F0.B7.03867.2EFE5785; Wed, 11 Jan 2017 09:42:13 +0100 (CET)
Received: from DNBF-EX1.AD.DDB.DE ([fe80::7076:30f7:60ad:16a0]) by dnbf-ex1.AD.DDB.DE ([fe80::7076:30f7:60ad:16a0%12]) with mapi id 14.03.0224.002; Wed, 11 Jan 2017 09:42:09 +0100
From: "Svensson, Lars" <L.Svensson@dnb.de>
To: Julian Reschke <julian.reschke@gmx.de>
Thread-Topic: [urn] Feedback on draft-ietf-urnbis-rfc2141bis-urn-16
Thread-Index: AQHSaQ2diiw30zGR+kafTGD0ekYhHqEte62AgAADiwCABWrnkA==
Date: Wed, 11 Jan 2017 08:42:08 +0000
Message-ID: <24637769D123E644A105A0AF0E1F92EF010D2ACF68@dnbf-ex1.AD.DDB.DE>
References: <ed99a67a-10b6-c505-f223-2250fac836c0@gmx.de> <e041edc5-7a17-e5cb-1bf2-417cfefa827e@gmx.de> <20022D35B6F9EC84EF0C7901@PSB> <ee4de10a-6798-8e89-1395-e9370be6012c@gmx.de>
In-Reply-To: <ee4de10a-6798-8e89-1395-e9370be6012c@gmx.de>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.69.12.193]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA11Tb0gTcRjut930nP7snM79Whl5Yh+sTCFEIlTMwDQqKmpJpWe7tuX8024T F1Gi+aGBQ8PAP5hZyw+ipQb9N3Ra2h8sBCsUNTHNqaUJTvpi3e1OO/323vM+z/M+7+/lcKli zFuNG3LMtCmHMpJeckx+IH5x18ScRRM10RkR+2hsVhZ7q3hekiBJnv99Ltnh+CM5KkmT79PS RkM+bdodlyHXF3feBXlNioJa97h3IWj1twEfHBF7UFPpDZkNyHEF0QVQf00Dxn88Aajb3gds wBv3IiLQnJ7jB7HV0Eg74GopEYraRiskXB1IJKIhe62M5+xHY42NgK8T0UN3jRdXY0Q4Gugt 9uCQSEWTZR3CqKcAjX5d8hj5EHtRTVGvxwgQIail5aOUH6ZCbZNLMj40gRwveRwRSuQaXxbw bajsusub50ehub46QbsDNdTPSPnBAeht1XesDCirRbbVIkm1SFItktwBWCPwZ7J10ZGUNlKr zYzU0m2Av8WPp8Den+QEBA5IP0jPmjUKGZXPWLOd4AguIZXww4xFo/DPzNVa9RSjTzdZjDRD BkH3KMuEq3CmxZhFboWPXSxZtYoyFibPcN6Qa2HSLSajEyBcykobplkS1FLWy7Qplzd0gs04 Rqqg69UGjYLQUWY6i6bzaNNKV4PjJIJdP1lhgInW0QUXDEbzSpvVPZ9iO4S44wkUCuO59Gpx Y30mCe7jBIdwPzZY0S8uGJNHZTMGneAdCCsdLOq3gnp8Q+Awt2jwCrjW8x04rlbBKi4swTH0 lpzVrOpgiLWyL7dR1OAs1dtgRxKjUWwS4Wtdp8FB9kSB8AHn68f+Uf8zKqCNS+4rgJ6IW+A3 LqJSwNZ7HWJvGwRPxzHcwmbKLF74vsuzsIAKC5dPexYWwLV26kKA5Z/NvHJT6ivJdXd+9s8O sn7qf2M/+8LLHu5uRsrytp33rCmve9QzYT3hhzPIsYoF1VGf2tb6EmxKc7U9zTGo77ttkx2O qbxEdqekgcHUlmvypOljk3GJ9ZNhlQt1aEZ+8dng4vaYkhHdculUoSFrIP5LwonmpeGTfxdO nXlfR2KMnoqOkJoY6h9tqnkqdAQAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/SYSyFhuAJqLWCpyYCSP1SWM1HSg>
Cc: "urn@ietf.org" <urn@ietf.org>
Subject: Re: [urn] Feedback on draft-ietf-urnbis-rfc2141bis-urn-16
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn/>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jan 2017 08:42:21 -0000

Julian, all

On Saturday, January 07, 2017 10:58 PM, urn [mailto:urn-bounces@ietf.org] On Behalf Of Julian Reschke wrote:

> >>>    For the sake of consistency with RFC 3986, neither the
> >>>    general syntax nor the semantics of q-components are
> >>>    defined by, or dependent on, the namespace of the URN.  In
> >>>    parallel with RFC 3896, specifics of syntax and semantics,
> >>>    e.g., which keywords or terms are meaningful, of course
> >>>    may depend on a particular namespace or even a particular
> >>>    resource.
> >>>
> >>> I agree that this is the right thing to do, but I'm not sure
> >>> what this has to do with 3986.  3986 allows a scheme to
> >>> mandate a specific syntax, no?
> >
> > Yes, at least as I read it.   But, IIR, there have been some
> > claims that 3986 does not obviously allow a scheme to delegate
> > the syntax to other (non-scheme) parts of the URI (specifically
> > a namespace in the urn scheme case).   At this point, I would
> > personally prefer sentences to the effect of "no matter what you
> > think 3986 says, URNs works this way...", but I don't think that
> > a proposal like that would be constructive or helpful.   If you
> > think this is important and want to propose alternate text,
> > please do so.
> > ...
> 
> So we agree on what RFC 3986 says :-). I think the right conclusion is
> to strip the prose wrt RFC 3986. Just say:
> 
> "Neither the general syntax nor the semantics of q-components are
> defined by, or dependent on, the namespace of the URN.  Specifics of
> syntax and semantics, e.g., which keywords or terms are meaningful, of
> course may depend on a particular namespace or even a particular
> resource."

Since the q-component is always passed directly to the resource representation returned by the URN resolver, I'd say that any syntactical and semantic constraints of the q-component depends _entirely_ on that resource representation. My suggestion would be to strip references to the URN namespace, too:

[[
Neither the general syntax, nor the semantics of q-components are defined or dependent on the namespace of the URN. Specifics of syntax and semantics, e. g., which keywords or terms are meaningful, depend entirely on the particular resource representation.
]]

Best,

Lars