IETF Logo Mail Archive

Re: [apps-discuss] Inclusion-mechanism for draft-nottingham-json-home-01?

Erik Wilde <dret@berkeley.edu> Thu, 19 July 2012 06:38 UTC

Return-Path: <dret@berkeley.edu>
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 CE4DC21F84F8 for <apps-discuss@ietfa.amsl.com>; Wed, 18 Jul 2012 23:38:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level:
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_41=0.6, RCVD_IN_DNSWL_MED=-4]
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 2Beo2LXBTBsJ for <apps-discuss@ietfa.amsl.com>; Wed, 18 Jul 2012 23:38:27 -0700 (PDT)
Received: from cm03fe.IST.Berkeley.EDU (cm03fe.IST.Berkeley.EDU [169.229.218.144]) by ietfa.amsl.com (Postfix) with ESMTP id E9B1B21F84F2 for <apps-discuss@ietf.org>; Wed, 18 Jul 2012 23:38:27 -0700 (PDT)
Received: from laubervilliers-151-13-21-144.w217-128.abo.wanadoo.fr ([217.128.60.144] helo=dretair.local) by cm03fe.ist.berkeley.edu with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (auth plain:dret@berkeley.edu) (envelope-from <dret@berkeley.edu>) id 1SrkOL-0007vw-AQ; Wed, 18 Jul 2012 23:39:19 -0700
Message-ID: <5007AB98.5060201@berkeley.edu>
Date: Thu, 19 Jul 2012 08:39:20 +0200
From: Erik Wilde <dret@berkeley.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
References: <C57C7266-58C1-4FAA-BAE6-C1B4F89561AC@nordsc.com> <666EFE37-22A2-4BE7-8461-351DE09EEE18@mnot.net>
In-Reply-To: <666EFE37-22A2-4BE7-8461-351DE09EEE18@mnot.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Inclusion-mechanism for draft-nottingham-json-home-01?
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: Thu, 19 Jul 2012 06:38:28 -0000

On 2012-07-19 06:08 , Mark Nottingham wrote:
> Inclusion mechanisms IME are very tricky unless they're very carefully designed; they made WSDL a mess, for example, and WADL wasn't much better. It *might* be necessary, but I'd like to get a lot more experience with the space before including (heh) it in the spec.
> Right now, my bet would be on using a pre-processor of some sort (i.e., a "JSON include" mechanism) to generate the document you publish, if it's a management problem on the back end your'e trying to solve.

for the XML version of home documents, that could translate into 
requiring that xml-home processors support XInclude, or publishers could 
run XInclude processes server-side, if the requirement for clients seems 
to be too much.

cheers,

dret.

-- 
erik wilde | mailto:dret@berkeley.edu  -  tel:+1-510-2061079 |
            | UC Berkeley  -  School of Information (ISchool) |
            | http://dret.net/netdret http://twitter.com/dret |

v2.23.0 | Report a Bug | By Email