9 messages in org.oasis-open.lists.ditaRe: [dita] Standard DITA processing i...| From | Sent On | Attachments |
|---|---|---|
| Park Seth-R01164 | Oct 2, 2009 11:02 am | |
| Michael Priestley | Oct 2, 2009 11:11 am | |
| ekimber | Oct 2, 2009 11:16 am | |
| Ogden, Jeff | Oct 2, 2009 11:22 am | |
| Rob Hanna | Oct 2, 2009 1:47 pm | |
| Park Seth-R01164 | Oct 5, 2009 9:29 am | |
| Su-Laine Yeo | Oct 9, 2009 6:18 pm | |
| Andrzej Zydron | Oct 10, 2009 6:12 am | |
| Grosso, Paul | Oct 11, 2009 9:12 am |
| Subject: | Re: [dita] Standard DITA processing instructions? | |
|---|---|---|
| From: | Michael Priestley (mpri...@ca.ibm.com) | |
| Date: | Oct 2, 2009 11:11:49 am | |
| List: | org.oasis-open.lists.dita | |
My usual thought is that if we want to standardize it, why make it PIs, which by their very nature cannot be controlled by a schema?
For example, for change tracking there's already some attributes that might be used - but if we wanted something new, we could create a domain specialized from <data> and make it broadly available.
Michael Priestley, Senior Technical Staff Member (STSM) Lead IBM DITA Architect mpri...@ca.ibm.com http://dita.xml.org/blog/25
From: "Park Seth-R01164" <seth...@freescale.com> To: "dita" <di...@lists.oasis-open.org> Date: 10/02/2009 02:04 PM Subject: [dita] Standard DITA processing instructions?
I hope this is not taboo to suggest, but...
Is it in the TC purview to provide a way for DITA application developers to undergo some level of coordination for processing-instructions for common user events?
For instance, if there were a common nomenclature for "change tracking" PI notation, an author, editor, reviewer, and publisher could use the most appropriate tool for his/her specific function and the change tracking feature would work across those different purpose-specific tools.
Something like this would allow DITA files to be exchanged where not only the content is guaranteed to be interoperable, but also commonly used application "features".
bracing for the blow, -seth