IBM XML certification questions

[s y]

Hello all
I am preparing for IBM xml certification.
I struck at the following questions.If possible please send me the answers of the following questions.
Answer to any question will be highly appreciated.
QUESTIONS:
1)Flat file editors & command line XSLT interpreters are considered to be the most important componants of XSLT development environment.
What are the most important componants of DTD development environment?
What are the most important componant of XML development environment?
2)What the "XML test cases" are supposed to exercise/contain?
3)It is recommended to go for single step XSL tranformation when processing logic is highly interrelated.
When to go for multistep tranformation?
4)Is it possible to convert SCHEMA to DTD?
5)Can we use both XSL & CSS in one stylesheet?
6)true/false
It is standard practice to use either XSL-FO or CSS for formatting a document,but not both simultaneously.
7)What is the input to XSLT?
XML file & XSL file
or Dom tree & xsl file

SHYAM
Chennai,India

[Mapraputa Is]

s y, unfortunately your name does not comply with the JavaRanch naming policy. We require names to have at least two words, separated by a space, and strongly recommend that you use your full real name. Please spare a moment and re-register with a name that meets the requirements.
Now I'll try to answer your questions.

1. What are the most important componants of DTD development environment?
Flat file editors
What are the most important componant of XML development environment?
Flat file editors also XML is just a plain text, so any text editor would suffice. There are a lot of specialized XML editors, or even IDE, which provide extra functionality, like hierarchical view or checking an XML instance against DTD, but it is not necessarily. From the other hand, XML is data format and as such is designed to be used by some program. To be used it should be parsed, so we need a parser. But if you ask only about "XML development" - then flat file editors.
2)What the "XML test cases" are supposed to exercise/contain?
According to IBM mock, XML test cases should
1.be derived or taken from real data
2.exercise the most probable error conditions to be expected when the system is used
3.exercise all the important element contexts and content variations to be handled by the system
3)It is recommended to go for single step XSL tranformation when processing logic is highly interrelated. When to go for multistep tranformation?
Frankly, I never had to apply multistep tranformation, maybe those who hasmore experience can put more light here
4)Is it possible to convert SCHEMA to DTD?
Yes, with possible loss of information. Schemas provide far more elaborated verification features, so it is very likely that some of them will be lost in " Schema to DTD" conversion.
5)Can we use both XSL & CSS in one stylesheet?
Yes. There are many issues involved in such marriage, you can read more here: http://www.xml.com/pub/a/2000/03/08/style/index.html http://www.xml.com/pub/a/2000/06/21/deviant/index.html
6)true/false
It is standard practice to use either XSL-FO or CSS for formatting a document,but not both simultaneously.
"XSL flow objects use CSS properties, so CSS is an integral part of the XSL formatting story. In addition, there's been considerable effort expended to make sure that a common formatting model is developed. This will allow people to learn a single display semantic and apply it equally well to CSS and XSL in the projects where each is appropriate."
Norman Walsh. The XSL Debate: One Expert's View http://www.xml.com/pub/a/1999/06/xsl_edit.html
"If we leave XSLT apart for the moment (since it can be used with CSS as well as with XSL Formatting Objects), then CSS is the 80% solution, XSL(FO) the high-end tool for the next 15%. The remaining 5% needs real programming.
On the scale between capabilities, usability, and ease of implementation, CSS stresses usability, then implementation, and is willing to limit its powers. XSL is the reverse. In other words: CSS should be accessible to everybody, XSL should be able to do almost anything.
XSL and CSS: One Year Later
by Leigh Dodds
June 21, 2000 http://www.xml.com/pub/a/2000/06/21/deviant/index.html
7)What is the input to XSLT?
XML file & XSL file
or Dom tree & xsl file
Answer: a hierarchical tree representing an XML document - typically DOM tree. XSLT transformation requires:
"- parser (typically DOM parser): read a document and transform it into tree repsesentation
- XSLT processor: receive “a hierarchical tree representing an XML document” as an input, transform it, and produce another hierarchical tree.
- ff there is a need to produce a file, than a serializer is called."

[This message has been edited by Mapraputa Is (edited November 18, 2001).]

[shyam yengantiwar]

Dear
Thank you very much for your quick reply.
It will really help me.
Thanks again.
Bye for noiw.
SHYAM

[Kelly Aus]

Dear Shyam,
First of all sorry for being so late! Actually I met with an accident and was on bed for more than a month and thus didn't participate on this forum. Also my email-id is no more valid as it has been blocked.
As far as your queries are concerned Mapraputa has answered them extremely well! Thanks Mapraputa!!! as far as the following point is concerned:
3)It is recommended to go for single step XSL tranformation when processing logic is highly interrelated.
When to go for multistep tranformation?
is concerned...even I haven't used multistep transformation as yet but from what I have read till now it is required to maintain intermediate steps of the transformation for understanding and maintainability. It is similar to breaking a large procedure into smaller methods for better comprehension.
Hope it helps.
Please let me know if there is anything else I can do to help.
Regards
Kelly

