\/\/\/\/\/\/\/\/\/\/
No. The well-formed form is:
\/\/\/\/\/\/\/\/\/\/
Yes, it is possible. This solution should be used if random access is required for the subset document.
Can this element contain an element <Role> that is not defined inside the associated schema ? Yes/No
\/\/\/\/\/\/\/\/\/\/
No. The AnyElement element can contain only elements that are defined in the associated schema. Pay attention that the element type ("ANY") can mislead you to believe that any element type is possible inside it.
Can you attach to it any attribute that is a valid XML name ? Yes/No
\/\/\/\/\/\/\/\/\/\/
No. The ANY type refers strictly to the content of the element, not to its attributes. If there is no additional ATTLIST declaration for the AnyElement element then it would have no attributes at all.
\/\/\/\/\/\/\/\/\/\/
a, b, c, e, g, i
\/\/\/\/\/\/\/\/\/\/
Yes, it is possible but it can lead to confusions.
\/\/\/\/\/\/\/\/\/\/
The first option (a) is better because we can impose a content model for the elements BillingAddress & MailAddress. In the second case we are not able to impose a content model because a content model cannot be build depending on the value of an attribute.
\/\/\/\/\/\/\/\/\/\/
No. This is a mixed element content. For the mixed content model the order of elements or their number *cannot* be controlled.
\/\/\/\/\/\/\/\/\/\/
No. The number of elements in a mixed content element *cannot* be controlled. As a result the only way to write it is:
\/\/\/\/\/\/\/\/\/\/
No. The above element is not deterministic, that means that if the tag <AAA> is present in the markup you have to look at the next tag in order to know what expression from the DTD matches the tag.
Exemplification:
a. the tag from the next xml markup is matched by AAA:
b. the tag from the next xml markup is matched by (AAA, BBB):
This type of look-ahead is not permitted. As a result this element can be flagged as an error by a validating parser. Pay attention that the parser *may* recover from this error and therefore it may fail to report the error. In any case the above element constitutes an error.
Obs:
The same analogy is true for the tag <BBB>.
\/\/\/\/\/\/\/\/\/\/
Answer: no.
Which elements are respecting the definition ?
a.\/\/\/\/\/\/\/\/\/\/
a,b,c,d. They are all valid! The year attribute is optional.
Which elements are respecting the definition ?
a.\/\/\/\/\/\/\/\/\/\/
b. The attribute "year" is mandatory and it can have only 2 valid values "2000" & "2001". Naturally, the string "two thousand" is not the same as "2000".
Which elements are respecting the definition ?
a.\/\/\/\/\/\/\/\/\/\/
a,b,c,d. They are all valid!
The attribute "year" is optional and it has a default value. In the first case (a) a validating parser would supply the default value (1995).
Which elements are respecting the definition ?
a.\/\/\/\/\/\/\/\/\/\/
Answer: a,b.
The "#FIXED" keyword states that the attribute must always have the default value, which in this case is "2001".
\/\/\/\/\/\/\/\/\/\/
No. If the attribute is explicitely defined as optional (using the "#IMPLIED" keyword) then a default value *cannot* be provided.
a. valid xml format;
b. Extended Backus-Naur Form (EBNF);
c. general schema format;
d. ISO 3091 format;
\/\/\/\/\/\/\/\/\/\/
Answer: b.
\/\/\/\/\/\/\/\/\/\/
Yes. The comment format is as follows:
\/\/\/\/\/\/\/\/\/\/
False. The internal subset declarations have higher priority and can be used to override the declarations from the external subset.
a. the external DTD subset;
b. the internal DTD subset;
c. the associated DTD file;
d. the DOCTYPE declaration;
\/\/\/\/\/\/\/\/\/\/
Answer: d.
The DOCTYPE declaration from the beginning of an xml document is the "Document Type Declaration". This declaration is commonly referred as the DOCTYPE declaration.
I wish you success in your certification effort.
If you wish to add something feel free to use the forums.
