Xml Overview

1. XML for Catalogers in 2009: Emerging Technologies, Tools, and Trends Kevin Reiss [email_address] Systems Librarian Office of Library Services City University of New York AJL-NYMA's 2009 Cataloging Workshop 4/22/2009

3. XML and MARC

4. XML Formats

5. Usage Scenarios

6. XML Tools

7. Experimentation & Questions

9. Give a basic understanding of XML syntax

10. Put in XML in the context of library, specifically cataloging, work

11. Highlight usage scenarios for XML

12. Discuss tools for editing XML

16. Literary Texts ( TEI )

19. XML is: The best data format we have to deal with this issue at the moment since MARC, in some respects, is becoming a liability where modern software is concerned.

21. Human-readable

22. Platform Independent

23. Verbose

24. Unicode-compliant

25. Used in data-centric applications

26. Used in document-centric applications

27. Editable by any editor that can handle plain-text files

29. Machine-readable semantic data

32. Nested Tags

33. Quoted attributes

35. Similar Display/Different Approaches

37. Which of the previous code snippets succeeds?

40. ISBD Punctuation

43. Individual XML documents are “instances”

44. Documents must adhere to a nested hierarchy

45. Start with an option XML declaration

47. Declares the character set

49. All other elements nest within this one

50. For example every XHTML Document has only one “<html>” Tag

51. Start <tag>

52. End </tag>

53. Web Page Source

55. Can contain other elements and text

56. Must have a <start> and </end> tag

57. Sometimes elements are “empty”

59. The image <img src=”mypicture.jpeg”/> element in XHTML is a good example

60. Elements in MODS <subject xmlns:xlink = "http://www.w3.org/1999/xlink" authority = "lcsh" > <topic> City and town life </topic> <topic> Fiction </topic> </subject>

62. Must be quoted ex; myattribute=”my attribute content”

63. Order is not important when attached to a given element

66. > - >

67. < - <

68. ' - '

70. Authoring software should escape these for you

72. Most web browsers are XML parsers

74. Validation - “strict checking”

75. Validation happens when the instance adheres to the rules defined in a specific Schema

78. Nested Data

79. Attribute syntax

81. Test this with your web browser

82. Well-formed XML Document

85. Validity is enforced by a “schema” that defines a particular XML application

88. Patterns, i.e. dates, MARCXML leader field

90. Could be called “strict checking”

91. Most major XML applications have some sort of schema

92. Data or document modeling work is done here

93. A schema supports “guided” editing

95. Data migration

98. Expressed in XML

100. Expressed in XML or non-XML

101. Guided Editing using Oxygen

103. MARC Leader Field validation rule [ ]{5}[A-Za-z ]{1}[A-Za-z]{1}[A-Za-z ]{3}(2| )(2| )[ ]{5}[A-Za-z ]{3}(4500| )

108. Many of you already do, see OCLC Connexion

110. Parser and schema carry out data-checking for you

111. Very easy to manipulate for programmers

112. Multi-language support via Unicode

114. Consists of nodes

115. Sample Instance

116. Document Parsed as a Tree

119. list = xml->GetAllElements(“genre”)

122. XML Transformations (XSLT)

123. Xlink (Linking within XML documents)

127. W3C Standard

128. Written in XML

130. Another text format (.csv, .txt)

131. Most commonly takes XML to XHTML

133. Language => 546

134. Publisher => 260

137. MARCXML -> MODS

138. MARCXML -> Dublin Core

139. MARCXML -> HTML

141. Can MARC and XML Co-Exist? I find it telling that the first step to designing any system around data currently in MARC, is that I have to take the data out of MARC, correct it for inconsistencies, massage it to make it more straightforward — just so that the information is useful within non-library systems. Terry Reese - 2007 Creator of MarcEdit

143. A very large part of the collective intellectual effort of our profession

144. Most modern software uses design paradigms far different than that of MARC

145. Not very interoperable outside of OCLC/ILS land

146. A factor in isolating library data

147. Supported by only a small number of software tools

