Date   

dita and Epic 5

imknewby <inewby@...>
 

Has anyone gotten dita working with EPIC 5?

I'm getting compilation errors when trying to create a new doc type in
EPIC.

Here's one of the errors:

Dtgen.exe Parser Error:
While parsing file C:&#92;dita&#92;dita13&#92;dtd&#92;topic.dtd:
The varname model token has been used ambiguously within the model of
filepath.
The parser must be able to choose a model token without look-ahead
(err:506 line:78 pos:3253)
Compile failed - rc=32

TIA

Ilana


Re: dita and Epic 5

Don Day <dond@...>
 

"imknewby" <inewby@...> wrote on 06/14/2004 07:15:47 PM:

I'm getting compilation errors when trying to create a new doc type in
EPIC.

Here's one of the errors:

Dtgen.exe Parser Error:
While parsing file C:&#92;dita&#92;dita13&#92;dtd&#92;topic.dtd:
The varname model token has been used ambiguously within the model of
filepath.
The parser must be able to choose a model token without look-ahead
You have run into a content model bug in the dita13 DTDs that I did not
catch when I tested them initially, Ilana. You can find a set of files
that patch this and some other subtle bugs in the zip file in this post:
http://lists.oasis-open.org/archives/dita/200405/msg00026.html

Let me know if you have trouble accessing these files--the OASIS access
policies may require a login. I'll try to upload a more current set in the
files area shortly.

Regards,
--
Don Day
IBM Lead DITA Architect


Re: dita and Epic 5

Don R. Day <dond@...>
 

"imknewby" <inewby@...> wrote on 06/14/2004 07:15:47 PM:

I'm getting compilation errors when trying to create a new doc type in
EPIC.

Here's one of the errors:

Dtgen.exe Parser Error:
While parsing file C:&#92;dita&#92;dita13&#92;dtd&#92;topic.dtd:
The varname model token has been used ambiguously within the model of
filepath.
The parser must be able to choose a model token without look-ahead
You have run into a content model bug in the dita13 DTDs that I did
not catch when I tested them initially, Ilana. You can find a set of
files that patch this and some other subtle bugs in the zip file in
this post: http://lists.oasis-open.org/archives/dita/200405/msg00026.html

Let me know if you have trouble accessing these files--the OASIS
access policies may require a login. I'll try to upload a more
current set into the files area of this list shortly.

Regards,
--
Don Day
IBM Lead DITA Architect


Re: dita and Epic 5

Robin Cover <robin@...>
 

You can find a set of files that patch this and some other subtle bugs...
Let me know if you have trouble accessing these files--the OASIS
access policies may require a login. I'll try to upload a more
current set into the files area of this list shortly.
Meantime, here are two accessible URLs:

http://www.oasis-open.org/committees/download.php/6749/OASIS-DITAsubmission-01.zip
http://xml.coverpages.org/OASIS-DITAsubmission-01-6749.zip

- robin

-----------------------------------------------------
Robin Cover
XML Cover Pages
WWW: http://xml.coverpages.org
ISOGEN: rcover@...
OASIS: robin.cover@...

On Tue, 15 Jun 2004, Don R. Day wrote:

"imknewby" <inewby@...> wrote on 06/14/2004 07:15:47 PM:

I'm getting compilation errors when trying to create a new doc type in
EPIC.

Here's one of the errors:

Dtgen.exe Parser Error:
While parsing file C:&#92;dita&#92;dita13&#92;dtd&#92;topic.dtd:
The varname model token has been used ambiguously within the model of
filepath.
The parser must be able to choose a model token without look-ahead
You have run into a content model bug in the dita13 DTDs that I did
not catch when I tested them initially, Ilana. You can find a set of
files that patch this and some other subtle bugs in the zip file in
this post: http://lists.oasis-open.org/archives/dita/200405/msg00026.html

Let me know if you have trouble accessing these files--the OASIS
access policies may require a login. I'll try to upload a more
current set into the files area of this list shortly.

Regards,
--
Don Day
IBM Lead DITA Architect






Yahoo! Groups Links






notes and tasks

joerg_2712
 

Hy,
can anybody give me a tip?
Sorry, my English ist not the best ;-)

