[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [plcs-dex] Capability/Dex structuring
Sounds reasonable to me Regards Rob ------------------------------------------- Rob Bodington Eurostep Limited Web Page: http://www.eurostep.com http://www.share-a-space.com Email: Rob.Bodington@eurostep.com Phone: +44 (0)1454 270030 Mobile: +44 (0)7796 176 401 > -----Original Message----- > From: Barker, Sean (UK) [mailto:sean.barker@baesystems.com] > Sent: 03 June 2004 16:45 > To: Tim > Cc: plcs-dex@lists.oasis-open.org > Subject: RE: [plcs-dex] Capability/Dex structuring > > > Tim > I would guess so, but Rob may have a view on this. > > Sean Barker > ATC Filton > 0117 302 8184 > > > -----Original Message----- > From: Tim [mailto:timturner11@bellsouth.net] > Sent: 03 June 2004 16:25 > To: Barker, Sean (UK) > Cc: plcs-dex@lists.oasis-open.org > Subject: RE: [plcs-dex] Capability/Dex structuring > > > Saun, > > So, when more than one capability requires the same functionality, I presume > that we should document that functionality independently (e.g. in another > capability) and then reference that by those that require it, right? > > In that case - since both capabilities C003 (Assemblies) and C004 (breakdowns) > both need to refer to Slots, I should create a separate capability, rather > than doing it twice, correct? > > regards, > Tim > > -----Original Message----- > From: Barker, Sean (UK) [mailto:sean.barker@baesystems.com] > Sent: 03 June 2004 11:09 > To: Tim > Cc: plcs-dex@lists.oasis-open.org > Subject: RE: [plcs-dex] Capability/Dex structuring > > > > Tim, > As I recall, no, though a capability can reference other capabilities. > > Sean Barker > ATC Filton > 0117 302 8184 > > -----Original Message----- > From: Tim [mailto:timturner11@bellsouth.net] > Sent: 03 June 2004 16:00 > To: plcs-dex@lists.oasis-open.org > Subject: [plcs-dex] Capability/Dex structuring > > > > A quick question to the wise. > > We have defined Dexs to be collections of capabilities. Is it also possible > that a capability can be a collection of other capabilities? > > Regards, > Tim > > > ******************************************************************** > This email and any attachments are confidential to the intended > recipient and may also be privileged. If you are not the intended > recipient please delete it from your system and notify the sender. > You should not copy it or use it for any purpose nor disclose or > distribute its contents to any other person. > ******************************************************************** > > ******************************************************************** > This email and any attachments are confidential to the intended > recipient and may also be privileged. If you are not the intended > recipient please delete it from your system and notify the sender. > You should not copy it or use it for any purpose nor disclose or > distribute its contents to any other person. > ********************************************************************
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]