Storing XML encoded W3C PROV provenance information embedded in GML

Copyright © 2014 Open Geospatial Consortium. 49 prov:entity... xmp:source xmp:processStep prov:activity... xmp:processStep xmp:namePlatinum springxmp:name xmp:Spring NOTE This encoding does not follow the object-property alternated notation where the objects have names in upper camel case and properties in lower camel case. The reason for this is that W3C PROV XML encoding does not follow this in their application schema. Again, we can use the xlink mechanism. This mechanism allows referencing provenance descriptions in other document by using just an id avoiding unnecessary repetitions. xmp:Spring gml:id=ID_SPRING_2 xmp:source xlink:href=https:bob.opengeospatial.orgSpringDatasetW3CLineage.xml SC_USGS xmp:procesStep xlink:href=https:bob.opengeospatial.orgSpringDatasetW3CLineage.xml PS_WPS_1 xmp:position... xmp:nameGold springxmp:name xmp:Spring

10.3 Storing provenance at different levels

As presented in the Subsection 5.5, provenance has different levels of granularity and it can be recorded at dataset, feature and attribute levels. In this section, we describe these levels and some strategies to include provenance in each of them. The dataset level includes the process steps involved and acquires the information of the inputs and outputs of the complete conflation WPS process as whole input and output datasets following the ISO 19115 standard and encoded in an ISO19139 document related with the dataset as a whole. However some features have different provenance information that is more detailed that the provenance provided at the dataset level. In some cases, feature attributes can have their own specific provenance. Recording provenance at feature and attribute level requires a high quantity of memory and database space, and the feature and attribute metadata can many times be reiterative, duplicating several sources and processes descriptions of the provenance and other metadata properties out of scope of this document such as quality indicators. To solve this issue, this proposal exposes a solution to reduce the space required to record the metadata at the feature and attribute level, and diminish redundancies by means of the xlink XML attribute previously presented.

10.3.1 Dataset level

We recommend using a full ISO 19115 metadata record encoded in XML that will contain the provenance information at a dataset level. There are two ways of doing this: 50 Copyright © 2014 Open Geospatial Consortium. modify the GML application schema or use the deprecated metaDataProperty. In both cases, we can opt to include embed a full metadata record or to use xlink to link to an external metadata document that can be a file or a record in a metadata CSW catalogue.

10.3.1.1 Personalized application schema

To do this, we just need to include a MD_Metadata object as a property of the feature collection. element name=SpringCollection type=xmp:SpringCollectionType substitutionGroup=gml:AbstractFeature complexType name=SpringCollectionType complexContent extension base=gml:AbstractFeatureType sequence element name=metadata type=xmp:SpringISOMetadataPropertyType minOccurs=0 element name=provenance type=xmp:SpringW3CProvPropertyType minOccurs=0 element name=spring type=xmp:SpringPropertyType minOccurs=0 maxOccurs=unbounded sequence extension complexContent complexType ?xml version=1.0 encoding=UTF-8? xmp:SpringCollection gml:id=OWS-10Conflatedmap xmp:metadata xlink:href=https:portal.opengeospatial.orgwikipubOWS10OWS10CCIPr ovenanceSpringDatasetISOLineage.xml ... xmp:SpringCollection

10.3.1.2 Using metaDataProperty

In some cases we will not have the capability to modify the application schema. For instance because we are working with an external WFS or we are using a GML profile e.g. in the Gazetteer case. In this case there is no other way than use the deprecated metaDataProperty element as a feature collection level. ?xml version=1.0 encoding=UTF-8? xmp:SpringCollection gml:id=OWS-10Conflatedmap gml:metaDataProperty xlink:href=https:portal.opengeospatial.orgwikipubOWS10OWS10CCIPr ovenanceSpringDatasetISOLineage.xml ... xmp:SpringCollection