GEA CoP DRM

1. GEA CoP DRM Briefing for July 13 Meeting with Andy Hoskinson This is a DRAFT FOR COMMENT Please send comments to kurtb@imagemattersllc.com

2. Agenda • GEA CoP WG Overview • Geospatial Profile Outline • DRM Guidance: Outline • Discussion

3. GEA CoP WG Overview: Purpose • Encourage communication between organizational geospatial professionals, IT / CIO offices, and business program managers / specialists across agencies at various levels of government • Examine and promote awareness of existing current EA practices, with focus on how geospatial data and services are being addressed in accomplishing EA needs for different lines of business within different government organizations • Leverage successful EA work to date to advance the development of Geospatial Enterprise Architecture Profile documentation that identifies and provides insight on best practices that should be employed when advancing EA • Identify and pursue opportunities to validate documented Geospatial Profile best practices through demonstration pilots against selected inter-organizational business use cases • Identify opportunities to leverage investments by fortifying and sharing common geospatial services across all levels of government

4. GEA CoP WG Overview: Scope • The GEA COP Working Group’s efforts are specific to the development and advancement of a national Geospatial Profile for enterprise architecture. • This Geospatial Profile is a cross-cutting guidance document that advises the development of consistent EA Reference Models useful to all levels of government but also in support of the Federal Enterprise Architecture (FEA). • The efforts of this working group are complimentary to the work of the Office of Management and Budget in advancing the Federal Enterprise Architecture of the Federal Geographic Data Committee in advancing the NSDI, and in local, regional, and state initiatives on business process engineering.

5. GEA CoP WG Overview: Responsibility • Build consensus on common terminology, concepts, and scope of efforts • Leverage the good work that has been done into an efficient inter-organizational EA approach that recognizes the geospatial perspective • Solicit, synthesize, and promote existing geospatial EA contributions from interested contributing organizations • Map existing geospatial concepts, standards, and practices into general EA Reference Models and the FEA through a Geospatial Profile document and supportive documentation. Provide updates to FEA Reference Models as appropriate. • Validate the integrity of the developed Geospatial Profile through pilot demonstrations of selected inter-organizational EA use cases identified and agreed upon by the this working group. • Assure reporting of activities, deliverables, issues and recommendations to all Working Group participants, the AIC to the CIO Council, the FGDC Steering Committee, and OMB.

6. Introduction Background Scope Audience Existing policy and drivers (legislation, exec orders, ...) Objectives Geospatial Basics Cross-cutting nature of geospatial Common Scenario Terminology Geospatial Capabilities in the FEA Reference Models How geospatial interacts with the various RMs Business Reference Model Performance Reference Model Service Reference Model Technical Reference Model Data Reference Model Relationship to other FEA profiles Application of this Profile Common scenario and related use cases Examples Appendix A: References Appendix B: Acronym List Appendix C: Terminology (Glossary) Geospatial Profile Outline

7. DRM Guidance: Outline • Scope and Purpose • FEA DRM Introduction and Overview • NSDI Introduction and Overview • FEA DRM/NSDI Interoperability and Integration Methodology • Recommended DRM Authoring Practices and Procedures • Listing of Data Related Standards and Specifications

8. DRM Guidance: Outline Scope and Purpose • Guidance to EA authors regarding geospatial data • Purpose to align with FEA DRM while retaining the effort of the geospatial community over many years

9. DRM Guidance: Outline FEA DRM Introduction and Overview • Context • Discovery • Exchange

10. DRM Guidance: Outline NSDI Introduction and Overview • Content Standard for Digital Geospatial Metadata • ISO 19115 • ISO 19139 • Geospatial-One Stop Portal • ISO 23950 • CSW 2.0 (as related to data) • WMS/WFS/WCS (as related to data) • Framework Content Standards

11. DRM Guidance: Outline FEA DRM/NSDI Interoperability and Integration Methodology • Single Pointer to Geospatial One Stop • Agency Holdings Referenced by FGDC Metadata

12. DRM Guidance: Outline Recommended DRM Authoring Practices and Procedures • TBD Content

13. DRM Guidance: Outline Listing of Data Related Standards and Specifications • The listing should be complete with information in support of decision-making. We must help EA authors decide which standards to reference and supplying a list with descriptions and recommended use statements will help tremendously. • Content Standards/Specifications • Exchange Standards/Specifications • Encodings and Format Standards/Specifications

14. Discussion FEA DRM/NSDI Interoperability and Integration Methodology FEA DRM Schema

15. Extract could be a harvest that invokes XSL transform on the NSDI metadata record FEA DRM Context NSDI Context DRM Registry DRM Record Contains an extract of the NSDI metadata record NSDI Catalog Data Metadata Record Metadata Record Metadata Record 1. FEA DRM/NSDI Interoperability and Integration Methodology • Option 1: Single Pointer to NSDI • One DRM Registry record that points to NSDI Catalog • Option 2: Agency Holdings Referenced by DRM • DRM Registry records point to NSDI records

16. 2. FEA DRM Schema Discussion (1) • drm:GeospatialEnabled • “A boolean flag indicating whether or not a particular data asset supports or provides Geospatial data.” • What does this mean? What requirement(s) does this element address? • “This is geospatial data” • “This data be portrayed geospatially” • Other • ddms:geospatialCoverage • “Geographic place names or coordinates that relate to the resource, such as a jurisdiction, point, area, or volume on land, in space, or at sea. This element can contain either a Facility element or Place element, but not both. This element is reused from the Department of Defense (DoD) Discovery Metadata Specification (DDMS) v. 1.2.” • Can be associated with either Resource, DataAsset, or ExchangePackage • Resource: “Encapsulates a single "page view" of unstructured or semi-structured data, referenceable via a URI. This element aggregates numerous sub-elements, mostly metadata tags reused from the Dublin Core 1.1 set.” • DataAsset: “An aggregated, managed container. A database, system, application, or other electronic entity that produces and/or houses data.” • ExchangePackage: “A description of a specific information exchange between organizations.” • What are the semantics of these associations and where is this described? What requirement(s) does this element address?

17. 2. FEA DRM Schema Discussion (2) • ISO 19115/19139 has concepts of: • Extent—contains information about the geographic, temporal, and the vertical extent of the referring entity. • The geographic extent can be a bounding polygon, a bounding box, or a geographic description • Geographic description is mean to refer to named places according to some authority (such as a gazetteer) • Address—found within the contact information of the responsible party (can be individual or organizational)