Re: [core] Web Link Attribute parsing problems
Carsten Bormann <cabo@tzi.org> Sat, 08 July 2017 04:01 UTC
Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6804127201 for <core@ietfa.amsl.com>; Fri, 7 Jul 2017 21:01:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3] 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 ZaiYhsYcRnOM for <core@ietfa.amsl.com>; Fri, 7 Jul 2017 21:01:06 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 A16ED126C2F for <core@ietf.org>; Fri, 7 Jul 2017 21:01:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v6840RBm010845; Sat, 8 Jul 2017 06:00:27 +0200 (CEST)
Received: from client-0003.vpn.uni-bremen.de (client-0003.vpn.uni-bremen.de [134.102.107.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3x4HnR2h7nz3ZWM; Sat, 8 Jul 2017 06:00:27 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <02b301d2f78f$14aad650$3e0082f0$@augustcellars.com>
Date: Sat, 08 Jul 2017 06:00:26 +0200
Cc: core@ietf.org
X-Mao-Original-Outgoing-Id: 521179226.139943-7c305af7fe4c705ce9c4be5d5910e539
Content-Transfer-Encoding: quoted-printable
Message-Id: <B13EE677-838B-4D59-8C24-E114794CB025@tzi.org>
References: <02b301d2f78f$14aad650$3e0082f0$@augustcellars.com>
To: Jim Schaad <ietf@augustcellars.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/1kWx9_jhHGQuHcYZ6zFbCjXbKc4>
Subject: Re: [core] Web Link Attribute parsing problems
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Jul 2017 04:01:08 -0000
Hi Jim, It is indeed a weakness of RFC 6690 that it does not define a way to find out which future attributes are going to be space-separated lists and which ones aren’t. (It is hinting at using this for "relation-type attributes”, but there is no way to guess whether that is the case for an attribute unknown to the parser.) > Is there a recommended way to proceed? Implementation-wise, I would give the application a way to provide a list of attribute names for “relation-type attributes”. Beyond that, I also don’t know how to implement functions such as discovery queries without that semantic knowledge. Maybe we should at least press forward with having a registry for attributes; the space-separatedness can then be a column in the registration template. Grüße, Carsten
- [core] Web Link Attribute parsing problems Jim Schaad
- Re: [core] Web Link Attribute parsing problems Carsten Bormann