Status report: Using issue tracking systems

[MURATA Makoto (FAMILY Given)]

Dear colleagues,

I have studied how we can use issue tracking systems for our 
work.  In particular:

A) Automatically extracting DR information from the DR Log of the 
   project editor and storing it in issue tracking systems

B) Providing links from issue tracking systems to the DR log file

C) Providing links from issue tracking systems to web pages for schema diffs

D) Associating files with DRs

I am inclined to use the Assembla ITS together with subversion.

The Assembla REST API allows A).  I plan to write a program in F#.

B) is a bit tricky, since PDF files or Word files do not provide
fragment identifiers.  (application/pdf actually provides fragment
identifiers, but the implementation is not great.)  I think that the
best solution is to create an HTML file from the latest DR log.  The
program for storing DR information into the Assembla ITS should embed
an URI followed by a fragment identifier for the DR.

Note: Does OOXML provide fragment identifiers?  They should be 
very useful.

We can achieve C) by typing "re #<chiketNumber>" when we commit
schemas.  We have to make sure that we commit with the right timing.
In other words, the correspondence between a commit action and a DR
should be one-to-one.  At least, one commit action should not 
cover more than one DR.

The Assembla ITS allows D).  Since we often create PDF files for the
discussion of DRs, I believe that D) is very useful.


Regards,

SC34/WG4 Convenor
MURATA Makoto (FAMILY Given)