[shyam yengantiwar]

Dear Kelly
I was shocked to know aout your accident.I hope you are in good health now.And do take care of yourself.
I still have some doubts.If possible write me back.
Thanks.
True/false
when preparing for a B2B XML transaction or message between collaborative partners & cerating a corresponding DTD for validation,it is best practice(considering flexibility)to define an enumerated attribute to represent contry codes.(as a predefined list of static valid values)
My guess is "true"
Let me know the corrct answer.
Is this content model allowed?
< !element Customer ((LastName, Ship-to-address) & LastName,Bill-to-address)>
for the following question I guess option 2 & 3 are not correct.I am confusing between 1 & 4.Which one is correct according to you?Please give the explanation.
"Country"is intended to imply a text name (as in"united states of america").If author want to describe "country" according to the ISO 3166 country code standard (3 character alpha code & 3 digit numeric code)
Select the best solution for describing the country element with ISO country codes from the list.
< !ELEMENT country (#PCDATA)>
< !ATTLIST country ISOAlpha3 CDATA<br /> ISONumeric3 CDATA>
1)Add an element for ISOcontry code with reference to two different types,one alpha & one numeric.
2)Separate the country element from address
3)Define element of name ISOAlpha3 and ISONumeric3
4)Define attributes of name ISOAlpha3 and ISONumeric3 subordinate to the country element.

What are the ISO country codes?
Cheers
shyam

Originally posted by Kelly Aus:
Dear Shyam,
First of all sorry for being so late! Actually I met with an accident and was on bed for more than a month and thus didn't participate on this forum. Also my email-id is no more valid as it has been blocked.
As far as your queries are concerned Mapraputa has answered them extremely well! Thanks Mapraputa!!! as far as the following point is concerned:
3)It is recommended to go for single step XSL tranformation when processing logic is highly interrelated.
When to go for multistep tranformation?
is concerned...even I haven't used multistep transformation as yet but from what I have read till now it is required to maintain intermediate steps of the transformation for understanding and maintainability. It is similar to breaking a large procedure into smaller methods for better comprehension.
Hope it helps.
Please let me know if there is anything else I can do to help.
Regards
Kelly

[shyam yengantiwar]

Dear Maraputra Is,
I hope you are in good health.
I have some doubts in following questions.I am giving different online free tests before going to final IBM test.These questions are from such tests in which I have doubts.If possible please give me the correct answers.
Cheers
SHYAM
#Which is the valid attribute declaration when attribute
values can contain "general entity" reference?
1)< !attlist myelement myattribute="myentity">
2)< !attlist myelement myattribute="&myentity;">
#Which is the valid attribute declaration when attribute values
can contain "external entity reference" reference?
1)< !attlist myelement myattribute="myentity">
2)< !attlist myelement myattribute="&myentity;">
#Is it a correct declaration?
< !ENTITY &&USA&& "United States of America">

#When is a multistep XSL transformation step preferable?
1)When processing logic is highly modular
2)When processing logic is highly interrelated
3)When XML documents are extremely large
4)When XML documents are extremely small
5)None of the above
#waht is true about xsl:variable and xsl aram
1)The xsl:variable is limited to a single style sheet.
2)The scope of the xsl:variable has no defined limit.
3)The scope of the xsl:variable is limited to the entire style
sheet.
4)None of the above
#Which one of the following is a possible implementation for a
component that converts web-based form data to XML transaction
data on the server?
1)Server-side C++ program
2)Java servlet
3)Perl script
4)Java applet

#True/false
when preparing for a B2B XML transaction or message between
collaborative partners & cerating a corresponding DTD for
validation,it is best practice(considering flexibility)to
define an enumerated attribute to represent contry codes.(as a
predefined list of static valid values)
My guess is "true"

#Is this content model allowed?
< !element Customer ((LastName, Ship-to-address) & LastName,Bill-<br /> to-address)>
for the following question I guess option 2 & 3 are not correct.I am confusing between 1 & 4.Which one is correct according to you?Please give the explanation.
#"Country"is intended to imply a text name (as in"united states of america").If author want to describe "country" according to the ISO 3166 country code standard (3 character alpha code & 3 digit numeric code)
Select the best solution for describing the country element with ISO country codes from the list.
< !ELEMENT country (#PCDATA)>
< !ATTLIST country ISOAlpha3 CDATA<br /> ISONumeric3 CDATA>
1)Add an element for ISOcontry code with reference to two different types,one alpha & one numeric.
2)Separate the country element from address
3)Define element of name ISOAlpha3 and ISONumeric3
4)Define attributes of name ISOAlpha3 and ISONumeric3 subordinate to the country element.

