ApplicationAreaDataArea| Description |
| SyncCompetencyDefinitions is used when the owner of the data is passing or publishing that information or change in information to other software components. This is to be used when the receiver of the SyncCompetencyDefinitions does not own the data. This verb is commonly used when mass changes are necessary or when a publish and subscribe mechanism is used in the integration architecture. The purposes of this verb include application integrity and ease of data entry for the business user by enabling a single point of input. CompetencyDefinitions Contains structured information about the semantics associated with a one or more competencies. A Reusable Competency Definition (RCD) is reusable in that it is without a specific context. In other words, it is a definition of a competency not yet associated with a person profile, position, or learning object. |
| Type : SyncCompetencyDefinitionsType |
| Definition |
|
SyncCompetencyDefinitions is used when the owner of the data is passing or publishing that information or change in information to other software components. This is to be used when the receiver of the SyncCompetencyDefinitions does not own the data. This verb is commonly used when mass changes are necessary or when a publish and subscribe mechanism is used in the integration architecture. The purposes of this verb include application integrity and ease of data entry for the business user by enabling a single point of input.
CompetencyDefinitions Contains structured information about the semantics associated with a one or more competencies. A Reusable Competency Definition (RCD) is reusable in that it is without a specific context. In other words, it is a definition of a competency not yet associated with a person profile, position, or learning object.
(Defined in file SyncCompetencyDefinitions.xsd , or a file it imports) |
| Elements | |||
| ApplicationArea | Provides the information that an application may need to know in order to communicate in an integration of two or more business applications. The ApplicationArea is used at the applications layer of communication. While the integration frameworks web services and middleware provide the communication layer that OAGIS operates on top of. | ||
| DataArea | The DataArea is the part of the BOD that contains business information. This information consists of a verb and one or more noun instances. | ||
| Attributes | |||
| languageCode | Indicates the language that the contents of the BOD is in unless otherwise stated. | ||
| releaseID | OAGIS Release this BOD Instances belongs or the OAGIS release that the derivative work is based on. | ||
| systemEnvironmentCode | Indicates whether this BOD is being sent in a "Test" or a "Production" mode. If the BOD is being sent in a test mode, it's information should not affect the business operation. However, if the BOD is sent in "Production" mode it is assumed that all test has been complete and the contents of the BOD are to affect the operation of the receiving business application(s). | ||
| versionID | Indicates the version of the given BOD definition. | ||