M1 contains the diverse data of the community of users, accessed for input, transformation, or output, through the viewpoint designs modeled at the M1 level, and populated where possible with M2 lookup values, e.g., the equipment data-values (selected from an M2 lookup) in the equipment form (M1).
You also built your integrating models at this level, e.g., a model for integrating M1 layer database designs across various M1 application designs and process models.
In general, SQL is good for closed-world views of unchanging things for limited numbers of viewpoints, while metadata repositories are good for open-world views of evolving, adaptive, continuously changing things for unlimited numbers of customized user viewpoints.
put into service; make work or employ for a particular purpose or for its inherent or natural purpose
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
the discipline dealing with the principles of design and construction and ornamentation of fine buildings
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
an abstraction belonging to or characteristic of an entity
M3 contains the object model (made available by the physical model/metadata repository software and hardware), where all modeled "things" are given their core inherited attributes and their core reusable "types" of relationships.
M1 contains the diverse models of viewpoints in the community of users (i.e., concept maps, data models, process models, business rules, forms, reports, business and geographic visualizations, ontologies as knowledge models and architectures, axiologies as value-chain models as in value-added economic models, database structures, software applications, etc.), built by referring (e.g., via automated lookup) to the M2 references.
obtainable or accessible and ready for use or service
M3 contains the object model (made available by the physical model/metadata repository software and hardware), where all modeled "things" are given their core inherited attributes and their core reusable "types" of relationships.
M1 contains the diverse models of viewpoints in the community of users (i.e., concept maps, data models, process models, business rules, forms, reports, business and geographic visualizations, ontologies as knowledge models and architectures, axiolo
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
the fundamental assumptions from which something is begun or developed or calculated or explained
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
With an open (i.e., non-proprietary) MDA Four Layer metamodeling approach, you can model anything and everything in the universe and beyond - any system not just software.
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
the principal activity in your life that you do to earn money
M1 contains the diverse models of viewpoints in the community of users (i.e., concept maps, data models, process models, business rules, forms, reports, business and geographic visualizations, ontologies as knowledge models and architectures, axiologies as value-chain models as in value-added economic models, database structures, software applications, etc.), built by referring (e.g., via automated lookup) to the M2 references.
a series of (usually metal) rings or links fitted into one another to make a flexible ligament
â€Â¢M1 contains the diverse models of viewpoints in the community of users (i.e., concept maps, data models, process models, business rules, forms, reports, business and geographic visualizations, ontologies as knowledge models and architectures, axiologies as value-chain models as in value-added economic models, database structures, software applications, etc.), built by referring (e.g., via automated lookup) to the M2 references.
In general, SQL is good for closed-world views of unchanging things for limited numbers of viewpoints, while metadata repositories are good for open-world views of evolving, adaptive, continuously changing things for unlimited numbers of customized user viewpoints.
In general, SQL is good for closed-world views of unchanging things for limited numbers of viewpoints, while metadata repositories are good for open-world views of evolving, adaptive, continuously changing things for unlimited numbers of customized user viewpoints.
a set of rules or principles or laws (especially written ones)
With a SQL DBMS, database, and application, the conceputal model, logical model, physical schema, database, and application code are separate from each other and much harder to change when needed.
a group of people living in a particular local area
M1 contains the diverse models of viewpoints in the community of users (i.e., concept maps, data models, process models, business rules, forms, reports, business and geographic visualizations, ontologies as knowledge models and architectures, axiologies as value-chain models as in value-added economic models, database structures, software applications, etc.), built by referring (e.g., via automated lookup) to the M2 references.
an abstract or general idea inferred or derived from specific instances
M1 contains the diverse models of viewpoints in the community of users (i.e., concept maps, data models, process models, business rules, forms, reports, business and geographic visualizations, ontologies as knowledge models and architectures, axiologies as value-chain models as in value-added economic models, database structures, software applications, etc.), built by referring (e.g., via automated lookup) to the M2 references.
For example, using such an open metadata repository, we could build a National Terminology for ARRA, having a unifying Management Life Cycle process to which other processes and life cycles are mapped, with consistent sets of management controls throughout the unifying life cycle, to which other processes' and applications' management controls, such as performance metrics, are mapped.
M3 contains the object model (made available by the physical model/metadata repository software and hardware), where all modeled "things" are given their core inherited attributes and their core reusable "types" of relationships.
In general, SQL is good for closed-world views of unchanging things for limited numbers of viewpoints, while metadata repositories are good for open-world views of evolving, adaptive, continuously changing things for unlimited numbers of customized user viewpoints.
For example, using such an open metadata repository, we could build a National Terminology for ARRA, having a unifying Management Life Cycle process to which other processes and life cycles are mapped, with consistent sets of management controls throughout the unifying life cycle, to which other processes' and applications' management controls, such as performance metrics, are mapped.
M3 contains the object model (made available by the physical model/metadata repository software and hardware), where all modeled "things" are given their core inherited attributes and their core reusable "types" of relationships.
For example, using such an open metadata repository, we could build a National Terminology for ARRA, having a unifying Management Life Cycle process to which other processes and life cycles are mapped, with consistent sets of management controls throughout the unifying life cycle, to which other processes' and applications' management controls, such as performance metrics, are mapped.
With a SQL DBMS, database, and application, the conceputal model, logical model, physical schema, database, and application code are separate from each other and much harder to change when needed.
the act of working out the form of something (as by making a sketch or outline or plan)
You also built your integrating models at this level, e.g., a model for integrating M1 layer database designs across various M1 application designs and process models.
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
You also built your integrating models at this level, e.g., a model for integrating M1 layer database designs across various M1 application designs and process models.
of or relating to an economy, the system of production and management of material wealth
â€Â¢M1 contains the diverse models of viewpoints in the community of users (i.e., concept maps, data models, process models, business rules, forms, reports, business and geographic visualizations, ontologies as knowledge models and architectures, axiologies as value-chain models as in value-added economic models, database structures, software applications, etc.), built by referring (e.g., via automated lookup) to the M2 references.
an instrumentality needed for an undertaking or to perform a service
M0 contains the diverse data of the community of users, accessed for input, transformation, or output, through the viewpoint designs modeled at the M1 level, and populated where possible with M2 lookup values, e.g., the equipment data-values (selected from an M2 lookup) in the equipment form (M1).
an item of information that is typical of a class or group
For example, using such an open metadata repository, we could build a National Terminology for ARRA, having a unifying Management Life Cycle process to which other processes and life cycles are mapped, with consistent sets of management controls throughout the unifying life cycle, to which other processes' and applications' management controls, such as performance metrics, are mapped.
For example, using such an open metadata repository, we could build a National Terminology for ARRA, having a unifying Management Life Cycle process to which other processes and life cycles are mapped, with consistent sets of management controls throughout the unifying life cycle, to which other processes' and applications' management controls, such as performance metrics, are mapped.
M1 contains the diverse models of viewpoints in the community of users (i.e., concept maps, data models, process models, business rules, forms, reports, business and geographic visualizations, ontologies as knowledge models and architectures, axiologies as value-chain models as in value-added economic models, database structures, software applications, etc.), built by referring (e.g., via automated lookup) to the M2 references.
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
the cardinal number that is the sum of three and one
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
M1 contains the diverse models of viewpoints in the community of users (i.e., concept maps, data models, process models, business rules, forms, reports, business and geographic visualizations, ontologies as knowledge models and architectures, axiologies as value-chain models as in value-added economic models, database structures, software applications, etc.), built by referring (e.g., via automated lookup) to the M2 references.
any number of entities (members) considered as a unit
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
instrumentalities (tools or implements) made of metal
M3 contains the object model (made available by the physical model/metadata repository software and hardware), where all modeled "things" are given their core inherited attributes and their core reusable "types" of relationships.
In general, SQL is good for closed-world views of unchanging things for limited numbers of viewpoints, while metadata repositories are good for open-world views of evolving, adaptive, continuously changing things for unlimited numbers of customized user viewpoints.
M3 contains the object model (made available by the physical model/metadata repository software and hardware), where all modeled "things" are given their core inherited attributes and their core reusable "types" of relationships.
occurring among members of a family usually by heredity
M3 contains the object model (made available by the physical model/metadata repository software and hardware), where all modeled "things" are given their core inherited attributes and their core reusable "types" of relationships.
M0 contains the diverse data of the community of users, accessed for input, transformation, or output, through the viewpoint designs modeled at the M1 level, and populated where possible with M2 lookup values, e.g., the equipment data-values (selected from an M2 lookup) in the equipment form (M1).
the action of incorporating a racial or religious group into a community
You also built your integrating models at this level, e.g., a model for integrating M1 layer database designs across various M1 application designs and process models.
the psychological result of perception and learning and reasoning
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
single thickness of usually some homogeneous substance
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
a relative position or degree of value in a graded group
You also built your integrating models at this level, e.g., a model for integrating M1 layer database designs across various M1 application designs and process models.
the organic phenomenon that distinguishes living organisms from nonliving ones
For example, using such an open metadata repository, we could build a National Terminology for ARRA, having a unifying Management Life Cycle process to which other processes and life cycles are mapped, with consistent sets of management controls throughout the unifying life cycle, to which other processes' and applications' management controls, such as performance metrics, are mapped.
a series of stages through which an organism passes between recurrences of a primary stage
For example, using such an open metadata repository, we could build a National Terminology for ARRA, having a unifying Management Life Cycle process to which other processes and life cycles are mapped, with consistent sets of management controls throughout the unifying life cycle, to which other processes' and applications' management controls, such as performance metrics, are mapped.
In general, SQL is good for closed-world views of unchanging things for limited numbers of viewpoints, while metadata repositories are good for open-world views of evolving, adaptive, continuously changing things for unlimited numbers of customized user viewpoints.
In general, SQL is good for closed-world views of unchanging things for limited numbers of viewpoints, while metadata repositories are good for open-world views of evolving, adaptive, continuously changing things for unlimited numbers of customized user viewpoints.
With a SQL DBMS, database, and application, the conceputal model, logical model, physical schema, database, and application code are separate from each other and much harder to change when needed.
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
an internal control performed by one or more managers
For example, using such an open metadata repository, we could build a National Terminology for ARRA, having a unifying Management Life Cycle process to which other processes and life cycles are mapped, with consistent sets of management controls throughout the unifying life cycle, to which other processes' and applications' management controls, such as performance metrics, are mapped.
a diagrammatic representation of the earth's surface (or part of it)
For example, using such an open metadata repository, we could build a National Terminology for ARRA, having a unifying Management Life Cycle process to which other processes and life cycles are mapped, with consistent sets of management controls throughout the unifying life cycle, to which other processes' and applications' management controls, such as performance metrics, are mapped.
For example, using such an open metadata repository, we could build a National Terminology for ARRA, having a unifying Management Life Cycle process to which other processes and life cycles are mapped, with consistent sets of management controls throughout the unifying life cycle, to which other processes' and applications' management controls, such as performance metrics, are mapped.
the study of poetic meter and the art of versification
For example, using such an open metadata repository, we could build a National Terminology for ARRA, having a unifying Management Life Cycle process to which other processes and life cycles are mapped, with consistent sets of management controls throughout the unifying life cycle, to which other processes' and applications' management controls, such as performance metrics, are mapped.
M3 contains the object model (made available by the physical model/metadata repository software and hardware), where all modeled "things" are given their core inherited attributes and their core reusable "types" of relationships.
of or relating to or belonging to a nation or country
For example, using such an open metadata repository, we could build a National Terminology for ARRA, having a unifying Management Life Cycle process to which other processes and life cycles are mapped, with consistent sets of management controls throughout the unifying life cycle, to which other processes' and applications' management controls, such as performance metrics, are mapped.
With a SQL DBMS, database, and application, the conceputal model, logical model, physical schema, database, and application code are separate from each other and much harder to change when needed.
With an open (i.e., non-proprietary) MDA Four Layer metamodeling approach, you can model anything and everything in the universe and beyond - any system not just software.
In general, SQL is good for closed-world views of unchanging things for limited numbers of viewpoints, while metadata repositories are good for open-world views of evolving, adaptive, continuously changing things for unlimited numbers of customized user viewpoints.
In general, SQL is good for closed-world views of unchanging things for limited numbers of viewpoints, while metadata repositories are good for open-world views of evolving, adaptive, continuously changing things for unlimited numbers of customized user viewpoints.
a tangible and visible entity; an entity that can cast a shadow
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
the metaphysical study of the nature of being and existence
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
In general, SQL is good for closed-world views of unchanging things for limited numbers of viewpoints, while metadata repositories are good for open-world views of evolving, adaptive, continuously changing things for unlimited numbers of customized user viewpoints.
M0 contains the diverse data of the community of users, accessed for input, transformation, or output, through the viewpoint designs modeled at the M1 level, and populated where possible with M2 lookup values, e.g., the equipment data-values (selected from an M2 lookup) in the equipment form (M1).
the act of performing; of doing something successfully; using knowledge as distinguished from merely possessing it
For example, using such an open metadata repository, we could build a National Terminology for ARRA, having a unifying Management Life Cycle process to which other processes and life cycles are mapped, with consistent sets of management controls throughout the unifying life cycle, to which other processes' and applications' management controls, such as performance metrics, are mapped.
involving the body as distinguished from the mind or spirit
With a SQL DBMS, database, and application, the conceputal model, logical model, physical schema, database, and application code are separate from each other and much harder to change when needed.
M0 contains the diverse data of the community of users, accessed for input, transformation, or output, through the viewpoint designs modeled at the M1 level, and populated where possible with M2 lookup values, e.g., the equipment data-values (selected from an M2 lookup) in the equipment form (M1).
protected by trademark or patent or copyright; made or produced or distributed by one having exclusive rights
With an open (i.e., non-proprietary) MDA Four Layer metamodeling approach, you can model anything and everything in the universe and beyond - any system not just software.
send or direct for treatment, information, or a decision
M1 contains the diverse models of viewpoints in the community of users (i.e., concept maps, data models, process models, business rules, forms, reports, business and geographic visualizations, ontologies as knowledge models and architectures, axiologies as value-chain models as in value-added economic models, database structures, software applications, etc.), built by referring (e.g., via automated lookup) to the M2 references.
a relation between people; (`relationship' is often used where `relation' would serve, as in `the relationship between inflation and unemployment', but the preferred usage of `relationship' is for human relations or states of relatedness)
â€Â¢M3 contains the object model (made available by the physical model/metadata repository software and hardware), where all modeled "things" are given their core inherited attributes and their core reusable "types" of relationships.
M3 contains the object model (made available by the physical model/metadata repository software and hardware), where all modeled "things" are given their core inherited attributes and their core reusable "types" of relationships.
M1 contains the diverse models of viewpoints in the community of users (i.e., concept maps, data models, process models, business rules, forms, reports, business and geographic visualizations, ontologies as knowledge models and architectures, axiologies as value-chain models as in value-added economic models, database structures, software applications, etc.), built by referring (e.g., via automated lookup) to the M2 references.
With a SQL DBMS, database, and application, the conceputal model, logical model, physical schema, database, and application code are separate from each other and much harder to change when needed.
pick out, select, or choose from a number of alternatives
M0 contains the diverse data of the community of users, accessed for input, transformation, or output, through the viewpoint designs modeled at the M1 level, and populated where possible with M2 lookup values, e.g., the equipment data-values (selected from an M2 lookup) in the equipment form (M1).
M0 contains the diverse data of the community of users, accessed for input, transformation, or output, through the viewpoint designs modeled at the M1 level, and populated where possible with M2 lookup values, e.g., the equipment data-values (selected from an M2 lookup) in the equipment form (M1).
standing apart; not attached to or supported by anything
With a SQL DBMS, database, and application, the conceputal model, logical model, physical schema, database, and application code are separate from each other and much harder to change when needed.
For example, using such an open metadata repository, we could build a National Terminology for ARRA, having a unifying Management Life Cycle process to which other processes and life cycles are mapped, with consistent sets of management controls throughout the unifying life cycle, to which other processes' and applications' management controls, such as performance metrics, are mapped.
(computer science) written programs or procedures or rules and associated documentation pertaining to the operation of a computer system and that are stored in read/write memory
With an open (i.e., non-proprietary) MDA Four Layer metamodeling approach, you can model anything and everything in the universe and beyond - any system not just software.
a thing constructed; a complex entity constructed of many parts
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
For example, using such an open metadata repository, we could build a National Terminology for ARRA, having a unifying Management Life Cycle process to which other processes and life cycles are mapped, with consistent sets of management controls throughout the unifying life cycle, to which other processes' and applications' management controls, such as performance metrics, are mapped.
a system of words used to name things in a particular discipline
For example, using such an open metadata repository, we could build a National Terminology for ARRA, having a unifying Management Life Cycle process to which other processes and life cycles are mapped, with consistent sets of management controls throughout the unifying life cycle, to which other processes' and applications' management controls, such as performance metrics, are mapped.
For example, using such an open metadata repository, we could build a National Terminology for ARRA, having a unifying Management Life Cycle process to which other processes and life cycles are mapped, with consistent sets of management controls throughout the unifying life cycle, to which other processes' and applications' management controls, such as performance metrics, are mapped.
the act of changing in form or shape or appearance
M0 contains the diverse data of the community of users, accessed for input, transformation, or output, through the viewpoint designs modeled at the M1 level, and populated where possible with M2 lookup values, e.g., the equipment data-values (selected from an M2 lookup) in the equipment form (M1).
In general, SQL is good for closed-world views of unchanging things for limited numbers of viewpoints, while metadata repositories are good for open-world views of evolving, adaptive, continuously changing things for unlimited numbers of customized user viewpoints.
For example, using such an open metadata repository, we could build a National Terminology for ARRA, having a unifying Management Life Cycle process to which other processes and life cycles are mapped, with consistent sets of management controls throughout the unifying life cycle, to which other processes' and applications' management controls, such as performance metrics, are mapped.
With an open (i.e., non-proprietary) MDA Four Layer metamodeling approach, you can model anything and everything in the universe and beyond - any system not just software.
In general, SQL is good for closed-world views of unchanging things for limited numbers of viewpoints, while metadata repositories are good for open-world views of evolving, adaptive, continuously changing things for unlimited numbers of customized user viewpoints.
a person who makes use of a thing; someone who uses or employs something
In general, SQL is good for closed-world views of unchanging things for limited numbers of viewpoints, while metadata repositories are good for open-world views of evolving, adaptive, continuously changing things for unlimited numbers of customized user viewpoints.
an act that exploits or victimizes someone (treats them unfairly)
Using the Object Management Group's (OMG) Model-driven architecture (MDA) approach for building and managing architectures (i.e., ontologies, viewpoints, knowledge-bases) of any type, you apply a four-layer metamodeling structure, with M3 being the foundation and M0 being the top.
the quality (positive or negative) that renders something desirable or valuable
M1 contains the diverse models of viewpoints in the community of users (i.e., concept maps, data models, process models, business rules, forms, reports, business and geographic visualizations, ontologies as knowledge models and architectures, axiologies as value-chain models as in value-added economic models, database structures, software applications, etc.), built by referring (e.g., via automated lookup) to the M2 references.
beliefs of a person or social group in which they have an emotional investment (either for or against something)
M0 contains the diverse data of the community of users, accessed for input, transformation, or output, through the viewpoint designs modeled at the M1 level, and populated where possible with M2 lookup values, e.g., the equipment data-values (selected from an M2 lookup) in the equipment form (M1).
You also built your integrating models at this level, e.g., a model for integrating M1 layer database designs across various M1 application designs and process models.
In general, SQL is good for closed-world views of unchanging things for limited numbers of viewpoints, while metadata repositories are good for open-world views of evolving, adaptive, continuously changing things for unlimited numbers of customized user viewpoints.
In general, SQL is good for closed-world views of unchanging things for limited numbers of viewpoints, while metadata repositories are good for open-world views of evolving, adaptive, continuously changing things for unlimited numbers of customized user viewpoints.
a mental image that is similar to a visual perception
M1 contains the diverse models of viewpoints in the community of users (i.e., concept maps, data models, process models, business rules, forms, reports, business and geographic visualizations, ontologies as knowledge models and architectures, axiologies as value-chain models as in value-added economic models, database structures, software applications, etc.), built by referring (e.g., via automated lookup) to the M2 references.
the 3rd planet from the sun; the planet we live on
In general, SQL is good for closed-world views of unchanging things for limited numbers of viewpoints, while metadata repositories are good for open-world views of evolving, adaptive, continuously changing things for unlimited numbers of customized user viewpoints.
In general, SQL is good for closed-world views of unchanging things for limited numbers of viewpoints, while metadata repositories are good for open-world views of evolving, adaptive, continuously changing things for unlimited numbers of customized user viewpoints.
access
