Automatically-generated change-tracked schema document (was Re: Upgrading the 29500 DR Processing System)

[MURATA Makoto (FAMILY Given)]

Dear colleagues,

> 2.1 Schema maintenance
> 
> Schemas should be maintained in the subversion repository of Assembla
> rather than changed-tracked MS-Word documents.
> 
> Rex> So long as the schemas are printed in annexes, I *need* to publish
> tracked changes in CORs and Amds to show how those annexes contents are
> changed. So, it is not an "either/or" situation; we need to deal with
> changes in the printed annex versions, and we need to deal with the
> electronic versions. Maybe my current approach can be used for the annexes,
> and assembla for the xsd/rnc file versions.

...

> An issue in the subversion approach (which maintains schema files
> only) is the creation of changed-tracked Word files.  I believe that
> this issue can be addressed by using Word for comparing two DOCX
> documents.
> 
> - Create a DOCX document containg old schemas.
> 
> - Create another DOCX document containing new schemas for the 
>   speficiation in question.
> 
> - Use the file comparison feature of MS Word for generating change-
>   tracked DOCX documents.
> 
> - Incorporaate the change-tracked DOCX documents as part of the 
>   (F)PDAM or DCOR.
> 
> Rex> At a glance, this sounds like a non-trivial process. When considering
> Murata-san's proposal, keep in mind that of the 213 DRs we closed in the
> DCOR1/FPDAM1 sets, only 37 (that is, 17%) involved changes to schema. So, we
> need to keep in perspective how sophisticated a system we really *need* to
> manage this. In any event, I don't recall any other members raising any
> concerns about their inability to do anything schema-related in terms of the
> DR Log machinery.

Attached please find an old schema document (PDF), a new schema document (PDF),
and an automatically-generated change-tracked schema document (PDF). 
They are created using MS Word 2007.  MS Word 2007 will generates
different change-tracked schema documents, if we specify different
options.  For example, it can ignore differences in paragraph formats.

I am sorry that warning message appears in Japanese in my environment.

Regards,

SC34/WG4 Convenor
MURATA Makoto (FAMILY Given)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: TransitionalSchemaRevised.pdf
Type: application/octet-stream
Size: 293886 bytes
Desc: not available
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20090930/a4e4b26f/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: TransitionalSchema.pdf
Type: application/octet-stream
Size: 266407 bytes
Desc: not available
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20090930/a4e4b26f/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ChangeTrackedTransitionalSchema.pdf
Type: application/octet-stream
Size: 381641 bytes
Desc: not available
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20090930/a4e4b26f/attachment-0002.obj>