Page History
...
Use Case Number | Init1pm16.5 |
Brief Description | The true test of whether the semantic infrastructure is handling ISO 21090 requirements is that it is possible to:
|
Actor(s) for this particular use case | System Architect |
Pre-condition | Two or more systems have correctly imported, localized, generated XML Schema, and registered information models with ISO 21090 datatypes. Furthermore, these information models are implemented by real systems with ECCF compliant APIs. |
Post condition | Touch points are discovered and data is successfully exchanged. |
Steps to take |
|
Alternate Flow | None. |
Priority | Medium None. |
Associated Links | |
Fit criterion/Acceptance Criterion | The documentation and semantic metadata should be sufficient information to determine the mechanism by which data can be exchanged between systems. |
Init1pm16.6 - 21090 Datatype Support - Translation Services
Use Case Number | Init1pm16.6 |
Brief Description | ISO 21090 data types have a specific encoding scheme that is significantly different than what has been used thus far in caBIG services. Rather than reengineering existing services entirely, it may be desirable to have a common translation service interface and implementation toolkit that can be used to "wrap" existing non-compliant services. |
Actor(s) for this particular use case | Software Engineer |
Pre-condition | One or more services exist that expose datatypes that are not ISO 21090 compliant. |
Post condition | A new service is implemented that exposes the same semantics but with ISO 21090 datatypes. |
Steps to take |
|
Alternate Flow | None. |
Priority | Low |
Associated Links | Init1bes12 - Mapping_transformation support for ISO21090 data types |
Fit criterion/Acceptance Criterion | As little coding as possible should be required. |