From jan.algermissen@nordsc.com Thu Jan 10 23:35:17 2013 Return-Path: X-Original-To: link-relations@ietfa.amsl.com Delivered-To: link-relations@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A65721F8A89 for ; Thu, 10 Jan 2013 23:35:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.249 X-Spam-Level: X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FH410jDm3HrI for ; Thu, 10 Jan 2013 23:35:15 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by ietfa.amsl.com (Postfix) with ESMTP id D580421F8689 for ; Thu, 10 Jan 2013 23:35:14 -0800 (PST) Received: from [172.20.10.2] (tmo-106-125.customers.d1-online.com [80.187.106.125]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0Lgt3C-1TEEpq2Rgk-00oRcm; Fri, 11 Jan 2013 08:35:13 +0100 From: Jan Algermissen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Review of draft-wmills-oauth-lrdd-06.txt Date: Fri, 11 Jan 2013 08:35:08 +0100 Message-Id: To: wmills_92105@yahoo.com, "link-relations@ietf.org" Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) X-Provags-ID: V02:K0:qXMUCdc36WX2ksVBZqZOFSeEjl8zwCVdUVXWCYPTH3v y9n0UAmXZiCWjMFdx03D+3G4F4hcH/OQ5StzN7D5KoY6HKZX1Q M5R7qg/Fn9R720EcqJmuPCYAF332BBHFGV+uAJifyhHj4S0R4E RNUzGjBdKYOb3fO79DKz1jZzbimwq4d4xnYwAMTdc5K3atJoQV mY6C1Vk3h2Lh35+BZFLenR60jTAMoKGqigDk4QhDbkqruCc+w0 9tW/fZZq1sey8fJDJtJphchBR4Cm2SKIZTG0weBZeZGD5YTjvr tC0BGyY7NQw76WYb096SjlFhtr7jipRRoOKk+TLO5zcuigZ0Bt a3Ab9VnsUenuLU8UCoBmpkd0UZUEL//gARUzDFb2lq8aX3tOZX BcySy9EliRX+A== Cc: Nevil Brownlee X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2013 07:35:17 -0000 [Resending this and added some comments on decoupling at the end] Hi, this is a review of draft-wmills-oauth-lrdd-06.txt Jan Overall: "link type" -> "link relation type" 1. Introduction I don't think that the I-D needs to reference "Web Host Metadata" and = "Web Finger" specs. The means of using the relation types is orthogonal = to their specification. 3. OAuth 2 Link Types (-> "Link Relation Types" :-) Consider s/endpoint/entrypoint/g - I know that OAuth uses 'endpoint', = but the proper term on the Web would really be 'entry point' 3.1 [Change headline to:] The 'oauth2-authorize' Link Relation Type Suggested rewording: "This link relation type indicates a resource that represents an OAuth 2 = authorization entry point to be used for user authentication/authorization to grant access to a protected resource." 3.2 [Change headline to:] The 'oauth2-token' Link Relation Type Suggested rewording: "This link relation type indicates a resource that represents an OAuth 2 = token entry point to be used for obtaining tokens to access protected services. This link type has two = link-extensions: ...." 4.1 - 4.3 Likewise 3.1 and 3.2 change the headline and text. What is to be defined = here is not the endpoint (erm, entry point) but the link relation type. In addition, I second Julian's comments made here: = http://www.ietf.org/mail-archive/web/link-relations/current/msg00418.html One final remark, Given that there are a number of OAuth-ish protocols existing and = emerging I think it would be a good idea to investigate decoupling the = link relation types from these protocols - if possible. An = 'authorization endpoint' likely has the same semantic across all of = those protocols. If clients can determine the actual variant at runtime, *after* = discovering the entry point resources we would not need to register = virtualy the same link relation types over and over again for all the = protcols. Please do take a look whether this is possible. (Your I-D does this = already for OAuth 1 and 2) UPDATE: What I mean is that the semantics of link relations for, for example, = the authorization resource are the same for any OAuth-ish protocol. Ther = eis no need to provide different link relation types for OAuth 1.0a and = 2. For a client (no matter whether 1.0a or 2 ... or maybe OZ[1]) it will be = sufficient to look for an 'authorization' resource. The differentiation = of the particular protocols should is a runtime issue. There is no need = to duplicate the semantics for each new OAutish protocol that comes = around. To illustrate: likewise you would not need new 'service' or 'edit' link = relations for each new AtomPub version that comes around. Client and = server will figure tat out at runtime. Such decoupling greatly improves the maintainability and evolvability of = specifications[2]. Hence, I suggest to remove the differentiation between 1.0a and 2 where = possible and to specifiy the link relations in a more genral sense. For = example: "The 'authorize' Link Relation Type Suggested rewording: "This link relation type indicates a resource that represents an = authorization entry point to be used for user authentication/authorization to grant access to a protected resource."" That way Link: ;rel=3Dauthorize will work for all OAuths, present = and future ones. The same goes for all the other link relation types. Clearer now? Jan [1] http://github.com/hueniverse/oz [2] http://www.w3.org/TR/webarch/#orthogonal-specs From ioseb.dzmanashvili@gmail.com Thu Jan 31 11:10:40 2013 Return-Path: X-Original-To: link-relations@ietfa.amsl.com Delivered-To: link-relations@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B401821F8E48 for ; Thu, 31 Jan 2013 11:10:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.901 X-Spam-Level: X-Spam-Status: No, score=-2.901 tagged_above=-999 required=5 tests=[AWL=0.698, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U8zwqzStBM6a for ; Thu, 31 Jan 2013 11:10:38 -0800 (PST) Received: from mail-ea0-f181.google.com (mail-ea0-f181.google.com [209.85.215.181]) by ietfa.amsl.com (Postfix) with ESMTP id 266F421F8D3B for ; Thu, 31 Jan 2013 11:10:37 -0800 (PST) Received: by mail-ea0-f181.google.com with SMTP id i13so1407354eaa.40 for ; Thu, 31 Jan 2013 11:10:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:message-id:subject:x-mailer:mime-version :content-type; bh=rcsUYbFSPHfPGFIdo018T8chBpsVN0Dzdj4ey0ybQuA=; b=yormi9sCryD7iig0GUtxvx3mwH0daGAxPMw+aivIK9uyVsFL+D5+5mtV933bbToveW XcvtVAXIP3H3jeHgPfVfxYhwrh03rQjCHg/2WAOD9UdkJ5skvMbtZyBFnDq4ACawNzKa e6bT9bPMqvC+za4keERHCOXJrojUk0fOR9vrKBEtNCq6F9gCzXMWESm6UpliBf5gYmA/ gv0ASQLwFWvlyuGl96OqR866MDZS4FFPA2siKAVHh1pHTCajKv8e7xWOFTiyid9GTT1q UabyF4mrfq7pJlPoqS+nxikA/LExZk7lUY8Kdsr7tB/JI6+g5tDPM4Tsl3GbmOMsREX2 HwbQ== X-Received: by 10.14.173.65 with SMTP id u41mr30356863eel.13.1359659434717; Thu, 31 Jan 2013 11:10:34 -0800 (PST) Received: from [192.168.1.7] ([176.73.174.236]) by mx.google.com with ESMTPS id h5sm8824427eem.1.2013.01.31.11.10.32 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 31 Jan 2013 11:10:33 -0800 (PST) Date: Thu, 31 Jan 2013 23:10:33 +0400 From: Ioseb Dzmanashvili To: link-relations@ietf.org Message-ID: <847FE4BC9B1845519A22874F71FE4BD9@gmail.com> Subject: NEW RELATION: action X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="510ac1a9_60c94a46_28a" X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 19:10:40 -0000 --510ac1a9_60c94a46_28a Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Dear All, I've submitted new draft of the 'create' link relation type: http://tools.ietf.org/html/draft-ioseb-dzmanashvili-action-link-relation-00 Description: - The link relation is intentionally generic, and it can be used with multiple media types in a wide variety of use cases. - When included in a resource which represents a collection, the 'form' link relation identifies a target resource that represents the form for adding a new member to the context collection. - The target IRI points to a resource that is responsible to perform an action that may affect state of the context resource or initiate process. Could you please review? Thanks in advance! Best regards, ioseb -- Ioseb Dzmanashvili AzRy LLC Software Architect #8, Chachava str. Tbilisi, 0159, Georgia Mobile: +(995) 99753388 github.com/ioseb (http://github.com/ioseb) pecl.php.net/user/ioseb (http://pecl.php.net/user/ioseb) twitter.com/iosebi (http://twitter.com/iosebi) --510ac1a9_60c94a46_28a Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Dear All,

