This wiki has undergone a migration to Confluence found Here
Publishing Facilitator Responsibilities
Revision as of 20:36, 11 February 2009 by Astechishin (talk | contribs) (New page: {{V3 Pub Closed Issue}} ==Introduction== What is required of a Publishing Facilitator? ==Discussion== The formal list of responsibilities was discussed and approved on [[V3_Publishing_C...)
|
This page documents a Closed, fully actioned V3 Publishing Issue, i.e. an issue requiring a resolution from V3 Publishing. |
Introduction
What is required of a Publishing Facilitator?
Discussion
The formal list of responsibilities was discussed and approved on V3 Pub conference call Mar 5, 2008
Resolution
As per the above minutes:
- Committees should use the message model walkthroughs (DMIMs and RMIMs) to document high-level model concepts. This can include classes (usually groups of clone classes), associations, business concepts, usage requirements, and business processes to which this message is relevant. The walkthrough is expected to be a few paragraphs at most.
- Message model class and attribute-level documentation shall be provided for each clone class and for all attributes (except for structural attributes which have fixed values in the model being documented). This shall include a description of each class and attribute (with the exception above). Best practice will be to include the rationale for the inclusion of this class/attribute in the model.