I need a lot of safety notes for use in operating instructions
of machines.
These shall be managing as _topics_ (not as a part of a topic, like
<note>) because they are standardized blocks with a variety of reuse.
They are exported from a special risk management database.
However, these topics must be placed in the context of a task
according to the title and in front of the procedure steps.
They are not part of the prerequesites, because in this context we
describe the operating mode and the position of the components.
Notes are too much different to this contents.

Thanks a lot

Joerg


Re: notes and tasks

Michael Priestley
 

Can you give a concrete example of a safety note and a procedure together?

How much content typically goes in these safety notes? EG a paragraph,
several paragraphs...?

I can think of several options, but not sure which ones are appropriate
without a better understanding of the content.

Michael Priestley
mpriestl@...
Dept PRG IBM Canada phone: 416-915-8262
Toronto Information Development




"joerg_2712"
<ferlein@infodok. To: dita-users@...
de> cc:
Subject: [dita-users] notes and tasks
06/22/2004 09:56
AM
Please respond to
dita-users




Hy,
can anybody give me a tip?
Sorry, my English ist not the best ;-)

I need a lot of safety notes for use in operating instructions
of machines.
These shall be managing as _topics_ (not as a part of a topic, like
<note>) because they are standardized blocks with a variety of reuse.
They are exported from a special risk management database.
However, these topics must be placed in the context of a task
according to the title and in front of the procedure steps.
They are not part of the prerequesites, because in this context we
describe the operating mode and the position of the components.
Notes are too much different to this contents.

Thanks a lot

Joerg







Yahoo! Groups Links


Re: notes and tasks

joerg_2712
 

Hy Michael,

Can you give a concrete example of a safety note and a procedure
together?

(Still) not in DITA ;-)

Generell structure of safety note (see ANSI Z535):
--------------------------------------------------
- Signal word: Danger/Warning/Caution/Note/Tip
- Safety sign (about 40 different signs):
- safety information: Description of hazards and risks.
- List of the measures for the risk minimization.


Examples of safety notes:
------------------------------------
"Sign"
Warning!
Raised or floating load can lead to severe injuries or serious damage
to property!
- Never go under floating load!
- Keep a sufficiently safe distance away!
- Transport parts as closely as possible over the floor!
- Do not reach below the load when lowering!

"Sign"
Warning!
Severe injuries due to fast rotating cutting set are possible.
- Do not reach into the rotating drive shaft or the cutting set.
- If the safty switch is released, switch off main switch and protect
against unauthorized restarting.
- Open hinged grate and outlet housing only when machine and knife
motor are at a standstill.


My proposal for solution of safety notes
----------------------------------------
Specialized topic <safetynote> only with the structure of <note>
- sign as <image>
- safety information as <p> and <ul>

Publishing in a simple table
+---------+-----------------------------------------+
I empty I signal word dependent from type of note I
+---------+-----------------------------------------+
I sign I safety information I
+---------+-----------------------------------------+


Generell structure of task (my idea):
----------------------------------

See DITA TASK specification with little modifications:
Special section <safety> and existing sections prereq / context /
steps / result / postreq with optional <title>-element.
(Suggestions for improvement in DITA-Standard ???)

Important: Safety notes are placed before the procedure steps!


Example of a task without safety notes (in simplified XML/DITA :-))
-------------------------------------------------------------------
<task>
<preqeq>
Select operation mode ...
Stop the infeeding ...

<context>
image of the machine, bla bla bla

<steps>
<step>Let the machine run with some water ...
<step>Switch off the knife motor.
<step>If necessary: Unscrew outlet pipe.
<step>Clean the outlet pipe with a pipe cleaner ...
</steps>

<result>

<postreq>

</task>


task with links to safety notes in XML
--------------------------------------

<task>

<safety>
Link to safety note
Link to safety note
Link to safety note
...
</safety>

<preqeq>
Select operation mode ...
Stop the infeeding ...

<context>
image of the machine, bla bla bla

<steps>
<result>
<postreq>
</task>


Thanks a lot

Joerg


Namespace For DITA?

Eliot Kimber <ekimber@...>
 

