\/\/\/\/\/\/\/\/\/\/
No. A well-formed id must start with a Unicode letter:
\/\/\/\/\/\/\/\/\/\/
Answer: No.
\/\/\/\/\/\/\/\/\/\/
Yes. A parsed entity will be parsed by a (validating?!) parser. A parsable entity is a valid entity (an entity that is well-formed XML). A parsable entity can be parsed or not, depending on its declaration in the DTD document.
\/\/\/\/\/\/\/\/\/\/
No. The apostrophe that ends the entity cannot be used to end the value of the attribute "some_attribute".
\/\/\/\/\/\/\/\/\/\/
Yes. The following DTD is perfectly valid:
Can this XML file have an external DTD attached to it ? Yes/No
\/\/\/\/\/\/\/\/\/\/
Yes, since the "standalone" declaration is just a hint to the parser and not a direct instruction.
\/\/\/\/\/\/\/\/\/\/
Answer: yes.
\/\/\/\/\/\/\/\/\/\/
No. This requirement is preserved in XML so that compatibility is maintained with SGML.
\/\/\/\/\/\/\/\/\/\/
No. Even if the end of the comment can be properly identified by "-->" it is forbidden to have the hyphen as the last character in the comment:
Most probably this requirement was enforced in order to preserve the compatibility with SGML.
\/\/\/\/\/\/\/\/\/\/
No. Nested comments are illegal:
\/\/\/\/\/\/\/\/\/\/
No. It is illegal to have a whitespace between <! and CDATA. The correct form is:
\/\/\/\/\/\/\/\/\/\/
Yes. The string used to end a CDATA section is "]]>". The string "]]" can be used anywhere inside a CDATA section because it does not have any special signification.
Are the parameters "version", "encoding" and "standalone" just standard attributes ? Yes/No
\/\/\/\/\/\/\/\/\/\/
No. They are not just standard attributes because their order is fixed (the order of the standard attributes is not important)
\/\/\/\/\/\/\/\/\/\/
The valid answers are: d,h.
a - invalid, because it containt the $ character;
b - invalid, because it contains the & character;
c - invalid, because it starts with a hyphen ("-"); only Unicode letters, underscore (_) and colons (:) are allowed to start an XML name;
e - invalid, because an XML name cannot start with a decimal digit;
f - invalid, because an XML name cannot begin with the string 'xml' (the capitalization does not matter: xml, Xml, xmL or XML are all illegal)
g - invalid, because an XML name cannot begin with the string 'xml';
a. < CELL >
b. <Value$>
c. <CP/M>
d. < /CELL>
e. </OperatingSystem_CP/M>
\/\/\/\/\/\/\/\/\/\/
All the enumerated tags are invalid:
a - invalid, because there is a whitespace bewteen "<" and "CELL"
b - invalid, because it contains an invalid character: "$"
c - invalid, bacause it contains an invalid character: "/"; the slash can only be used to start and ending tag; the slash cannot appear in the middle of the tag name.
d - invalid, because there is a whitespace bewteen "<" and "/CELL"
e - invalid, bacause it contains an invalid character: "/".
a. <cell/>
b. <cell />
c. <cell / >
\/\/\/\/\/\/\/\/\/\/
The valid tags are a & b. The c tag is invalid because the whitespace is not allowed between / and >.
\/\/\/\/\/\/\/\/\/\/
True. The declaration can specify other encodings for the rest of the document but the line of the declaration must be in US-ASCII format because prior to this line there is no information regarding the true encoding of the document.
\/\/\/\/\/\/\/\/\/\/
No. An XSL stylesheet can only be used to convert a *valid* XML document into something else.
a. xml:lang
b. xml:width
c. xml:space
d. xmlns:
e. xmlns:some_ns
f. xml:base
\/\/\/\/\/\/\/\/\/\/
The valid choices are:
a - this is a special attribute that must be recognized by conforming parsers; please note that "xml" is not a namespace;
c - the same as a;
d - this is the standard way to declare a default namespace;
e - this is the standard way to declare a namespace;
f - the same as a;
\/\/\/\/\/\/\/\/\/\/
Answer: No.
I wish you success in your certification effort.
If you wish to add something feel free to use the forums.