- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Sun, 13 Apr 2014 20:28:12 -0400
- To: public-lod@w3.org
- Message-ID: <534B2B9C.4020801@openlinksw.com>
On 4/13/14 5:12 PM, Luca Matteis wrote: > On Sun, Apr 13, 2014 at 8:40 PM, Simon Spero <sesuncedu@gmail.com> wrote: >> Whilst Peter may have some memory lapses about some ambiguous parts of the >> OWL spec :), I do not believe that he has false memories of co-editing the >> second edition of the RDF Semantics document. >> >> http://www.w3.org/TR/2014/REC-rdf11-mt-20140225/ > Sorry didn't know he was the co-editor of the spec. Anyway it doesn't > hurt to clarify whether RDF actually holds any meaning for triples. I > always presumed that was part of the vocabularies and not part of RDF. > > RDF is a language, thus it is comprised of the following: 1. signs -- for entity denotation (in this case IRIs) 2. syntax -- constructing statements that represents entity relationships (in this case subject, predicate, object, triple patterns) 3. semantics -- for understanding the meaning of different types of relationships (in this case the meaning of the subject, predicate, and object relationship roles). A language is a framework for encoding and decoding information. This is what RDF is all about. 2 out of 3 (above) isn't RDF it has to be all three, since it's a language. What can make RDF confusing is the fact that you can create RDF document content using a variety of notations or so called "concrete syntaxes" (N-Triples, Turtle, RDF/XML, JSON-LD, HTML+RDFa, HTML+Microdata etc..). I hope this helps. Links: [1] http://bit.ly/1fluti1 -- Resource Description Framework (RDF) [2] http://bit.ly/1fVZDi5 -- Language . -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter Profile: https://twitter.com/kidehen Google+ Profile: https://plus.google.com/+KingsleyIdehen/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Monday, 14 April 2014 00:28:35 UTC