Difference between revisions of "Linked Paleo Data"
(put in figure and created basic structure) |
|||
| Line 1: | Line 1: | ||
| + | = LiPD: Linked Paleo Data = | ||
| − | + | == The LiPD vision == | |
| + | |||
| + | Paleoclimate investigators have made a major effort over the past decade to make their data available to the broader community, largely through online archiving systems like the [https://www.ncdc.noaa.gov/data-access/paleoclimatology-data World Data Center for Paleoclimatology] and [http://www.pangaea.de/ Pangaea]. However, there is no agreed-upon data standard for how to store and exchange such data. As the number of records in these archives has grown, making connections manually has thus become more and more challenging, hampering integrative efforts at the very time they should be flourishing. Paleoclimatologists thus need a common tongue to describe their datasets to each other and to machines. | ||
| + | |||
| + | LiPD (Linked Paleo Data) proposes such a common tongue. It is a universally-readable data container that organizes data and metadata in a uniform way, such that they may be web-searchable, and such that a variety of code functionalities may be built and apply instantly to any dataset that observes that standard. | ||
| + | |||
| + | For more details, see [http://www.clim-past-discuss.net/11/4309/2015/cpd-11-4309-2015.html this article]. | ||
| + | |||
| + | == LiPD in LinkedEarth == | ||
| + | |||
| + | LipD is a convenient way to store and exchange paleoclimate format, and is an important building block of the LinkedEarth edifice. However, it is important to note that the LinkedEarth database grown via the [http://linked.earth/?projects=linkedearth-wiki wiki] is not reliant on LiPD. LiPD is merely a convenient way to exchange paleoclimate data in the Cloud. LiPD is closely aligned with the [http://linked.earth/projects/ontology/ LinkedEarth ontology], so any change in one is reflected in the other (with a small lag). | ||
| + | |||
| + | = Structuring data : the LiPD Way = | ||
| + | == LiPD components == | ||
| + | |||
| + | [[File:Lipd_structure.png|300px|thumb|left|structure of a lipd file]] | ||
| + | |||
| + | In its current version (1.3), there are 6 major components to a LiPD container: | ||
| + | === Root Metadata === | ||
| + | |||
| + | === Geographic Metadata === | ||
| + | |||
| + | === Publication Metadata === | ||
| + | |||
| + | === Funding Metadata === | ||
| + | === PaleoData Table === | ||
| + | === ChronData Table === | ||
| + | |||
| + | |||
| + | |||
| + | == LiPD implementation == | ||
| + | |||
| + | LiPD is centered on [http://json-ld.org/ JSON-LD], a [http://www.json.org/ JSON]-based format compliant with the [https://vimeo.com/36752317 Linked Data] paradigm. JavaScript Object Notation (JSON) is an extremely lightweight and flexible way to encode information, and has become the leading format for data exchange on the Web. [http://www.ted.com/talks/tim_berners_lee_on_the_next_web Linked Data] are datasets that observe common rules to be able to be automatically linked through the World Wide Web. A LiPD file (.lpd) is in fact a zipped folder containing: | ||
| + | |||
| + | LIST CONTENTS OF A LIPD FILE (csv files, JSON-LD file, md5 tag, etc) | ||
Revision as of 06:09, 26 February 2017
Contents
LiPD: Linked Paleo Data
The LiPD vision
Paleoclimate investigators have made a major effort over the past decade to make their data available to the broader community, largely through online archiving systems like the World Data Center for Paleoclimatology and Pangaea. However, there is no agreed-upon data standard for how to store and exchange such data. As the number of records in these archives has grown, making connections manually has thus become more and more challenging, hampering integrative efforts at the very time they should be flourishing. Paleoclimatologists thus need a common tongue to describe their datasets to each other and to machines.
LiPD (Linked Paleo Data) proposes such a common tongue. It is a universally-readable data container that organizes data and metadata in a uniform way, such that they may be web-searchable, and such that a variety of code functionalities may be built and apply instantly to any dataset that observes that standard.
For more details, see this article.
LiPD in LinkedEarth
LipD is a convenient way to store and exchange paleoclimate format, and is an important building block of the LinkedEarth edifice. However, it is important to note that the LinkedEarth database grown via the wiki is not reliant on LiPD. LiPD is merely a convenient way to exchange paleoclimate data in the Cloud. LiPD is closely aligned with the LinkedEarth ontology, so any change in one is reflected in the other (with a small lag).
Structuring data : the LiPD Way
LiPD components
In its current version (1.3), there are 6 major components to a LiPD container:
Root Metadata
Geographic Metadata
Publication Metadata
Funding Metadata
PaleoData Table
ChronData Table
LiPD implementation
LiPD is centered on JSON-LD, a JSON-based format compliant with the Linked Data paradigm. JavaScript Object Notation (JSON) is an extremely lightweight and flexible way to encode information, and has become the leading format for data exchange on the Web. Linked Data are datasets that observe common rules to be able to be automatically linked through the World Wide Web. A LiPD file (.lpd) is in fact a zipped folder containing:
LIST CONTENTS OF A LIPD FILE (csv files, JSON-LD file, md5 tag, etc)
