public:99_annexes:annex-b-terms-and-definitions:p:provider_implementation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:p:provider_implementation [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:p:provider_implementation [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Provider Implementation ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Provider Implementation realizes defined capabilities through the products, services, interfaces, resource types, and operational mechanisms supplied by a particular provider.
 +
 +The provider may supply:
 +
 +  * Cloud infrastructure
 +  * Hosting services
 +  * Compute services
 +  * Storage services
 +  * Network services
 +  * Identity services
 +  * Security services
 +  * Monitoring services
 +  * Data services
 +  * Messaging services
 +  * Platform services
 +  * Deployment interfaces
 +
 +A Provider Implementation may consume [[public:99_annexes:annex-b-terms-and-definitions:p:platform_specific_information|Platform Specific Information]] such as:
 +
 +  * Resource identifiers
 +  * Service names
 +  * Image identifiers
 +  * Machine types
 +  * Regions
 +  * Network identifiers
 +  * Storage classes
 +  * Credentials
 +  * Provider-specific configuration values
 +  * [[public:99_annexes:annex-b-terms-and-definitions:p:platform_specific_parameter|Platform Specific Parameters]]
 +
 +A Provider Implementation differs from the provider organization:
 +
 +  * The provider organization is the entity that supplies products or services
 +  * The Provider Implementation is the technical realization supplied by that entity
 +
 +A Provider Implementation also differs from [[public:99_annexes:annex-b-terms-and-definitions:p:platform_independent_information|Platform Independent Information]]:
 +
 +  * Platform Independent Information describes implementation-neutral intent
 +  * A Provider Implementation realizes that intent through provider-specific technologies and mechanisms
 +
 +Multiple Provider Implementations may realize the same platform-independent specification through different Platform Specific Information.
 +
 +===== Definition =====
 +
 +//implementation that realizes defined capabilities through the products, services, interfaces, and operational mechanisms supplied by a particular provider//
 +
 +===== Source =====
 +
 +Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +===== Note =====
 +
 +A Provider Implementation may be:
 +
 +  * Public cloud
 +  * Private cloud
 +  * Community cloud
 +  * Hybrid cloud
 +  * On-premises infrastructure
 +  * Hosted infrastructure
 +  * Virtualized infrastructure
 +  * Physical infrastructure
 +
 +The term does not imply that the provider supplies every component used by the implementation.
 +
 +A Provider Implementation may incorporate third-party products, open-source components, external services, or customer-managed resources.
 +
 +Conformance of one Provider Implementation does not establish conformance of another Provider Implementation.
 +
 +===== Example =====
 +
 +One Provider Implementation realizes a platform-independent compute, storage, and networking specification through one cloud provider's virtual-machine, block-storage, virtual-network, and identity services. Another Provider Implementation realizes the same specification through corresponding services supplied by a different provider.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>