Re: [Uri-review] Review Request of new URI Scheme
Eric Johnson <eric@tibco.com> Fri, 09 August 2013 20:34 UTC
Return-Path: <eric@tibco.com>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B7921F0D8F for <uri-review@ietfa.amsl.com>; Fri, 9 Aug 2013 13:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pamzl13fV2VD for <uri-review@ietfa.amsl.com>; Fri, 9 Aug 2013 13:34:40 -0700 (PDT)
Received: from mx2-app.tibco.com (mx2-app.tibco.com [63.100.100.143]) by ietfa.amsl.com (Postfix) with ESMTP id 984EA21F9C8B for <uri-review@ietf.org>; Fri, 9 Aug 2013 13:29:30 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.89,848,1367996400"; d="scan'208";a="74417234"
Received: from tibco-5.tibco.com (HELO PA-CASHUB02.na.tibco.com) ([63.100.100.5]) by mx2-app.tibco.com with ESMTP/TLS/AES128-SHA; 09 Aug 2013 13:29:30 -0700
Received: from PA-MBX01.na.tibco.com ([fe80::e097:9c1b:e6c3:5bc1]) by PA-CASHUB02.na.tibco.com ([fe80::bd2a:d214:3097:6897%10]) with mapi id 14.03.0123.003; Fri, 9 Aug 2013 13:29:29 -0700
From: Eric Johnson <eric@tibco.com>
To: Mirko Nosenzo <mirko.n@incomedia.eu>
Thread-Topic: [Uri-review] Review Request of new URI Scheme
Thread-Index: AQHOlOq8lST9h9zZe0m2CFecV2hoJJmNVHbd
Date: Fri, 09 Aug 2013 20:29:29 +0000
Message-ID: <5209AE78-9A6C-4549-BD79-05DFF1617918@tibco.com>
References: <490F1DBE-15CF-4F1D-96EE-DB5B465C936D@incomedia.eu>
In-Reply-To: <490F1DBE-15CF-4F1D-96EE-DB5B465C936D@incomedia.eu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "uri-review@ietf.org" <uri-review@ietf.org>
Subject: Re: [Uri-review] Review Request of new URI Scheme
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uri-review>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Aug 2013 20:34:44 -0000
This doesn't strike me as a URI, so much as a string that follows - almost - the URI syntax. In any event, the documentation below strikes me as insufficient. Especially the semantics part doesn't make it even the slightest bit clear as to why a new URI scheme might be useful, and if it is useful, how to use it. As near as I can tell, the "feedready:https://..." form contains exactly the same information and semantics as just doing "https://..." Eric Sent from my iPad On Aug 9, 2013, at 3:25 AM, "Mirko Nosenzo" <mirko.n@incomedia.eu> wrote: > Hello, > please review the following URI scheme: > > ------------------------------------------------------------------- > Resource Identifier (RI) Scheme name: feedready > > Status: provisional > > Scheme syntax: > feedready:<absolute_uri> or feedready://<hierarchical part> > examples: feedready://example.com/rss.xml and feedready:https://example.com/rss.xml > > Scheme semantics: > FeedReady is a feed reader application developed by Incomedia. > > Encoding considerations: > Unknown, use with care. > > Applications/protocols that use this scheme name: > FeedReady application > > Interoperability considerations: > Unknown, use with care. > May be unsuitable for open use on the public internet. > > Security considerations: > Unknown, use with care. > > Contact: > Registering party: Mirko Nosenzo <mirko.n@incomedia.eu> > Scheme creator: Incomedia > > Author/Change controller: > Either the registering party or someone who is verified to represent > the scheme creator. See previous answer. > > References: > http://feedready.com > ------------------------------------------------------------------- > > Thanks, > /*******************************************************************/ > /* Mirko Nosenzo / Software Architect / Incomedia */ > /* mirko.n@incomedia.eu / http://incomedia.eu */ > /*******************************************************************/ > > _______________________________________________ > Uri-review mailing list > Uri-review@ietf.org > https://www.ietf.org/mailman/listinfo/uri-review
- [Uri-review] Review Request of new URI Scheme Kang Su Gatlin
- Re: [Uri-review] Review Request of new URI Scheme Bjoern Hoehrmann
- Re: [Uri-review] Review Request of new URI Scheme Daniel R. Tobias
- Re: [Uri-review] Review Request of new URI Scheme Kang Su Gatlin
- Re: [Uri-review] Review Request of new URI Scheme Eric Johnson
- [Uri-review] Review Request of new URI Scheme Mirko Nosenzo
- Re: [Uri-review] Review Request of new URI Scheme Eric Johnson
- Re: [Uri-review] Review Request of new URI Scheme Mirko Nosenzo
- Re: [Uri-review] Review Request of new URI Scheme Larry Masinter
- Re: [Uri-review] Review Request of new URI Scheme Mark Baker