1. MEDIN Standards Workshop Standards / XML / Validation / Transformation / ESRI / Search

2. © HR Wallingford 2010 Page 2 Introduction Standards XML Schema and Validation −XSD Schema −Schematron Transformation −Stylesheets ESRI ArcGIS Search

3. © HR Wallingford 2010 Page 3 Standards ISO / TC 211 (de jure standards) ISO 19115 −Underlying content standard −Defines a logical model for metadata structure ISO 19139 −XML encoding standard −Implements the ISO 19115 logical model ESRI core (de facto industry standard?) −XML encoding −Implements the ISO 19115 logical model MEDIN INSPIRE UKGEMINI

4. XML

5. © HR Wallingford 2010 Page 5 XML Extensible Markup Language (XML) A metamarkup language The basic unit is called an element Apparently similar to HTML but… element value Element Attribute Opening tag Closing tag

6. © HR Wallingford 2010 Page 6 Metamarkup? What does metamarkup mean? There is no predefined and fixed set of tags for XML XML allows implementers to define their own set of tags to meet their needs Examples Office Open XML (ISO/IEC 29500) Geography Markup Language (ISO 19136)

7. © HR Wallingford 2010 Page 7 Markup – ESRI ArcGIS 10 XML Title 20110906

8. © HR Wallingford 2010 Page 8 Markup – ISO 19139 XML Title 2011-09-06 creation

9. © HR Wallingford 2010 Page 9 Well-Formed XML has strict rules, e.g.: There must be one, and only one root element All elements must have an opening and closing tag Element names are case sensitive: − is different from XML conforming to the rules is said to be well- formed

10. © HR Wallingford 2010 Page 10 Well-Formed Title 20110906 Title 20110906 Summary No closing tag Opening and closing tags are different Two root elements

11. © HR Wallingford 2010 Page 11 Structure The markup defines data structure: It signifies which elements are associated It can define semantics: It says nothing about how to display data (there are exceptions to this rule) 20110906

12. © HR Wallingford 2010 Page 12 XML is machine readable And… Human readable… honestly

13. © HR Wallingford 2010 Page 13

14. Schema and Validation

15. © HR Wallingford 2010 Page 15 Schema Schemas document the elements that are permitted in an XML application XML that conforms to a schema is said to be schema-valid XML that does not conform to a schema is said to be invalid XSD Schemas Schematron Schemas

16. © HR Wallingford 2010 Page 16 XML Schema Definition Language... <xs:element name="title" type="gco:CharacterString_PropertyType"/> <xs:element name="alternateTitle" type="gco:CharacterString_PropertyType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="date" type="gmd:CI_Date_PropertyType" maxOccurs="unbounded"/>...

17. © HR Wallingford 2010 Page 17 Markup – ISO 19139 XML Title 2011-09-06 creation

18. © HR Wallingford 2010 Page 18 Schematron Schematron is: A schema language for XML −Document Schema Definition Language (DSDL) Written in XML Uses XPath to encode assertions It’s an ISO Standard – ISO 19757-3 Find out more at: http://www.schematron.com/

19. © HR Wallingford 2010 Page 19 Why use Schematron? XSD schema is unable to test some constraints: The ability to specify a choice of attributes The ability to vary the content model based on the value of an element or attribute (this sort of constraint is common in the ISO 19115 logical model) Implementing profiles (e.g. MEDIN): With Schematron there’s no need to edit the underlying standardised XSD

20. © HR Wallingford 2010 Page 20

21. © HR Wallingford 2010 Page 21 What’s in a name? Schematron’s a funny name… It’s just a reaction to the common use of acronyms – MEDIN ;-) – according to the author, Rick Jelliffe It was originally to be called the Pink Schematron apparently −see http://www.xmlhack.com/read.php?item=121&v=1

22. © HR Wallingford 2010 Page 22 Validation Workflow XSD Schema ValidationSchematron Validation

23. © HR Wallingford 2010 Page 23 Validation Tools Select profile XSD Schema Schematron schemas

24. Transformation

25. © HR Wallingford 2010 Page 25 XSLT Extensible Stylesheet Language Transformations (XSLT) Specifies rules for transforming one XML instance into another XML instance The output XML instance will have a different structure from the input XML instance

26. © HR Wallingford 2010 Page 26 ESRI XML to MEDIN XML MEDIN XML must be follow the ISO 19139 XML encoding Users may wish to use other software to create and manage metadata (e.g. ESRI desktop GIS) ESRI software manages metadata using XML The XML does not following the ISO 19139 standard The XML can be transformed to ISO 19139 MEDIN provides resources to support this

27. © HR Wallingford 2010 Page 27 Stylesheet Tools

28. ESRI ArcGIS

29. © HR Wallingford 2010 Page 29 Versions ArcGIS 9 FGDC / ISO ArcGIS 10 ESRI Core Metadata Both use XML encoding The encodings are slightly different Why the change at version 10?

30. © HR Wallingford 2010 Page 30 ESRI ArcCatalog – Options

31. © HR Wallingford 2010 Page 31 ESRI ArcCatalog

32. © HR Wallingford 2010 Page 32 Transformation ArcGIS 9 Metadata ArcGIS 10 Metadata MEDIN Metadata Transformation e.g. Internal usee.g. External / Publish to DAC

33. © HR Wallingford 2010 Page 33 Transform Options Use MEDIN stylesheets ArcGIS 9 version ArcGIS 10 version Implementation Any XSL stylesheet processor (version1.0), e.g: −ArcGIS 9 or 10 ArcToolBox −Metadata Maestro

34. Search

35. © HR Wallingford 2010 Page 35

36. © HR Wallingford 2010 Page 36 Custom Search Applications CS-W Client – Metadata Maestro Version 2.0.2 of the OGC CS-W standard E.g. connect to GeoNetwork Opensource CS-W server instances Bespoke Search Applications Technology is readily available to support the building of XML search applications

37. © HR Wallingford 2010 Page 37 CS-W Search Client

38. © HR Wallingford 2010 Page 38 Bespoke Search Application

39. © HR Wallingford 2010 Page 39 Questions? Contact james.rapaport_at_seazone.com