I am writing a little DITA importer for my toy content management system XIRUSS-T (xiruss-t.sourceforge.net). XIRUSS only supports schemas (and even if I supported DTDs I wouldn't use DTD external identifiers as document type identifiers as a matter of principal).

My importer framework uses namespaces to associate XML documents with the appropriate processing, so in order to implement automatic recognition of DITA documents a document has to be in the DITA name space. In addition, if a document references a schema the importer will automatically import the schema document if it's not already in the repository.

However, the schemas provided in the IBM DITA 1.3 distribution and the initial OASIS submission don't declare a target namespace.

Is there a normative namespace for IBM DITA? I know that we have not defined one yet for OASIS DITA.

If there's not one then I'll just make one up for my testing purposes.

Thanks,

Eliot
--
W. Eliot Kimber
Professional Services
Innodata Isogen
9030 Research Blvd, #410
Austin, TX 78758
(512) 372-8122

eliot@...
www.innodata-isogen.com


Re: Namespace For DITA?

Don Day <dond@...>
 

Eliot Kimber <ekimber@...> wrote on 06/22/2004 03:30:13 PM:

Is there a normative namespace for IBM DITA? I know that we have not
defined one yet for OASIS DITA.

If there's not one then I'll just make one up for my testing purposes.
There has been no formal work to define one for IBM DITA, Eliot, in part
because specialization tends to put off the need for it except for cases
such as yours. So, go for it... just document somewhere that whatever you
end up with is just a working version, not a formally declared one.

Would you mind pointing the OASIS TC to info on how to formally define
and/or register a namespace for a given DTD? Obviously the TC needs to
wrestle with how a namespace would behave in a specialized document, how a
topic with namespaced content would generalize, etc.. It seems to me to be
a "one DTD, one namespace" framework for now, which doesn't look all that
useful for DITA content, although DITA topics could certainly include
standard namespaced fragments such as SVG or MathML.

Regards,
--
Don Day <dond@...>
Chair, OASIS DITA Technical Committee
IBM Lead DITA Architect
11501 Burnet Rd., MS 9037D018, Austin TX 78758
Ph. 512-838-8550 (T/L 678-8550)

"Where is the wisdom we have lost in knowledge?
Where is the knowledge we have lost in information?"
--T.S. Eliot


Re: notes and tasks

Michael Priestley
 

Hi Joerg,

If the notes are implemented as separate topics that you link to from the
task:


<safety>
Link to safety note
Link to safety note
Link to safety note
...
</safety>

You may not need a specialization of the taskbody to enable this. DITA
supports the separation of links from the body, into the related-links
section, but they can actually be re-sorted on output and placed wherever.
So rather than specializing taskbody to create a link container, you could
customize the processing for taskbody to pull in the safety links at the
right place.

To summarize:

1) create a specialization for authoring safety notes as separate topics,
as you suggest
2) create an override for task processing that pulls links to safety notes
(based on type) into the appropriate place in the task (either before or
after the shortdesc, your call) on output to HTML
3) also override the processing for related-links, to suppress the safety
note links from processing at the bottom when they appear in a task (or let
them repeat there, if the redundancy is ok)

What do you think? Would this be an appropriate approach?

Michael Priestley
mpriestl@...
Dept PRG IBM Canada phone: 416-915-8262
Toronto Information Development


Re: Namespace For DITA?

W. Eliot Kimber <ekimber@...>
 

--- In dita-users@..., Don Day <dond@u...> wrote:





Eliot Kimber <ekimber@i...> wrote on 06/22/2004 03:30:13 PM:

Is there a normative namespace for IBM DITA? I know that we have
not
defined one yet for OASIS DITA.

If there's not one then I'll just make one up for my testing
purposes.

There has been no formal work to define one for IBM DITA, Eliot, in
part
because specialization tends to put off the need for it except for
cases
such as yours. So, go for it... just document somewhere that
whatever you
end up with is just a working version, not a formally declared one.

Would you mind pointing the OASIS TC to info on how to formally
define
and/or register a namespace for a given DTD?
A namespace is just a URI, so it would be up to OASIS to define its
rules for constructing URIs, presumably with the oasis-open.org
domain. The namespace would be "registered" by publishing a
specification that says something like "the namespace 'blah' is the
namespace for the vocabulary 'blarg' as defined in this
specification", as well as publishing a normative XSD schema that
specifies a targetNamespace="blah" attribute.

