Re: [apps-discuss] JSON Hypertext Application Language
Mike Kelly <mikekelly321@gmail.com> Sat, 09 June 2012 07:55 UTC
Return-Path: <mikekelly321@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A82621F85B5 for <apps-discuss@ietfa.amsl.com>; Sat, 9 Jun 2012 00:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.539
X-Spam-Level:
X-Spam-Status: No, score=-3.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 NmeXzjbJqvZM for <apps-discuss@ietfa.amsl.com>; Sat, 9 Jun 2012 00:55:43 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3049621F85B4 for <apps-discuss@ietf.org>; Sat, 9 Jun 2012 00:55:27 -0700 (PDT)
Received: by obbeh20 with SMTP id eh20so4714242obb.31 for <apps-discuss@ietf.org>; Sat, 09 Jun 2012 00:55:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=b3MV3dCTGuxJGBk2PsoxDccUF5zBsKDsV0cjsnfzGR4=; b=iuiH1f0Z4A2rqdZ68jApW6Awbsk05YKTRxmaGepDOTAZaDIdcBABvETobYxI4sqcuS dw5USJ5kNSed6kFByir9YVX8mkEoNCFJD1hsvzAVVobimkr4Bh1zrn0PSq+4mKV8etAe GCXOqlTL3wz7bbetfWXM5YLBdKBsPtHWjvgnTASMcoQtt2iRymml24nmHfLqQmPxlHw5 cnwBU0/vOQmOOMJLXd2CA80Y16mzPO8EiIy9bYMQ6IfmtymkjVby0v2hfvnlydr8zf3Q QcBTrzXFWoQDLOhzbBQpsC7agCC87xPrBcptBpi936WJLD5/pKvZxH/CP3fqYG3fCfyn 5EIA==
MIME-Version: 1.0
Received: by 10.60.30.101 with SMTP id r5mr9840757oeh.68.1339228526761; Sat, 09 Jun 2012 00:55:26 -0700 (PDT)
Received: by 10.60.28.195 with HTTP; Sat, 9 Jun 2012 00:55:26 -0700 (PDT)
In-Reply-To: <CABP7Rbd+siKJz7qecx-z9wZv602ceC3LWXmLfCknPrAQm6h-Sw@mail.gmail.com>
References: <CANqiZJa7GrBRbiV8X=o3Xkv-WcBEdKEntiZSFhMj4efQiNPEaQ@mail.gmail.com> <CABkgnnXVFqEhS5oympA7E_GHhzYB+P5TQh1PugK5p16qNWSBVQ@mail.gmail.com> <CANqiZJbGMVzFrcsvuW2dZaq4pOEzi4x=iamxs_1etetKGeZz2A@mail.gmail.com> <CABkgnnXMJX7EPXi3cqoswKbJDRupPdf5dt8Og1VqkROpM+P80A@mail.gmail.com> <CABP7Rbd+siKJz7qecx-z9wZv602ceC3LWXmLfCknPrAQm6h-Sw@mail.gmail.com>
Date: Sat, 09 Jun 2012 08:55:26 +0100
Message-ID: <CANqiZJbQT_40Q_mLP0EOtrM6L6zZct6U36ZqRiLEMepBDbUdAQ@mail.gmail.com>
From: Mike Kelly <mikekelly321@gmail.com>
To: James M Snell <jasnell@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] JSON Hypertext Application Language
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2012 07:55:44 -0000
On Sat, Jun 9, 2012 at 2:04 AM, James M Snell <jasnell@gmail.com> wrote: > HAL will just be way too verbose to be practical. I think 'way too verbose' is overstating the importance of this. You are the first person to raise this as an issue at all, let alone as a significant one. Link Objects are necessary to allow for the "templated" indicator (for when the link is a URI Template), for including the additional link params established in the Web Linking RFC, and to provide the opportunity for extension of link objects in any future types wanting to extend HAL e.g. by adding additional controls or hints. Fwiw, I did actually consider also adding a direct string as you have suggested here but decided against in the interests of simplicity/consistency, given that the Link Object approach is unavoidable (for the reasons stated above). On another note - HAL has been established for a while now (as a less formal, public specification) and has a growing list of server and client tooling, seems to me like it would be a win for Activity Streams to adopt HAL's already established conventions, given that your recent new proposal is so close to it anyway. Cheers, M
- [apps-discuss] JSON Hypertext Application Language Mike Kelly
- Re: [apps-discuss] JSON Hypertext Application Lan… Martin Thomson
- Re: [apps-discuss] JSON Hypertext Application Lan… Mike Kelly
- Re: [apps-discuss] JSON Hypertext Application Lan… Martin Thomson
- Re: [apps-discuss] JSON Hypertext Application Lan… Graham Klyne
- Re: [apps-discuss] JSON Hypertext Application Lan… Mike Kelly
- Re: [apps-discuss] JSON Hypertext Application Lan… James M Snell
- Re: [apps-discuss] JSON Hypertext Application Lan… Mike Kelly
- Re: [apps-discuss] JSON Hypertext Application Lan… Manuel Simoni
- Re: [apps-discuss] JSON Hypertext Application Lan… Mike Kelly
- Re: [apps-discuss] JSON Hypertext Application Lan… James M Snell
- [apps-discuss] JSON Hypertext Application Language Mike Kelly