The Information School at the University of Washington LIS 549 U/TU: Intro to Content Management Fall 2003 * Bob Boiko * MSIM Associate Chair XML Schemas

The Information School at the University of Washington LIS 549 U/TU: Intro to Content Management * Fall 2004 * Bob Boiko * MSIM Associate Chair Instance documents Are they too much? –Why would I bother to do all that work just to create a Web page that I could have typed in? Are they enough? How about: –Making new instances –Keeping control over the tags and their and use –Making sure others know how to create the instance –Using parts of other people’s instances –Adding format to the XML

The Information School at the University of Washington LIS 549 U/TU: Intro to Content Management * Fall 2004 * Bob Boiko * MSIM Associate Chair Enter Schemas The schema contains all the rules –What elements are allowed –What elements within what elements –What attributes –What attribute values Well formed vs. valid Namespaces Document Type Definitions (DTD)

The Information School at the University of Washington LIS 549 U/TU: Intro to Content Management * Fall 2004 * Bob Boiko * MSIM Associate Chair What are Schemas? They are XML! They are rules and regulations They are MODELS

The Information School at the University of Washington LIS 549 U/TU: Intro to Content Management * Fall 2004 * Bob Boiko * MSIM Associate Chair What are the Major Players? 1.Text or a visual design environment 2.Elements 3.Attributes 4.Nesting 5.Reuse

The Information School at the University of Washington LIS 549 U/TU: Intro to Content Management * Fall 2004 * Bob Boiko * MSIM Associate Chair Schema overview Elements –Required vs. Optional –Bounded vs. unbounded –Mixed (allows text) vs. elements only –Reference vs. locally defined Attributes –Required vs. Optional –Type –Allowed values Nesting –Sequence –Choice Reuse –Element Groups Block elements (my term) Inline elements (my term)

The Information School at the University of Washington LIS 549 U/TU: Intro to Content Management * Fall 2004 * Bob Boiko * MSIM Associate Chair The Spy visual environment NavigatorElement properties Attribute properties Element Hierarchy

The Information School at the University of Washington LIS 549 U/TU: Intro to Content Management * Fall 2004 * Bob Boiko * MSIM Associate Chair A quick look at schema text

The Information School at the University of Washington LIS 549 U/TU: Intro to Content Management * Fall 2004 * Bob Boiko * MSIM Associate Chair Elements Required vs. Optional Bounded vs. unbounded Mixed (allows text) vs. elements only Reference vs. locally defined

The Information School at the University of Washington LIS 549 U/TU: Intro to Content Management * Fall 2004 * Bob Boiko * MSIM Associate Chair Text in Elements Only Text Allowed Text and Elements Allowed Only Elements Allowed

The Information School at the University of Washington LIS 549 U/TU: Intro to Content Management * Fall 2004 * Bob Boiko * MSIM Associate Chair Allowed number (Cardinality)

The Information School at the University of Washington LIS 549 U/TU: Intro to Content Management * Fall 2004 * Bob Boiko * MSIM Associate Chair Attributes Required vs. Optional Type Allowed values ID and IDREF An ID is a unique value (starting with a character) An IDREF is a reference to the ID of an other element You use them for the same reason you always use Id’s Group

The Information School at the University of Washington LIS 549 U/TU: Intro to Content Management * Fall 2004 * Bob Boiko * MSIM Associate Chair Nesting Sequence (required) Choice (optional, unbounded)

The Information School at the University of Washington LIS 549 U/TU: Intro to Content Management * Fall 2004 * Bob Boiko * MSIM Associate Chair My block and inline model Group name

The Information School at the University of Washington LIS 549 U/TU: Intro to Content Management * Fall 2004 * Bob Boiko * MSIM Associate Chair Back to content modeling What do you have to figure out? What is it called? What does it contain? How many? How do you encode it? Root element Child elements Child attributes

The Information School at the University of Washington LIS 549 U/TU: Intro to Content Management * Fall 2004 * Bob Boiko * MSIM Associate Chair Forward from a content model Figure out what parts of your information need to be named Figure out what metadata you need to attach to your information –Descriptive –Management –Access Build a system that lets you gather, tag and distribute your information