OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [dita] Potential new DITA interest area

Forwarding to the list since I noticed that my response went only to Robert ...

From: Kristen Eberlein 
Sent: Monday, October 11, 2010 12:25 PM
To: 'Robert D Anderson'
Subject: RE: [dita] Potential new DITA interest area

I think this would be a great idea; I've been asked several times over the past week about DITA specializations to work with .NET APIs. 

I don't have bandwidth to be involved with another subcommittee, but will forward this e-mail chain to folks I've been talking to.

Additionally, I can see if I can get a sense of how frequently Trisoft customers have built plug-ins to work with APIs.

Best regards,
Kristen James Eberlein l DITA Architect and Technical Specialist l SDL Structured Content Technologies Division l (t) + 1 (919) 682-2290 l keberlein@sdl.com
Please consider the environment before printing this e-mail

-----Original Message-----
From: Robert D Anderson [mailto:robander@us.ibm.com] 
Sent: Monday, October 11, 2010 9:45 AM
To: dita
Subject: [dita] Potential new DITA interest area


We've got a lot of people inside IBM using DITA specializations to mix API
information with other documentation. These specializations have been
released through the DITA Open Toolkit, as a core set of generic API
document types, along with more specialized types specifically for Java.
Nokia recently released an additional set of specializations for C++ based
on the same core set of API modules, and I've gotten a lot of queries about
extending them for other languages.

Is there interest from anybody else on the TC in making these document
types a little more formal? For example, we could start up something like a
"DITA for Programmers" subcommittee that at least works on the core API
Document types, and potentially the extensions into some language specific
modules.  Eventually, I would hope that any approved API modules like this
could be released as independent packages - that is, I would not expect
them to be part of the eventual DITA 1.3 specification itself.

Thanks -

Robert D Anderson
IBM Authoring Tools Development
Chief Architect, DITA Open Toolkit

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:

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]