• ( + )Solution
The correct answer is A (xs:date) and C (xs:gMonthDay). These two are embedded simple types representing time and date under XML Schema. Embedded simple types that are used quite often are the same as data types used for common programming languages. Embedded simple types that are difficult to map to types used in current programming languages and databases tend to not be used very often.

Select which of the following is a correct XML Schema description matching the conditions below. Select all that apply. Assume the XML Schema Namespace prefix is "xs."

Conditions: The "Address" attribute is defined as a string type that may be omitted.

1. <xs:attribute name="Address" type="xs:string" use="optional"/>
2. <xs:attribute name="Address" type="xs:string" optional="true"/>
3. <xs:attribute name="Address" type="xs:string" required="optional"/>
4. <xs:attribute name="Address" type="xs:string" use="required"/>

• ( + )Solution
Attribute occurrences are designated using the use attribute of the attribute element. Designating the value as "optional" allows the attribute description to be omitted. Since this meets the required conditions of the question, the correct answer is A. No optional attribute or required attribute exists for the attribute element, and the syntax itself contains an error. Accordingly, answers B and C are incorrect. Designating "required" as the value of the use attribute for the attribute element means that the attribute description is required. The syntax itself is correct, but does not meet the required condition of providing a definition allowing the Address attribute to be omitted. Accordingly, answer D is incorrect.

Select which of the following is a valid XML document with respect to the following XML Schema Document.

●XML Schema Document
<?xml version="1.0"?>
  <xs:schema
   xmlns:xs="http://www.w3.org/2001/XMLSchema" >
  <xs:element name="Employee" type="EmployeeType" />
  <xs:complexType name="EmployeeType">
    <xs:sequence maxOccurs="unbounded">
      <xs:element ref="Name" />
      <xs:element ref="Department" />
    </xs:sequence>
  </xs:complexType>
  <xs:element name="Name" type="xs:string" />
  <xs:element name="Department" type="xs:string" />
  </xs:schema>

1. <Employee></Employee>
2. <Employee>
   <Name>Masashi Tanaka</Name>
   <Name>Makiko Okamura</Name>
   </Employee>
3. <Employee>
   <Name>Masashi Tanaka</Name>
   <Name>Makiko Okamura</Name>
   <Department>Sales Department</Department>
   <Department>Accounting Department</Department>
   </Employee>
4. Neither A, B, nor C follows the definition in XML Schema Document

• ( + )Solution
The content defined in this XML Schema Document place the "Name" element and the "Department" element as child elements of the "Employee" element, with the "Name" element and "Department" element occurring in that order. Since the minOccurs attribute of the sequence element is omitted, the combination of "Name" and "Department" elements occur at least once; the maxOccurs attribute is designated as "unbounded," allowing for an unlimited number of occurrences. Rewriting this XML Schema Document under DTD would result in . Under answer A, the "Employee" element is an empty element, and as such does not fulfill the number of occurrences defined in XML Schema Document. Accordingly, answer A is incorrect With answer B, only the "Name" element occurs repeatedly, while there is no description provided for the "Department" element. Accordingly, answer B is also incorrect. Under answer C, first the "Name" element occurs, after which the "Department" element occurs; the "Name" and "Department" elements do not occur in combination. Accordingly, answer C is incorrect. Answer D is correct, because the XML documents of neither A, B, nor C follow the definitions of the XML Schema Document. In this volume, we have discussed the differences between XML Schema and DTD definitions, as well as the methods for declaring XML Schema elements and attributes. DTD does not support Namespace, while XML Schema does support Namespace. Due to constraints of the page, we did not offer a full explanation in this regard. Also, the default attribute and fixed attribute may be designated in element declarations?a fact about which we hope all XML professionals develop a firm grasp.

Select which of the following is incorrect as an XML Schema description. Assume that the namespace prefix xs is declared as "http://www.w3.org/2001/XMLSchema."

<xs:simpleType name="Data_Type">
  <xs:restriction base="xs:int">
    <xs:minExclusive value="20"/>
    <xs:maxInclusive value="200"/>
  </xs:restriction>
</xs:simpleType>
<xs:element name="Price" type="Data_Type"/>

1. A value of 20 is allowed under the Price element
2. A value of 23.4 is not allowed under the Price element
3. A value of 200 is allowed under the Price element
4. A value of 99 is allowed under the Price element

