bjhargrave
commented
9 years ago Comment author: @bjhargrave
The recently updated specification in Release 6 included the definition of osgi.implementation and osgi.service capabilities.
We should define these capabilities for the remaining specifications. While we may not want to revise each spec it include these, we can prepare a web page to hold them. Then as each specification is updated for some other feature, we can then include the capabilities.
Here is a draft of the initial proposal from the CPEG mail list:
100 Remote Services: Nothing required 101 Log Service: Service capability, implementation cap "osgi.log" 102 Http Service: Service capability, implementation cap "osgi.httpservice" ("osgi.http" taken by http whiteboard) 103 Device Access: Implementation capability with name “osgi.device" 104 Config Admin: Service capability and Implementation capability with name “osgi.cm” 105 Metatype: Already in the spec 106 Preferences: Service capability, implementation cap "osgi.prefs" 107 User Admin: Service capability and Implementation capability with name “osgi.useradmin” 108 Wire Admin: Service capability and Implementation capability with name “osgi.wireadmin” 109 IO Connector: Implementation capability with name osgi.io 110 Initial Provisioning: Service capability, implementation cap "osgi.provisioning" 111 UPnP Device: Implementation capability with name osgi.upnp 112 Declarative Services: Already in the spec 113 Event Admin: Service capability and Implementation capability with name “osgi.event” 114 Deployment Admin: Service capability, implementation cap "osgi.deploymentadmin" 115 Auto Configuration: Add nothing 116 Application Admin: implementation cap "osgi.application" 117 Device Management: Service capability and Implementation capability with name “osgi.dmt” 119 Monitor Admin: service cap, implementation cap "osgi.monitor" 120 Foreign Application Access: Add nothing 121 Blueprint Container: Service capability and extender capability with name “osgi.blueprint” 122 Remote Service Admin: Already in the spec 123 JTA service: Service capability and Implementation capability with name “osgi.jta” 124 JMX Management: Implementation capability with name “osgi.jmx" 125 JDBC service: Service capability 126 JNDI service: Service capability and Implementation capability with name “osgi.jndi” 127 JPA service: Extender Capability for “osgi.jpa" 128 Web Applications: Extender Capability for “osgi.web” Implementation capability for “osgi.web.url” 129 SCA: Removed from spec 130 Coordinator Service: Service capability, implementation cap "osgi.coordinator" 131 TR069 Connector Service: Service capability, implementation cap "osgi.tr069todmt" 132 Repository Service: Already in the spec 133 Service Loader: Already in the spec 134 Subsystem Service: Already in the spec 135 Common Namespaces: Nothing Required 136 Resolver Service: Service capability, implementation cap "osgi.resolver" 137 REST management: Already in the spec 138 Async Service: Already in the spec 140 Http Whiteboard: Already in the spec 141 Device Abstraction Layer: nothing. There is no central entity to require. (there is a DAL RI?) 142 Device Abstraction Layer Functions: nothing. There is no central entity to require. 143 Network Interface Information Service: Service capability 144 Resource Monitoring: Service cap, Implementation capability with name “osgi.resourcemonitoring” 145 USB Information Device Category: nothing. There is no central entity to require. (why different than 143?) 145 Serial Device Service: nothing. There is no central entity to require. (why different than 143?) 702 XML Parser: Nothing needed 703 Position: Nothing needed 704 Measurement: Nothing needed 705 Promises: Nothing needed 999 Execution Environment: Nothing needed
Original bug ID: BZ#2874 From: @bjhargrave Reported version: R6