148. 02805cam 2200589 450000100070000000500170000700800410002403500210006590600450008601000170013104000420014804300120019005000230020205101140022505101580033905100850049705101080058205101230069005100830081305101060089608200130100210000300101524500310104526000370107630000500111350000250116350000300118850000340121850000600125265000330131265100310134565000290137665000250140565000220143065500330145265500280148565500280151371000610154195200310160295200630163398500360169698500350173299100680176799100510183599100480188699100500193499100510198499100510203599100500208699100500213609900290218627430020010920145828.0891030s1934 nyuag 000 1 eng 9(DLC) 34002348 a7bcbccorignewd1eocipf19gy-gencatlg a 34002348 aDLCcDLCdDLCdOCoLCdDLCdOCoLCdDLC ae-ie---00aPR6019.O9bU4 1934 aPR6019.O9bU4 1934bcAnother impression. "Second printing, January 1934"--P. [v]. Copyright deposit (#70193). aMicrofilmb75965 PRcMicrofilm of preceding impression. Washington, D.C. : Library of Congress, Photoduplication Service, 1979. 1 microfilm reel ; 35 mm. aPR6019.O9bU4 1934ccAnother impression. "Fourth printing, January 1934"--P. [v] aPR6019.O9bU4 1934c Copy 2cCopy 2 of the preceding impression. Gift of Willard L. Hart, Mar. 17, 1952. aPR6019.O9bU4 1934dcAnother impression. "Fifth printing, February 1934--P. [v] Purchase, Mar. 20, 1934 (DLC #452310). aPR6019.O9bU4 1934ecAnother impression. "Seventh printing, Nov. 1934"--P. [v] aPR6019.ObU4 1934e Copy 2cCopy 2 of the preceding impression. Purchase, Feb. 25, 1936 (DLC #494329).00a823/.9121 aJoyce, James,d1882-1941.10aUlyssesc[by] James Joyce. a[New York,bRandom house,c1934] axvii, 767, [1] p.billus. (music)c21 1/2 cm. aTitle on two leaves. a"First American edition." aLC copy has dust jacket.5DLC aSource: Gift of Herman Finkelstein, Dec. 30, 1980.5DLC 0aCity and town lifevFiction. 0aDublin (Ireland)vFiction. 0aMarried peoplevFiction. 0aJewish menvFiction. 0aArtistsvFiction. 7aPsychological fiction.2lcsh 7aDomestic fiction.2lcsh 7aEpic literature.2gsafd2 aHerman Finkelstein Collection (Library of Congress)5DLC aForm AACR 2: vj05 04-26-89 aCopy 1 of 4th printing missing in inventory: vj05 04-26-89 ararebk/finkerbcfqr05 02-19-93 ararebk/rbcerbcfqr05 02-19-93 bc-RareBookhPR6019.O9iU4 1934tCopy 1mFinkelstein CollwBOOKS bc-RareBookhPR6019.O9iU4 1934btCopy 1wBOOKS bc-MicRRhMicrofilmi75965 PRtCopy 1wBOOKS bc-GenCollhPR6019.O9iU4 1934ctCopy 1wBOOKS bc-RareBookhPR6019.O9iU4 1934ctCopy 2wBOOKS bc-RareBookhPR6019.O9iU4 1934dtCopy 1wBOOKS bc-GenCollhPR6019.O9iU4 1934etCopy 1wBOOKS bc-RareBookhPR6019.OiU4 1934etCopy 2wBOOKS ajoyce-ulysses-1072275128 From Another Computing Era

149. MARC | MARCXML

150. Meaningful Output in Browser

152. Utilize Perl Programming to parse MARC to MARCXML

153. PHP also has a MARC library

154. These have internal crosswalks that produce a MARCXML representation

155. MARC => MARCXML <datafield tag = "245" ind1 = "1" ind2 = "0" > <subfield code = "a" > Ulysses </subfield> <subfield code = "c" > [by] James Joyce. </subfield> </datafield> <datafield tag = "260" ind1 = " " ind2 = " " > <subfield code = "a" > [New York, </subfield> <subfield code = "b" > Random house, </subfield> <subfield code = "c" > 1934] </subfield> </datafield>

157. MARCXMLifying this isn't necessarily going to help make this more easily digestible to a piece of software

158. MARCXML essentially maintains MARC as it is and puts it into a parsable XML wrapper

161. TEI

162. XHTML

163. RSS/ Atom

164. RDF

166. Spreadsheet export formats

167. Metadata

169. Mixed content

172. Institutional Repositories

175. 15 basic elements

177. Publisher =

179. Default format for the OAI-PMH Protocol for Metadata Harvesting

181. Archival Findings Aids

182. One of the oldest XML formats

183. Straddles the data and document-centric worlds

184. Crosswalks available in MarcEdit and other places

186. Designed to encode any kind of text

187. Humanities Computing Initiative

188. Support in the special collections community

189. Intellectually rich XML application

191. Detailed linguistic analysis

193. HTML that confirms to XML rules

194. Has become ubiquitous on the web

198. An instance of RSS is known as a feed

199. Users can subscribe to a particular RSS feed

200. New additions to the feed are pushed out

201. RSS feeds are easily incorporate into webpages

202. Most web portals (i.e. your yahoo, or google account are built around RSS feeds)

203. In a catalog

204. RSS within a Catalog

206. RSS can be used an export protocol to a repository, i.e. turn something into connexion for a institutional repositories

207. Any content creation tool could send items to a repository

208. SWORD (Simple Web-service Offering Repository Deposit)

209. Uses Atom, an RSS dialect to accomplish this

210. http://www.swordapp.org/

212. Semantic Web Technology

213. Linked Data using URI(L)s

214. Machine Readable semantics a level above what XML provides

215. RDF fragment of Project Gutenberg data

216. Sample RDF Assertion describing a Person taken from RDF Primer

218. XML versions of RDA will likely be produced in RDF

220. RDA in RDF/XML

222. Data processing (ILS go-between)

223. Crosswalks (MARCXML=>All of the Above)

224. Metadata Harvesting (OAI-PMH)

225. Full-text Indexing

226. AJAX – XML Behind the Scenes

229. Reports

230. Customizable XSL stylesheets to format the XML produced by these transactions

232. Anything to Dublin Core

234. Dublin Core is the default format here

235. Expose information about digital collections/repository content to the wider world

237. OAI Metadata Example with Dublin Core

243. Direct MARC Support

244. Global Editing of MARC Data

245. Crosswalk utilities

247. Electronic MARC Record Processing

248. MarcEdit Crosswalk Options

249. Harvest OAI Data

250. End of OAI Harvest in MarcEdit

253. Document-centric work

254. General authoring XML

256. Complete XML Management Solution

257. Supports all types of XML Schema

258. XSLT Support w/debugger

259. Many academic users

260. XML Aware Editing in Oxygen

264. Library data has a better chance of strong support in XML than not in XML

266. Perl/PHP/Python/Ruby all have support with varying levels of MARC support

268. maintained by a small, but dedicated group of programmers

269. Not part of most languages' “standard” distribution

271. Terry Reese's Weblog

272. Watch for how RDA interacts with XML

273. Eric Lease Morgan's Workshop for those with a more technical bent - “ XML in Libraries ”

275. It is a useful one

276. The intellectual work of cataloging will still be the same

277. Relying on the MARC format as our primary data store is becoming problematic

Xml Overview

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (7)

Similar to Xml Overview

Similar to Xml Overview (20)

Recently uploaded

Recently uploaded (20)

Xml Overview