10. Table Title Papers of John Ruskin Dates 1864-1888 Extent 10 boxes Held At University of London Library
11.
12.
13.
14.
15.
16.
17.
18.
19.
20. What about display? XML file DTD or Schema Valid XML Blue Elephant Papers …………………… ………… Blue Elephant Papers Browse List
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
Notas do Editor
Contents of this section
Can be helpful when thinking about using XML to remember that it is just a means to mark up content. You then need to do stuff with the content – there are plenty of tools out there for this.
XML syntax is quite straightforward – elements are commonly just content wrapped in opening and closing tags.
Attributes enable you to add further information to refine your basic tagged content. Think of the language, for example, as the basic content; the attribute adds information about the encoded version (standards compliant code). The normal attribute in archives is used for date searching – meaning ‘ normalised ’ date.
XML rules can introduce some information about content, but you should think of XML primarily as a means to structure data.
Here is a very simple sample record.
This is the sample data wrapped in tags so that each part of the content is given meaning so that it is easier to machine process. E.g. search just for <title> content, or display just <title> and <date> content.
Well-formed applies to XML generally; ‘Valid’ applies to XML conforming to the specific rules you are following – in our case for EAD.
There are DTDs or Schemas for a huge range of data types.
Many archivists using EAD still use the DTD. Moving to the schema is not entirely straightforward.
The note element is said to be of a complex type because it contains other elements. The other elements (to, from, heading, body) are said to be simple types because they do not contain other elements. Rather than defining the data type ‘ string ’ you could have a date or time or integer.
Archivists generally don’t need to concern themselves with the more technical aspects of XML tools, although it can be useful to have some idea of what you can do. The DOM (an API) represents a tree view of an XML document - a programmer can create an XML document, navigate its structure, and add, modify, or delete its elements. the objective for the XML DOM has been to provide a standard programming interface to a wide variety of applications. SAX (an API) is also an option for analysing and extracting information XForms use XML to create forms on the Web Xlink, Xpointer – ability to link XML documents API - The interface (calling convention) by which an application program accesses a service
Once you have XML, you can use a stylesheet (XSLT) to create (X)HTMLoutput to display your description in a browser. You can also output other formats, such as PDF or text.
Some people get confused between HTML and XML. HTML is for display of data – it is not readily machine processable because it does not mark data up in meaningful ways, e.g. it does not identify the title, date, extent, access conditions, etc. XML does not carry information about how to display it. Remember, the tags are invented by the author.