Re: [apps-discuss] Links and graphs

Erik Wilde <dret@berkeley.edu> Thu, 15 November 2012 17:36 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 3E82721F8896 for <apps-discuss@ietfa.amsl.com>; Thu, 15 Nov 2012 09:36:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 YnhBaLGZgKsc for <apps-discuss@ietfa.amsl.com>; Thu, 15 Nov 2012 09:36:38 -0800 (PST)
Received: from cm03fe.IST.Berkeley.EDU (cm03fe.IST.Berkeley.EDU [169.229.218.144]) by ietfa.amsl.com (Postfix) with ESMTP id 5C63B21F88CC for <apps-discuss@ietf.org>; Thu, 15 Nov 2012 09:36:38 -0800 (PST)
Received: from 108-67-66-127.lightspeed.sntcca.sbcglobal.net ([108.67.66.127] helo=[192.168.1.64]) 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 1TZ3MX-0005wW-BD; Thu, 15 Nov 2012 09:36:27 -0800
Message-ID: <50A52817.7010505@berkeley.edu>
Date: Thu, 15 Nov 2012 09:36:23 -0800
From: Erik Wilde <dret@berkeley.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Graham Klyne <GK@ninebynine.org>
References: <50A38259.4050304@googlemail.com> <3B530232-381D-4370-980B-B5B308443DDF@mnot.net> <CANqiZJZtcRsxNVt8iAnEMsP8y2xujx7d0mN0LzZ4Gew7pz3qaA@mail.gmail.com> <50A4E7FD.5000705@ninebynine.org>
In-Reply-To: <50A4E7FD.5000705@ninebynine.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: LDP WG <public-ldp-wg@w3.org>, IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Links and graphs
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, 15 Nov 2012 17:36:39 -0000

hello graham.

On 2012-11-15 5:02 , Graham Klyne wrote:
> I don't follow what you're saying here.  I don't disagree (as someone
> involved with RDF) that RDF has made its life hard in several ways, but
> if what you have and want to pass around is a graph, how does one *not*
> push it down into the data?

the big problem with RDF on the level we're discussing here is that RDF 
pushes everything into vocabularies, and thus renders media types almost 
meaningless (apart from distinguishing RDF serializations). that's a 
problem for home documents or similar web-oriented approaches that rely 
on the media type being a crucial signal for understanding the 
interaction semantics of resources.

> (Personally, I'd like to see json-home be something that has a clear
> mapping to RDF, but that's a different discussion.)

fwiw, https://github.com/dret/I-D-1/tree/master/json-home is where i 
have started creating a mapping to XML, and i'd be more than happy to 
collaborate with others to do the same for an RDF schema. but like i 
said above, the whole concept of home documents hinges around the 
assumption that a media type signals interaction semantics, so that 
clients can decide what resources to engage with. in RDF, this is not 
how the world works (yet, i still hope that we'll see this tackled at 
some point in time), so maybe there's a little less utility in the whole 
approach. regardless of that, we have discovered in our current work in 
the "Linked Data Platform" W3C WG that we probably need some concept of 
a "service document" or a "home document", and thus it might be 
interesting to look at how the current json-home approach could be 
mapped to RDF and would give us some useful foundation.

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 |