RE: how does a term definition include all of : type, id, and alias

On 20 Jul 2014 at 15:24, james anderson wrote:
> good afternoon;
> 
> On 20 Jul 2014, at 13:01, Markus Lanthaler <markus.lanthaler@gmx.net>
wrote:
> 
>>> [ . eliding apparent confusion about how one represents graph
transformations .]
>> 
>> Simply speaking, terms such as myIdAlias are first replaced with the
keyword
>> they alias (@id) and then processed as usual. The processing is defined
in
>> detail in the JSON-LD Processing Algorithms & API specification:
>> 
>>  http://www.w3.org/TR/json-ld-api/
> 
> must one use an intermediate json-equivalent data model in order use
json-ld
> as the abstract means to frame rdf?

You don't need to but that's how the algorithm is currently specified.
Please note that framing isn't standardized yet!


>>> i note, also, that as the expression conflates either the processing
>>> role and the universal identifier, or the member term and the
>>> universal identifier, it lacks the degrees of freedom required to
>>> specify all combinations.
>> 
>> Could you elaborate?
>> 
>> 
>>> is there yet another alternative?
>> 
>> I can tell you if you explain me what you are trying to achieve :-)
>> 
> 
> how would one declare how to frame
> 
> _:thing1 <http://example.com/id> <http://example.com/thing#1> .
> _:thing1 <http://example.com/type> <http://example.com/ImportantThing> .
> _:thing2 <http://example.com/feature> <http://example.com/thing#2> .
> _:thing2 <http://example.com/id> <http://example.com/thing#2> .
> _:thing2 <http://example.com/type> <http://example.com/Feature> .
> _:thing2 <http://example.com/characteristic> "low power consumption" .

I assume you meant this instead, otherwise the JSON snippet below doesn't
make much sense as the two blank nodes aren't connected to each other (at
least not directly):

<http://example.com/thing#1> <http://example.com/type>
<http://example.com/ImportantThing> .
<http://example.com/thing#1> <http://example.com/feature>
<http://example.com/thing#2> .
<http://example.com/thing#2> <http://example.com/type>
<http://example.com/Feature> .
<http://example.com/thing#2> <http://example.com/characteristic> "low power
consumption" .

> into
> 
> [ { "key" : <http://example.com/thing#1>,
>     "class":  <http://example.com/ImportantThing>,
>     "features" : [ { "key" : <http://example.com/thing#2>, "class":
> <http://example.com/Feature>, "detail": "low power consumption" } ]  } ]

You can use the following frame

  {
    "@context": {
      "key": "@id",
      "class": { "@id": "http://example.com/type", "@type": "@id" },
      "features": "http://example.com/feature",
      "detail": "http://example.com/characteristic"
    },
    "features": {}
  }

http://tinyurl.com/maezvet



--
Markus Lanthaler
@markuslanthaler

Received on Sunday, 20 July 2014 14:03:30 UTC