Dear Wiki user, You have subscribed to a wiki page or wiki category on "Clerezza Wiki" for change notification.
The "LinkedDataPlatform" page has been changed by RetoBachmannGmuer: http://wiki.apache.org/clerezza/LinkedDataPlatform?action=diff&rev1=2&rev2=3 A page to describe in how far Clerrezza complias with W3C [[http://www.w3.org/TR/ldp/|LDP]] best practices for a read-write Linked Data architecture. - Looking at the various requirements + Looking at the various requirements ("Yes" means that Clerrezza satisfies all should and must level requirementst) * 4.1.1 LDPR servers must at least be HTTP/1.1 conformant servers [HTTP11]. @@ -54, +54 @@ [REC!] This requirements seems to imply that the properties have a preferred direction, which contradict http://dig.csail.mit.edu/breadcrumbs/node/72. Clerezza does not currently enforce a link it is possible to add to the contentgraph a triple with a subject IRI not otherwise used and a literal object. The resources generated by clerezza do have at least a type statement, would this qualify as link? + * 4.1.11 LDPR servers may support additional standard representations. These could be other RDF formats, like N3 or NTriples, but non-RDF formats like HTML [HTML401] and JSON [RFC4627] would be likely be common. + + Yes. + + * 4.1.12 LDPRs may be created, updated and deleted using methods not defined in this document, for example through application-specific means, SPARQL UPDATE, etc. [SPARQL-UPDATE] + + Yes. + + * 4.1.13 LDPR server responses must contain accurate response ETag header values. + + No. + + * 4.2.1 LDPR servers must support the HTTP GET Method for LDPRs. + + Yes + + * 4.2.2 LDPR servers must provide an text/turtle representation of the requested LDPR.[TURTLE] + + Yes + + * 4.2.3 LDPR servers should provide a application/rdf+xml representation of the requested LDPR.[RDF-SYNTAX] + + Yes. + + 4.2.4 In the absence of special knowledge of the application or domain, LDPR clients must assume that any LDPR may have multiple values for rdf:type. + + Yes. (For the limited code where clerezza acts as client) + + 4.2.5 In the absence of special knowledge of the application or domain, LDPR clients must assume that the rdf:type values of a given LDPR may change over time. + + + Partially. DbPedia client makes no assumption on persistence but Resource providers doesn't update. +