#What are the ISO country codes?
#What are the different approaches to predict the depth of the documents structure?
SHYAM

Originally posted by Mapraputa Is:
s y, unfortunately your name does not comply with the JavaRanch naming policy. We require names to have at least two words, separated by a space, and strongly recommend that you use your full real name. Please spare a moment and re-register with a name that meets the requirements.
Now I'll try to answer your questions.

1. What are the most important componants of DTD development environment?
Flat file editors
What are the most important componant of XML development environment?
Flat file editors also XML is just a plain text, so any text editor would suffice. There are a lot of specialized XML editors, or even IDE, which provide extra functionality, like hierarchical view or checking an XML instance against DTD, but it is not necessarily. From the other hand, XML is data format and as such is designed to be used by some program. To be used it should be parsed, so we need a parser. But if you ask only about "XML development" - then flat file editors.
2)What the "XML test cases" are supposed to exercise/contain?
According to IBM mock, XML test cases should
1.be derived or taken from real data
2.exercise the most probable error conditions to be expected when the system is used
3.exercise all the important element contexts and content variations to be handled by the system
3)It is recommended to go for single step XSL tranformation when processing logic is highly interrelated. When to go for multistep tranformation?
Frankly, I never had to apply multistep tranformation, maybe those who hasmore experience can put more light here
4)Is it possible to convert SCHEMA to DTD?
Yes, with possible loss of information. Schemas provide far more elaborated verification features, so it is very likely that some of them will be lost in " Schema to DTD" conversion.
5)Can we use both XSL & CSS in one stylesheet?
Yes. There are many issues involved in such marriage, you can read more here: http://www.xml.com/pub/a/2000/03/08/style/index.html http://www.xml.com/pub/a/2000/06/21/deviant/index.html
6)true/false
It is standard practice to use either XSL-FO or CSS for formatting a document,but not both simultaneously.
"XSL flow objects use CSS properties, so CSS is an integral part of the XSL formatting story. In addition, there's been considerable effort expended to make sure that a common formatting model is developed. This will allow people to learn a single display semantic and apply it equally well to CSS and XSL in the projects where each is appropriate."
Norman Walsh. The XSL Debate: One Expert's View http://www.xml.com/pub/a/1999/06/xsl_edit.html
"If we leave XSLT apart for the moment (since it can be used with CSS as well as with XSL Formatting Objects), then CSS is the 80% solution, XSL(FO) the high-end tool for the next 15%. The remaining 5% needs real programming.
On the scale between capabilities, usability, and ease of implementation, CSS stresses usability, then implementation, and is willing to limit its powers. XSL is the reverse. In other words: CSS should be accessible to everybody, XSL should be able to do almost anything.
XSL and CSS: One Year Later
by Leigh Dodds
June 21, 2000 http://www.xml.com/pub/a/2000/06/21/deviant/index.html
7)What is the input to XSLT?
XML file & XSL file
or Dom tree & xsl file
Answer: a hierarchical tree representing an XML document - typically DOM tree. XSLT transformation requires:
"- parser (typically DOM parser): read a document and transform it into tree repsesentation
- XSLT processor: receive �a hierarchical tree representing an XML document� as an input, transform it, and produce another hierarchical tree.
- ff there is a need to produce a file, than a serializer is called."

[This message has been edited by Mapraputa Is (edited November 18, 2001).]

[shyam yengantiwar]

Dear Kelly,
I hope you are in good health.
I have some doubts in following questions.I am giving different online free tests before going to final IBM test.These questions are from such tests in which I have doubts.If possible please give me the correct answers.
Cheers
SHYAM
#Which is the valid attribute declaration when attribute
values can contain "general entity" reference?
1)< !attlist myelement myattribute="myentity">
2)< !attlist myelement myattribute="&myentity;">
#Which is the valid attribute declaration when attribute values
can contain "external entity reference" reference?
1)< !attlist myelement myattribute="myentity">
2)< !attlist myelement myattribute="&myentity;">
#Is it a correct declaration?
< !ENTITY &&USA&& "United States of America">

#When is a multistep XSL transformation step preferable?
1)When processing logic is highly modular
2)When processing logic is highly interrelated
3)When XML documents are extremely large
4)When XML documents are extremely small
5)None of the above
#waht is true about xsl:variable and xsl aram
1)The xsl:variable is limited to a single style sheet.
2)The scope of the xsl:variable has no defined limit.
3)The scope of the xsl:variable is limited to the entire style
sheet.
4)None of the above
#Which one of the following is a possible implementation for a
component that converts web-based form data to XML transaction
data on the server?
1)Server-side C++ program
2)Java servlet
3)Perl script
4)Java applet

