Here are a few key points about the LDP Container resource:- Containers can have membership predicates other than rdfs:member to define the relationship between the container and its members. In this example it is o:asset.- The subject of the membership for a container's members can be something other than the container itself. Here it is the overall NetWorth resource. - Additional information about container members, like their types, can be provided inline rather than requiring separate requests. This gives clients a complete representation of the container and its members.- Large containers can be paginated to allow clients to retrieve subsets of the overall membership. Cursors or other paging controls would need to be supported
10+ Deploys Per Day: Dev and Ops Cooperation at Flickr
Similar a Here are a few key points about the LDP Container resource:- Containers can have membership predicates other than rdfs:member to define the relationship between the container and its members. In this example it is o:asset.- The subject of the membership for a container's members can be something other than the container itself. Here it is the overall NetWorth resource. - Additional information about container members, like their types, can be provided inline rather than requiring separate requests. This gives clients a complete representation of the container and its members.- Large containers can be paginated to allow clients to retrieve subsets of the overall membership. Cursors or other paging controls would need to be supported
Similar a Here are a few key points about the LDP Container resource:- Containers can have membership predicates other than rdfs:member to define the relationship between the container and its members. In this example it is o:asset.- The subject of the membership for a container's members can be something other than the container itself. Here it is the overall NetWorth resource. - Additional information about container members, like their types, can be provided inline rather than requiring separate requests. This gives clients a complete representation of the container and its members.- Large containers can be paginated to allow clients to retrieve subsets of the overall membership. Cursors or other paging controls would need to be supported (20)
Here are a few key points about the LDP Container resource:- Containers can have membership predicates other than rdfs:member to define the relationship between the container and its members. In this example it is o:asset.- The subject of the membership for a container's members can be something other than the container itself. Here it is the overall NetWorth resource. - Additional information about container members, like their types, can be provided inline rather than requiring separate requests. This gives clients a complete representation of the container and its members.- Large containers can be paginated to allow clients to retrieve subsets of the overall membership. Cursors or other paging controls would need to be supported
Reference: “Linked Data”, Tim Berners-Lee, 2006-07-27
Points:At the core is a set of Statements (aka facts), which are typically written down or learnedTell the story as if the present is a tester, they have knowledge of their test cases and of Joe. In the Web 1.0/2.0 way to learn these things is by publishing on a HTML page for a human consumer of itThis follows TBL’s 4 rules for linked dataFirst we give these statement URIs so computers can identify them and understand them. Grouping into subject-predicate-object builds the statementNext we can do a HTTP GET to learn moreWhen we learn more, it is in the form of more statements with URIsThose URIs point to more things or relate things back to things we already know (Joe)Jira http://www.atlassian.com/software/jira/overview
Points:Same information as the previous slide but just as a direct graphHighlight this is just the way the web worksCan point out that easy to extend to include things like: can learn when dependent software has been fixed, built and where it is available
Key pointsRequest URI == subjectResource has a typeSimple defnResponse representation is the full state of the resource (there is no other data the server knows about it, all other data is either inbound links or stored where it doesn’t know)
http://incubator.apache.org/clerezza/ Clerezza allows to easily develop semantic web applications by providing tools to manipulate RDF data, create RESTful Web Serviceshttp://stanbol.apache.org/index.html Apache Stanbol's intended use is to extend traditional content management systems with semantic serviceshttp://jena.apache.org/documentation/serving_data/index.html Apache Jena and FusekiFuseki is a SPARQL server. It provides REST-style SPARQL HTTP Update, SPARQL Query, and SPARQL Update using the SPARQL protocol over HTTP.http://incubator.apache.org/wink/ http://eclipse/lyo