Standards Committee: Difference between revisions
Joe.andrieu (talk | contribs) No edit summary |
Joe.andrieu (talk | contribs) (switched language from use cases to Services, reflecting current usage) |
||
| Line 6: | Line 6: | ||
The near term strategies of the standards committee are three-fold: | The near term strategies of the standards committee are three-fold: | ||
#Create a public mailing list for VRM tech issues | #Create a public mailing list for VRM tech issues | ||
#Work on VRM [[Services]], starting with the Change of Address | #Work on VRM [[Services]], starting with the [[Personal Address Manager Service]], which started life as the Change of Address Use Case at IIW2007b. | ||
#Develop an organizational capability in creating and working with use cases | #Develop an organizational capability in creating and working with use cases | ||
Revision as of 01:22, 16 March 2008
The objective of the Standards Committee is to Ensure the Development and publishing of open standards and specifications for VRM services.
This page will be the central point of organization for the committee.
The near term strategies of the standards committee are three-fold:
- Create a public mailing list for VRM tech issues
- Work on VRM Services, starting with the Personal Address Manager Service, which started life as the Change of Address Use Case at IIW2007b.
- Develop an organizational capability in creating and working with use cases
If you would like to contribute to these efforts, please email [Joe Andrieu], the chair of this committee and we can arrange for you to join the Standards Committee mailing list. (This is a working list for the committee, not the discussion list of item 1 above.) Please specifically mention the Standards Committee so I can distinguish your interest from general VRM inquiries.
You might also want to review the Initiatives page, which was an early draft of a proposed process for developing VRM standards. Our language has changed a bit and we will not be focusing on Use Cases rather than initiatives, but we will be doing much of the same work.