<IDA

type=channel/pool/device

imp=mascot-name

scope=local/global/container/
argument/device

name =instance-name

factory = factory-method-name />

IDAs are of a type and referred to by their instance-name. The meaning of the imp attribute is scope dependent as follows:

• local - the mascot-name of the implementation

• global - if in the global context the mascot- name of the implementation, otherwise the instance-name is a reference in the global context.

• container - the instance-name is a reference in the containing subsystem’s context.

• argument - an integer that is the index of the IDA reference in the subsystem’s argument list. Instance-name is this IDA’s alias in this subsystem.

• device – the device name. Instance-name is the name of the specific device instance to open.

In the case where the scope implies the creation of an instance, this is sensitive to the ‘factory’ entry. If it exists then it is taken to be a static method name on the class referred to by mascot- name.

<activity

root=mascot-name

name=instance-name

factory = method-name >

An activity entity. The activity’s root is its implementation; its name is its identity in the subsystem. Instance-names should be unique in the context of the defining subsystem. If ‘factory’ is defined then it is taken to be a static method name on the class referred to by mascot- name.

<device

handler=mascot-name

name=device-name />

Install a device with the implementation handler and the name device-name. All devices have global scope even if defined in a subsystem and will be installed in the global context. Device- names must be unique in the global context.

<arguments>

<String

index=integer

value=string-value />

<Integer

index=integer

name=integer-value />

Activity arguments may be either Strings or Integers. Argument entries define a value and an index. The index is the argument’s index in the activity’s argument array.

</arguments>

•
•
•

</activity>