A contradiction is removed which incorrectly stated that ranking order is in ascending service.ranking order. The sentence is corrected to:

Therefore, the ranking order is in descending service.ranking numeric order where ties give a preference to the earlier registrant.

9.2.1, 9.2.2 and 9.3.7

The specification is corrected to allow the system bundle to be adapted to BundleStartLevel.

7.4

This section is updated to state that the osgi.identity capability of a fragment is part of the fragment's Bundle Wiring and is not part of a host bundle's Bundle Wiring. That is, each Bundle Wiring has exactly one osgi.identity capability. However, osgi.identity requirements declared by a fragment are not part of the fragment's Bundle Wiring and are instead hosted by the host bundle's Bundle Wiring.

10.4.8.10

The ordering of items in the returned list is updated to state that dynamically established wires are added to the end of the list in the order they are established.

Enterprise

102.2

The URL example is missing the ? before the query string. The correct URL is http://www.acme.com/servlet?name=bugs.

104.13.3.4

The getChangeCount method is corrected to state that it must throw IllegalStateException if this configuration is deleted.

112.13.3.5

The enabled element is incorrectly described as having the value false if unspecified. If unspecified, the value of enabled is true.

124.13.1.1

The AUTORIZATION_TYPE field is incorrectly specified to consists of the NAME_ITEM and TYPE_ITEM items. The field consists of the NAME_ITEM and ROLES_ITEM items. (The name of this field is also incorrectly spelled which will be corrected in a future release.)

The text incorrectly refers to the example importing a service when the example is meant to show exporting a service. In the example, the header name is incorrect and is corrected to be Subsystem-ExportService.

134.18.7

SubsystemPermission incorrectly refers to the Subsystem.getHeaders method for the metadata action. The proper name of the method is getSubsystemHeaders.

136

The Resolver Service Specification is incorrectly numbered. Due to a production error, the Resolver Service Specification was numbered 131 which is already used by the TR069 Connector Service Specification. The correct number for the Resolver Service Specification is 136 which will be used in the next release of the specification document.

Compendium

104.12.3.4

The getChangeCount method is corrected to state that it must throw IllegalStateException if this configuration is deleted.

112.13.3.5

The enabled element is incorrectly described as having the value false if unspecified. If unspecified, the value of enabled is true.

117.11.8

The description of Figure 117.22 is corrected to state that the SESSION_OPENED event is published when the Dmt Session is opened. The remaining events are published when the Dmt Session is closed.

134.18.6

SubsystemPermission incorrectly refers to the Subsystem.getHeaders method for the metadata action. The proper name of the method is getSubsystemHeaders.