Replace the S-RAMP SOA/ServiceImpl model with something comprehensive for "services" ------------------------------------------------------------------------------------ Key: ARTIF-675 URL: https://issues.jboss.org/browse/ARTIF-675 Project: Artificer Issue Type: Sub-task Reporter: Brett Meyer Assignee: Brett Meyer Define a new, generic, logical metadata-only model to better encapsulate "services", discovery, and re-use. This should use *some* of the concepts in S-RAMP's SOA/ServiceImplementation models. Arguably, some concepts should probably be rolled into the core Artifact model as well. Ideas (from various sources): - Provides a catalog of information, what services exist and are available for use - Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc. - Provides information about the version of the services - Allows you to record and retrieve multiple versions of the same service - Allows you to dynamically refer to the latest version of the service - Allows dynamically at runtime to search and select end-point chosen service - Collects information who and what services are used - Provides information that services are repeatedly used and which are not - Determining the impact of changes the services to existing dependent services - Providing information to consumers of the services about ongoing or planned changes to of the services - Identify the environments (OS, app server, etc.) supported by the artifact - Differentiate between front and back end artifacts - Security: what version of SSL is used, etc. (extremely valuable for security audits)