DCLite4G
DCLite4G is short for "Dublin Core Lightweight Profile for Geospatial". It is a minimal information model for metadata about geospatial data. DCLite4G consists of:
- an abstract information model
- an implementation reference exploiting common standard vocabularies - Dublin Core, GeoRSS.
- a namespace used to define extra properties needed to usefully specify the properties of geospatial data.
The URL at which the namespace lives, contains an OWL ontology showing the structure, providing where possible mappings to various metadata schemas.
Information Model
Data Set
A Data Set is an abstract object. It corresponds to the ideal of a data set, independent of a physical form or an encoding in which it is being distributed. For example, "TIGER 2005" or "OpenStreetmap from 2007-04-20", or "SRTM" would be considered data sets.
A Data Set can be associated with one or many Data Sources which correspond to concrete resources which can be got at in order to explore the data. All the properties which are shared across multiple Data Sources, are properties of the Data Set. If the properties of a Source are different - e.g. a smaller spatial extent, or a generalised subset of features in the same extent - then it is an instance of a different Data Set.
One goal in this is to make it more possible to trace and annotate the recombination of different sources of data into one package - keeping track of what is known as "lineage" of data packages.
Properties
| Name | A name given to a data set. Does not have to be unique or "canonical". |
| Abstract | A text description of the contents of a data set, remarks on anything interesting contained therein. |
| Keywords | A layer may have none or many keywords associated with it. |
| Publisher | Contact information for the Agent publishing the data set |
| Originator | Contact information for the original creator of the data set |
| Publication Date | Date on which the data was made available |
| License | URL of a data license whose terms cover the distribution of this data set. |
| Object type | Currently, one of 'Vector','Raster','Coverage' |
| Extents | A bounding box or polygon specified in WGS84, regardless of the original projection and datum of the data. |
| Projection | The original spatial projection of the data |
| Resolution | (for Raster, Coverage types) |
| Colour Depth | (for Raster, Coverage types) e.g. 8, 16, 24 bit |
| Transparency | (for Raster type) |
Relations
- A Data Set can have optionally many Layers
- A Data Set can have optionally many Data Sources
- A Data Set is made available by an Agent
- A Data Set is originally compiled by an Agent
- A Data Set may be a source of another Data Set
Data Source
Properties
| Name | If desired, a text name indicating a specific data source (otherwise one can infer that the name is shared with the data set) |
| URI | A URI giving the location of the data. If this is a W*S resource, the URI would be that of a GetCapabilities request to it. |
| Abstract | Any notes or other marginalia of interest regarding this data source |
| Format | If the Source is a service this would be, for example OGC:WMS or OGC:WCS. For files, this is a text identifier which follows as a guideline the output of gdalinfo. |
Relations
- A Data Source is an instance of exactly one Data Set
- A Data Source can be a component of another Data Source (e.g. a shapefile may also be one tile within a tile index
Layer
Vector data formats often provide multiple Layers of data as part of a data set. OGC Web Services also often provide multiple Layers through one service. This is useful metadata which it would be a shame to throw away.
Properties
| Name | The layer's name, free text |
| Abstract | A description of the contents of the layer, with any remarks of interest |
| Keywords | A layer may have none or many keywords associated with it. |
Relations
- A Data Set can have none or many Layers
(note - though we get information about layers through looking at a Data Source, they are related to the abstract Data Set, because the Layers on all the different Sources will be the same.
Agent
An Agent may be a person, an organisation, or a machine agent. This term derives from foaf:Agent, and is used in the same way as 'Principal' is used in security terms.
Properties
| Name | The name of the agent |
| A contact email address given as mailto:foo@example.com | |
| Description | More random details about the Agent |
| Location | A WGS84 lat-lon pair, or a URI indicating a near location |
Relations
- An Agent is the original provider of such-and-such a Data Set
- An Agent is the publisher of such-and-such a Data Set
- An Agent is the maintainer of such-and-such a Data Source
Namespace / Ontology
It is possible or advisable to extend many XML-based metadata carrier formats with namespaces which can provide semantics for different properties, taking a "mix-in" approach with the use of small vocabularies for different domains.
Thus DCLite4G attempts not to provide a full model for metadata for geographic information but to reuse properties from other well-known namespaces or ontologies - GeoRSS, Dublin Core, FOAF - and provide a subset of Dublin Core with extra rigour of expression suitable for better machine readability and reuse. This is also what is known as a Dublin Core Application Profile.
http://xmlns.com/2007/dclite4g/ is the namespace reserved for DCLite4G. It should and will come to contain an OWL ontology showing the structure, providing where possible mappings to various metadata schemas.
References
- Dublin Core lite for Geo
- OGC Catalog Services 2 Specification 6.3.3, Core returnable properties
- OGC ebRIM profile of CSW specification, Appendix B.5, Table B.3 - Slots defined in the Basic package
- iGeoResourceInfo class in uDig
- GeodataCommons Metadata Whitepaper
- Open FOSSGIS Community Response to INSPIRE Metadata Draft Implementing Rules