• ( + )Solution
The content defined in this XML Schema Document place the "Name" element and the "Department" element as child elements of the "Employee" element, with the "Name" element and "Department" element occurring in that order. Since the minOccurs attribute of the sequence element is omitted, the combination of "Name" and "Department" elements occur at least once; the maxOccurs attribute is designated as "unbounded," allowing for an unlimited number of occurrences. Rewriting this XML Schema Document under DTD would result in . Under answer A, the "Employee" element is an empty element, and as such does not fulfill the number of occurrences defined in XML Schema Document. Accordingly, answer A is incorrect With answer B, only the "Name" element occurs repeatedly, while there is no description provided for the "Department" element. Accordingly, answer B is also incorrect. Under answer C, first the "Name" element occurs, after which the "Department" element occurs; the "Name" and "Department" elements do not occur in combination. Accordingly, answer C is incorrect. Answer D is correct, because the XML documents of neither A, B, nor C follow the definitions of the XML Schema Document.

Select which of the following is an XML Schema document that correctly defines the Unit Price element as either 3500 or 4500.

1. <xs:simpleType name="priceType">
     <xs:restriction base="xs:int">
       <xs:minInclusive value="3500"/>
       <xs:maxInclusive value="4500"/>
     </xs:restriction>
   </xs:simpleType>
   <xs:element name="Unit Price" type="priceType"/>
2. <xs:simpleType name="priceType">
     <xs:restriction base="xs:int">
       <xs:minExclusive value="3500"/>
       <xs:maxExclusive value="4500"/>
     </xs:restriction>
   </xs:simpleType>
   <xs:element name="Unit Price" type="priceType"/>
3. <xs:simpleType name="priceType">
     <xs:restriction base="xs:int">
       <xs:enumeration value="3500"/>
       <xs:enumeration value="4500"/>
     </xs:restriction>
   </xs:simpleType>
   <xs:element name="Unit Price" type="priceType"/>
4. <xs:simpleType name="priceType">
     <xs:restriction base="xs:int">
       <xs:minlength value="3500"/>
       <xs:maxlength value="4500"/>
     </xs:restriction>
   </xs:simpleType>
   <xs:element name="Unit Price" type="priceType"/>

• ( + )Solution
This question also involves a simpleType element and restriction element, forming a simple type restriction. Since A uses minInclusive and maxInclusive, the value designated for the Unit Price element is 3500 or greater and 4500 or less, which does not meet the required conditions. Answer B uses minExclusive and maxExclusive, which means that the value designated for the Unit Price element is greater than 3500 and less than 4500, contrary to the requirements defined. Accordingly, B is also incorrect as an answer here. Answer C uses enumeration, meaning that the value designated for the Unit Price element is either 3500 or 4500. This satisfies the conditions, and is accordingly our correct answer. Answer D uses minLength and maxLength. If the base type is "int," then minLength and maxLength cannot be designated, and therefore, D is an incorrect answer.

Select which two of the XML documents below are valid with respect to the following XML Schema document.

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
 <xs:element name="Product" default="Computer">
  <xs:complexType>
   <xs:simpleContent>
    <xs:extension base="xs:string">
     <xs:attribute name="ship_date" type="xs:date" use="required" />
    </xs:extension>
   </xs:simpleContent>
  </xs:complexType>
 </xs:element>
</xs:schema>

1. <Product ship_date = "April 4, 2006">Notebook Computer</Product>
2. <Product ship_date="2006-04-15">Mouse</Product>
3. <Product ship_date="2006-4-20">Hard Disk</Product>
4. <Product ship_date="2006-04-30"></Product>

• ( + )Solution
This XML Schema document makes the following definitions * The Product element is text data, with a default value of "Computer" * The Product element has a date type Ship_date attribute, and the attribute must be designated The Product Name element has a default attribute assigned. It is only in the event that content for the "Product Name" element is not described that the default attribute value will be applied. The Ship_date attribute is designated as "required" in a use attribute. Accordingly, any content is allowed as long as it is date type data. The pattern for date type is "XXXX-XX-XX (2006-05-12)." Accordingly, the correct answer is B and D.

Select two of the following that represent valid XML documents with respect to the XML Schema document below:

