1 / 7

How to Reach the Citizen Developer A Story from TWC LOGD

How to Reach the Citizen Developer A Story from TWC LOGD. Li Ding Tetherless World Constellation Rensselaer Polytechnic Institute Nov 8, 2010. Data Organization at TWC LOGD Portal. Conversion Layer. LOGD (raw). LOGD (e1). …. Version. OGD (part1) Snapshot. OGD (part2) Snapshot. ….

garson
Télécharger la présentation

How to Reach the Citizen Developer A Story from TWC LOGD

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. How to Reach the Citizen DeveloperA Story from TWC LOGD Li Ding Tetherless World Constellation Rensselaer Polytechnic Institute Nov 8, 2010

  2. Data Organization at TWC LOGD Portal Conversion Layer LOGD (raw) LOGD (e1) … Version OGD (part1) Snapshot OGD (part2) Snapshot … Data publishing stages Source Dataset Table Record … high Levels of structural data granularity low

  3. TWC LOGD Metadata Explained: Levels of structural data granularity • "source" refers to the data publishers who maintains a catalog OGD datasets for download. An example source is Data.gov (http://data.gov). • "dataset" refers to an OGD dataset. A dataset is typically determined by the data publishers, for example, "Dataset 1623 (OMH Claims Listed by State)" is a dataset entry in Data.gov catalog (see http://www.data.gov/details/1623). • "table" refers to a data table (organized in tabular structure) in OGD datasets. Although an OGD dataset often contains one table, it may also contain multiple tables. In "Dataset 1623", there is only one table. Note that the data in OGD dataset may be stored in non-tabular structure, e.g. an XML tree. Those data structures are out of scope of this tutorial. • "record" refers to a data row in a data table.

  4. TWC LOGD Metadata Explained: Data Publishing Stages • at "dataset" stage, raw OGD data are available for download at certain Web locations. Note that raw OGD data are subject to change by the data publishers: users may download different versions of dataset from the same URL. • at "version" stage, snapshots of raw OGD data are created and versioned. This stage archives the content of the OGD data at a certain time point and provides persistent access to the capture version of the raw OGD data. Note that a dataset may contain multiple parts (e.g. data tables) each of which is stored in a static file. • at "conversion layer" stage, conversion configurations are used to convert the raw OGD data into the corresponding LOGD data. The basic conversion configuration is "raw", which is automatically generated with the minimal manual input. A number of manually crafted enhancement configurations are also allowed to generate monotonically incremental LOGD data.

  5. Human Friendly URI Naming • <source_uri> ::= <base_uri>/source/<source_identifier> • <dataset_uri> ::= <source_uri>/dataset/<dataeset_identifier> • <version_uri> ::= <dataset_uri> /version/<version_identifier> • <record_uri> ::= <version_uri>/<record_identifier> • <conversion_uri> ::= <dataset_uri> /conversion/<conversion_identifier> • <conversion_identifier> ::= raw | enhancement/1 | enhancement/2 | … • <predicate_uri> ::= <dataset_uri>/vocab/<conversion_identifier>

  6. TWC LOGD Organization Described by VOID Metadata Sample Conversion Layer (e1) rdf:type Conversion Layer (raw) rdf:type void:subSet Version (v2) void:Dataset rdf:type Version (v1) Meta rdf:type Dataset void:subSet rdf:type

  7. Data-related Features at TWC LOGD Portal • Monotonic Data Growth • Record Versions of Data • Old versions never override by new version • Flexible Conversion Layer • “raw” conversion requires minimal human efforts • “enhancement” conversion is highly customizable (via a RDF-based configure file) to support conversion-stage enhancements • Flexible Data Access • Download RDF data dumps • LD Content-negotiation for resolving URIs • Access SPARQL Endpoint • Aggregated Metadata Publishing for dataset • VOID metadata generated at conversion time • Metadata collected from other sources • Manually contributed by TWC LOGD Portal Users

More Related