RE: [dita] Standard DITA processing instructions?

["Grosso, Paul" <pgrosso@ptc.com>]

Andrzej,

Perhaps you could give us a specific URL.  

Just surfing around I saw nothing that seemed relevant, and
a search on that web site for "processing instruction" failed, 
and a search for "change tracking" and "change markup" didn't
return anything that seemed immediately relevant.

paul
 

> -----Original Message-----
> From: Andrzej Zydron [mailto:azydron@xml-intl.com]
> Sent: Saturday, 2009 October 10 8:16
> To: Su-Laine Yeo
> Cc: rob@ascan.ca; Ogden, Jeff; Michael Priestley; Park Seth-R01164;
> dita
> Subject: Re: [dita] Standard DITA processing instructions?
> 
> Hi Su-Laine,
> 
> A standard for this already exists:
> 
> http://www.lisa.org/XML-Text-Memory-xml.107.0.html
> 
> Best Regards,
> 
> AZ
> 
> Su-Laine Yeo wrote:
> >
> > (Merging threads)
> >
> > Using PIs for change tracking makes sense, and standardization of
> > change-tracking markup across tools would also be beneficial to XML
> > users if it were possible. I don't know the extent to which it would
> > be possible.
> >
> > However, I don't see the use of PIs for change tracking as being a
> > DITA-specific issue at all. Tool developers would be much more
> > motivated to standardize change-tracking markup across tools if they
> > only have to do it once for all XML dialects. I doubt that the
> > change-tracking issues are any different for Docbook or XHTML or
> > S1000D, however if we're not the only dialect-specific TC to look
> into
> > this issue then in theory the TCs for different dialects could come
> up
> > with different standards, and that would be a problem. Is there a
> more
> > general TC that could address change-tracking markup?
> >
> > Su-Laine
> >
> > *Su-Laine Yeo*
> > Interaction Design Specialist
> >
> > *JustSystems Canada, Inc.
> > *Office: 778-327-6356
> > syeo@justsystems.com <mailto:syeo@justsystems.com>
> >
> > www.justsystems.com <http://www.xmetal.com>
> >
> > *From:* Park Seth-R01164 [mailto:seth.park@freescale.com]
> > *Sent:* Monday, October 05, 2009 9:30 AM
> > *To:* dita
> > *Subject:* RE: [dita] Standard DITA processing instructions?
> > *Importance:* Low
> >
> > I've captured some information about this suggestion in the DITA
> wiki:
> >
> > http://wiki.oasis-open.org/dita/DitaProcessingInstructions
> >
<BLOCKED::http://wiki.oasis-open.org/dita/DitaProcessingInstructions>
> >
> > After my arch spec responsibilities are completed, I'll try to
> > formalize this request/idea in a way that can be actionable.
> >
> > -seth park
> >
> > *From:* Rob Hanna [mailto:rob@ascan.ca]
> > *Sent:* Friday, October 02, 2009 1:48 PM
> > *To:* 'Ogden, Jeff'; 'Michael Priestley'; 'Park Seth-R01164'
> > *Cc:* 'dita'
> > *Subject:* RE: [dita] Standard DITA processing instructions?
> >
> > I suggest that the real differentiator should be whether the item is
> > useful, persistent, human-readable metadata or if simply transitory
> > machine-readable data. The former managed as elements and attributes
> > and the latter managed as PIs.
> >
> > I think change tracking is very transitory and of little value as
> > human-readable metadata (unlike change history or review comments
> > which are human-readable). Change tracking really has little value
> > outside of the editing environment. Change bars and other change
> > tracking marks do not usually persist beyond a single revision.
> >
> > For what it is worth, I think this is a good use of PIs.
> >
> > Cheers,
> >
> > Rob Hanna
> >
> > *From:* Ogden, Jeff [mailto:jogden@ptc.com]
> > *Sent:* October 2, 2009 2:23 PM
> > *To:* Michael Priestley; Park Seth-R01164
> > *Cc:* dita
> > *Subject:* RE: [dita] Standard DITA processing instructions?
> >
> > I think the DITA TC could include discussion of "DITA standard PIs"
> in
> > the spec.
> >
> > I think having something standard for change tracking would be a
good
> > thing, but I wonder if that might not be better done in a way that
> > would work for DITA and non-DITA document types. And if you buy into
> > that, the question is what group would be a good one to work on it?
I
> > guess it could be a recommendation from the DITA TC that had wider
> > application than just DITA, but I can imagine that there may be some
> > other group that might be appropriate and willing to do that work
> too.
> >
> > I think you have to look at using PIs vs. more traditional
> > element/attribute markup on a case by case basis.
> >
> > An advantage of PIs is that implementations that don't understand or
> > support a particular PI should ignore them. That isn't as true for
> > element markup.
> >
> > In the case of change tracking, I think there could be some real
> > advantages to using PIs.
> >
> > -Jeff
> >
> > *From:* Michael Priestley [mailto:mpriestl@ca.ibm.com]
> > *Sent:* Friday, October 02, 2009 2:12 PM
> > *To:* Park Seth-R01164
> > *Cc:* dita
> > *Subject:* Re: [dita] Standard DITA processing instructions?
> >
> >
> > 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
> >
> 
> --
> email - azydron@xml-intl.com
> smail - c/o Mr. A.Zydron
> 	PO Box 2167
>         Gerrards Cross
>         Bucks SL9 8XF
> 	United Kingdom
> Mobile +(44) 7966 477 181
> FAX    +(44) 1753 480 465
> www - http://www.xml-intl.com
> 
> This message contains confidential information and is intended only
for
> the individual named.  If you are not the named addressee you may not
> disseminate, distribute or copy this e-mail.  Please notify the sender
> immediately by e-mail if you have received this e-mail by mistake and
> delete this e-mail from your system.
> E-mail transmission cannot be guaranteed to be secure or error-free as
> information could be intercepted, corrupted, lost, destroyed, arrive
> late or incomplete, or contain viruses.  The sender therefore does not
> accept liability for any errors or omissions in the contents of this
> message which arise as a result of e-mail transmission.  If
> verification
> is required please request a hard-copy version. Unless explicitly
> stated
> otherwise this message is provided for informational purposes only and
> should not be construed as a solicitation or offer.
>