Re: JSON-LD terminology

On 8/29/12 12:59 PM, Gregg Kellogg wrote:
> On Aug 28, 2012, at 4:11 PM, Kingsley Idehen <kidehen@openlinksw.com> wrote:
>
>> On 8/28/12 2:57 PM, Gregg Kellogg wrote:
>>> [[[
>>> 1. Linked Data is a set of documents, each containing a representation of a linked data graph.
>> A quick dump for editorial massaging:
>>
>> Linked Data , as per TimBL's meme, describes a particular kind of resource (or data object). Basically, this resource type exhibits the following characteristics:
>>
>> 1. every entity is denoted (named) using a de-referencable URI -- this applies to web documents and other entities
> When this was discussed some time ago, it was agreed that we would leave room for BNodes in addition to IRIs, which indeed we need to do to represent arbitrary RDF. In step 8, we do say that IRIs SHOULD be dereferencable to a Linked Data document:
>
> [[[
> 8. IRIs used within a linked data graph SHOULD be dereferenceable to a Linked Data document describing the resource denoted by that IRI.
> ]]]
>
> Is this adequate?

Yes.

>
>> 2. every URI resolves to structured content representing the resource -- name resolution occurs by explicit or implicit indirection such that said URI always resolves its descriptor in the form of structured (description oriented) content
> Andy makes a similar point later; we never say that a Linked Data document need be a JSON-LD document, and I don't really think that's implied. I think that implicitly, a Linked Data document is one which conforms to these criteria, which includes the range of RDF formats. Perhaps that should be clarified in this section somehow.

Yes.

Try to make it consistent with TimBL's meme modulo the parenthesized 
items in #3 that list RDF and SPARQL in manners that are FUD friendly 
and easy pickings for those with R-D-F reflux etc..

>
>> 3. content structure is constrained by the RDF data model (and for those with R-D-F reflux condition, its: the EAV model + de-referencable URIs + explicit [rather than implicit] semantics)
>>
>> 4. content structure  takes the form entity-attribute-value (EAV) or subject-predicate-object (SPO) triple based statements.
> Ii think the preceding declaration should handle this, thanks!

Yes.

Kingsley
>
> Gregg
>
>> -- 
>>
>> Regards,
>>
>> Kingsley Idehen	
>> Founder & CEO
>> OpenLink Software
>> Company Web: http://www.openlinksw.com
>> Personal Weblog: http://www.openlinksw.com/blog/~kidehen
>> Twitter/Identi.ca handle: @kidehen
>> Google+ Profile: https://plus.google.com/112399767740508618350/about
>> LinkedIn Profile: http://www.linkedin.com/in/kidehen
>>
>>
>>
>>
>>
>
>


-- 

Regards,

Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen