Welcome to the Action Methodology
The AM uses an abstraction framework to meet diverse ontology needs of its users. A three layer framework is simple and flexible meeting the needs of different ontologies and domain needs within an knowledge domain.
The AM is implemented based on three layered framework:
Top-level abstraction defines universal concepts such as processes, requirements, actions and data.
Mid-level abstractions core abstraction needed define different categories of data such as agents, address, measurement, ownership, etc. Mid-level abstractions support a common language or understanding based on the needs of specific groups or categories of need supply chains for hardware and software. Mid-level abstractions are designed to satisfy a wide range of implementations within an industry.
Mid-level abstractions require industry knowledge an some understanding of the language structure of the implementation methodology.
Domain implementations are likened to a user application that supports the data collection needs of a specific domain. These implementations are domain specific data sets for simplified implementations.
Mid-level abstractions determines the flexibility of the implementation to a domain user.
The high-level abstraction supports the mid-level abstraction which supports the domain implementation.
Domain layers can be described as template implementations of the mid-layer. Templates are task or requirements based.
The Action Methodology is at the heart of the implementation of the hardware bill of material and related supply chain. Without the action methodology, the SPDX supply chain would be near impossible.
The truth of this statement is supported by these key features:
The ability to create decomposable abstracts.
Naming convention standardization.
Use of relationships to create a graph for common operation.
Mapping of elements to create templates for flexibility and ease of use.
Product history, product specifications and bill of material are examples of templates used to capture important information owners and sellers share.
Templates are forms. A PDF, MSWord doc, or an application are forms or a template for data capture. Template replace existing forms or support the implementation of new forms to replace 1 or more old forms.
Templates are based on standards or specifications as defined by industry as part of a mid-layer design. Forms or templates use a standard ontology which can be understood by anyone within an industry.
Templates are built using JSON, XML, RDF schema or another data format that is machine readable. A structured data file is then shared electronically with parties based on information needs. This makes it easy to send a accurate and current document with an order or shipment. The same document can then be forwarded to a buyer up the distribution chain.
Data from different sources such a database populate a form or template (using various services). It is easy to generate and share templates of different types.
NOTE:
JSON is an open standard file format and data interchange format that uses human-readable text to store and transmit data objects consisting of name–value pairs and arrays. It is a commonly used data format with diverse uses in electronic data interchange.
The Resource Description (RDF) framework is a method to describe and exchange graph data. It was originally designed as a data model for metadata by the World Wide Web Consortium.
XML, or Extensible Markup Language, is a markup language used for storing and transporting data in a structured format that is both human-readable and machine-readable.
The high-level abstraction defined in "AM Definition" has been integrated into System Packaging Data Exchange (SPDX) and Enterprise Resource Metadata Attribution (ERMA). SPDX and ERMA as interchangeable data sharing formats.
SPDX is a Linux Foundation standard while ERMA is a standard in development with the Object Management Group (OMG) with the support of Smart Talk Beacon Solutions.
Defining requirements and processes as core elements data sharing platforms support the creation of mid-level and low-level meta models.
SPDX is the most widely used open package exchange format .
Action Mythology
ERMA
SPDX reduces redundant work by providing common formats for organizations and communities to share important data, thereby streamlining and improving compliance, security, and dependability.
The Action Methodology is a systematic modeling approach used to identify requirements and implement processes to solve technical information problems. It provides a universal ontology that ensures consistency, reliability, and effectiveness in capturing diverse information related to key actions. The framework facilitates the integration of diverse actions and data.
Enterprise Resource Metadata Attribution (ERMA) is a real-time metadata collection, management and exchange format. Metadata is used by various tools to provide insights related to data integrity, system security, business and operational policies, and regulatory compliance.
ERMAs use Data Centric Security for tagging and sharing metadata.
The internet is a backbone for data sharing. SPDX is migrating from a static document to a universal data sharing framework with addition of ERMA security structures and the open Action Methodology.