<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:element name="Customer_Information" type="CustomerType" />
  <xs:complexType name="InfoType">
   <xs:sequence>
    <xs:choice>
     <xs:sequence>
      <xs:element ref="Company" />
      <xs:element ref="Address" />
     </xs:sequence>
     <xs:sequence>
      <xs:element ref="LastName" />
      <xs:element ref="FirstName" />
     </xs:sequence>
    </xs:choice>
  </xs:sequence>
</xs:complexType>

<xs:complexType name="CustomerType">
  <xs:complexContent>
   <xs:extension base="InfoType">
    <xs:choice>
     <xs:element ref="Telephone" />
     <xs:element ref="Mobile" />
    </xs:choice>
   </xs:extension>
  </xs:complexContent>
 </xs:complexType>
 <xs:element name="Company" type="xs:string" />
 <xs:element name="Address" type="xs:string" />
 <xs:element name="LastName" type="xs:string" />
 <xs:element name="FirstName" type="xs:string" />
 <xs:element name="Telephone" type="xs:string" />
 <xs:element name="Mobile" type="xs:string" />
</xs:schema>

1. <Customer_Information>
   <Company>masashi</Company>
   <Address>okamura</Address>
   <Mobile>090-9231-3678</Mobile>
   <Mobile>090-6345-6989</Mobile>
   </Customer_Information>
2. <?xml version="1.0" ?>
   <Customer_Information>
   <Company>masashi</Company>
   <Address>okamura</Address>
   <Mobile>090-9231-3678</Mobile>
   </Customer_Information>
3. <?xml version="1.0" ?>
   <Customer_Information>
   <Company>Okamura</Company>
   <Address>Masashi</Address>
   <Telephone>03-0001-6789</Telephone>
   </Customer_Information>
4. <?xml version="1.0" ?>
   <Customer_Information>
   <Company>Okamura</Company>
   <Address>Masashi</Address>
   <LastName>masashi</LastName>
   <FirstName>okamura</FirstName>
   <Telephone>03-0001-6789</Telephone>
   <Mobile>090-9231-3678</Mobile>
   </Customer_Information>

• ( + )Solution
This question deals with a complex type extension. Looking at the XML Schema document designated in this problem, the definitions below can be inferred: * The root element is the Customer_Information element * The Company element and Address element occur in that order * The LastName element and FirstName element occur in that order * Either the combination of the Last Name element and the Address element, or the combination of the LastName element and the FirstName element occurs * Either the Telephone element or the Mobile element occurs one time Accordingly, only the XML document that meets the conditions above is a valid XML document. In A, the "Mobile" element occurs two times, so this is not a valid XML document. Both B and C fulfill the conditions, and are therefore valid XML documents. In answer D, all of the elements defined within the XML Schema document occur, so this is not a valid XML document. Accordingly, the correct answer is B and C.

Select which of the following correctly represents what should be described in (1) of the XML Schema document in order to correctly define the following XML Document (the Location_of_Origin attribute of Fruit element is mandatory):

［XML Document］
<?xml version="1.0" ?>
<Fruit Location_of_Origin="Aomori">
  <Name>Apple</Name>
  <Price>350</Price>
</Fruit>

［XML Schema Document］
<?xml version="1.0" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:element name="Fruit" type="fruitType" />
  <xs:complexType name="baseType">
    <xs:sequence>
     <xs:element ref="Name" />
    </xs:sequence>
  </xs:complexType>

  <xs:element name="Name" type="xs:string" />
  <xs:element name="Price" type="xs:integer" />
</xs:schema>
 

1. <xs:complexType name="fruitType">
     <xs:complexContent>
      <xs:restriction base="baseType">
       <xs:sequence>
        <xs:element ref="Price" />
       </xs:sequence>
       <xs:attribute name="Location_of_Origin"
       type="xs:string" use="required" />
      </xs:restriction>
     </xs:complexContent>
   </xs:complexType>
2. <xs:complexType name="fruitType">
     <xs:complexContent>
      <xs:extension base="baseType">
       <xs:sequence>
        <xs:element ref="Price" />
       </xs:sequence>
       <xs:attribute name="Location_of_Origin"
         type="xs:string" use="required" />
       </xs:extension>
     </xs:complexContent>
   </xs:complexType>
3. <xs:complexType name="fruitType">
     <xs:simpleContent>
      <xs:extension base="baseType">
            <xs:sequence>
       <xs:element ref="Price" />
      </xs:sequence>
      <xs:attribute name="Location_of_Origin"
        type="xs:string" use="required" />
      </xs:extension>
     </xs:simpleContent>
   </xs:complexType>
   
