dita message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [dita] Standard DITA processing instructions?
- From: Michael Priestley <mpriestl@ca.ibm.com>
- To: "Park Seth-R01164" <seth.park@freescale.com>
- Date: Fri, 2 Oct 2009 14:12:12 -0400
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
mpriestl@ca.ibm.com
http://dita.xml.org/blog/25
From:
| "Park Seth-R01164" <seth.park@freescale.com>
|
To:
| "dita" <dita@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
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]