I do not know why osgi.ds was picked in advance of the spec. "ds" is not 
what has been used as a string anywhere in the spec and is too short for 
use in a spec. This is why the RFC uses "component" which is the most 
significant portion of the package name. Blueprint will use osgi.blueprint 
(not osgi.bp :-).
-- 

BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
[email protected]

office: +1 386 848 1781
mobile: +1 386 848 3788




From:   Neil Bartlett <[email protected]>
To:     OSGi Developer Mail List <[email protected]>
Date:   2013/09/23 09:26
Subject:        Re: [osgi-dev] namespace for DS osgi.extender capability?
Sent by:        [email protected]



Well this is going to cause a hell of a migration headache!

Bindex, bnd and Bndtools have been using "osgi.ds" for well over a year 
while waiting for the EG to revise the spec.


On Mon, Sep 23, 2013 at 1:44 PM, Cristiano Gavião <[email protected]> 
wrote:
Thanks BJ.


On 21/09/13 16:13, BJ Hargrave wrote:
See 
https://github.com/osgi/design/blob/master/rfcs/rfc0190/rfc-0190-Declarative_Services_Enhancements.pdf
 
for the current design doc. 
-- 

BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
[email protected] 

office: +1 386 848 1781
mobile: +1 386 848 3788




From:        Cristiano Gavião <[email protected]> 
To:        [email protected] 
Date:        2013/09/21 11:39 
Subject:        [osgi-dev] namespace for DS osgi.extender capability? 
Sent by:        [email protected] 



Hi,

could someone point me which is the Declarative Service capability 
namespace?

it was defined in any spec ?

thanks,

Cristiano
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev




_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev


_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to