Card Set Information

2012-10-08 15:06:37

XML & XSD Schemas
Show Answers:

  1. XML
    eXtensible Markup Language that allows you to create your own tags
  2. HTML vs XML (3)
    • 1. HTML easier to use (single technology, only a few tags need to be known to create web pages)
    • 2. HTML faster for web page development
    • 3. HTML makes smaller web pages (about 1/6 size)
  3. XML good for
    • Standard for data stream manipulation.
    • Format used to transfer and store data stream
    • transferring data, storing software settings and structuring documents (win word)
  4. Application Programming Interface (API)
    Web service that allows programmers access to social networking sites so they an develop apps for those sites (facebook, amazon, etc)
  5. REST
    Representational State Transfer - web service that supports collection of operations (GET, PUT, POST) for interacting with API through XML
  6. XML Namespace
    collection of rules that tell reader how to use document
  7. XML Attribute (3)
    • 1. Convey information about data (metadata)
    • 2. Must be surrounded by quotes
    • 3. Can never repeat
  8. Well formed XML
    XML that follows syntax rules
  9. XML well formed Syntax (6)
    • 1. XML document must contain single root element
    • 2. Every tag needs either a terminating tag (if has children) or a terminating character (if no children)
    • 3. No overlapping nesting
    • 4. XML is case sensitive
    • 5. Attributes must be in quotes
    • 6. Entities must be used for special characters (& needs to be &)
  10. Root element
    Unique tags that open and close around a document
  11. Object Oriented design
    • 1.elements match tables, attributes match columns
    • 2. Result in shorter data streams
    • 3. easier import/export to database
  12. XML readability does not matter (3)
    • 1. XML always generated, never typed out
    • 2. XML hardly ever loaded to browser (usually to a database)
    • 3. XSL style sheets help to make look good anyway
  13. XML validation (4)
    • 1. Use XSD schema
    • 2. Match XML with database
    • 3. Ensure data integrity
    • 4. Make sure receiving and sending ends understand data
  14. XSD Schema (3)
    • 1. Common database format
    • 2. Type of contract between sender/receiver where everyone agrees how data should look
    • 3, How XML file should look. Meta data description of XML
  15. Valid XML
    XML that is both well formed & has been validated against an XSD schema
  16. Creating XSD (5)
    • 1. Add schema to namespace outermost element
    • 2. Declare XSD namespace - Define namespace in root tag at top of XSD
    • 3.Define innermost comlex types
    • 4. Define outermost element types
    • 5. Define root element
  17. All schema commands must be preceded by:
  18. xs:attribute
    • Defines how attribute is defined
    • - name
    • - data type (string, integer, etc.)
    • - should specifiy use (optional or required)
  19. MaxOccurs
    limit number of child elements (unbounded = no max)
  20. MinOccurs
    Min number of child elements
  21. type attribute
    data type (integer, string)
  22. xs:Sequence tag
    states that elements need to appear in the order that they appear in the schema
  23. Complex Element
    • 1. Cannot use until you declare it as a complex type
    • Must delclare these elements
  24. DTD validation
    Document Translation Definition (DTD) - concentrated on relationships between tags and attributes rather than the data types and valid data within attributes. Not sufficient to validate XML data streams
  25. XDR validation
    Old Microsoft standard. No longer supported overall