1. ACG 4401 XML Schemas XML Namespaces XLink

2. + The XML Foundation Many participants – an extended family! XML Instance documents – carry data in context Each must be parsed into its component parts XML Schemas – define the rules a class of documents must follow Can be used to validate documents & contents XSLT – provide processing instructions Can be used to process XML documents Namespaces – qualify elements & attributes Differentiate & associate them with a URI Xlink

3. + XML Schema Language Language used to create Schema Documents Schema Used to define the structure and content of Instance documents Well-formatted XML document Definition: “provide a means for defining the structure, content and semantics of XML documents.” (W3C)W3C Defines structure and contents of Instance Document Similar to an ER-Diagram for databases Defines Each Element and Attribute Its Structure Includes Business Rules Cardinalities Used to Validate Instance Document Means Instance Document conforms to Schema Rules

4. + XML Schema.xsd extension But won’t open in IE so use.xml if using that browser Defines each attribute and element

5. + Vocabularies & Schemas XBRL & UBL are vocabularies XBRL for Financial Reporting UBL for Business Documents Vocabularies are designed using Agreed upon element names Agreed upon element types Agreed upon element sequence/structure Defined by Schemas

6. + Namespaces Each XML Vocabulary is associated with a unique NameSpace A unique identifier (think, primary key) Universal Resource Identifier (URI) Local Name (e.g. TeeTimeResevations.xml) URL (http://www……) Used to prevent naming collisions (more later) 6

7. + Vocabularies and Namespaces Namespace A Unique Identifier Unique Prefix refers to URI Points to where information in an XML Document can be found. (URI) Attribute of Root Element Definition: “XML namespace: In XML, a namespace is a collection of names, identified by a URI reference, that are used in XML documents as element types and attribute names. In order for XML documents to be able to use elements and attributes that have the same name but come from different sources, there must be a way to differentiate between the markup elements that come from the different sources.” (Webopeida) (Technical Information from W3.org)“XMLURIattributeWebopeidaTechnical Information Used to preclude naming collisions Method for distinguishing between the same element name for different elements 10001... 18897

8. + Types of Elements Simple contain only data 98765 Complex contain other elements (i.e. Root & Parent) Bicycles Online, Inc. contain attributes 730.55 8

9. + Simple Element Definition Declare Name Declare Type Type= Defines the data type: string Integer date decimal other types

10. + Complex Element (Parent) Declares Name Declares type Declares Structure

11. + Complex Party Element 11

12. + Complex Element (Parent) xml 12

13. + Complex Element (attribute) Declare Name Declare Type Define element and attribute(s) For example: 730.55

14. + Complex (Attribute) xml 14

15. + Create a Schema from a non- vocabulary instance document Identify types of elements Simple Complex – Parent Complex – Attribute Create Prolog Create Root element Work down from 1 st element to last

16. + Root Element Root element is used to declare namespace(s) xs: = namespace prefix xmlns:xs defines prefix to use for namespace “http:www.w3.org/2001/XMLSchema” location of Namespace, where the dictionary is Prefix is used before each tag xs:tagname 16

17. + Creating Schema from Instance Document PizzaOrders 17

18. + Identify Element Types PizzaOrder.xml 18

19. + UBL Schemas Schemas for each document type Common Basic Components Defines Simple Elements Defines Complex (attribute) Elements Prefix: cbc (Namespace prefix) Common Aggregate Components Defines Complex (Parent) Elements Prefix: cac (Namespace prefix)

20. + Creating UBL Document Schemas 1. Declare NameSpaces and qualifiers 2. Import necessary Schemas 3. Define Root Element 1. Reference Reusable data components 2. Declare Cardinalities

21. + Declaring a Namespace (in the UBL Instance document) <Catalogue xmlns="UBLCatalogueDocument" xmlns:cbc="UBLCommonBasicComponents" xmlns:cac="UBLCommonAggregateComponents"> Since UBLCatalogueDocument does NOT have a prefix any element in the instance document without a prefix relates to this namespace. UBL Catalogue Instance with namespaces

22. + 1. UBL Namespace Declaration in Root Element <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="UBLCatalogueDocument" xmlns="UBLCatalogueDocument" xmlns:cbc="UBLCommonBasicComponents" xmlns:cac="UBLCommonAggregateComponents" elementFormDefault="qualified" attributeFormDefault="unqualified">

23. + Namespace Clarification targetNamespace="UBLCatalogueDocument“ The schema being created/used is applied to the UBLCatalogueDocument namespace elementFormDefault="qualified“ Element names will use a namespace prefix CAC: CBC: attributeFormDefault="unqualified“ Attribute names will not use a namespace prefix

24. + 2. UBL Import <xs:import namespace="UBLCommonBasicComponents" schemaLocation="http://www.buec.udel.edu/whitec/UBL CommonBasicComponents/UBLCommonBasicComponent sSchema.xsd"/> <xs:import namespace="UBLCommonAggregateComponents" schemaLocation="http://www.buec.udel.edu/whitec/UBL CommonAggregateComponents/UBLCommonAggregate ComponentsSchema.xsd"/>

25. + 3. UBL Root Element (Catalogue) Put it all together: The Entire Schema

26. + Validating XML Ensure that Instance Document Follows business rules Data types are correct Data is properly sequenced

27. + XML Linking Language XLink Uses attributes to describe relationships between elements Simple: HTML type links Extended: More complex Relationship links

28. + Simple links Unidirectional and always Outbound From element within Instance document to an outside resource Link to list of approved Vendor 28

29. + Extended Links Attributes: xlink:type=“extended” Used in Parent element Xlink:type=“locator” Remote resource In Child element Xlink:href=“http://….” In Child Element http://PurchaseOrders.x ml http://ReceivingRpts.xml http://Vouchers.xml 29