Refine Technical Charter

[wrathwolf]

Problem description
Arpit Joshipura (CAMARA Executive Director) has requested that we remove the technical overview from the Technical Charter.

Expected action
Arpit expects to keep the scope in the technical document; he wants to move the technical overview into a separate document.
Following the draft proposal, TSC should review and approve any changes.

[hdamker]

@wrathwolf Looking forward to the proposal. I would expect that the technical scope is still defined within the charter, not just in a separate document. As I won't be able to work on it within the next weeks, I removed my assignment , but happy to review.

cc: @MarkusKuemmerle

[wrathwolf]

I think I worded this poorly.
We have been looking at the other LF TSC charters, and all of them have a 2-3 bullet mission statement since the technical details change over time, and we don't want the charter to be outdated. It should focus on how TSC is governed and how decisions are made as a community. (which is the 2nd half)
I will have a proposal for the TSC to restructure the opening sections.

Before we make any official proposal, I will be coordinating with the original architects of the document. I still need to review details, so this isn't the proposal, but we were suggesting something like:

Mission
The CAMARA Project exists to:

• Define and develop open, vendor-neutral APIs that expose network capabilities across global telecommunications operators through collaborative, contribution-driven development
• Ensure technical excellence and interoperability through harmonized API specifications, reference implementations, and comprehensive testing that enable seamless operation across different networks and countries
• Accelerate ecosystem adoption by providing developer-friendly documentation, deployment packages, and integration with relevant developer environments while maintaining transparent governance

Scope
In Scope:

• Customer-facing northbound telco APIs (Service APIs and Service Management APIs)
• API specifications, documentation, and reference implementations
• Test plans, cases, and validation tools
• Transformation functions as example implementations (not harmonized)
• Developer-friendly deployment packages
• Collaboration with GSMA OPG, TM Forum, and other standards bodies

Out of Scope:

• API monetization and commercial terms
• East-west federation/roaming APIs
• Operate APIs (covered by TM Forum)
• Operator-internal southbound interfaces (3GPP, ETSI, etc.)
• Mandated implementation of transformation functions

Technical Details:
Comprehensive technical specifications, API categories, architecture diagrams, and implementation guidelines are maintained in the Technical Reference Document.] (Not yet created)

Then move into the Governance section.