Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Lyo/LDPImpl"
(→Plans) |
|||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | This page is dedicated to Lyo's reference implementation for the [http://www.w3.org/TR/ldp/ W3C Linked Data Platform] which provides the basis for OSLC 3. | + | This page is dedicated to Lyo's [http://wiki.eclipse.org/Lyo/BuildLDPSample reference implementation] for the [http://www.w3.org/TR/ldp/ W3C Linked Data Platform] which provides the basis for [http://open-services.net OSLC] 3. |
== Approach == | == Approach == | ||
| − | Build | + | Build a minimalistic reference implementation based on a set of community prioritized technologies. Initial work will be using Java-based frameworks such as JAX-RS with Apache Jena. From this, plan to learn about how an SDK might be developed and for OSLC needs, how OSLC4J will evolve. |
== Design == | == Design == | ||
| − | + | Simple approach to have 1 interface/class per type of LDP resource. There are usually 2 named graph per resource, named by the URL itself and a companion one to hold implementation specific information (appended with "?config"). Have Jena specific extensions. | |
| + | |||
| + | Goal is to learn from this experience, not for it to initially be highly scalable and reusable framework. | ||
| + | |||
| + | Information on how to get access to source code and build instructions is located on a [http://wiki.eclipse.org/Lyo/BuildLDPSample separate page]. | ||
== Specification Conformance == | == Specification Conformance == | ||
| Line 16: | Line 20: | ||
|- | |- | ||
| LDP Basic Containers | | LDP Basic Containers | ||
| − | | | + | | completed |
| | | | ||
|- | |- | ||
| LDP Direct Containers | | LDP Direct Containers | ||
| − | | | + | | completed |
| − | | | + | | All variants supported : membershipResource, hasMemberRelation, isMemberOfRelation |
|- | |- | ||
| LDP Indirect Containers | | LDP Indirect Containers | ||
| not started | | not started | ||
| uncertain when/if we do | | uncertain when/if we do | ||
| + | |- | ||
| + | | LDP Non-RDF Sources | ||
| + | | completed | ||
| + | | | ||
|} | |} | ||
| + | |||
| + | === Testsuite compliance === | ||
| + | |||
| + | Test [https://dvcs.w3.org/hg/ldpwg/raw-file/default/tests/reports/ldp.html results have been submitted] and plan to update as both this reference implementation improves as well as the [http://w3c.github.io/ldp-testsuite/ ldp-testsuite] as well. | ||
== Plans == | == Plans == | ||
| − | Actively working on a near-complete reference implementation in support of LDP implementation feedback. | + | Actively working on a near-complete reference implementation in support of LDP implementation feedback. Investigating a place to have it publicly hosted. Considering provide more robust logging and also provide reports for client testing. |
Latest revision as of 09:04, 11 August 2014
This page is dedicated to Lyo's reference implementation for the W3C Linked Data Platform which provides the basis for OSLC 3.
Approach
Build a minimalistic reference implementation based on a set of community prioritized technologies. Initial work will be using Java-based frameworks such as JAX-RS with Apache Jena. From this, plan to learn about how an SDK might be developed and for OSLC needs, how OSLC4J will evolve.
Design
Simple approach to have 1 interface/class per type of LDP resource. There are usually 2 named graph per resource, named by the URL itself and a companion one to hold implementation specific information (appended with "?config"). Have Jena specific extensions.
Goal is to learn from this experience, not for it to initially be highly scalable and reusable framework.
Information on how to get access to source code and build instructions is located on a separate page.
Specification Conformance
| Feature | Status | Notes |
|---|---|---|
| LDP Basic Containers | completed | |
| LDP Direct Containers | completed | All variants supported : membershipResource, hasMemberRelation, isMemberOfRelation |
| LDP Indirect Containers | not started | uncertain when/if we do |
| LDP Non-RDF Sources | completed |
Testsuite compliance
Test results have been submitted and plan to update as both this reference implementation improves as well as the ldp-testsuite as well.
Plans
Actively working on a near-complete reference implementation in support of LDP implementation feedback. Investigating a place to have it publicly hosted. Considering provide more robust logging and also provide reports for client testing.