- From: carmen <_@whats-your.name>
- Date: Fri, 28 Nov 2014 21:51:06 +0000
- To: public-hydra@w3.org
> This mail should clear up all the LDF / TPF / SPARQL confusion LDP Containers can host triple-pattern matches as well, <http://www.w3.org/ns/ldp#> has some properties: :hasMemberRelation rdfs:comment "Indicates which predicate is used in membership triples, and that the membership triple pattern is < membership-constant-URI , object-of-hasMemberRelation, member-URI >."; :isMemberOfRelation a rdf:Property; rdfs:comment "Indicates which predicate is used in membership triples, and that the membership triple pattern is < member-URI , object-of-isMemberOfRelation, membership-constant-URI >."; i don't pretend to know all the subtleties regarding Indirect vs Direct vs Basic vs Regular containers, or the confusing usage of both "membership" and "containment" for different things - will wait for Sandro's "LDP Lite" if he's planning one. when using a Container this way, a Link relation in the HTTP Header alongside rel=next,rel=prev might be informative container URI as subject||object URI, predicate URI specified for this request, a full-triple is finished with a list of URIs, linebreak/space/tab-seperated as you might pass around between UNIX utilities - maybe 'bloomd' for set-intersection https://github.com/armon/bloomd , append-only URI-lists as files to evade SPARQL-on-SQL-ACID-commit-rollback-replica-socket-missing 503-fragility or what have you? am using a MIME called text/uri-list for this, is there an existing one? , irregardless of trying to reach some interoperable consensus on pattern/pagination/simple-sets for a second.. curl -H 'Accept: text/uri-list' 'http://m.whats-your.name/address/p/public-hydra@w3.org/?c=64&set=page'
Received on Friday, 28 November 2014 21:51:30 UTC