Re: [XXE] Fwd: /n in para of xml file (line length)

[Hussein Shafie]

On 07/01/2015 02:03 PM, Nicolai Andler wrote:

I have the XMLmind XML Editor Professional Edition 6.3.0 on a mac
10.10.3 Yosemite

this is rather urgent, as it causes chaos when parsing the xml files.

the para element has a line break
the line length in the para element is currently limited, _but I need it
unlimited (without a line break)_
there is an 'invisible' line break that is not visible in the xml editor
window ..I used a text editor and display hidden elements to see this
'grey bracket/ para break'
see pic below



I changed the xmlEditor preference (set from 80 to 1000 and untick) and
did a 'save as' over a existing xml file
but the result is even worse as it is now adding new lines in the middle
of the xml tags


see attached xml. file


Some users like the following save options:

1) *Check* "Indent". (All your ``problems'' comes from the fact that you 
have unchecked "Indent".)

2) Set "Indentation" to 0.

3) Set "Max line length" to 10000000 (10 millions; 100 millions; 
something huge)

4) Uncheck "Add open lines".

See attached screenshot.

This will give you something formatted like in attached 
Problem_definition.xml


<?xml version="1.0" encoding="utf-8"?>
<section remap="western" vendor="toolname" version="5.0" xml:id="Problem_definition" xml:lang="en" xmlns="http://docbook.org/ns/docbook"; xmlns:xlink="http://www.w3.org/1999/xlink"; xmlns:xi="http://www.w3.org/2001/XInclude"; xmlns:ns5="http://www.w3.org/2000/svg"; xmlns:ns4="http://www.w3.org/1999/xhtml"; xmlns:ns3="http://www.w3.org/1998/Math/MathML"; xmlns:d="http://docbook.org/ns/docbook";>
<info>
<title vendor="tool_title">Problem definition</title>
</info>
<section remap="western" vendor="Quote">
<title>Quote</title>
<para remap="western"><emphasis>What is the problem? The whole discussion is confusing and overwhelming. </emphasis></para>
</section>
<section remap="western" vendor="Intention">
<title>Intention (Why and when do I use it?)</title>
<mediaobject>
<videoobject>
<videodata fileref="V_problemDefinition1.mp4" width="80%"/>
</videoobject>
<caption>
<para>When to use this tool?</para>
</caption>
</mediaobject>
<para remap="western">Your first diagnose activities as part of a problem solving initiative should ideally be the clear ring-fencing and definition of the problem as well as differentiating between the root cause, the symptoms and the effects. The problem definition is the other diagnosis activities’ point of departure.</para>
<mediaobject>
<videoobject>
<videodata fileref="V_problemDefinition2.mp4" width="100%"/>
</videoobject>
<caption>
<para>What is the problem definition tool about?</para>
</caption>
</mediaobject>
</section>
<section remap="western" vendor="Purpose">
<title>Purpose (What does it do?)</title>
<para remap="western">The problem definition consists of two parts: The preliminary definition of the problem – this is often part of the initial project brief/assignment – and the more detailed structuring and ‘dissection’ of the problem, sub-problems and relevant aspects. This second part is best done with the help of tools such as Problem tree (<xref linkend="Problem_tree"/>) , Hypothesis tree (<xref linkend="Hypothesis_tree"/>) and Issue tree (<xref linkend="Issue_tree"/>)</para>
<mediaobject>
<videoobject>
<videodata fileref="V_problemDefinition3.mp4"/>
</videoobject>
<caption>
<para>The problem definition tool</para>
</caption>
</mediaobject>
</section>
<section remap="western" vendor="Instruction">
<title>Instruction (How do I do it?)</title>
<itemizedlist>
<listitem>
<para remap="list-itemised-western">The main objective of a typical problem definition workshop is the exploration. What is really the problem? Phrase the problem statement in such a way that everybody can comprehend it without further clarifying questions and explanations.</para>
<mediaobject>
<videoobject>
<videodata fileref="V_problemDefinition4.mp4"/>
</videoobject>
</mediaobject>
</listitem>
<listitem>
<para remap="list-itemised-western">Define the current situation and context of the problem and the surrounding aspects with the help of the 7 criteria listed below:</para>
</listitem>
</itemizedlist>
<orderedlist>
<listitem>
<para remap="list-numbered-western"><emphasis role="bold">Point of departure and brief problem description</emphasis>: Describe the current As-Is situation, circumstances and known issues. For example: ‘a 40 % revenue decline in the last 12 months in the core franchise business due to a change in consumer eating behaviour as well as new fast-food franchise competitors.’</para>
</listitem>
<listitem>
<para remap="list-numbered-western"><emphasis role="bold">Project brief</emphasis>: What is the project assignment about? What is the stated objective? Use plain, jargon-free English to describe the initial project objective, which is presumably intended to remedy the problem situation. For example: ‘Grow the US market through the introduction of a new franchise concept in the health(ier)-food sector over the next 12 months.’</para>
</listitem>
<listitem>
<para remap="list-numbered-western"><emphasis role="bold">Decision makers/stakeholders</emphasis>: Who are the sponsors and relevant decision makers of this project (idea)? Who are the stakeholders responsible for the relevant areas? For example: ‘The franchise business development director, CFO, head of market research, etc.’</para>
</listitem>
<listitem>
<para remap="list-numbered-western"><emphasis role="bold">Success factors</emphasis>: What are the prerequisites and assumptions for success? For example: ‘Quick market entry, first-to-market and product-to-market turnaround times.’</para>
</listitem>
<listitem>
<para remap="list-numbered-western"><emphasis role="bold">Performance indicators and decision criteria</emphasis>: What are the criteria and indicators to measure and evaluate the project progress as well as the project outcome? These could be, for example, market share %, productivity increase, cost saving %, revenue, etc.</para>
</listitem>
<listitem>
<para remap="list-numbered-western"><emphasis role="bold">Boundaries and limitations</emphasis>: What are the acceptable ‘go and no-go’ areas for potential solutions and/or the project? What are the existing boundaries, for example, the budget, intellectual property, existing supplier agreements or alliances, immovable assets, etc.? An example of limitations could be that the core business and existing clients mustn’t be cannibalised, while, by the same measure, existing franchisees mustn’t be affected either.</para>
</listitem>
<listitem>
<para remap="list-numbered-western"><emphasis role="bold">Scope</emphasis>: What is included in the problem/project scope and what is ‘out of bounds’? Which areas and aspects, for example, the geographic production sites, products, markets, customer segments, production methods, etc. are included?</para>
</listitem>
</orderedlist>
<itemizedlist>
<listitem>
<para remap="list-itemised-western">Document your findings and conclusion. Make sure that the relevant stakeholders review, approve and sign this document.</para>
</listitem>
</itemizedlist>
<bridgehead>Watch out for those typical mistakes and avoid them:</bridgehead>
<itemizedlist>
<listitem>
<para remap="list-itemised-western">Be cautious with vague statements. Inaccurate descriptions of problems can lead to confusion and will obscure the real picture. Examples of inaccurate problem statements are:</para>
<itemizedlist>
<listitem>
<para remap="list-itemised-western">The employed machines are not efficient.</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Poverty is the issue.</para>
</listitem>
<listitem>
<para remap="list-itemised-western">The training intervention does not work.</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Management is incompetent.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para remap="list-itemised-western">Avoid judging and/or criticising individuals, departments or a specific group of individuals, which causes unnecessary conflicts. Examples of inappropriate statements are:</para>
<itemizedlist>
<listitem>
<para remap="list-itemised-western">Employees are incompetent and unqualified.</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Management refuses to support the initiative.</para>
</listitem>
<listitem>
<para remap="list-itemised-western">The marketing department does not perform and deliver.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para remap="list-itemised-western">Resist the temptation to jump to the solution before properly understanding the problem. Signs of premature conclusions about the causes and the appropriate solution are statements such as “due to the lack of…, inadequate…, inappropriate …, insufficient ….” The example statements below are not problem definitions but rather preconceived opinions about the root causes of the problem and the ‘obvious solution’:</para>
<itemizedlist>
<listitem>
<para remap="list-itemised-western">The lack of appropriate employee training …</para>
</listitem>
<listitem>
<para remap="list-itemised-western">A lack of fertiliser and water pumps for the crop fields …</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Insufficient medical equipment …</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Inappropriate procedural guidelines …</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para remap="list-itemised-western">Avoid falling into the trap of generalising the problem statement and ending up with a ‘one size fits all’ statement which clouds the real circumstances and root causes. Be as specific as possible. Statements like the ones below are not useful:</para>
<itemizedlist>
<listitem>
<para remap="list-itemised-western">“The problem is the bad school education.” – It is better to ask: “What type of schools? In which region? Are there exceptions and, if so, where?”</para>
</listitem>
<listitem>
<para remap="list-itemised-western">“High absenteeism rates are the causes.” – Rather ascertain: “Who and how? Under which circumstances? Where is absenteeism high and where is it low?”</para>
</listitem>
<listitem>
<para remap="list-itemised-western">“High speed driving causes accidents.” – Rather refine and clarify through questions such as: “Where is this true and not true? What are the circumstances and conditions for each? How is this measured? Where is this relevant and where not?”</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para remap="list-itemised-western">The problem (that everybody is talking about) is not always the problem (that you are supposed to address and then resolve).</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Avoid the ‘herd mentality’ and stop following others blindly. You might be tempted to overlook information or select data based on the ‘preconceived group consensus’, which you might be tempted to follow.</para>
</listitem>
</itemizedlist>
<para remap="western"><bridgehead>Guideline for the problem definition:</bridgehead></para>
<itemizedlist>
<listitem>
<para remap="list-itemised-western">Use tangible, measurable facts and figures to illustrate the problem. Instead of maintaining, “The training intervention does not work”, you could say, “60 % of the participants would not recommend this training to their colleagues”. Instead of blaming “inefficient machines”, you could say, “The reject rate of 20 % is too high, hence 20 % of the manufactured parts cannot be used and require costly reworks.”</para>
</listitem>
<listitem>
<para remap="list-itemised-western">When you maintain that behaviour is part of the problem, be aware that you may be inherently subjective. Make sure that you use facts and numbers to ‘prove’ the behaviour that you have observed. Instead of using labels such as “incompetent employees”, rather use tangible statements like, “During the last 2 months, 8 of the 10 employees either submitted their reports late or the reports contained mistakes.”</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Describe the observable problem and do not interpret or provide your suggestion for a solution. For example, “a lack of pesticides” is not the problem, but rather 'the vine fretter, an insect that infests and eats the vines, which then die.' So, don't describe the fact that the presumed solution has not been implemented (a lack of pesticides) as the problem statement. Describe what you can observe.</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Ring-fence the problem and then narrow it down. Pinpointing where the problems are will avoid a ‘one size fits all’ intervention. Identifying where problems occur will help provide insights into the context, practices and malpractices, skills and behaviours of stakeholders. Instead of maintaining, “the problem is the bad school education”, rather define the problem as, “Government high schools in rural areas (villages &lt; 25,000 inhabitants) have a school dropout/truancy rate of 20 % compared to the average of 5 %. 67 % of these pupils have had no form of education or income for at least 18 months.” (Note those facts are just sample statement, not based on actual statistic facts.)</para>
</listitem>
</itemizedlist>
</section>
<section remap="western" vendor="Tips">
<title>Tips and suggestions</title>
<itemizedlist>
<listitem>
<para remap="list-itemised-western">Once you have completed the first snapshot of the problem, continue to refine the problem definition. Use the tools described in detail on the following pages:</para>
<itemizedlist>
<listitem>
<para remap="list-itemised-western">The Problem tree (<xref linkend="Problem_tree"/>) divides the problem into its sub-elements and components and determines the causes and effects. Basically, the problem explores the ‘what’ – what is the problem? What are the root causes and effects? For example, what are the reasons and root causes for the decline in revenue?</para>
</listitem>
<listitem>
<para remap="list-itemised-western">The Hypothesis tree (<xref linkend="Hypothesis_tree"/>) focuses on and builds up an argument or conclusion and helps you test your hypotheses and scrutinise of your assumptions. The tool deals with the ‘why’ – why do we have this problem and (why) are the assumptions regarding the problem and root cause correct? (Why) Should we either increase the sales volume or increase the price to increase the revenue?</para>
</listitem>
<listitem>
<para remap="list-itemised-western">The Issue tree (<xref linkend="Issue_tree"/>) helps with the identification of potential ideas and options to tackle the problem. The tool asks ‘how’ – how can we produce the desired outcome? How can we increase the revenue?</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para remap="list-itemised-western">Use the section on the ‘Mental thinking levels during problem solving’ (<xref linkend="ChapterPS_PS_thinking_levels_types"/>) to remind you of the appropriate instrumental and functional mental focus.</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Many people find problems somehow negative and prefer dealing with the positive and exciting part, which is the solution. Avoid jumping onto the solution-hunting bandwagon when you facilitate such a discussion. Check your subconscious assumptions and beliefs about the problem’s root causes. Which are really facts and which are just your opinions?</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Use the <emphasis role="bold">FOG rule</emphasis>. Distinguish between the following three aspects when, for example, defining a problem. Mark/tag your information with one of the three labels: F, O, G (on the index cards when facilitating a workshop). Or use Post-it® notes of different colours. Then work on transforming opinions and assumptions into facts.</para>
<itemizedlist>
<listitem>
<para remap="list-itemised-western">Facts–are known and accepted facts and realities that can be measured and proven and are undeniably known to be true and accepted. It depends on you and the amount of time you want to invest to prove that your facts are truly facts.</para>
</listitem>
<listitem>
<para>Opinions –are mostly information you find or gather. They are the thoughts of people and have not been verified or proven to be facts, or most people do not consider them to be facts. The biggest problem is that many people believe their opinions are facts. So, distinguish between facts and opinions and clearly mark them as such.</para>
</listitem>
<listitem>
<para>Guesses–are unacknowledged or unproven ideas that are commonly accepted as not being facts, but rather unsafe assumptions. These guesses and assumed information can be the result of a creativity exercise and can sometimes be very valuable and insightful. Don’t ignore the rough diamond! (Source: Straker)</para>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para remap="list-itemised-western">Rational or emotional? There are two thinking dimensions and it is important to know in which one you are operating. Both dimensions are important and valuable, so make sure you ‘cross-pollinate’ and leverage them.</para>
<itemizedlist>
<listitem>
<para remap="list-itemised-western">The rational dimension deals with the structuring, boundaries, logic chains, and identification of drivers, success factors, defects, root causes, effects, etc.</para>
</listitem>
<listitem>
<para remap="list-itemised-western">The emotional dimension examines the following aspects (Source: Haberfellner):</para>
<itemizedlist>
<listitem>
<para remap="list-itemised-western">How did the problem develop?</para>
</listitem>
<listitem>
<para remap="list-itemised-western">What has been done so far?</para>
</listitem>
<listitem>
<para remap="list-itemised-western">What seems to be the problem?</para>
</listitem>
<listitem>
<para remap="list-itemised-western">What would be the best, ideal solution – think blue sky, no limits …</para>
</listitem>
<listitem>
<para remap="list-itemised-western">If you were allowed a pipe dream/wishful thinking, what would this be?</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Where else does the problem lie?</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Is there another way of looking at this?</para>
</listitem>
<listitem>
<para remap="list-itemised-western">What have you not taken into consideration? What is it you are ignoring or not thinking of?</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Don’t forget that each person, department and company is unique. They are not all the same, don’t have the same problems and are not in exactly the same situation.</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Remember: Every individual, area, locality and organisation is unique. Even though there are similarities and patterns, not all of them have the same problems or are in the same situation. Once you have located where the problems lie, start your analysis. Prepare a Problem tree (<xref linkend="Problem_tree"/>) .</para>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para remap="list-itemised-western">The focus and objective of the Problem definition tool is to define the problem. Conceptionally, the equivalent tool focusing on the project definition is, however, the Project contract tool (<xref linkend="Project_contract"/>). Be aware of the potential overlaps illustrated in the ‘Scenario: Good practice for project and problem definition’ (<xref linkend="Scenario_Good_practice_project_problem_definition"/>).</para>
</listitem>
</itemizedlist>
</section>
<section remap="western" vendor="purpose_example">
<title>Example: New business strategy</title>
<bridgehead>Fictitious example of a healthy Fast-Food business strategy - using the problem definition</bridgehead>
<para remap="western"><emphasis role="bold">Problem definition: Successful new strategic business area </emphasis></para>
<informaltable>
<tgroup cols="2">
<colspec colwidth="341*"/>
<colspec colwidth="659*"/>
<tbody>
<row>
<entry><para remap="western">Situation and brief problem description </para></entry>
<entry><para remap="western">40 % revenue decline in the last 12 months in the core franchise business due to a change in consumer eating behaviour as well as new fast-food franchise competitors </para></entry>
</row>
<row>
<entry><para remap="western">Project brief </para></entry>
<entry><para remap="western">Grow the US market through the introduction of a new franchise concept in the health(ier)-food sector over the next 12 months</para></entry>
</row>
<row>
<entry><para remap="western">Decision makers/ stakeholders </para></entry>
<entry><para remap="western">Franchise business development director, CFO, head of market research </para></entry>
</row>
<row>
<entry><para remap="western"> Success factors </para></entry>
<entry><para remap="western">Quick market entry, first-to-market and product-to-market turnaround times </para></entry>
</row>
<row>
<entry><para remap="western">Performance indicators and decision criteria </para></entry>
<entry><para remap="western">Market share of a min. of 25 % in the next 36 months. Break even within 36 months. </para></entry>
</row>
<row>
<entry><para remap="western">Boundaries and limitations </para></entry>
<entry><para remap="western">The core business and existing clients mustn't be cannibalised and, equally, the existing franchisees mustn't be affected either. </para></entry>
</row>
<row>
<entry><para remap="western">Scope (in scope) </para></entry>
<entry><para remap="western">US market, new product development, new production technologies, new franchise concept, new distribution channels </para></entry>
</row>
</tbody>
</tgroup>
</informaltable>
</section>
<section remap="western" vendor="Cross_reference">
<title>Cross-reference to related tools in this book</title>
<para remap="western">Problem tree (<xref linkend="Problem_tree"/>) , Hypotheses tool (<xref linkend="Hypotheses"/>), Hypothesis tree (<xref linkend="Hypothesis_tree"/>) , Reverse the problem (<xref linkend="Reverse_the_problem"/>), Issue tree (<xref linkend="Issue_tree"/>).</para>
</section>
<section remap="western" vendor="Resource_source">
<title>Source</title>
<para remap="western">Straker, Haberfellner, Woodrow</para>
</section>
<section vendor="topics">
<title>Topics</title>
<para>Text</para>
</section>
<section vendor="abstract">
<title>Abstract</title>
<para>Text</para>
</section>
<section vendor="example_exercise">
<title>Example exercise</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
<para>Text</para>
</section>
<section vendor="application_areasC">
<title>Application areas (categories based)</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
</section>
<section vendor="application_areasT">
<title>Application areas (free text)</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
</section>
<section vendor="resource_biblio">
<title>bibliographic sources</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
</section>
<section vendor="resource_rec_lit">
<title>Recommended literature</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
</section>
<section vendor="Resource_other">
<title>other resources</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
</section>
<section vendor="audience_type">
<title>Type of audience/ participants</title>
<para>Text</para>
</section>
<section vendor="audience_size">
<title>Audience size</title>
<para>Text</para>
</section>
<section vendor="Resouce_underpinning">
<title>Theoretical / psychological underpinning of tool</title>
<para>Text</para>
</section>
<section vendor="limitations">
<title>Limitations of the tool</title>
<para>Text</para>
</section>
<section vendor="prerequisites">
<title>Prerequisites</title>
<para>Text</para>
</section>
<section vendor="assumptions">
<title>Assumptions</title>
<para>Text</para>
</section>
<section vendor="mistakes">
<title>Typical mistakes during application</title>
<para>Text</para>
</section>
<section vendor="required_skills">
<title>Required Skills</title>
<para>Text</para>
</section>
<section vendor="emotional_effects">
<title>Emotional side effects</title>
<para>Text</para>
</section>
<section vendor="rating_difficulty">
<title>Difficulty rating</title>
<para>Text</para>
</section>
<section vendor="rating_value">
<title>Value for money rating</title>
<para>Text</para>
</section>
<section vendor="required_equipment">
<title>Equipment/resources required</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
</section>
<section vendor="required_effort">
<title>Estimate of effort/ time</title>
<para>Text</para>
</section>
<section vendor="user_roles">
<title>Applicable user roles</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
</section>
<section vendor="meta_info">
<title>Meta info/ key words</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
</section>
<section vendor="consulting_process">
<title>Consulting process phase</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
</section>
<section vendor="abstraction_level">
<title>Level of abstraction</title>
<para>Text</para>
</section>
<section vendor="cstudy_descrip_a">
<title>Description of solution – based on case study A</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
</section>
<section vendor="cstudy_diagram_a">
<title>Solution diagram based on case study A</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
</section>
<section vendor="cstudy_descrip_b">
<title>Description of solution – based on case study B</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
</section>
<section vendor="cstudy_diagram_b">
<title>Solution diagram based on case study B</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
</section>
<section vendor="cstudy_descrip_c">
<title>Description of solution – based on case study C</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
<para>Text</para>
<figure>
<title/>
<mediaobject>
<imageobject>
<imagedata fileref="???"/>
</imageobject>
</mediaobject>
</figure>
</section>
<section vendor="cstudy_diagram_c">
<title>Solution diagram based on case study C</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
<para>Text</para>
<figure>
<title/>
<mediaobject>
<imageobject>
<imagedata fileref="???"/>
</imageobject>
</mediaobject>
</figure>
</section>
<section vendor="project_examples">
<title>project samples and application examples</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para>sd</para>
</listitem>
<listitem>
<para>sdf</para>
</listitem>
</itemizedlist>
<para>Text</para>
<figure>
<title/>
<mediaobject>
<imageobject>
<imagedata fileref="???"/>
</imageobject>
</mediaobject>
</figure>
</section>
<section vendor="resource_academic">
<title>Other academic references</title>
<para>Text</para>
<para/>
</section>
<section vendor="resource_template">
<title>Template</title>
<para>Text</para>
<para/>
</section>
<section vendor="resource_tutorial_video">
<title>Tutorial video</title>
<para>Text</para>
<figure>
<title/>
<mediaobject>
<imageobject>
<imagedata fileref="???"/>
</imageobject>
</mediaobject>
</figure>
<para/>
</section>
<section vendor="assess_quiz_questions">
<title>Quiz questions for self-assessment</title>
<para>Text</para>
<para/>
</section>
<section vendor="assess_quiz_solution">
<title>Quiz questions master solutions</title>
<para>Text</para>
<para/>
</section>
<section vendor="assess_exam_questions">
<title>Exam questions related to the tool</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
<para/>
</section>
<section vendor="assess_exam_solution">
<title>Master solution for the exam questions</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
<para/>
</section>
<section vendor="text_advert">
<title>Text used for advertising/PR</title>
<para>Text</para>
<para/>
</section>
<section vendor="text_user_feedback">
<title>User feedback/ comments relating to tool</title>
<para>Text</para>
<itemizedlist>
<listitem userlevel="basic">
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text</para>
</listitem>
<listitem>
<para remap="list-itemised-western">Text<emphasis remap="#000000" role="color"> </emphasis></para>
</listitem>
</itemizedlist>
<para/>
</section>
<section vendor="text_user_rating">
<title>User rating of the tool</title>
<para>Text</para>
<para/>
</section>
<section vendor="other">
<title>Other</title>
<para>Text</para>
<para/>
</section>
</section>
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support