RE: [dita-adoption] DITA Generator by Elovirta

["Gershon Joseph (gerjosep)" <gerjosep@cisco.com>]

Hi Marc,

I didn't see a response to your question, though may have missed it. I think you can keep the existing work on using the tool to create a new specialization. Perhaps it should be a separate article, so that we have one article focusing on customizing the OOTB DITA elements available by creating a custom shell, with the other article discussing how to use the tool to create a new specialization.

I think an article on how to integrate the tool with 3rd party XML tools is a good idea, but best done outside of OASIS. For example, if you could develop that as a separate article and post it directly on dita.xml.org, I don't think anyone on this TC would have any objections.

Cheers,
Gershon

-----Original Message-----
From: Marc Speyer [mailto:m.y.speyer@inter.nl.net] 
Sent: Tuesday, February 15, 2011 12:45 PM
To: 'DITA Adoption TC'
Cc: 'Joann Hackos'
Subject: RE: [dita-adoption] DITA Generator by Elovirta

Hi JoAnn,

Thanks for the clarifications. Indeed my understanding was to write an
article explaining how the DITA Generator tool could be used as a starting
point for specializations, but as you rightfully mention in your email, the
tool can also be used just to create a shell DTDs with some of the standard
domains removed (e.g. like the scenario you have described). I am glad you
have put me back on the right track (as you know I could not be in the
meeting last year where presumably this scope was discussed) and I will
change the paper accordingly. Do you think I should also address how (well)
the generated shell DTD can be integrated into a few popular authoring
tools, or are we on thin ice again if commercial tools are mentioned?

Best regards,
Marc

>-----Original Message-----
>From: Joann Hackos [mailto:joann.hackos@comtech-serv.com]
>Sent: dinsdag 15 februari 2011 0:18
>To: m.y.speyer@inter.nl.net; DITA Adoption TC
>Subject: Re: [dita-adoption] DITA Generator by Elovirta
>
>Hi Marc,
>I think there is a basic misconception about our interest in the Elovirta
tool.
>We were primarily interested in its capability to create a shell model that
>would remove some of the DITA domains in the standard package.
>
>For example, I might not want the programming domain in my organization,
>because we document hardware, not software. We don't want the writers to
>have to struggle with all the programming domain elements. Or, I might not
>want to use the Learning and Training specialization. The Elovirta tools
allows
>me to select which parts of the full package I want and which parts I don't
>want. Then it creates a new "shell model" that I can reference with my
>authoring tool.
>
>The draft you've written seems to consider the process of defining a
>specialization rather than a shell model. I don't think we want to do that.
>Also, the original idea was to help Elovirta create a more usable interface
for
>DITA beginners and to write some documentation to help people understand
>why and how to use this tool to create shell models.
>
>Let me know if you have questions about the intent of the action item.
>
>Best regards,
>JoAnn
>
>
>On 2/14/11 9:19 AM, "m.y.speyer@inter.nl.net" <m.y.speyer@inter.nl.net>
>wrote:
>
>> Hi everyone,
>>
>> Since this action item was introduced such a long time ago I went back
>> to the minutes to find out about the item I had volunteered to action
>> and found this
>> text: "Marc Speyer volunteered to prepare the initial draft of the
>> reason detre". I have started with an article on the Elovirta DITA
>> Generator tool. I have uploaded a PDF document with what I have so far
>> (setting the scene and
>> TOC) and would appreciate your feedback. I hope to get the article
>> done and present it in our next meeting.
>>
>> Best regards,
>>
>> Marc Speyer


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php