Hi,

On Wed, 16 Sep 2009 10:04:22 -0400, Matt Whipple <[email protected]>
wrote:
> Florent André wrote:
[[...]]
>> - So, for you, what is the main advantage of the DITA format in front of
>> possibilities offer by other html,xhtml,... format ? 
>>   
> This is not supposed to be an advertisement, and I apologize if this bit 
> is wandering OT
Year ! Sure not an advertisement, just a question from a DITA's newbee to
an expert !:)

> 
> To briefly repeat what you've likely read (and for others): the 
> topic-based structuring of DITA allows for modular creation of data 
> (with some advanced selection, automatic referencing etc.).  This allows 
> for comprehensive user documentation to be quickly produced by 
> assembling background information from preexisting files which can then 
> be slightly tailored and built on top of.  Any changes are also easily 
> propagated through all of the documentation which uses the files, easing 
> maintenance. 
> 

During my reading, I also like this concepts : 
- Topic orientation
- transclusion
- Conditional text

I already think to something like that... Now I have to try DITA on
concrete example to decide if I love it ! :)

[[...]]
>> - What kind of usecase do you imagine for the DITA/Lenya couple ?
>>   
> I'm primarily interested in the fairly simple use of Lenya to manage the 
> DITA source (XML) files.  Allowing an interface to easily create/modify 
> the files according to their schema (ported to RelaxNG), and maintain 
> the file structure.  I would handle the creation of distributables using 
> Lenya-less  Cocoon, which could then be incorporated back into Lenya to 
> provide previews or other relevant functionality. 
> 
> My personal goal is to use Lenya to manage the files to be used outside 
> of Lenya; the optional driving of Lenya using DITA files could follow 
> (bringing some advantages with it) that but would likely require 
> significantly more time (which I likely wouldn't spend unless the 
> project gains momentum).  I would think this could be beneficial to 
> Lenya as a whole also since it brings inherent information logic which 
> could smoothly carry into publications. This would enable things like 
> well structured sites to be automagically created from topics which 
> remain focused on the data.

Yes, it seems to be a really good project/idea. Please keep in touch, I'm
really interesting in, if I have some time I will be glad to give an hand.

Where are you now in the dev ? 

> 
>> ---------------------------
[[...]]

>> If you have another example, simple tutorial, cool information,... I
will
>> be glad to read them.
>>
>>   

I find a french page with some interesting english links at the bottom.

> Because it has yet to be widely adopted, there doesn't seem to be an 
> abundance of user information.  If you're looking for a good overview 
> and want to kill some time, the videos at the link below cover all the 
> basics.
> 
>
http://dita.xml.org/dita-introduction-authoring-and-information-architecture-workshop-full-day

Thanks ! You will save me the future fucking raining WE :) 

++

> 
>> have a good day.
>>
>> On Tue, 15 Sep 2009 09:36:40 -0400, Matt Whipple <[email protected]>
>> wrote:
>>   
>>> I've just started to use Lenya and am interested in integrating DITA 
>>> (http://en.wikipedia.org/wiki/Darwin_Information_Typing_Architecture) 
>>> into it.  I've started to work on an initial ResourceType module but am

>>> wondering if there are any existing solutions already out there.  Any 
>>> guidance would be appreciated.
>>>
>>>
>>>     
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>   
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to