URL for chart of workflow and metadata

Hello all,

Per my action item from our last call, I have created a sheet (http://bit.ly/HB2OtK) that shows the which parts of the model workflow consume, generate, or pass through specific metadata items, as defined below:

consume: the process requires this metadata item for its functionality
generate: the process produces this metadata as an output of its functionality
pass through: the process does not directly use the metadata for its functionality but may be required to transform it in some fashion (e.g., an XLIFF transformation may read in the translate attribute and change it into a native representation).

If a space is blank (grayed out) it either means that it doesn't apply or that the process simply should not touch any existing instances of the metadata category. (It may also mean “I don’t know” so do not assume that a blank means anything positive.

I fully expect that my categorization is off, so please feel free to edit. To edit, simply add an "x" to a cell you want to enable.

(In order to prevent problems from having an editable URL exposed to the public (and thus potentially encouraging spammers to mess things up), I will send an editing link to the Partners list. Anyone who doesn't get that but would like to edit, please let me know and I will send you a link directly.)

A few notes:

I think that the scenario here is probably missing a few steps (like integration of QA/revision with existing linguistic resources). I did add a few that weren't covered, but we may want to add more.
I'm really quite uncertain about what to put in these two sections: Annotate w/process & qual data, Annotate provenance of lang. res. Anyone who knows more than I do, please feel free to fix those columns
I know I really should use the wiki for this, but editing and maintaining the content as HTML code in the wiki would be almost impossible. When we have a final working version, I will be happy to do a *ONE-TIME* conversion into HTML code for the wiki, but I do not want to make a habit of working with that HTML code or cleaning it up if it gets broken (which it would, given the complexity). If there is another easy-to-use resource for maintaining this that I should use (other than a Google doc), please let me know.
Best,

Arle