Dear Wiki user, You have subscribed to a wiki page or wiki category on "Marmotta Wiki" for change notification.
The "LDPImplementationReport" page has been changed by JakobFrank: https://wiki.apache.org/marmotta/LDPImplementationReport?action=diff&rev1=28&rev2=29 Comment: Updated Implementation Report We agree on some restrictions: * '''Identifiers''' - * trailing slash is ignored (removed) for URI generation. + * trailing slash is ignored (removed) for URI generation. - thus http://example.com/foo and http://example.com/foo/ are treated as identic. + thus http://example.com/foo and http://example.com/foo/ are treated as identical. - * query part of an URL will never be used as part of a URI. + * query part of an URL will never be used as part of a URI. query parameters might be used for some LDP operations such as non-membership triples (tbd) * resources with fragments can't be addressed directly, but can be accessed via their container (URL without fragment) * '''Storage''' - * internally every LDP-R will be stored in its own (Sesame) context (as could be interpreted from [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#h4_ldpc-post-createrdf|sec 6.4.5]]) + * internally every LDPR will be stored in its own (Sesame) context (as could be interpreted from [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#h5_ldpc-post-createrdf|sec 5.2.3.4]]) * that would allow us to extend the Resource concept beyond the common understanding in triplestores (just one level of outgoing triples) - * '''Paging''' and '''Sorting''' will be not supported + * '''Paging''' and '''Sorting''' is not supported Anyway the WG has resolved (Feb 17, 2014) to move out paging and ordering into a separate spec: [[http://www.w3.org/2013/meeting/ldp/2014-02-17#resolution_5|2014-02-17#r5]] + * '''ETags''' for LDP-RS are ''weak'' and soley based on the {{{dcterms:modified}}} value, while ETags for LDP-NR are based on the md5sum of the file content. + * Both '''LDP-NR''' and '''LDP-NR''' are supported - * '''ETags''' are ''weak'' and soley based on the {{{dcterms:modified}}} value - This is something to improve for the future - * We will provide support to the full LDP hierarchy ([[http://mail-archives.apache.org/mod_mbox/marmotta-dev/201402.mbox/%3C52FA14DD.6090506%40salzburgresearch.at%3E|discussion on the mailing-list]]). * Our interpretation of Sec. 5.2.3.12 implements that POST of content types not managed by the platform (i.e., not suitable Rio parser registered) adds a LDP-RS as member of the container, linking ({{{dct:hasFormat}}}/{{{dct:isFormatOf}}}) to the actual LDP-NR (URI is build by appending the file extension according the content type) - * Sec. 5.2.11 ('''{{{rel='describedby'}}}-Link''') will be fulfilled by pointing to this page. + * '''Only LDP-BC''' is supported, since current use cases do not justify the inclusion of LDP-DC or LDP-IC + * Sec. 4.2.1.6 ('''{{{rel='ldp:constrainedBy'}}}-Link''') is fulfilled by pointing to [[LDPImplementationReport/2014-09-16|this page]]. - {{{Link: <http://wiki.apache.org/marmotta/LDPImplementationReport>; rel="describedby"}}} + {{{Link: <http://wiki.apache.org/marmotta/LDPImplementationReport/2014-09-16>; rel="http://www.w3.org/ns/ldp#constrainedBy"}}} - * For the time beeing, '''only LDP-BCs are supported''' - * '''PATCH''' accepts [[http://afs.github.io/rdf-patch/|application/rdf-patch]] only + * '''PATCH''' accepts [[http://afs.github.io/rdf-patch/|application/rdf-patch]] only (LD Patch support will be discussed) Patches with the predicate {{{ldp:contains}}} will result in a {{{HTTP 409 Conflict}}} == Instructions ==
