This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.
Meeting 7th March 2011

Agenda

  • Outsdanding Action items:
    • Feedback from JimConallen is oslc.properties being REQUIRED is acceptable to his implementation effort. (Now closed.)
    • IanGreen has completed the RDFS vocabulary and shared this with the community. Recommendation to publish this to open-services.net.
    • IanGreen continued soliciting IP covenant declarations.
  • Agree that RDFS vocabulary is ready to publish (see RmSpecificationVocabularyV2)?
  • Requirements Organization discussion
    • I'd like us to review Andy's document. In it he makes some assertions - for eample, that a requirement should reference the folder which contains it (should a requirement change when it is moved to another folder?) Should we deal with requirement ordering? For example, how would a Report (via OSLC Reporting) over a specification be possible?
Edit | Attach | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 04 Mar 2011 - 10:35:16 - IanGreen
 
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback