DESCRIPTION: A document that prescribes technical requirements to be fulfilled by a product, process or service. - Note 1 to entry: A technical specification should indicate, whenever appropriate, the procedure(s) by means of which it may be determined whether the requirements given are fulfilled. - Note 2 to entry: A technical specification may be a standard, a part of a standard or independent of a standard. Source: https://www.iso.org/obp/ui/#iso:std:iso-iec:20944:-1:ed-1:v1:en:term:3.1.3.8] INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP, Behavioral IoP, Governance IoP The Technical Specification ABB is salient for technical interoperability because it assesses the characteristics required of a product to support technical solutions. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): AS4 Profile specification The eDelivery AS4 Profile is a modular profile of the ebMS3 and AS4 OASIS specifications. Its core is a mandatory Common Profile that selects, extends and profiles the AS4 ebHandler Conformance Profile and AS4 Additional Features and provides a common Usage Profile. This Common Profile can be implemented using open source or closed source AS4 software implementations. It is aligned with, and corresponds to a subset of, the AS4 profile for TSOs (Transmission System Operators) developed by ENTSOG (the European Network of Transmission System Operators for Gas). In addition to the Common Profile, this specification provides a number of optional Profile Enhancement modules that specify functionality enhancements covering AS4 message exchange in four corner topologies, the use of AS4 in conjunction with the UN/CEFACT Standard Business Document Header (SBDH) specification, and Dynamic Receiver and Dynamic Sender behavior. https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+AS4+-+1.13