Presentation on theme: "Paper Overview Introduction to FISH and MIDAS MIDAS XML"— Presentation transcript:
1Paper OverviewIntroduction to FISH and MIDASMIDAS XMLHeritage Exchange ProtocolData Validation ToolConclusions
2Forum for Information Standards in Heritage: FISH and MIDASForum for Information Standards in Heritage:English HeritageThe National TrustThe Archaeology Data ServiceScottish and Welsh Royal CommissionsMany others…MIDAS: Monument Inventory Data StandardData standard used throughout UK for Monument InventoriesTen years development and useUsed for monuments and related information including:Related EventsRelated ReferencesCultural Heritage and Monument Management
3MIDAS XML and the FISH Toolkit Initiative by FISH to create interoperability ‘Toolkit’ for heritage professionals:XML schemataData ValidatorsExchange ProtocolsMIDAS XMLImproved version of MIDASFormalised StructureXML Encapsulated
4XML Technology Overview Open standard:Well used, well documented & well supportedText based:XML files are human-readable and logically organisedCan be viewed/editing using simple text editorDesigned for encapsulation and exchange:XML can contain one monument or entire HERDesigned for interoperabilityFormally structured:XML schema dictates structureStructural capabilities contribute to future development
5MIDAS XML Design Philosophy Keep it SimpleIdentify and standardise common componentsRe-use existing terminology wherever possibleKeep it Usable:Do not sacrifice usability to obtain pure semantic clarityMake it scalable, extensibleKeep it Loose:Flexible schema encourages useDo not enforce HER benchmarks with XML schema (do this by other means)Continue to tighten schema as sector’s use of XML matures
6MIDAS XML Overview Three primary schemata: Seven supporting schemata: MONUMENTSEVENTSREFERENCESeven supporting schemata:Craft: watercraft and aircraft annexArtefact: small find and artefactsActor: all people and groupsMeta: metadata structureSpatial: GIS and place-related informationTemporal: time and datesCommon: elements common to MIDASCasework: Monument maintenance and status
10Mobile: use to exchange geographic data for single spatial feature. Spatial Schema…Consolidated: records Address, Placename, Geographic (GIS), and map data in a single element setUniversal: common element used in monument, event and casework schemataVersatile: geography node can be used to record all spatial aspects of a monument, including monument location, scheduled area, ownership and land use.Shapely: Can be used to represent monuments/events as points, lines or polygons.Mobile: use to exchange geographic data for single spatial feature.Standard: Based on OGC (Open Geographic Consortium) and CRMVendor-Neutral: GIS platform independent
11Historic Environment Exchange Protocol Designed to facilitate and formalise communication and data exchange between two Heritage Services using MIDAS XMLProtocol Document: text document that uses a very formal, specific language. It does not cover implementation of a HER Service, but only the communication between Services.Schemata: The HEEP relies on MIDAS XML for the exchange of data, but has its own schemas for inter-Service querying and communication.The protocol is not a working application, but rather a set of rules that developers can use to create another major toolkit component.
12What can the HEEP do?Archive Updates: a local service can automatically update itself at weekly intervals with data from a national serviceData Synchronisation: two national research framework projects studying sites with rock art, one in North England, one in Scotland, can synchronise their data with a central database of UK rock art.Transparent querying and Linking: a user viewing a webpage of an historic building will be shown a list of hyperlinks on nearby ancient monumentsAmalgamation: a user running an ‘Ancient Britain’ website writes an application which collects and gathers all information from the NMR, RCHMS, and CADW relating to henge monuments.
13REQUESTS: CAPABILITIES EXCEPTIONS HEEP Schemata Structure of queries that are sent to a HEEP ServiceCAPABILITIESHow HEEP Services report their capabilities (what data they hold and what they can do with it)EXCEPTIONSHow HEEP Services report errors
14Data Validation Tool: Overview Validates the contents of MIDAS XML documents against formal wordlists and thesauriProvides a level of content control that XML schema cannot matchCore ComponentsPHP Code: the magic that makes it happenDocumentation: explains the code and how to use itDatabase Configuration: one database contains HER Benchmark configurations, the other contains the configurations for the DVT application itself.
15Data Validation Tool: How it Works XML document is uploaded to the DVT validatorThe document is parsed, and the number of monuments, events, etc. within the document are countedThe system looks up the rules and rulesets required for the requested benchmarkEach monument/event/reference is validated against rules and rulesetsThe monument (event, etc.) fails if any rules or rulesets failThe XML document fails if any of the monuments it contains failResults of the validation are returned to the user
16Data Validation Tool: results Rule nameValue(s) in brackets(rule failed)Rule SetRecord result
17Data Validation Tool: Network Overview The DVT can run on one or more machinesThe DVT can use one or more INSCRIPTION databasesThe current system:One possible system:DVT at OAD+DVT and INSCRIPTION onOAD’s Development ServerInternetEH ThesauriNT and ALGAO lists*The DVT is completely separated from the resources it uses for validationRCHMS thesauri
18Data Validation Tool Summary Validates content as well as structureCan connect and validate against any online thesaurus or wordlistIs extensible, customisable and can be regionalisedProvides formal mechanism for producing ‘seal of approval’Can enrich data after validating:Translate coordinate and long/lat from grid referenceSupply preferred terms
19Final Conclusions on the Toolkit I18n: International in scopeModular: complete separating of tools from data and applicationWeb Service based: platform and OS independentUse through Usability: aim of FISH is to promote standards use and adoption through the provision of professional, desired, usable and well-considered information tools.
20http://www.fish-forum.info Tyler Bell: firstname.lastname@example.org Andrew Larcombe:Yegor Veter: