Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Lyo/LDPImpl"
(→Specification Conformance) |
|||
| 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 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 == | ||
| Line 5: | Line 5: | ||
== Design == | == Design == | ||
| − | Simple approach to have 1 interface/class per type of LDP resource. Have Jena specific extensions. Goal is to learn from this experience, not for it to initially be highly scalable and reusable framework. | + | 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. | ||
== Specification Conformance == | == Specification Conformance == | ||
| Line 21: | Line 23: | ||
| LDP Direct Containers | | LDP Direct Containers | ||
| completed | | completed | ||
| − | | | + | | All variants supported : membershipResource, hasMemberRelation, isMemberOfRelation |
|- | |- | ||
| LDP Indirect Containers | | LDP Indirect Containers | ||
| Line 28: | Line 30: | ||
|- | |- | ||
| LDP Non-RDF Sources | | LDP Non-RDF Sources | ||
| − | | | + | | completed |
| − | | | + | | |
|} | |} | ||
== 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. |
Revision as of 09:47, 30 June 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 minimalistically a 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.
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 |
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.