W3C home > Mailing lists > Public > public-linked-json@w3.org > February 2017

Re: Scoping context based on @type

From: David Booth <david@dbooth.org>
Date: Wed, 15 Feb 2017 17:48:47 -0500
To: public-linked-json@w3.org
Message-ID: <fbe20b87-c5d1-a509-9474-056566b4589d@dbooth.org>
Would the new feature for scoping context based on @type allow a 
different URI to be assigned for the different uses of "code" in the 
following example?  This was a limitation that we ran into a couple of 
years ago when investigating whether we could retrofit FHIR/JSON to 
become JSON-LD, and concluded at that time that we could not.

Here is the excerpt of FHIR/JSON that we were analyzing:
"resourceType": "Observation",
   "id": "example",
   "code": {
     "coding": [
         "system": "http://loinc.org",
         "code": "3141­9",
         "display": "Weight Measured"

Notice that in one use of "code", the value is an object, whereas in the 
other use it is a literal.  We want these two uses of "code" to be 
separate properties (with distinct URIs).

David Booth

On 02/15/2017 02:53 PM, Gregg Kellogg wrote:
> I’ve merged this PR.
> Gregg Kellogg
> gregg@greggkellogg.net
>> On Feb 4, 2017, at 1:21 PM, Gregg Kellogg <gregg@greggkellogg.net> wrote:
>> Closely related to term-based scoping when the term is used as a property is scoping based on type. As explained in Issue #415 [1], this comes into play when different kinds of things are related hierarchically using similar property names, but where either those properties need different IRIs, or properties used within those entities use a different vocabulary scope. See, in particular, Rob Sanderson’s examples from CIDOC-CRM [2].
>> This is addressed in PR #462 [3] with fairly minor changes to the expansion and compaction algorithms.
>> Reviews requested, and we’ll plan on merging this at the end of the week, unless feedback dictates making further changes.
>> Updated documents are available on my fork [4][5]. Note that change highlighting is cumulative.
>> Gregg Kellogg
>> gregg@greggkellogg.net
>> [1] https://github.com/json-ld/json-ld.org/issues/415
>> [2] https://github.com/json-ld/json-ld.org/issues/415#issuecomment-277021112
>> [3] https://github.com/json-ld/json-ld.org/pull/462
>> [4] http://gkellogg.github.io/json-ld.org/spec/latest/json-ld/
>> [5] http://gkellogg.github.io/json-ld.org/spec/latest/json-ld-api/
Received on Wednesday, 15 February 2017 22:49:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:49 UTC