#True/false
when preparing for a B2B XML transaction or message between
collaborative partners & cerating a corresponding DTD for
validation,it is best practice(considering flexibility)to
define an enumerated attribute to represent contry codes.(as a
predefined list of static valid values)
My guess is "true"

#Is this content model allowed?
< !element Customer ((LastName, Ship-to-address) & LastName,Bill-<br /> to-address)>
for the following question I guess option 2 & 3 are not correct.I am confusing between 1 & 4.Which one is correct according to you?Please give the explanation.
#"Country"is intended to imply a text name (as in"united states
of america").If author want to describe "country" according to
the ISO 3166 country code standard (3 character alpha code & 3
digit numeric code)
Select the best solution for describing the country element
with ISO country codes from the list.
< !ELEMENT country (#PCDATA)>
< !ATTLIST country ISOAlpha3 CDATA<br /> ISONumeric3 CDATA>
1)Add an element for ISOcontry code with reference to two
different types,one alpha & one numeric.
2)Separate the country element from address
3)Define element of name ISOAlpha3 and ISONumeric3
4)Define attributes of name ISOAlpha3 and ISONumeric3
subordinate to the country element.

#What are the ISO country codes?
#What are the different approaches to predict the depth of the documents structure?

SHYAM

Originally posted by Kelly Aus:
Dear Shyam,
First of all sorry for being so late! Actually I met with an accident and was on bed for more than a month and thus didn't participate on this forum. Also my email-id is no more valid as it has been blocked.
As far as your queries are concerned Mapraputa has answered them extremely well! Thanks Mapraputa!!! as far as the following point is concerned:
3)It is recommended to go for single step XSL tranformation when processing logic is highly interrelated.
When to go for multistep tranformation?
is concerned...even I haven't used multistep transformation as yet but from what I have read till now it is required to maintain intermediate steps of the transformation for understanding and maintainability. It is similar to breaking a large procedure into smaller methods for better comprehension.
Hope it helps.
Please let me know if there is anything else I can do to help.
Regards
Kelly

[Mapraputa Is]

Ok, I did some more research on "multi-step transformation". The best source I found is Jeni Tennison's new book "XSLT and XPath On The Edge" - that's a really good book! She calls it "multiple transformations". You can achieve it either within the same stylesheet, in which case you need to save intermediate result somewhow and then apply the next transformation (she also calls it "filter"), or by chaining multiple stylesheets. As far as I understood, XSLT 1.0 spec doesn't provide any temporary storage of "XML tree" type, but XSLT 1.1 does. So you have either to use XSLT 1.1 compliant processor, or to rely on proprietary extension functions, such as node-set(). In both cases your stylesheet will not be portable.
Memory is another issue. If you use "multi-step transformation" within the same stylesheet and keep temporary results, memory usage is increased, that means you do not want to do it on client side.
Another possibility is to have a separate stylesheet for each "step" and chain/pipe them, so the output of the first will be an input for the second etc.
In any case, "multi-step transformation" makes sense when we need to perform independent tasks.
I also have an alternative explanation why one may consider a chain of transformations. XSLT is a functional language, and "functional" paradigm is quite different from procedural or object-oriented. Until you get used to it, programming is difficult and often you may feel that there is simply no way to do what you want to do. In this case you can goof away and resort to "multi-step transformation" instead of figuring out a way to code your algorithm withing one step. But this is probably not the answer IBM-140 exam expects from you .

[shyam yengantiwar]

Dear maraputra
Thank you for the efforts.
Have a great day.
SHYAM

Originally posted by Mapraputa Is:
Ok, I did some more research on "multi-step transformation". The best source I found is Jeni Tennison's new book "XSLT and XPath On The Edge" - that's a really good book! She calls it "multiple transformations". You can achieve it either within the same stylesheet, in which case you need to save intermediate result somewhow and then apply the next transformation (she also calls it "filter"), or by chaining multiple stylesheets. As far as I understood, XSLT 1.0 spec doesn't provide any temporary storage of "XML tree" type, but XSLT 1.1 does. So you have either to use XSLT 1.1 compliant processor, or to rely on proprietary extension functions, such as node-set(). In both cases your stylesheet will not be portable.
Memory is another issue. If you use "multi-step transformation" within the same stylesheet and keep temporary results, memory usage is increased, that means you do not want to do it on client side.
Another possibility is to have a separate stylesheet for each "step" and chain/pipe them, so the output of the first will be an input for the second etc.
In any case, "multi-step transformation" makes sense when we need to perform independent tasks.
I also have an alternative explanation why one may consider a chain of transformations. XSLT is a functional language, and "functional" paradigm is quite different from procedural or object-oriented. Until you get used to it, programming is difficult and often you may feel that there is simply no way to do what you want to do. In this case you can goof away and resort to "multi-step transformation" instead of figuring out a way to code your algorithm withing one step. But this is probably not the answer IBM-140 exam expects from you .