Registry Technical Training

download Registry Technical Training

of 102

  • date post

    23-Aug-2014
  • Category

    Internet

  • view

    110
  • download

    2

Embed Size (px)

description

Technical "how to" training course on use of the Linked Data registry and the associated data conversion service.

Transcript of Registry Technical Training

  • Registry Environment registry service Technical training
  • Registry Course scope Enable participants to: prepare a code list for registration register a code list manage a registered list access a code list Out of scope delegation and proxy support detailed update API general data modelling system deployment and management Preamble
  • Registry Prerequisites Required: familiar with material from introductory webinar notion and purpose of registry high level information model Preferable: some familiarity with JSON syntax Helpful but not necessary: some knowledge of RDF and Turtle syntax Preamble
  • Registry Course structure 1. Preamble 2. End to end example 3. Design and data preparation 4. Publication 5. Managing entries 6. Accessing content 7. Advanced cases (some optional) 8. Wrap up discussion Design Data preparation Publish Manage Access Preamble
  • Registry End to end example Demonstration csv code list - rbd.csv convert upload set status view download Demo
  • Registry Design and data preparation Case: local code list to be published openly no existing URIs (see advanced section for external entity case) Topics to cover: URI structure standard code list cases data conversion utility simple code list hierarchical code list organizations representation and vocabularies custom code lists small extensions direct formatting see advanced topics later
  • Registry URI structure Why? URIs are opaque so technically doesnt matter but predictable patterns help data users URI structure ties to administration structure Formal guidance: http://tinyurl.com/UKGovLD-revisedUriPatterns http://{domain}{/collection*} [/id][/{concept}/{key}]*[/{concept}][#id] - uri sets [/def]{/vocabulary*}[/{term}][#{term}] - vocabs Design and data preparation
  • Registry URI structure Registry convention treat as vocabularies (concepts) use top level sub-collections to ease management http://environment.data.gov.uk/registry /def/{collection}/{code-list} http://environment.data.gov.uk/registry /def/{collection}/{code-list}/{code} Design and data preparation
  • Registry URI structure {collection} choose a name to reflect the nature of the lists that can be kept stable that is legal in a URI segment registry admin/organization SRO creates, delegate to publisher example: catchment-planning {code-list} chose stable, legal, name reflecting nature of the list often noun reflecting type of the entity in the list example: RiverBasinDistrict {code} unique identifier for the entry in the list typically available as an id or notation, otherwise mangle label Design and data preparation
  • Registry URI structure Registry upload allows relative URIs create list using {code-list}/{code} then upload to: http://environment.data.gov.uk/registry /def/{collection} Design and data preparation
  • Registry SPARQL Standard cases ETL JSON Code list server proxy requests Registry service Existing local code lists registry-util converter [CSV] RDF Design and data preparation
  • Registry Standard cases Supported by data conversion tool http://environment.data.gov.uk/registry-util/ predefined templates for some common formats more templates can be added form for metadata preview raw converted data generates (RDF) file ready for publication Design and data preparation
  • Registry Standard cases Simple, flat code list simple-skos labelled-skos (if no notation column) CSV structure: label description notation note definition label used for presentation and UIs explanation of code (text) notation used in data supplementary note (text) formal definition (text) Required Optional Optional (can use label) Optional Optional Design and data preparation
  • Registry Standard cases Hierarchical code list hierarchical-skos CSV structure: label1 label2 label3 description notation note definition label (top level code) explanation of code (optional) notation used in data (optional) (optional) label (second level code) explanation of code (optional) notation used in data (optional) (optional) label (third level code) explanation of code (optional) notation used in data (optional) (optional) Design and data preparation
  • Registry Standard cases Simple organization two-level-organization CSV structure:org suborg description label of a parent organization description of the organization label of sub-organization description of the sub- organization label of sub-organization description of the sub- organization Design and data preparation
  • Registry Standard cases Will demonstrate shortly ... But first look at the representation details helpful background understand conversion previews only strictly necessary if developing custom lists Design and data preparation
  • Registry Representation and vocabularies What do you want to say about a code? How should it be represented in the data? Recall information model: each registered item is identified by a URI described by a set of property values each property is itself identified by a URI standard vocabularies of useful properties open, can freely add properties mandatory minimum is a type and label Design and data preparation
  • Registry Aside on notation Prefix notation avoid writing long URIs for types and properties prefix:local for example: rdfs:label skos:Concept prefix maps to a namespace URI related to qnames in XML but just concatenation skos:Concept = http://www.w3.org/2004/02/skos/core#Concept Design and data preparation
  • Registry Common prefixes Registry preloaded with common prefixes [Just another register, so can extend] Prefix Vocabulary Examples rdf RDF core rdf:type rdfs RDF schema rdfs:label, rdfs:comment skos Simple Knowledge Organization Scheme skos:Concept, skos:prefLabel, skos:broader dct Dublin core terms dct:description, dct:publisher org Organization ontology org:Organization reg Registry vocabulary reg:Register ldp Linked data platform ldp:Collection ldp:membershipPredicate xsd Xml Schema Datatypes xsd:string Design and data preparation
  • Registry Representation and vocabularies Standard templates SKOS examples a single code row is given the properties: Property value rdf:type skos:Concept skos:prefLabel label rdfs:label label skos:notation notation or clean(label) dct:description description skos:note note skos:definition definition skos:inScheme skos:topConceptOf if top level skos:narrower Design and data preparation
  • Registry Example Hierarchical code list look at vehicles.csv create project and upload select template fill in metadata convert browse Design and data preparation Demo
  • Registry Custom code lists Sometimes want a richer representation custom types for entries additional properties correspondence mappings whole different representation Various options to achieve this: request additional templates for the registry-util generic property columns custom data generation (see later) Design and data preparation
  • Registry Generic property columns Situation standard SKOS template is mostly fine but want to get entries additional types or additional properties Solution add column in sheet for additional property column name give URI for property in if column value is in then its treated as a URI else its a literal (string, number, date) Design and data preparation
  • Registry Generic property columns - example River Basin Districts would like to also type each entry to match WFD vocabulary Design and data preparation
  • Registry Publication Security model Upload forms
  • Registry Security model Authentication not needed to read and browse username/password or OpenID (e.g. Yahoo) can set password for OpenID as a backup register using OpenID provider or email/password up to administrator to grant you permissions Authorization rights granted to Register or Item rights on Register inherit to sub-registers/items manager role register, update, status-update, grant maintainer role update, grant can set a Register fully open - any registered user can update Publication
  • Registry Publish a prepared registration Login Publication
  • Registry Publish a prepared registration Login Publication