Re: [apps-discuss] NEW RELATION: property and context

"Markus Lanthaler" <markus.lanthaler@gmx.net> Tue, 28 May 2013 22:57 UTC

Return-Path: <markus.lanthaler@gmx.net>
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 F1BD021F90D2 for <apps-discuss@ietfa.amsl.com>; Tue, 28 May 2013 15:57:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.15
X-Spam-Level:
X-Spam-Status: No, score=-1.15 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449]
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 Fl+Oobjbc6Tk for <apps-discuss@ietfa.amsl.com>; Tue, 28 May 2013 15:57:41 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id 7179A21F90E0 for <apps-discuss@ietf.org>; Tue, 28 May 2013 15:57:34 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.20]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0M21p7-1USYPW1VUJ-00tzdC for <apps-discuss@ietf.org>; Wed, 29 May 2013 00:57:33 +0200
Received: (qmail invoked by alias); 28 May 2013 22:57:33 -0000
Received: from 84-115-182-43.dynamic.surfer.at (EHLO Vostro3500) [84.115.182.43] by mail.gmx.net (mp020) with SMTP; 29 May 2013 00:57:33 +0200
X-Authenticated: #419883
X-Provags-ID: V01U2FsdGVkX18otGAtoOMowNodJAkYVi5GO6iGdULAee1NKExaDM scnGCh6GI3iLVG
From: Markus Lanthaler <markus.lanthaler@gmx.net>
To: 'Ioseb Dzmanashvili' <ioseb.dzmanashvili@gmail.com>
References: <CA3AB5FFC57B456DBAB05E3CE5C8996A@gmail.com> <CAKioOqtvVYApV3p+FBkn9P=3=0bW0J1=AUSZ=XCZA-oukycGzw@mail.gmail.com> <5289AF00-A443-4FAD-BFA5-D62E0D2FE0BC@gmail.com> <51a285da.48ac0e0a.7995.ffffdc06SMTPIN_ADDED_BROKEN@mx.google.com> <E677715B30A941BDB52545500CAC19A7@gmail.com>
In-Reply-To: <E677715B30A941BDB52545500CAC19A7@gmail.com>
Date: Wed, 29 May 2013 00:57:08 +0200
Message-ID: <000001ce5bf6$c03a4610$40aed230$@lanthaler>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac5aq7+OUdjHB5AwRc2KieZr+QbfEgA+qCTw
Content-Language: de
X-Y-GMX-Trusted: 0
Cc: apps-discuss@ietf.org, link-relations@ietf.org
Subject: Re: [apps-discuss] NEW RELATION: property and context
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: Tue, 28 May 2013 22:57:46 -0000

On Monday, May 27, 2013 9:28 AM, Ioseb Dzmanashvili wrote:

> My RDF knowledge is rudimentary, but what i can say for sure the
> "context" link relation and "@context" from JSON-LD are different
> things.

Of course. I just mentioned it because they use exactly the same terminology and I was not the only one to be confused by this.


> Here is what JSON-LD[1] documentation says: "The secret lies
> in the @context, which instructs Linked Data-aware processors on how
> to interpret the JSON object." which is not the case for the "context"
> link relation... it's much simpler and must be used to indicate that a
> resource is a member of another resource and only in cases when we do
> not have collection/item relationships.

Sorry, I don't understand this. It indicates that resource I is a member of a resource C but only if resource I is not an item of collection C!? In which case then? Aren't you contradicting yourself?


> For example if i share
> resource URI which is a member of another resource i can use the
> "context" link rel to inform processing agent that shared resource is
> a member of another resource.

Unfortunately, this doesn't make it any clearer to me.


> > How do you know which link to follow in your apps? Do you do that
> > based on the title attribute?
>
> No, title attribute is only used for user interfaces i do not think
> anyone uses it for other purposes. In my apps i only use rel attribute
> values to decide which link to follow.

As Erik already clarified in another thread I'm interested in how your application is able to select the correct link to follow if you have multiple links, e.g.:

Link: </propertyA>; rel="property"; title="Property A"
Link: </propertyB>; rel="property"; title="Property B"
Link: </propertyC>; rel="property"; title="Property C"

Since there's no other information than the rel and the title (and the URL) you obviously would have to program against the title. If you need another rel as you showed in the other thread:

> Link: </book;title>; rel="property http://rels.service.org/properties#title";
>       title="Human friendly text here..."

Then why do you need "property"? Isn't http://rels.service.org/properties#title all you need then?



--
Markus Lanthaler
@markuslanthaler