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=1&rev2=2

  
  * 4.1.7 LDPR representations should have at least one rdf:type set 
explicitly. This makes the representations much more useful to client 
applications that don’t support inferencing.
  
+ Partially. Resources generated by Clerezza conform to the requirement but its 
possible to insert arbitrary data.
+ 
  The description of any named resource in the content graph is served if a get 
request for that resource is sent against the clerezza instance and the URI is 
not handled by a dedicated Jax-RS resource and the resource if not of a type 
for which a Typehandler is registered. When addin triples to the content graph 
there's no mechanism enforcing that all named resources have an RDF type 
statement.
  
- 4.1.8 Predicate URIs used in LDPR representations should be HTTP URLs. These 
predicate URIs must identify LDPRs whose representations are retrievable. LDPR 
servers should provide an RDF Schema [RDF-SCHEMA] representation of these 
predicates. 
+ * 4.1.8 Predicate URIs used in LDPR representations should be HTTP URLs. 
These predicate URIs must identify LDPRs whose representations are retrievable. 
LDPR servers should provide an RDF Schema [RDF-SCHEMA] representation of these 
predicates. 
+ 
+ Partially. Triples generated by Clerezza should conform to the requirement 
but its possible to insert arbitrary data.
  
  As arbitrary triples can be uploaded there's no mechanism enforcing 
meaningfull dereferenceability of the type statements.
  
+ * 4.1.9 LDPR representations must use only the following standard datatypes. 
RDF does not by itself define datatypes to be used for literal property values, 
therefore a set of standard datatypes based on [XMLSCHEMA11-2] and [RDF-PRIMER] 
are to be used: xsd types + rdf-xml
+ 
+ Partially. With the exception of the WebId module [verify] literals generated 
by Clerezza conform to the requirement but its possible to insert arbitrary 
data. 
+ 
+ * 4.1.10 LDPRs must use at least one RDF triple to represent a link 
(relationship) to another resource. In other words, having the source 
resource’s URI as the subject and the target resource’s URI as the object of 
the triple represent the link (relationship) is enough and does not require the 
creation of an intermediate link resource to describe the relationship. 
+ 
+ [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?
+ 

Reply via email to