> I do not know why osgi.ds was picked in advance of the spec Because we had to pick something. The choice at the time seemed to be between osgi.ds and osgi.scr; I think it would have seemed presumptive for the Bndtools developers to use "osgi.component", thereby designating DS as the One True component model. However if the EEG is prepared to bestow that mantle, who am I to argue?
Nevertheless we will still need to work out how to manage the migration... probably using both namespaces concurrently as suggested by Christian. Neil On Mon, Sep 23, 2013 at 3:05 PM, BJ Hargrave <[email protected]> wrote: > 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* <http://www.osgi.org/>* > **[email protected]* <[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]*<[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 > *<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* <http://www.osgi.org/>* > **[email protected]* <[email protected]> > > office: *+1 386 848 1781* <%2B1%20386%20848%201781> > mobile: *+1 386 848 3788* <%2B1%20386%20848%203788> > > > > > > From: Cristiano Gavião *<[email protected]>* <[email protected]> > To: *[email protected]* <[email protected]> > Date: 2013/09/21 11:39 > Subject: [osgi-dev] namespace for DS osgi.extender capability? > Sent by: > *[email protected]*<[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]* <[email protected]>* > **https://mail.osgi.org/mailman/listinfo/osgi-dev*<https://mail.osgi.org/mailman/listinfo/osgi-dev> > > > > > _______________________________________________ > OSGi Developer Mail List > *[email protected]* <[email protected]> > *https://mail.osgi.org/mailman/listinfo/osgi-dev*<https://mail.osgi.org/mailman/listinfo/osgi-dev> > > > _______________________________________________ > OSGi Developer Mail List* > **[email protected]* <[email protected]>* > **https://mail.osgi.org/mailman/listinfo/osgi-dev*<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
