MDWG Definitions OpenWork Ltd Byron Cochrane What we
MDWG Definitions OpenWork Ltd Byron Cochrane What we proposed Objective: Provide substantive information to use for future evidence base analysis as to the differences between existing applications of the ISO 19115-1 metadata standard in organisations. This will be used to resolve differences in application of this standard and provide guidance to future use. Tasks - Insert and Populate ISO 19115-1 definitions column on the Metadata Mappings Between Profiles table CKAN (data.gov.au) definitions column on the Metadata Mappings Between Profiles DCAT definitions column on the Metadata Mappings Between Profiles table
In parallel, ask participants for best and most complete examples of metadata records from each of the 3 organisations that have submitted ISO 19115-1 metadata to the Metadata Mappings Between Profiles table. For each of the 58 elements, we will create a table containing: ISO 19115-1 element definition real examples from each of the 3 above mentioned organisations of how the element is populated a cursory stoplight level assessment of the level agreement between organisations on use of each element Results to be compiled and shared with all participants for review and further analysis. As our focus was on alignment of definitions to gain mutual agreement on terminology and use, we have chosen not to address obligation and cardinality issues. We have limited in this report to those elements cited in Metadata Mappings Between Profiles_main 2.xlsx Notes and Variances
The ISO Definitions consist of 3 columns one that contains the path, one that contains the ISO definitions for each node in the path, and one that creates a summary definition of the element based on its location in the element path. This was done in order to add context to the element definitions in a transparent way. These definitions are sourced from the official AS/NZS standard document ASNZSISO19115.1-2015+A1.pdf Notes and Variances The data.gov.au elements (CKAN) are defined by two columns sourced from the Description and Vocab Control columns in the tables at https://toolkit.data.gov.au/index.php/Discovering _Metadata . Notes and Variances DCAT definitions are described using the latest
documentation from the W3C Dataset Exchange Working Group (DXWG) with two columns added DCAT def and Notes. These are sourced from https://w3c.github.io/dxwg/dcat/ and https:// github.com/w3c/dxwg/blob/gh -pages/DCAT-ISO19115-mapping.xlsx respectively Notes and Variances Due to lack of access to needed participants over the holidays, we used two rather than three ISO 19115-3 examples. From ABARES we used the test.xml from Evert supplied with his earlier documentation.
For GA, we randomly chose a ISO19115-3 record from their catalogue, Geomorphic features of the Antarctic and Southern Ocean 2012 http://www.ga.gov.au/metadata-gateway/metadata/record/102441. ?AADC records? We also include example metadata from data.gov.au which provides insight to how the metadata field mappings align between the two standards. Notes and Variances In the MDWG Definitions report spreadsheet, we included definitions supplied by ABARES from draftDataMetadataReqV0.4.xlsx definitions supplied by GA
GA Profile 19115_1 0.2 draft.pdf. MDWG element definitions.xlsx Column Names Package Element Path ISO definitions ISO definition summary Copied from Metadata Mappings Between Profiles_main 2.xlsx Copied from Metadata Mappings Between Profiles_main 2.xlsx The full ISO nested path to the element, expressed in CSS fashion using > for descendant elements, and + for sibling elements String of linked definitions in alignment with the ISO nested path A more human readable definition derived from the string of definitions in the ISO Definition field
ABARES Definition Copied from draftDataMetadataReqV0.4.xlsx supplied by Evert Bleys ABARES help Copied from draftDataMetadataReqV0.4.xlsx supplied by Evert Bleys GA Attribute Justification Copied from GA Profile 19115_1 0.2 draft.pdf GA Other Uses Copied from GA Profile 19115_1 0.2 draft.pdf Data.gov.au refs Sourced from https://toolkit.data.gov.au/index.php/Discovering_Metadata
Data.gov.au notes Sourced from https://toolkit.data.gov.au/index.php/Discovering_Metadata Sourced from https://w3c.github.io/dxwg/dcat/#Property:record_update_date DCAT Defs DCAT Notes Sourced from the spreadsheet DCAT-ISO19115-mapping.xlsx supplied by Nick Car ABARES Example Sourced from test.xml ISO 19115-3 record supplied for example by by Evert GA Example Sourced fromGeomorphic features of the Antarctic and Southern
Ocean 2012 - Data.gov.au example Sourced from https://w3c.github.io/dxwg/dcat/#Property:record_update_date OWL Notes Our comments on identified issues Identified issues Metadata Capture Resource information Resource Status not captured by GA What advice (if any) should we give about browse graphics? (later discussion)
Resource Point of Contact differences Need best practice for use of xlinks for this and other sections where xlinks are used especially in relation to DCAT linked data Organisation contact, individual in org contact, individual contact best practices? GA use of contactinstructions = 1 ? What does this mean? Is it only internal?
(applies to all GA CI_ResponsibleParty reccords in example metadata) Identified issues MD Capture Resource Info - cont Keyword section needs further discussion and recommendations developed Use Thesauri! Standard and recommended thesauri how to address in best practice Which ones?
Common location? How to use in schema? GA use of Published_External as a general keyword What is this? Looks likely to support identification of externally published records. If so, there are other tools available especially in GeoNetwork, but also in the standard Should we encourage this type of use of keywords or other fields? Can we identify best practice ways to separate Internal data management metadata from external metadata? GeoNetwork provides options.
Identified issues MD Capture Resource Info - cont Distribution GA incorrectly cites Geoscience Australia as format distributor. Should be mrd:MD_Distributor/mrd:distributorContact/cit:CI_Responsib ility/cit:party/cit:CI_Organisation/cit:name Digital transfer options undefined in GA example metadata Identified issues MD Capture Resource Info - cont
Extents ABARES record lacks gml namespace on date information on sample record Linage, Usage. Associated resource, Spatial Representation, Data Attribute definition Not populated in either example metadata record Need to review what we want to do with these in Best Practice terms Identified issues Metadata Capture Metadata
Best practice needed for identifiers and URL. Metadata constraints - Thin on metadata use constraints is this okay? Should we consider recommending point of truth dereferencable URIs (later discussion) ABARES Heavy reliance on generic MD_Constraints/mco:useLimitations Citation of General Public and AnyPosition under individual within organisation contact information
Cryptic X3 Licence type: Copyright Commonwealth of Australia 2018 entry under /mco:MD_LegalConstraints/mco:otherConstraints Vague reference codeListValue="copyright" under mco:MD_LegalConstraints/mco:releasability/mco:MD_Releasability/mco:disseminationConstraints GA - No metadata constraint info captured in example record Identified issues MD Capture Resource Info - cont Constraints ABARES cites Creative Commons under mco:otherConstraints instead of mco:MD_LegalContraints
A general discussion is needed about copyright, license and other legal constraints and where they apply. Special guidance with legal advice to draft is recommended General Issues Copyrights (DISCLAIMER I am not a lawyer!) Are primarily for Distributions or Collections Different distributions can have different copyright licence Facts cannot be copyrighted
There is a difference between copyright holders and copyright licence Creative commons is a licence granted by a copyright holder End user licence agreements are not licence in themselves but are a contract containing a grant a licence (which allows more restrictions than otherwise available under copyright) There are important copyright considerations inherent in provenance/lineage Legal advice would be advised to gain authoritative clarity General Issues
Metadata Identity Toolkit.data.gov.au Mappings Human Readable Name AGLS Map DCAT Map ANZLIC Map Identifier agls:fileIdentifier dcat:Dataset/dct:identifier MD_Metadata.fileIdentifier Identifier of resource (Dublin Core)
Definition: An unambiguous reference to the resource within a given context. Comment: Recommended best practice is to identify the resource by means of a string conforming to a formal identification system. Examples: Identifier="http://purl.oclc.org/metadata/dublin_core/" Identifier="0385424728" [ISBN] Identifier="H-A-X 5690B" [publisher number]
Identifier of dataset (CKAN) Unique identifier dataset has a unique URL which is customizable by the publisher. Identifier of Metadata record (ISO 19115) GeoNetwork allowance of URIs? Search A Shopping Experience Avoid immediate Buy trap Direct the shopper to find out more Move from general to detailed product information Pictures are useful Thumbnails Customise the experience to the product type
Jobs Cars Homes Geodata Statistical data One size / One box does not fit all / GOOGLE search box GN Default Summary CSW Result No Links Metadata UUID as Identifier 886fc989-406c-321c-0ad5-8dd185b72dabNZ Land DistrictsdatasetNew ZealandboundariesplanningCadastre
This layer provides Land District shapes and their name. A Land District is an administrative area that all titles and surveys were registered against prior to Landonline. It is required to uniquely identify survey and title records created prior to Landonline. Full request PyCSW (Mod) Summary CSW Added Link Metadata UUID 886fc989-406c-321c-0ad5-8dd185b72dabNZ Land DistrictsdatasetNew Zealandboundarieshttps://data.linz.govt.nz/layer/50785-nz-land-districts/
dct:references> 2012-01-28This layer provides Land District shapes and their name. A Land District is an administrative area that all titles and surveys were registered against prior to Landonline. It is required to uniquely identify survey and title records created prior to Landonline.-47.73 -175.5-34.0 General Issues Confusion often occurs in what is being described The Resource? A Distribution of the resource?
The Metadata describing the resource? Confusion as to what the metadata describes A data resource? A distribution of a data resource? General Issues Lineage What is important to capture here? Copyright considerations? (European copyright directive, GDPR) Tie-ins to FSDF The LINK? Workshop Topics 1. Review key elements and definitions 2. Identifiers
Data Pre-processing Data Pre-processing Example of Normalized Input Vector Input vector : (2 4 5 6 10 4)t Mean of vector : Standard deviation : Normalized vector : Mean of normalized vector is zero Standard deviation of normalized vector is...
Title IX of the Education Amendments of 1972 Rights Under Title IX Students, Faculty, and Staff have the right to: Be free from all types of sex discrimination including sexual misconduct, sexual harassment, and sexual violence Bring forward a complaint...
MITIE Group Plc. MONRASA (MANTENIMIENTOS Y MONTAJES RÍA DE AVILÉS S.A.) MSL SOFTWARE S.L. Münchner Volkshochschule GmbH. Municipal Organisation for Social Intervention & Health (DOKPY) Musgrave SuperValue Centra. Musikschule Muri-Gümligen. MUTUA EGARA. 50 Wholesale trade/durable goods. Niedersächsisches Landeskrankenhaus Tiefenbrunn
The draft of the NIST Big Data functional reference architecture (RA v.1.0) is available as M0226v8. Next Steps. Continue the editorial and alignment effort. Map generic Big Data use cases to RA. Map specific collected Big Data cases to RA....
Office 365 FastTrack Planning EngagementsGet paid to plan and make the right first impression. 3-day and 10-day Deployment Planning Services offerings and guidance now available for all Cloud Deployment Partners. Funds partners to assist the customer getting started with Office...