OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

humanmarkup message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: TC.Projectplan: Administrative Roles: Editor

Let me pass this to you all before posting, just to insure it seems to be reasonable (with thanks to Joseph, who's template I stole):
TC.Projectplan:  Administrative Role: Editor
Editor: Kurt Cagle
September 28, 2001
Adminstrative Roles
I) Role 1: To Create, Maintain, and Edit All Formal Documentation Pertaining to the HumanML TC. Editor will:
 a) assure that documents shall be free of copyrights and any form of legal encumbrances
 b) assure that documents are in apppropriate and consistent formats (currently text, soon XML and XHTML).
 c) integrate materials coming into the TC by members and observers with the existing documentation
 d) annotate materials to reflect points of contention or versioning issues, and change documents to incorporate changes resulting from these, when approved by the TC.
II) Role 2: Define Norms and Standard Methodologies for Documentation Consistency. Editor will:
 a) guarantee that all documents submitted conform to relevant schemas.
 b) develop style documents for displaying documentation and retrieving relevant content.
 c) work with the Web Manager to insure documentation is properly linked and reachable.
 d) work with the R&D Manager to insure that applications and application documentation are consistent and conformant with standards over time.
 e) All submissions, revisions, and proposed changes shall conform with the Specifications set forward by the HumanMarkup Technical Committee
 f) Maintain versioning information to insure that the documentation is both current and can be audited.
IV) Role 4: To Provide Support and Outreach to Outside Communities. Editor will:
 a) Work with other TC Editors to insure that documentation standards are consistent with OASIS, W3C, IETF and other standards bodies, as appropriate.
 b) Make schemas and stylesheets available to other OASIS editors for their use as needed.

1) Move current documentation to XML format
2) Develop stylesheets and schemas for the display of such documents.
3) Create archive of discussion summaries for Phase 1 of HumanML development.
***More specific deliverables TBA***


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC