Changes between Version 34 and Version 35 of rdfstore


Ignore:
Timestamp:
Oct 29, 2012, 12:53:15 AM (12 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • rdfstore

    v34 v35  
    1717
    1818The essence of this proposal is to change this process as follows:
    19  * transform the metadata record into an RDF (resource data format) document when it is ingested by !GeoNetwork
    20  * store the RDF document in an RDF triple store
    21  * use the RDF triple store and the SPARQL query language for searching
     19 * transform the metadata record into RDF (resource description framework) facts when it is ingested by !GeoNetwork
     20 * store the RDF facts in an RDF store
     21 * use the RDF store and the SPARQL/GeoSPARQL query language for searching these facts
    2222
    2323Why would we do this?
    24  * Simplify the architecture of !GeoNetwork: metadata would be stored and searched in the same persistence solution - the RDF triple store
    25  * RDF is purpose designed for representing facts and relationships between facts
    26  * RDF triple stores and the SPARQL/GEOSPARQL query language are designed to query facts and relationships between facts
    27  * A lot of resources have been devoted to managing ISO19115 metadata records and ISO19115 metadata objects in GeoNetwork - switching to RDF would focus attention on supporting generic metadata objects that can be reused within as well as outside the ISO world-view - history shows that no single metadata standard has ever gained ascendancy over all domains eg. Taxon Concept Schema and Darwin Core are popular for biological data, Dublin Core remains popular for (which?) some applications, SDMX is used for statistical metadata and so on - using a generic fact representation seems to be a more worthwhile and sustainable approach
     24 * A metadata record is a collection of facts: RDF is purpose designed for representing facts and relationships between facts
     25 * RDF stores and the SPARQL/GEOSPARQL query language are designed to query facts and relationships between facts
     26 * Simplify the architecture of !GeoNetwork: metadata would be stored and searched in the same persistence solution - the RDF store
    2827
    2928=== Proposal Type ===
    … …  
    4746
    4847== Motivations ==
    49 TBA
     48
     49RDF (Resource Description Framework) is a general method to decompose knowledge into small pieces. A piece of knowledge in RDF refers to two objects and a relationship between them (often called a triple).
     50
     51A lot of resources in the !GeoNetwork space have been devoted to managing ISO19115 metadata records, ISO19115 metadata objects and relationships between objects and records. In many ways, exploring RDF is an attempt to achieve the same outcomemeans that metadata records would be broken down into small facts that can be used and reused in any metadata record (not just an ISO metadata record) - history shows that no single metadata standard has ever gained ascendancy over all domains eg. Taxon Concept Schema and Darwin Core are popular for biological data, Dublin Core remains popular for (which?) some applications, SDMX is used for statistical metadata and so on - using a generic fact representation seems to be a more worthwhile and sustainable approach
    5052
    5153== Proposal ==