Re: [Uri-review] Request for review

"Mark Baker" <distobj@acm.org> Sat, 20 May 2006 19:34 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FhXDi-0006J2-8y; Sat, 20 May 2006 15:34:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FhXDh-0006Ix-S7 for uri-review@ietf.org; Sat, 20 May 2006 15:34:37 -0400
Received: from py-out-1112.google.com ([64.233.166.183]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FhXDg-0003eM-Km for uri-review@ietf.org; Sat, 20 May 2006 15:34:37 -0400
Received: by py-out-1112.google.com with SMTP id f28so1142559pyf for <uri-review@ietf.org>; Sat, 20 May 2006 12:34:36 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=OAQuaV8JWH2QUeaRG5hvn8KjWOskdEDIBb6YlOvlcy7bI72V+dUwyIhTBsZJkXs5BklMF17lGIIJLK5MVM4PMmy40FbPOhjQCVjNAqKpJk27PBFJxaTKzR4+r8I0MD+AMeN4NX2LQekdXcL7sX3y5tzAW+5GABZ2S6O3jLa7T+Y=
Received: by 10.35.109.2 with SMTP id l2mr238523pym; Sat, 20 May 2006 12:34:35 -0700 (PDT)
Received: by 10.35.70.20 with HTTP; Sat, 20 May 2006 12:34:35 -0700 (PDT)
Message-ID: <c70bc85d0605201234l59d17edfud97c1776fa550f63@mail.gmail.com>
Date: Sat, 20 May 2006 21:34:35 +0200
From: Mark Baker <distobj@acm.org>
To: Andrey Shur <andreysh@exchange.microsoft.com>
Subject: Re: [Uri-review] Request for review
In-Reply-To: <1D4A05136773CF4DB373F6FE4E103150110EEAEB@df-pug-msg.exchange.corp.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <c70bc85d0605200740u7d451d09j1e7fa47a86ee078d@mail.gmail.com> <1D4A05136773CF4DB373F6FE4E103150110EEAEB@df-pug-msg.exchange.corp.microsoft.com>
X-Google-Sender-Auth: 3fc151f836167f12
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: Ted Hardie <hardie@qualcomm.com>, "uri-review@ietf.org" <uri-review@ietf.org>, Jerry Dunietz <jerryd@windows.microsoft.com>, Gregg Brown <greggb@microsoft.com>, "John Calhoon (LCA)" <john.calhoon@microsoft.com>
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
Errors-To: uri-review-bounces@ietf.org

Andrey,

First, my sincere apologies for botching your name earlier.  I didn't
look closely enough, obviously ...

On 5/20/06, Andrey Shur <andreysh@exchange.microsoft.com> wrote:
> Mark,
>
> Thank you for the question. The primary reason why we did not use the
> approach you describe is the requirement for relative references within a
> package parts to refer to parts within the same package.
> Our registration template says:
>
>    The purposes of the "pack" URI scheme are:
>
>    1. To identify a part resource within a package that conforms to
>       Open Packaging Conventions [4].
>    2. To enable the use of a part's URI as a base URI for resolving
>       relative references to parts within the same package.
>
> Let's assume that in your example part identified by the Uri
> http://www.mysite.com/my.package/a/b/foo.xaml
> holds relative reference /bar.xml.
> Being resolved against the base Uri of the part it gives us
> http://www.mysite.com/bar.xml which is outside of the package.

Ok, thanks.  But why do you need to refer to a part using "/bar.xml"?
What purpose does that serve?  Why does "bar.xml" not suffice?

Perhaps the packaging spec could shed some light on this, and I'm sure
you're just doing what your lawyers suggested by using a license, but
I'm not about to accept its terms without running it by my employer's
lawyers, lest I get my employer in trouble by accepting (even though
I'm not representing them here).  And I'm not sure about the IETF
rules about this stuff, but I believe it to be (at least) considered
bad form.

Mark.

_______________________________________________
Uri-review mailing list
Uri-review@ietf.org
https://www1.ietf.org/mailman/listinfo/uri-review