This sounds like a very valuable contribution. And thanks for your interest in OSLC.
OSLC specification development is in the process of migrating to OASIS. The existing OSLC 2.0 specifications will continue to be maintained here on open-services.net. And OASIS specifications may make normative references to open-services.net specifications, especially during the migration process.
The open-services.net site is sill an excellent place to collaborate on the identification of new specification opportunities, addressing defects in the current open-services.net OSLC 2.0 specifications, and for exploring usage patterns and best practices for leveraging OSLC enabling technologies to support effective integration.
There are many reasons for utilizing OASIS for OSLC standards development, but the primary one is to encourage and facilitate broader participation in standards development. You may consider submitting your charter proposal to the OASIS OSLC Member Section Steering Committee for the creation of a new OSLC domain Technical Committee. See the OASIS Technical Committee Process for further details.
Regarding your charter, it looks very comprehensive and well thought out. My only suggestion is to consider the use of the word “interchange”. OSLC is based on RDF and Linked-Data principles that allow applications to integrate and share federated data without interchange and data copy that can result in data redundancy and lifecycle management problems. OSLC prefers integration over interchange since interchange often focuses on copying data between tools that do similar things (focusing on overlap) while integration focuses on linking data between tools that do different things (focusing on collaboration and increased business value).