And the Forum for Information Standards Toolkit MIDAS XML Paper Overview n Introduction to FISH and MIDAS n MIDAS XML n Heritage Exchange Protocol n Data

and the Forum for Information Standards Toolkitand the Forum for Information Standards Toolkit

MIDAS XMLMIDAS XML

Paper OverviewPaper Overview

Introduction to FISH and MIDASIntroduction to FISH and MIDAS

MIDAS XMLMIDAS XML

Heritage Exchange ProtocolHeritage Exchange Protocol

Data Validation ToolData Validation Tool

ConclusionsConclusions


MIDAS XMLMIDAS XML

FISH and MIDASFISH and MIDAS

Forum for Information Standards in Heritage:Forum for Information Standards in Heritage: English HeritageEnglish Heritage The National TrustThe National Trust The Archaeology Data ServiceThe Archaeology Data Service Scottish and Welsh Royal CommissionsScottish and Welsh Royal Commissions Many others…Many others…

MIDAS: Monument Inventory Data Standard MIDAS: Monument Inventory Data Standard Data standard used throughout UK for Monument InventoriesData standard used throughout UK for Monument Inventories Ten years development and useTen years development and use Used for monuments and related information including:Used for monuments and related information including:

Related Events Related References Cultural Heritage and Monument Management


MIDAS XMLMIDAS XML

FISH Toolkit:FISH Toolkit: Initiative by FISH to create interoperability ‘Toolkit’ for Initiative by FISH to create interoperability ‘Toolkit’ for

heritage professionals:heritage professionals: XML schemata Data Validators Exchange Protocols

MIDAS XMLMIDAS XML Improved version of MIDASImproved version of MIDAS Formalised StructureFormalised Structure XML EncapsulatedXML Encapsulated

MIDAS XML and the FISH ToolkitMIDAS XML and the FISH Toolkit


MIDAS XMLMIDAS XML

XML Technology OverviewXML Technology Overview Open standard: Open standard:

Well used, well documented & well supportedWell used, well documented & well supported

Text based:Text based: XML files are human-readable and logically organisedXML files are human-readable and logically organised Can be viewed/editing using simple text editorCan be viewed/editing using simple text editor

Designed for encapsulation and exchange:Designed for encapsulation and exchange: XML can contain one monument or entire HERXML can contain one monument or entire HER Designed for interoperabilityDesigned for interoperability

Formally structured:Formally structured: XML schema dictates structureXML schema dictates structure Structural capabilities contribute to future developmentStructural capabilities contribute to future development


MIDAS XMLMIDAS XML

MIDAS XML Design PhilosophyMIDAS XML Design Philosophy Keep it SimpleKeep it Simple

Identify and standardise common componentsIdentify and standardise common components Re-use existing terminology wherever possibleRe-use existing terminology wherever possible

Keep it Usable:Keep it Usable:

• Do not sacrifice usability to obtain pure semantic clarityDo not sacrifice usability to obtain pure semantic clarity

• Make it scalable, extensibleMake it scalable, extensible

Keep it Loose:Keep it Loose:

• Flexible schema encourages useFlexible schema encourages use

• Do not enforce HER benchmarks with XML schema (do this by other Do not enforce HER benchmarks with XML schema (do this by other means)means)

• Continue to tighten schema as sector’s use of XML maturesContinue to tighten schema as sector’s use of XML matures


MIDAS XMLMIDAS XML

Three primary schemata:Three primary schemata:

MONUMENTSMONUMENTS

EVENTSEVENTS

REFERENCEREFERENCE

Seven supporting schemata:Seven supporting schemata:

CraftCraft:: watercraft and aircraft annexwatercraft and aircraft annex

ArtefactArtefact: : small find and artefactssmall find and artefacts

ActorActor: : all people and groupsall people and groups

MetaMeta: : metadata structuremetadata structure

SpatialSpatial: : GIS and place-related informationGIS and place-related information

TemporalTemporal: : time and datestime and dates

CommonCommon: : elements common to MIDASelements common to MIDAS

CaseworkCasework: Monument maintenance and status: Monument maintenance and status

MIDAS XML OverviewMIDAS XML Overview


MIDAS XMLMIDAS XML

The MONUMENT structureThe MONUMENT structure


MIDAS XMLMIDAS XML

The EVENT structureThe EVENT structure


MIDAS XMLMIDAS XML

The REFERENCE structureThe REFERENCE structure


MIDAS XMLMIDAS XML

Spatial Schema…Spatial Schema…

• Consolidated: Consolidated: records Address, Placename, Geographic (GIS), and map records Address, Placename, Geographic (GIS), and map data in a single element setdata in a single element set

• Universal: Universal: common element used in monument, event and casework common element used in monument, event and casework schemataschemata

• Versatile: Versatile: geography node can be used to record all spatial aspects of a geography node can be used to record all spatial aspects of a monument, including monument location, scheduled area, ownership and monument, including monument location, scheduled area, ownership and

land use.land use.

• Shapely: Shapely: Can be used to represent monuments/events as points, lines or Can be used to represent monuments/events as points, lines or polygons.polygons.

• Mobile: Mobile: use to exchange geographic data for single spatial feature.use to exchange geographic data for single spatial feature.

• Standard: Standard: Based on OGC (Open Geographic Consortium) and CRM Based on OGC (Open Geographic Consortium) and CRM

• Vendor-Neutral: Vendor-Neutral: GIS platform independentGIS platform independent


MIDAS XMLMIDAS XML

Designed to facilitate and formalise communication and data Designed to facilitate and formalise communication and data exchange between two Heritage Services using MIDAS XMLexchange between two Heritage Services using MIDAS XML

Protocol Document:Protocol Document:text document that uses a very formal, specific language. It does not text document that uses a very formal, specific language. It does not cover implementation of a HER Service, but only the communication cover implementation of a HER Service, but only the communication between Services.between Services.

Schemata:Schemata:The HEEP relies on MIDAS XML for the exchange of data, but has its The HEEP relies on MIDAS XML for the exchange of data, but has its own schemas for inter-Service querying and communication.own schemas for inter-Service querying and communication.

The protocol is not a working application, but rather a set of rules that The protocol is not a working application, but rather a set of rules that developers can use to create another major toolkit component.developers can use to create another major toolkit component.

Historic Environment Exchange ProtocolHistoric Environment Exchange Protocol


MIDAS XMLMIDAS XML

1. Archive Updates: a local service can automatically update itself at a local service can automatically update itself at weekly intervals with data from a national serviceweekly intervals with data from a national service

2. Data Synchronisation: two national research framework projects two national research framework projects studying sites with rock art, one in North England, one in Scotland, can studying sites with rock art, one in North England, one in Scotland, can synchronise their data with a central database of UK rock art.synchronise their data with a central database of UK rock art.

3. Transparent querying and Linking: a user viewing a webpage of an a user viewing a webpage of an historic building will be shown a list of hyperlinks on nearby ancient historic building will be shown a list of hyperlinks on nearby ancient monuments monuments

4. Amalgamation: a user running an ‘Ancient Britain’ website writes an a user running an ‘Ancient Britain’ website writes an application which collects and gathers all information from the NMR, application which collects and gathers all information from the NMR, RCHMS, and CADW relating to henge monuments.RCHMS, and CADW relating to henge monuments.

What can the HEEP do?What can the HEEP do?


MIDAS XMLMIDAS XML

REQUESTS: REQUESTS: Structure of queries that are sent to a HEEP ServiceStructure of queries that are sent to a HEEP Service

CAPABILITIESCAPABILITIESHow HEEP Services report their capabilities (what data they hold How HEEP Services report their capabilities (what data they hold and what they can do with it)and what they can do with it)

EXCEPTIONSEXCEPTIONSHow HEEP Services report errorsHow HEEP Services report errors

HEEP SchemataHEEP Schemata


MIDAS XMLMIDAS XML

Validates the contents of MIDAS XML documents against Validates the contents of MIDAS XML documents against formal wordlists and thesauriformal wordlists and thesauri

Provides a level of content control that XML schema cannot Provides a level of content control that XML schema cannot match match

Core ComponentsCore Components PHP Code: PHP Code: the magic that makes it happenthe magic that makes it happen Documentation: Documentation: explains the code and how to use it explains the code and how to use it Database Configuration: Database Configuration: one database contains HER one database contains HER

Benchmark configurations, the other contains the configurations for the Benchmark configurations, the other contains the configurations for the DVT application itself.DVT application itself.

Data Validation Tool: OverviewData Validation Tool: Overview


MIDAS XMLMIDAS XML

Data Validation Tool: How it WorksData Validation Tool: How it Works

1.1. XML document is uploaded to the DVT validatorXML document is uploaded to the DVT validator

2.2. The document is parsed, and the number of monuments, events, The document is parsed, and the number of monuments, events, etc. within the document are countedetc. within the document are counted

3.3. The system looks up the rules and rulesets required for the The system looks up the rules and rulesets required for the requested benchmarkrequested benchmark

4.4. Each monument/event/reference is validated against rules and Each monument/event/reference is validated against rules and rulesetsrulesets

5.5. The monument (event, etc.) fails if any rules or rulesets failThe monument (event, etc.) fails if any rules or rulesets fail

6.6. The XML document fails if any of the monuments it contains failThe XML document fails if any of the monuments it contains fail

7.7. Results of the validation are returned to the userResults of the validation are returned to the user


MIDAS XMLMIDAS XML

Data Validation Tool: resultsData Validation Tool: results

Rule name

(rule failed)

Value(s) in brackets

Rule Set

Record result


MIDAS XMLMIDAS XML

Data Validation Tool: Network OverviewData Validation Tool: Network Overview

•The DVT can run on one or more machines•The DVT can use one or more INSCRIPTION databases

The current system:

DVT and INSCRIPTION on OAD’s Development Server

One possible system:

DVT at OAD

EH Thesauri NT and ALGAO lists

RCHMS thesauri

+

Internet

*The DVT is completely separated from the resources it uses for validation


MIDAS XMLMIDAS XML

Data Validation Tool SummaryData Validation Tool Summary

Validates content as well as structureValidates content as well as structure

Can connect and validate against any online thesaurus or wordlistCan connect and validate against any online thesaurus or wordlist

Is extensible, customisable and can be regionalisedIs extensible, customisable and can be regionalised

Provides formal mechanism for producing ‘seal of approval’Provides formal mechanism for producing ‘seal of approval’

Can enrich data after validating: Can enrich data after validating: Translate coordinate and long/lat from grid referenceTranslate coordinate and long/lat from grid reference Supply preferred terms Supply preferred terms


MIDAS XMLMIDAS XML

Final Conclusions on the ToolkitFinal Conclusions on the Toolkit

I18n: I18n: International in scopeInternational in scope

Modular: Modular: complete separating of tools from data and complete separating of tools from data and applicationapplication

Web Service based: Web Service based: platform and OS independentplatform and OS independent

Use through Usability: Use through Usability: aim of FISH is to promote standards aim of FISH is to promote standards use and adoption through the provision of professional, desired, use and adoption through the provision of professional, desired, usable and well-considered information tools.usable and well-considered information tools.


MIDAS XMLMIDAS XML

http://www.fish-forum.infohttp://www.fish-forum.info

Tyler Bell: [email protected] Bell: [email protected] Larcombe: [email protected] Larcombe: [email protected] Veter: [email protected] Veter: [email protected]

Documents

And the Forum for Information Standards Toolkit MIDAS XML Paper Overview n Introduction to FISH and MIDAS n MIDAS XML n Heritage Exchange Protocol n Data