4. <xs:complexType name="fruitType">
     <xs:simpleContent>
      <xs:restriction base="baseType">
       <xs:sequence>
        <xs:element ref="Price" />
       </xs:sequence>
       <xs:attribute name="Location_of_Origin"
         type="xs:string" use="required" />
       </xs:restriction>
     </xs:simpleContent>
   </xs:complexType>

• ( + )Solution
The XML Document contains a Fruit element having a Location_of_Origin attribute, and a Name element and Price element as child elements of the Fruit element. For the XML Schema Document, the Fruit element is a fruitType type, defined as a baseType type having only a Name element. Accordingly, to derive the answer to this question, all one needs to do is define the fruitType type to which the string type Price element and Location_of_Origin attribute have been added, based on the baseType type. The complex type extension syntax is as follows: Designate the Model Group Designate the Attribute Let's look at each choice based on this syntax. Answer A defines the content as a complex type using the complexContent element, and the restriction element defines the complex type restriction, meaning that this answer is incorrect. Originally, the baseType attribute has no Location_of_Origin attribute, which will cause an error during validation. Answer B defines the content as a complex type using the complexContent element, and defines the complex type extension for the extension element. Accordingly, this answer is correct. Answers C and D define the content as a simple type using the simpleContent element, and are therefore incorrect. Accordingly, the correct answer is B.

Select which of the following correctly describes the results of performing a validation check on "XML Document".

Assume that the XML parser correctly processes the XML Schema noNamespaceSchemaLocation attribute and the schemaLocation attribute.

[XML Document]
<document xmlns:sec="urn:xmlmaster:document:sec"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:noNamespaceSchemaLocation="document.xsd"
    xsi:schemaLocation="urn:xmlmaster:document:sec section.xsd">
  <sec:section number="1" name="section1" />
  <sec:section number="2" name="section2" />
</document>

[document.xsd]
<xs:schema
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns:sec="urn:xmlmaster:document:sec">
  <xs:element name="document" type="documentType" />
  <xs:complexType name="documentType">
    <xs:sequence>
      <xs:element ref="sec:section" maxOccurs="unbounded" />
    </xs:sequence>
  </xs:complexType>
</xs:schema>

[section.xsd]
<xs:schema
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    targetNamespace="urn:xmlmaster:document:sec"
    xmlns:tns="urn:xmlmaster:document:sec">
  <xs:element name="section" type="tns:sectionType" />
  <xs:complexType name="sectionType">
    <xs:attribute name="number" type="xs:int" />
    <xs:attribute name="name" type="xs:string" />
  </xs:complexType>
</xs:schema>

A. Valid
B. The coding for the XML Document is not appropriate; therefore, an error is thrown (initial error) when processing the XML Document [xsi:schemaLocation="urn:xmlmaster:document:sec section.xsd"]
C. The coding for the XML Schema Document is not appropriate; therefore, an error is thrown (initial error) when processing the "document.xsd" [<xs:element ref="sec:section" maxOccurs="unbounded" />]
D. No processing error, but is not valid

• ( + )Solution
C

Select which of the following incorrectly describes the structure defined by the following XML Schema.

[XML Schema]
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:element name="ProductItem" type="ProductType" />
  <xs:complexType name="ProductType">
    <xs:sequence minOccurs="0" maxOccurs="unbounded">
      <xs:element ref="ProductCode" />
      <xs:element ref="ProductName" />
      <xs:element ref="ProductQuantity" />
      <xs:choice>
        <xs:element name="ProductPrice01" type="xs:string" />
        <xs:element name="ProductPrice02" type="xs:unsignedInt" />
      </xs:choice>
    </xs:sequence>
    <xs:attribute name="LotCode" type="xs:string" use="required"/>
  </xs:complexType>
  <xs:element name="ProductCode" type="xs:string" />
  <xs:element name="ProductName" type="xs:string" />
  <xs:element name="ProductQuantity" type="xs:unsignedInt" />
</xs:schema>

A. The "ProductItem" element must include a "LotCode" attribute
B. The "ProductCode" element has no limitations as to the number of appearances
C. The order of appearance of the "ProductItem" element child element is random
D. Either the "ProductPrice01" element or the "ProductPrice02" element can be coded

• ( + )Solution
C