MEF API Development
How does MEF facilitate the development of APIs?
1To facilitate automation, MEF begins with the definition and standardization of MEF 3.0 services.
2From these service definitions, information or object models are developed. These include common MEF types and constructs and a common taxonomy and behavior that span all MEF 3.0 services.Specific resource, service, policy, and business model representations are developed for each MEF 3.0 service. Some of these models relate to more than one LSO interface reference points (e.g. There is a significant overlap of product models applied at LSO Sonata and Cantata).
3The Business Requirements and Use Cases (BRUC) are specific to each LSO interface reference point and they define the functional requirements, use cases, business process flows, state transitions, etc., related to the specific LSO interface (e.g. LSO Sonata).
4From these BRUCs, MEF maps the applicable information models to relevant data schemas which are then packaged into SDKs along with related documentation, code samples, and developer guides, to support the development of MEF APIs for each of the LSO interface reference points.
MEF incorporates industry work, in a collaborative manner, to leverage ongoing projects in specific domains, e.g TMF Open APIs, ONF TAPI, that facilitate rapid and frictionless adoption with industry stakeholders.
MEF’s Approach to Standard APIs
To support automation within and between providers, both the services and the information models need to be standardized.
From Service Standards to Standard APIs