That is, as far as I know, there is no registrar of name spaces nor
does there need to be one since the name space of namespace names is
already a managed name space (namely the namespace of URIs). As for
SGML public IDs, it's up to the owner of the domain to manage how
URIs within that domain are associated with tag vocabularies and
document types.

Note that the W3C namespace spec itself says nothing about how
namespaces might be formally associated with document types--any such
association must be from the direction of the document type itself.

Obviously the TC needs to
wrestle with how a namespace would behave in a specialized
document, how a
topic with namespaced content would generalize, etc.. It seems to
me to be
a "one DTD, one namespace" framework for now, which doesn't look
all that
useful for DITA content, although DITA topics could certainly
include
standard namespaced fragments such as SVG or MathML.
It's useful in the sense that we have to have a way to formally and
unambiguously identify a given document as being a DITA document, and
namespaces clearly mapped to schemas (and by extensions the abstract
document types they reflect) is the only standard-defined mechanism
we have in the XML world (it could also be done with HyTime
architectures but I'm presuming that HyTime is essentially a dead
standard in this context).

The question of whether DITA needs to define a single namespace or
several is definitely an open question that will have to be taken up
by the DITA TC, at least in the DITA 1.1 time frame, if not before
(it is probably sufficient to define a single namespace for 1.0 as
that reflects what the current DTDs do and doesn't require any change
to the current schemas beyond adding the targetNamespace= attribute
to each schema component involved).

This is probably not a question to discuss in this forum, which is
for users.

Cheers,

Eliot
Innodata Isogen


Re: Namespace For DITA?

W. Eliot Kimber <ekimber@...>
 

--- In dita-users@..., Eliot Kimber <ekimber@i...> wrote:

However, the schemas provided in the IBM DITA 1.3 distribution and
the
initial OASIS submission don't declare a target namespace.

Is there a normative namespace for IBM DITA? I know that we have
not
defined one yet for OASIS DITA.
I subsequently realized that I had also not properly appreciated
the "no namespace" feature of XSD schemas, which the current DITA
schemas use.

However, for my purposes (building an automatic DITA importer within
a content management system) that is not particularly useful since
without a namespace I have no way to know that a given XSD schema
instance happens to in fact be a DITA schema and therefore no way to
know that a given document is in fact a DITA document, with the
importing human providing some out-of-band indication that the
document is in fact a DITA document (and even then I wouldn't be able
to check their assertion).

Therefore, for my testing purposes I just made up a namespace as Don
suggested.

But as a matter of principle, I suggest that nobody should ever
create a schema for use with more than one document instance that
does not also declare the namespace it governs.

Cheers,

Eliot
Innodata Isogen


Re: Namespace For DITA?

Tsao, Scott <scott.tsao@...>
 

--- In dita-users@..., "W. Eliot Kimber" <ekimber@i...> wrote:

A namespace is just a URI, so it would be up to OASIS to define its
rules for constructing URIs, presumably with the oasis-open.org
domain. The namespace would be "registered" by publishing a
specification that says something like "the namespace 'blah' is the
namespace for the vocabulary 'blarg' as defined in this
specification", as well as publishing a normative XSD schema that
specifies a targetNamespace="blah" attribute.
Perhaps a good example is the target namespaces for UBL, see:

http://xml.coverpages.org/ni2004-04-30-b.html#codeListSchemas

e.g.,

targetNamespace="urn:oasis:names:tc:ubl:codelist:AcknowledgementResponseCode:1:0"

Note that they chose to use URN (instead of URL) for the namespace names.

Regards,

Scott


Re: Namespace For DITA?

Eric Sirois
 


From: "W. Eliot Kimber" <ekimber@...>
Date: 2004/06/23 Wed PM 04:10:20 EDT> To: dita-users@...
Subject: [dita-users] Re: Namespace For DITA?

Hi Eliot,

