← Prev in month
← Prev in thread
[office] Work Packages Proposal
Hello all, One of my action items was to suggest work packages. To do so, I proceeded as follows: I have extracted all element names from the base DTD. I then grouped those into chapters representing 'conceptual' units that make sense to be convered together. Each (sub-)chapter then would constitute a work packages. I have added some comments where I felt my choices needed explanation. A problem with the 'conceptual' units is that the amounts of time per package may differ widely; this must be taken into account when using them as basis for planning. Note that the work packages strictly follows the existing base specification. It doesn't include any of the other first phase issues, such as defining extension mechanisms and policies. [1] Also, you will no doubt notice that I cheated in a few spots: There are some chapters labeled 'Other ...', which really means I'm not quite done with the grouping. :-P Without preempting Michael's prerogative to set the meeting agenda, I would suggest that we start with chapter one (essentially, the top-level structure of the document, without the document details). We've got to start somewhere... :-) Sincerely, Daniel [1] ...which I expect to be a rather controversial topic: Users and the content management crowd will almost certainly prefer general and powerful extensibility. As an applications person, however, I'm well aware that very general extensibility is easy to define but basically impossible to implement in an office app. The challenge is to find something implementable, which is good enough and powerful enough for the users.
← Prev in month
← Prev in thread