Toby,
I'm still grappling with all this - and seeing we need tiered layers and clear separation.
Right now we seem to be mixing it all into one big cement mixer and grinding it up - that is NOT good!
OK - so who many types of EMIX messages are we building?
- Tier 1 - eMarketplace for commodity trading (EMIX-CT)
- Tier 2 - Contract, marketplace and delivery management (EMIX-eBay)
- Tier 3 - Power delivery (EMIX-PWR)
I'd suggest that Tier 1 - we really need to look at existing stuff - like TWIST - instead of reinventing the wheel. And then just publish a TWIST-EMIX profile and workflow patterns with specific power-centric criteria / codelists / vocabulary.
Similarly Tier 2 - OASIS ebXML Contract work covers this already - again just need a profile showing how.
Tier 3 - OK - this is IMHO where we do build XML - maybe two sets EMIX-PWR (power exchange) and EMIX-GRID (device configuration)
So the answer to the question is Yes! But lets see how to do that using existing work like TWIST...?
Thanks, DW