No rework of the schema definitions (*.mod) is needed to support namespaces. We would just define the namespace and targetNamespacein the head schemas (ditabase.xsd, topic.xsd, etc) to support namspacesBecause the XML Schemas depend heavily on subsitution groups we can't add namespaces in the *.mod files because substitution groups only work when element are in the null namespace or same namespcace.

By simply defining a namespace in the head schema the module would assume that namespace (chameloen effect).

The two main reason for *not* including namspaces in the OASIS submission are:
1)XSLT tools - The public package of DITA at developerworks includes a number of XSL stylesheets to process DITA documents into HTML and PDF files. If the XML Schemas had included a namespace all of those tools useless. A complete duplicate of namespace aware set of tools would have been created and maintained for the XML Schemas.


2)Backwards compatibilityRather than modifying all instance documents that would currently be using DTDs for validation, JAXP (Java API for XML Processing) provides functionality to programatically ignore the DOCTYPE declaration and validate against a schema. If a schema had a namespace, then you could always turn off namespace awareness on the parser and get the same results, but you would also loose any information in the xml namespace (xml:lang, xml:space, or xml:base).

Better support for local name template matching is supposed to be part of XSLT 2.0.

General XML Editor woes
Stylus Studio (SS) products use Xerces as their main XML parser. In SS v5.1 you can specify other parsers to validate XML Schemas/DTDs.

The errors reported would be like this:
[Error] task.mod:157:37: rcase-Recurse.2: There is not a complete functional mapping between the particles.
[Error] task.mod:157:37: derivation-ok-restriction.5.3.2: Error for type 'step.class'. The particle of the type is not a valid restriction of the particle of the base.

[Error] task.mod:96:41: rcase-MapAndSum.1: There is not a complete functional mapping between the particles.
[Error] task.mod:96:41: derivation-ok-restriction.5.3.2: Error for type 'taskbody.class'. The particle of the type is not a valid restriction of the particle of the base.

This is documented in the developerWorks package. In General, the parsers will have problems with the schemas. It's not a problem with the schemas per se, but rather with the algorithms defined the XML Schema(XS) 1.0 spec. We are working with our XML Schema WG rep (IBM) on getting this 'fix' into the XS 1.1 spec.

There is way to fix the schemas to avoid these errors, but that would mean not being able to take advantage of XS inheritance architecture. This will affect any applcation using Xerces or MSXML v4.0 as their parser. Some applications that uses their own proprietary parser will not experience these errors. For example, XMLSpy and Syntext Serna. This will affect the validation of the schema and not the valdation of the instance documents. With Xerces, you can validate the instance document without having to validate the schemas. Unfortunately, this is not true for the MSXML parser.

Here is a snippet of an explanation I got from Henry Thompson (from XML Schema WG) regarding the content model errors.

<snip>
I think I now see your problem.

As written, the W3C XML Schema REC tries to define _syntactic_
properties of content models which guarantee a _validation_ semantics
of type subsumption, that is, members of a restricted type must all be
members of its base type. To do this, it basically insists (in
section 3.9.6 [1]) that it be possible to set the components of the
restricted model in a one-to-one correspondence with those in the base
model, with gaps allowed a) where there's a choice and b) where
there's optionality. What it _doesn't_ do is collapse real choices.

Your problem is that if you expand out all the group references,
you've got, in DTD notation

((a|b)|e|(c|d))* as the base,
and
(a|b)* as the restriction

(ignoring the substitution group stuff).

Although it's true that every member of the restriction will be a
member of the base, the rules in REC don't have enough sophistication
to figure that out -- the rules will try to match the restriction's
*ed choice with two branches against the base's one with three
branches, but it's not smart enough to use the _same_ branch from the
base both times, which is what it needs to do to win.

We hope to improve the REC in this area at the next revision, I'm
sorry it's bitten you here.

ht</snip>

I hope this helps.

Kind regards,
EricIBM Canada Ltd.

1


Re: Namespace For DITA?

W. Eliot Kimber <ekimber@...>
 

--- In dita-users@..., <easirois@r...> wrote:

From: "W. Eliot Kimber" <ekimber@i...>
Date: 2004/06/23 Wed PM 04:10:20 EDT> To: dita-
users@...
Subject: [dita-users] Re: Namespace For DITA?

Hi Eliot,

No rework of the schema definitions (*.mod) is needed to support
namespaces. We would just define the namespace and targetNamespacein
the head schemas (ditabase.xsd, topic.xsd, etc) to support
namspacesBecause the XML Schemas depend heavily on subsitution groups
we can't add namespaces in the *.mod files because substitution
groups only work when element are in the null namespace or same
namespcace.

By simply defining a namespace in the head schema the module would
assume that namespace (chameloen effect).

I didn't realize this would work--I was probably thrown off by the
bogus error reports I got from Stylus Studio. This would certainly
simplify things.

The two main reason for *not* including namspaces in the OASIS
submission are:
1)XSLT tools - The public package of DITA at developerworks
includes a number of XSL stylesheets to process DITA documents into
HTML and PDF files. If the XML Schemas had included a namespace all
of those tools useless. A complete duplicate of namespace aware set
of tools would have been created and maintained for the XML Schemas.

This discussion should really be moved to the DITA TC list, but I
imagine that we will need to issue a new set of tools for OASIS DITA
1.0 in any case, so adding namespace awareness could be added to that
code as part of its normal development.

2)Backwards compatibilityRather than modifying all instance
documents that would currently be using DTDs for validation, JAXP
(Java API for XML Processing) provides functionality to
programatically ignore the DOCTYPE declaration and validate against a
schema. If a schema had a namespace, then you could always turn off
namespace awareness on the parser and get the same results, but you
would also loose any information in the xml namespace (xml:lang,
xml:space, or xml:base).

Again, I don't personally think that backward compatibility with the
IBM DITA distribution is a requirement--obviously we'd want to be as
similar as possible, but at least for this issue I would argue that
the value of having a namespace for DITA would far outweigh any
compatibility concerns. For any existing documents that currently use
DTDs that you wanted to move to schemas you'd have to at least add a
targetNamespace= attribute anyway, so also adding a namespace
declaration wouldn't really add any cost. If DITA uses exactly one
namespace then you can just define the DITA namespace as the root
namespace and none of the other tags in instance documents have to be
changed (assuming this was the only change from the IBM distribution).

Cheers,

Eliot
Innodata Isogen


Output of Link with a role of Next using map2html.xsl

imknewby <inewby@...>
 

I have the following syntax in a concept file.

<link href="test.xml" role="next" scope="local" type="concept"></link>

After I run the transform (map2html.xsl) the html includes the
following:

<div><p><b>Next topic
[ColonSymbol]
</b> <a href="test.html" title="">This is a test</a><br
clear="all"/></p></div>

What do I need to do in order to get rid of [ColonSymbol] ?

Is there some kind of entitiy file I need?

TIA

--Ilana


Conref woes

imknewby <inewby@...>
 

Hopefully this will be my last post for a while. I'm trying to use
conref and am not getting the results I want.

testin1.xml contains:
<dita>
<concept id="rss001">
<title>Reference Services and Resources</title>
<conbody>
<section>
<title id="rs001title">Types of Reference Services</title>
....
</section></conbody></concept>
</dita>

test.xml contains:
<dita>
<concept id="rss000">
<title>Reference Services and Resources</title>
<conbody>
<p>After reading this you will know about:</p>
<ul><li><xref conref="testin1.xml#rs001title"
scope="local"></li></ul>
</cobody></concept>
</dita>