I've submitte= d new draft of the 'create' link relation type: http://tools.ietf.org/htm= l/draft-ioseb-dzmanashvili-action-link-relation-00

Description:
- The link relation is intentionally generic, a= nd it can be used with  multiple media types in a wide variety of us= e cases.
- When included in a resource which represents a colle= ction, the 'form'  link relation identifies a target resource that r= epresents the form for adding a new member to the context collection.
- The target IRI points to a resource that is responsible to perfo= rm an action that may affect state of the context resource or
&= nbsp;initiate process.

Could you please review=3F=
Thanks in advance=21

Best regards,
ioseb
-- 
Ioseb Dzmanash= vili
AzRy LLC
Software Architect
=238,= Chachava str.
Tbilisi, 0159, Georgia
Mobile: += (995) 99753388
--510ac1a9_60c94a46_28a-- From ioseb.dzmanashvili@gmail.com Thu Jan 31 11:20:08 2013 Return-Path: X-Original-To: link-relations@ietfa.amsl.com Delivered-To: link-relations@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24E5821F861A for ; Thu, 31 Jan 2013 11:20:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.249 X-Spam-Level: X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[AWL=0.349, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zoVbHZ4S4o0f for ; Thu, 31 Jan 2013 11:20:07 -0800 (PST) Received: from mail-ea0-f170.google.com (mail-ea0-f170.google.com [209.85.215.170]) by ietfa.amsl.com (Postfix) with ESMTP id D1F9721F8521 for ; Thu, 31 Jan 2013 11:20:06 -0800 (PST) Received: by mail-ea0-f170.google.com with SMTP id a11so1377421eaa.15 for ; Thu, 31 Jan 2013 11:20:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:message-id:in-reply-to:references:subject :x-mailer:mime-version:content-type; bh=xMTIu/BHIKOzAw/TedqMg0OQicm/NwSEJZB4yoLRDJ4=; b=iKmfmYJymCfK1M0ewTq65Kl3u9yE9iwxYbY6K/oLO50KPHHHk8W/LU8+SU7XgivKQE 8BLU/j1t4Kj0WCEc96B7y4Ny62lbMBWjrKKjAKuMVWhKzWBnmy+I1CVu47JKyVBWTrKK Eo6FfhvmaLHr5BVvAq9q2MUcuEvSTBwZFNKRHxvTZZxBWS8HuSzC8g72z2lr68Ywo07d Rin507JIiT07ZH/DA2ZZWZHvtzvHxbDjYGtQgF6EGjcyDu73O7XEKlcQwZQTv3/X55xM Fen5sOzdWov7axfgebWJB0cjQObu5KZNzpD2V+6ydO5VlR6a52aqvWyW1ENzF3j7IGTA hFoQ== X-Received: by 10.14.221.9 with SMTP id q9mr30766710eep.3.1359660005860; Thu, 31 Jan 2013 11:20:05 -0800 (PST) Received: from [192.168.1.7] ([176.73.174.236]) by mx.google.com with ESMTPS id j46sm5483887eeo.3.2013.01.31.11.20.04 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 31 Jan 2013 11:20:04 -0800 (PST) Date: Thu, 31 Jan 2013 23:20:05 +0400 From: Ioseb Dzmanashvili To: link-relations@ietf.org Message-ID: <794CDFAD77B74630AAEE2B0C293B3246@gmail.com> In-Reply-To: <847FE4BC9B1845519A22874F71FE4BD9@gmail.com> References: <847FE4BC9B1845519A22874F71FE4BD9@gmail.com> Subject: Re: NEW RELATION: action X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="510ac3e5_6599b689_28a" X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 19:20:08 -0000 --510ac3e5_6599b689_28a Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Second line in the previous message: "When included in a resource which represents a collection, the 'form' link relation identifies a target resource that represents the form for adding a new member to the context collection." is not related to this draft, i copied it accidentally from the old email. Please ignore it. Cheers, ioseb On Thursday, January 31, 2013 at 11:10 PM, Ioseb Dzmanashvili wrote: > Dear All, > > I've submitted new draft of the 'create' link relation type: http://tools.ietf.org/html/draft-ioseb-dzmanashvili-action-link-relation-00 > > Description: > - The link relation is intentionally generic, and it can be used with multiple media types in a wide variety of use cases. > - When included in a resource which represents a collection, the 'form' link relation identifies a target resource that represents the form for adding a new member to the context collection. > - The target IRI points to a resource that is responsible to perform an action that may affect state of the context resource or > initiate process. > > Could you please review? > Thanks in advance! > > Best regards, > ioseb > > -- > Ioseb Dzmanashvili > AzRy LLC > Software Architect > #8, Chachava str. > Tbilisi, 0159, Georgia > > Mobile: +(995) 99753388 > github.com/ioseb (http://github.com/ioseb) > pecl.php.net/user/ioseb (http://pecl.php.net/user/ioseb) > twitter.com/iosebi (http://twitter.com/iosebi) > > > > --510ac3e5_6599b689_28a Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Second line in the previous message: =22When included= in a resource which represents a collection, the 'form'  link relat= ion identifies a target resource that represents the form for adding a ne= w member to the context collection.=22 is not related to this draft, i co= pied it accidentally from the old email. Please ignore it.

Cheers,
ioseb
=20

On Thursday, January 3= 1, 2013 at 11:10 PM, Ioseb Dzmanashvili wrote:

Dear All,

I've submitte= d new draft of the 'create' link relation type: http:/= /tools.ietf.org/html/draft-ioseb-dzmanashvili-action-link-relation-00=

Description:
- The link relation is i= ntentionally generic, and it can be used with  multiple media types = in a wide variety of use cases.
- When included in a resource w= hich represents a collection, the 'form'  link relation identifies a= target resource that represents the form for adding a new member to the = context collection.
- The target IRI points to a resource that = is responsible to perform an action that may affect state of the context = resource or
 initiate process.

Co= uld you please review=3F
Thanks in advance=21

Best regards,
ioseb
-- 
=
Ioseb Dzmanashvili
AzRy LLC
Software Archit= ect
=238, Chachava str.
Tbilisi, 0159, Georgia
Mobile: +(995) 99753388
=20 =20 =20 =20
=20

--510ac3e5_6599b689_28a-- From jan.algermissen@nordsc.com Thu Jan 31 15:11:39 2013 Return-Path: X-Original-To: link-relations@ietfa.amsl.com Delivered-To: link-relations@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F8AD21F888E for ; Thu, 31 Jan 2013 15:11:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.249 X-Spam-Level: X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6BbYCimPwVPz for ; Thu, 31 Jan 2013 15:11:38 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by ietfa.amsl.com (Postfix) with ESMTP id ED27921F888B for ; Thu, 31 Jan 2013 15:11:37 -0800 (PST) Received: from [192.168.2.103] (p548F9E9F.dip.t-dialin.net [84.143.158.159]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0MgYEB-1UNnFH3YBz-00O5su; Fri, 01 Feb 2013 00:11:36 +0100 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: NEW RELATION: action From: Jan Algermissen In-Reply-To: <847FE4BC9B1845519A22874F71FE4BD9@gmail.com> Date: Fri, 1 Feb 2013 00:11:36 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <74AC1732-B805-471A-97F4-277E937E1CB2@nordsc.com> References: <847FE4BC9B1845519A22874F71FE4BD9@gmail.com> To: Ioseb Dzmanashvili X-Mailer: Apple Mail (2.1499) X-Provags-ID: V02:K0:5fPneYwuDbqmPFRkrRDfM7OFOS/YMIgJZPTYH3MuzfX U7C5jOPpQaiNeeK2FpgOPYL+Gj9/rpV344qguQMfb7G/O6PmD0 ptX8+ET7iilNn1F7X74Zavz1sjxCGXb5asVWI0CyZQwy/CES7L g9cbTl6nZE3FELXd//d0B0JUQ23Qw6ahwGPd6KiLMfhlrBOlm0 jaTCFqal2XDb0Ef6StnknIEDNTXyyKjLLPsRQ+qNpTnG/YGZV+ sCLOHe8wAQ9F+/nnjU2PW1ZzYAF++76i0+NoO/7JMdLqS7QEDU k8/Wny4ItjA/Rg4OkoVcu6MRomo47Ma7eUsoGgfg159f+pqrLK bjQEnQtCNX0cpJlttFLe0rKzWCWzCQtY1+VPhatYd8cyXMNulX 6Sn3diBNRXF2g== Cc: link-relations@ietf.org X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 23:11:39 -0000 Hi Ioseb, can you explain your use case? To me this smells a lot like a (REST-) anti pattern. For example, instead of invoking an action resource like GET /content/article/22/publish you'd rather set it's state: PUT /content/article/22/publish ... published ... No need for link and 'action' link rel, because you know the resource to = change anyhow. Maybe I am missing your point though. Jan On 31.01.2013, at 20:10, Ioseb Dzmanashvili = wrote: > Dear All, >=20 > I've submitted new draft of the 'create' link relation type: = http://tools.ietf.org/html/draft-ioseb-dzmanashvili-action-link-relation-0= 0 >=20 > Description: > - The link relation is intentionally generic, and it can be used with = multiple media types in a wide variety of use cases. > - When included in a resource which represents a collection, the = 'form' link relation identifies a target resource that represents the = form for adding a new member to the context collection. > - The target IRI points to a resource that is responsible to perform = an action that may affect state of the context resource or > initiate process. >=20 > Could you please review? > Thanks in advance! >=20 > Best regards, > ioseb > --=20 > Ioseb Dzmanashvili > AzRy LLC > Software Architect > #8, Chachava str. > Tbilisi, 0159, Georgia > Mobile: +(995) 99753388 > github.com/ioseb > pecl.php.net/user/ioseb > twitter.com/iosebi > _______________________________________________ > link-relations mailing list > link-relations@ietf.org > https://www.ietf.org/mailman/listinfo/link-relations