Changes between Version 12 and Version 13 of RdsWipOneProcess

Timestamp:

11/20/08 16:06:56 (16 years ago)

Author:

jbourne (IP: 69.156.14.78)

Comment:

--

RdsWipOneProcess

@@ -216 +216 @@
 Whatever the source of the original submission, the submitted source is archived on the server machine (backed up offsite nightly) into an individual, sequenced directory.  Each variant of the source, including all step points in transformations through to OWL/RDF is archived in the same place.  This allows reconstruction of the submission from any step in the chain of transformations.
 
-=== Submission Allocation ====
+=== Submission Allocation ===
 
 In preparation for insertion into the nominated endpoint, non-resolvable identifiers (apart from blank nodes) in the OWL/RDF source are replaced with allocations from the ID generator (again, for the nominated endpoint).
@@ -230 +230 @@
 Any names or designations in the source will be transformed to kinds of rdf:label in the specified graph.  Due to the additional indexing and the configuration of cursor-based search in the triplestore, this allows searching for any terms by which the information in the submission is known.
 
+==== Query Technical ====
+
+Each endpoint supports SPARQL query over HTTP, using both CGI and SOAP according to the relevant W3C standards.  Result sets for SPARQL ''select'' queries are returned to the client encoding in XML according to the relevant W3C standards.
+
+This technology allows applications to dynamically query the endpoint at the machine to machine level.  While an understanding of the RDF assembly of the content is required, SPARQL itself requires no construction of RDF, and RDF parsers are not required to read the SPARQL result set.  This means that relatively simple CGI and XML parsing technology can be used to interoperate with the RDS/WIP. 
+
 === Presentation ===
 
@@ -236 +242 @@
 From here, the server will identify that the client is a browser, and redirect the client to request a CGI encoded-query with the fragment id included, rather than the URI itself bare.
 
-This CGI query results in the generation on the server of a page of content that aggregates information about the submission item.
-
-==== Presentation Detail ====
+This CGI query results in the generation on the server of a page of content that aggregates information about the submission item.  This single page is returned the client web browser.
+
+==== Presentation Technology ====
 
 The presentation is interpreted via a scheme developed by IDS-ADI named "infofilter" which is a means of mixing XSLT and SPARQL together with a namespace that allows specification of staged filters built on same.
 
 Since this system utilizes open standards and a manifestly simply filter staging system, it can be edited by those with no knowledge of the specific implementation: SPARQL and XSLT are all that is required to generate the most complex parts of the filter, and by convention in the design of the specific filter stages used, only XSLT is needed for the final transformation into XHTML for presentation.
-
 
 ==== RSS Feeds ====