I'd like the output of text.xml to grad the title from testin1.xml,
but it doesn't. I've tried various combinations of conref
(e.g.,testin1.xml#/rs001title, testin1.xml#rs001/rs001title)

but nothing works. What's the correct syntax?

TIA,

Ilana


Re: notes and tasks

joerg_2712
 

Hi Michael,

thank you very much for the tips.

You may not need a specialization of the taskbody to enable this.
OK, that's a possibility. However, I think that safety notes are so much important,
that they should be anchored in an special section.

My opinion:
Changing the processing of "related links" is not so nice, because a safety note is
a integrated part of the task. A "related topic" contains additinal but not strong
forcing information for users.

Hyperlinks are the choice for the publishing of related links, but hyperlinks are
very dangerous for the publishing of safety notes.
The different character of the information types is the (my) main reason for the
distinction of related links and safety notes.

I don't understand why this fact isn't implemented in the standard task-definition,
particularly in the USA. The liability and the safety are so much important aspects.
OK, DITA is not specialized but near by the software documentation and the risks are
not so high as the risks in mechanical engineering.

I think, we had to specialize a "d-task" (dangerous task) with a safety-section.

Another reason: Every task can contain real related links, for example to descriptions
of disturbances. If I change the processing of related links, then this applies to all
related links, not for safety notes only. Descriptions as real related links must be placed
after the procedure.

What is your opinion as an experienced technical writer and DITA-architect?

Joerg



Hi Joerg,

If the notes are implemented as separate topics that you link to from the
task:


<safety>
Link to safety note
Link to safety note
Link to safety note
...
</safety>

You may not need a specialization of the taskbody to enable this. DITA
supports the separation of links from the body, into the related-links
section, but they can actually be re-sorted on output and placed wherever.
So rather than specializing taskbody to create a link container, you could
customize the processing for taskbody to pull in the safety links at the
right place.

To summarize:

1) create a specialization for authoring safety notes as separate topics,
as you suggest
2) create an override for task processing that pulls links to safety notes
(based on type) into the appropriate place in the task (either before or
after the shortdesc, your call) on output to HTML
3) also override the processing for related-links, to suppress the safety
note links from processing at the bottom when they appear in a task (or let
them repeat there, if the redundancy is ok)

What do you think? Would this be an appropriate approach?

Michael Priestley
mpriestl@...
Dept PRG IBM Canada phone: 416-915-8262
Toronto Information Development



________________________________________________________________________
________________________________________________________________________



------------------------------------------------------------------------
Yahoo! Groups Links




------------------------------------------------------------------------



processing of maps

joerg_2712
 

Hi,

I am testing the processing of maps and topics. I will create a website
with a toc. I am using the map2WebHTMLTOC.xsl from dita13.
Topic transformation is ok, the output-directory (outputdir) is "html".
The map-file docu.xml was transformed to docu.html, but not in the directory
"html". The HTML-file was stored in the same directory as the XML source file.

The links in the toc are the same as in xml. So the prefix "html" is missing.

XML (MAP)
<map title="Doku" locktitle="yes" toc="yes">
<topicref href="p/21727.xml" title="21727" type="topic" navtitle="21727"/>
<topicref href="p/21728.xml" title="21728" type="topic" navtitle="21728"/>
<topicref href="p/21730.xml" title="21730" type="topic" navtitle="21730"/>
</map>


Created HTML:
<html><head><title>Doku</title></head><body><h1>Doku</h1>
<ul>
<li><a href="p/21727.html" class="topicref">Vakuumfüller P10 SE Typ 59521727</a></li>
<li><a href="p/21728.html" class="topicref">Vakuumfüller P10 SE Typ 59521728</a></li>
<li><a href="p/21730.html" class="topicref">Vakuumfüller P10 SE Typ 59521730</a></li>
</ul></body></html>

Could somebody help me?

Thanks and best regards

Joerg

________________________________________________
Jörg Ferlein

Ringstraße 69
73666 Baltmannsweiler

Tel. 07153 55 74 50
Fax 07153 55 74 51
E-Mail: ferlein@...


Re: Output of Link with a role of Next using map2html.xsl

Don R. Day <dond@...>
 

--- In dita-users@..., "imknewby" <inewby@p...> wrote:

What do I need to do in order to get rid of [ColonSymbol] ?

Is there some kind of entitiy file I need?
This was a case of an internationalized definition in the transforms
that I overlooked to pre-define in the strings.xml file in the
dita13/xsl directory, Ilana.

Try adding the following line under the English set of text
replacement strings in that strings.xml file:

<str xml:lang="en" name="ColonSymbol">:</str>

You can repeat this also for the German and Spanish sample instances
if you wish, changing the xml:lang value to "de" and "es"
respectively. The support is only language-specific at this
time--we'll have to add locale awareness later.

Thanks for reporting this. I'll add this correction to the bug list
for a next update, and will check for other such undefined references
in the transforms.

--
Don Day
IBM Lead DITA Architect