...

domain name - Not sure but I would say domain uri minus any attached configuration parameters, i.e. the bit after the ? (see http://en.wikipedia.org/wiki/URI_scheme#Generic_syntax^{Image Removed})

node - the domain's representative in a class loading space

...

manage domain configuration (currently done through createNode/SCAClient)

• Set domian URI
• Set parameters that describe how to connect to the domain registry

manage node configuration (TBD)

• Associate with domain configuration (via domain URI)
• Specify contributions to pre-load
• Specify composites to deploy
• Specify extension defaults, e.g. binding root URLs

create node (nodeFactory)

• Empty - createNode()
• Preloaded - createNode() taking a variety of parameters

managing contributions - (node)

• add/update/remove contributions

manage composite

• start() / deploy()
• stop() / undeploy()
• could be at domain, node or individual composite level

manage domain

• we don't support a domain manager as yet in 2.x
  The approach thus far is that the individual views of the domain (node) control their part of the domain
  and share information (endpoints) via the domain registry as required. This doesn't rule out the
  domain being managed elsewhere with the nodes being told to run a pre-canned configuration it's just that
  we don't do that at the moment. We should look at what the complete domain registry interface looks like

domain registry

• endpoints - for reference target resolution
• TODO - system level intents and policies - for reference target resolution
• TODO - interface descriptions (as WSDL) - for reference target resolution
• TODO - installed contributions
• TODO - deployed composites
• TODO - nodes - record of running nodes (specifically config, i.e. installed contributions and deployed composites)

2.x Version1 - 26/8/2009

Need to define what the different parts do and if they are all required

...