
From nobody Fri Jan 22 12:27:47 2016
Return-Path: <ben@nostrum.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35B111A8758; Fri, 22 Jan 2016 12:27:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
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 E7x-GZiuY9KK; Fri, 22 Jan 2016 12:27:45 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10F381A8726; Fri, 22 Jan 2016 12:27:45 -0800 (PST)
Received: from [10.0.1.10] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u0MKRf33088428 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 22 Jan 2016 14:27:42 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.10]
From: "Ben Campbell" <ben@nostrum.com>
To: urn@ietf.org
Date: Fri, 22 Jan 2016 14:27:41 -0600
Message-ID: <E96AC288-9E77-4C06-976C-90C33D9563DC@nostrum.com>
MIME-Version: 1.0
X-Mailer: MailMate (1.9.3r5187)
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/0fgIJapfnfRa2zVvKRCiEwEhtQQ>
Cc: ART ADs <art-ads@ietf.org>, urnbis-chairs@ietf.org, Alexey Melnikov <aamelnikov@fastmail.fm>
Subject: [urn] message to urnbis
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 22 Jan 2016 20:27:46 -0000

Hi Everyone,

As part of the AD transition from Barry to Alexey, and because urnbis
is in need of a new co-chair with Andy, we are making the following
changes to the urnbis working group management:

1. Ben Campbell will take over as responsible AD until IETF 95.

2. Alexey Melnikov will take over as responsible AD after IETF 95.
Between now and then, Ben will delegate the AD responsibilities to
Alexey to the extent possible, retaining formal responsibility.

3. Barry Leiba will co-chair the working group with Andy Newton.

During this period, anything that can't be resolved with the chairs
should be brought jointly to Alexey and Ben.

Thanks!

Ben


From nobody Wed Jan 27 06:10:54 2016
Return-Path: <cabo@tzi.org>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9659F1B2E78 for <urn@ietfa.amsl.com>; Wed, 27 Jan 2016 06:10:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level: 
X-Spam-Status: No, score=-0.701 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 wDjltmm0mPce for <urn@ietfa.amsl.com>; Wed, 27 Jan 2016 06:10:50 -0800 (PST)
Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D74161B2E74 for <urn@ietf.org>; Wed, 27 Jan 2016 06:10:49 -0800 (PST)
Received: from mfilter31-d.gandi.net (mfilter31-d.gandi.net [217.70.178.162]) by relay4-d.mail.gandi.net (Postfix) with ESMTP id 60C0A1720E9; Wed, 27 Jan 2016 15:10:48 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mfilter31-d.gandi.net
Received: from relay4-d.mail.gandi.net ([IPv6:::ffff:217.70.183.196]) by mfilter31-d.gandi.net (mfilter31-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id fXO37wYjcvf7; Wed, 27 Jan 2016 15:10:46 +0100 (CET)
X-Originating-IP: 134.102.218.240
Received: from pptp-218-1.informatik.uni-bremen.de (pptp-218-1.informatik.uni-bremen.de [134.102.218.240]) (Authenticated sender: cabo@cabo.im) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id 583B81720A4; Wed, 27 Jan 2016 15:10:45 +0100 (CET)
Message-ID: <56A8CFE5.5010200@tzi.org>
Date: Wed, 27 Jan 2016 15:10:45 +0100
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: urn@ietf.org
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn/DsBZbdOZu-zYwjwlaK9b_Wg7x_k>
Subject: [urn] URNs for media types and other protocol constants relevant to interoperability
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.15
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, 27 Jan 2016 14:10:51 -0000

In W3C WoT IG, we are looking at employing RDF to represent information
that is today often held in Web links (RFC 6690, RFC 5988).
That includes media types, but also maybe link relation types and other
registry content.
It would be great to have a canonical mapping to URIs for all these.
Has there been any attempt in the past to define, say, URNs for media types?
Any other advice on how to obtain stable URIs for protocol constants?
(I don't think we want to use the URL to the IANA registry page.)

Grüße, Carsten

