--- a/ldp-ucr.html Mon Jul 08 12:35:20 2013 +0100
+++ b/ldp-ucr.html Mon Jul 08 12:45:47 2013 +0100
@@ -130,60 +130,7 @@
data, especially public data, available on the web has grown
rapidly, and an impressive number of extremely creative and useful
“mashups” have been created using this data as result.</p>
- <p>There has been much less focus on the potential of Linked
- Data as a model for managing data on the web - the majority of the
- Application Programming Interfaces (APIs) available on the
- Internet for creating and updating data follow a Remote Procedure
- Call (RPC) model rather than a Linked Data model.</p>
- <p>If Linked Data were just another model for doing something
- that RPC models can already do, it would be of only marginal
- interest. Interest in Linked Data arises from the fact that
- applications with an interface defined using Linked Data can be
- much more easily and seamlessly integrated with each other than
- applications that offer an RPC interface. In many problem domains,
- the most important problems and the greatest value are found not
- in the implementation of new applications, but in the successful
- integration of multiple applications into larger systems.</p>
- <p>Some of the features that make Linked Data exceptionally
- well suited for integration include:</p>
- <ul>
- <li>A single interface – defined by a common set of HTTP
- methods – that is universally understood and is constant across
- all applications. This is in contrast with the RPC architecture
- where each application has a unique interface that has to be
- learned and coded to.</li>
- <li>A universal addressing scheme – provided by HTTP URLs –
- for both identifying and accessing all “entities”. This is in
- contrast with the RPC architecture where there is no uniform way
- to either identify or access data.</li>
- <li>A simple yet extensible data model – provided by RDF –
- for describing data about a resource in a way which doesn’t
- require prior knowledge of vocabulary being used.</li>
- </ul>
- <p>Experience implementing applications and integrating them
- using Linked Data has shown very promising results, but has also
- demonstrated that the original four rules defined by Tim
- Berners-Lee for Linked Data are not sufficient to guide and
- constrain a writable Linked Data API. As was the case with the
- original four rules, the need generally is not for the invention
- of fundamental new technologies, but rather for a series of
- additional rules and patterns that guide and constrain the use of
- existing technologies in the construction of a
- [[LINKED-DATA-PLATFORM]] to achieve interoperability.</p>
- <p>The following list illustrates a few of the issues that
- require additional rules and patterns:</p>
- <ul>
- <li>What URLs do I post to in order to create new resources?
- </li>
- <li>How do I get lists of existing resources, and how do I
- get basic information about them without having to access each
- one?</li>
- <li>How should I detect and deal with race conditions on
- write?</li>
- <li>What media-types/representations should I use?</li>
- <li>What standard vocabularies should I use?</li>
- <li>What primitive data types should I use?</li>
- </ul>
+
<p>The goal for the [[LINKED-DATA-PLATFORM]] is
to define a specification required to allow the definition of a
writable Linked Data API equivalent to the simple application APIs