1. ACG 4401 Chapter 2 1

2.  A language used to create other languages  Vocabularies  Describes:  Rules and  Syntax for  Well-Formed and Valid XML Documents ▪ Structuring Documents!  Does NOT describe tag names 2

3.  Meta-Language  A language that can be used to create others (vocabularies) ▪ Universal Business Language (UBL) ▪ Extensible Business Reporting Language (XBRL)  Application has sets of xml documents  Instance Document.xml ▪ contains the data (chapter 2 & Chapter 4)  Schema Document.xsd ▪ Describes allowed structure (data types, element names) of instance document (chapter 3)  Stylesheet.xsl ▪ Formatting instructions for data in the instance document (chapter 5)

4.  Preferred way of moving data between software applications.  So why not use it to move accounting data? 4

5.  Well Formed documents  meet basic rules for XML (chapter 2)  Valid documents  Meets rules regarding structure, order and data- types as described in Schema (chapter 3) 5

6. TTags MMeta-data ▪d▪description of data enclosed within brackets ▪ <> opening /> closing EElement OOpening tag, data, and Closing tag ▪<▪<instructor>Dr. Hornik</instructor> AAttribute ▪D▪Data that adds meaning to the data adding meaning to the data ▪D▪Data describing the tag ▪<▪<Instructor Department=“Accounting”>Dr. Hornik</Instructor> XXML does not prescribe Tags to be used AAnyone can make up tags <tag> for any purpose as long as XML document is well- formed. 6

7. 1. The first line of an XML document must contain the prologue. 2. The main theme of the XML document – the root element - must enclose all the other elements in the document. There can be only one root element. 3. Every element must have an opening tag name <> and a closing tag name and they must match (case sensitive).  Documents can have empty elements. ▪

8. 4. Elements must be properly nested, that is you close the tag that was opened last – think of tags as using a LIFO convention or more properly a LOFC Last Opened First Closed convention (though it doesn’t have quite the same ring to it). 5. Elements can have attributes.  Attributes follow the opening tag name ▪ attributeName=“attributeValue” ▪ attributeName is not included in the closing tag

9.  Every XML document starts with a prolog  It lets the XML enabled processor know that this is an XML document to be processed  UCS Transformation Format—8-bit) is a variable-width encoding that can represent every character in the Unicode character set.  Comment

10.  Hierarchy  Child/Simple ▪ Encloses Data ▪ Dr. Hornik  Parent/Complex ▪ Does not enclose data ▪ Encloses/Contains other elements ▪  Dr. Hornik ▪  Root Element (special parent element) ▪ Encloses All other elements in Instance Document 10 Parent Child

11. Belmopan Cayo Belize 11100 5 130 88.44 17.27 Belmopan is the capital of Belize Belmopan was established following the devastation of the former capital,Belize City, by Hurricane Hattie in 1965. High ground and open space influenced the choice and ground-breaking began in 1966. By 1970 most government offices and operations had already moved to the new location. Root element Parent element

12. Universal Business Language 12

13.  Organization for the Advancement of Structured Information Standards (OASIS)  Complete XML based library of business document  A Dictionary of standard, predefined element names and  A Library of standard, predefined documents  Where the elements can appear 13

14. 14

15.  When possible UBL uses the same structure for elements in different documents  PostalAddress can be used in:  Catalogue  Purchase Order  Invoice  … ▪ So it has the same structure ▪ Main St. ▪ 56A ▪ Newark ▪ 19716 ▪ DE ▪ ▪ USA ▪

16.  Each has a unique Root Element  Each has a required ID (child element)  Uniquely Identify document  Each has a required IssueDate (child element)  Determine when document is created  Optional IssueTime  Each has two Party elements (parent elements)  Provider/Supplier  Customer/Buyer  Each has at least one line element (parent element)  CatalogueLine  OrderLine

17.  UBL Schema’s UBL Schema’s 17

18.  Compare the non-Vocabulary (homegrown) based PO to the UBL PO 18

19.  UBL defines what the root element name is 

20.  Parent elements contain or enclose other elements  Root ( ) Parent of:  ▪  ▪  ▪ What are the Parent elements within this element?

21.  Attributes are contained within an opening element tag <>  attributeName=“attribute value”  Name-pair value  575.55  1

22. Processes Covered

23.  In-class/Windows use NotePad  Mac use TextWrangler  You must use a Text Editor (not a word processor)  XML editor – Exchanger XML Lite (PC and Mac)  Testing XML  Open in Browser (IE, Firefox, Safari??)  If it opens it’s well formed  If you receive an error message it’s not 23

24.  Assume Customers place Pizza Order over phone  What data is captured with order?  Customer ▪ Phone# ▪ Name ▪ Address  Order ▪ Items ▪ Delivery/Pickup ▪ Total Amount 24

25.  Sample Despatch Advice Sample Despatch Advice

26. 26