[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
Specifically there are things you cannot do without both. Example - semantic classification of BPEL scripts and components - and associations between them - so that you can provide users of a solution the ability to classify and search intelligently by business domains and application areas as well as traverse associative linkages to packages of related components. All the squabbling aside - I would advise that you may just want to take up the offer here from the ebXML registry folks to provide a guide to using BPEL with Registry. Of course if you don't want people to be able to organize their BPEL scripts in a semantically rich environment - that is of course entirely up to you. Afterall the harder it is for people to discover meaningful BPEL components the less compliants and issues you will get as a TC - since you'll have fewer people using them in the first place. You should also note that there is also absolutely no connection to Abstract BPEL work and semantically rich registry environments. Cheers, DW.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]