At this point, ProtocolParameters are only really used for the "template" set of parameters that determine how a protocol definition gets expanded into a set of ProtocolApplications and output Material and Data objects. Some sample xars have used ProtocolParameters for descriptive information about a particular step in a protocol, but no CPAS UI or functionality has been built around this usage. So there are no pre-defined prefixes to OntolotyEntryURI nor any meaning attached to particular ones (other than the Template ones).

If you are starting out designing xars and trying to decide where to hang additional information about your protocol or its application, my advice would be to follow the basic structure of the new Assay feature in 2.2. Assays use a property of the parent Protocol object to specify the domain of properties on the ExperimentRun object produced by the protocol.

Hi Peter,

Thanks for the response.

A quick question... Some example XAR files have ProtocolParameters associated with Protocols and also ProtocolApplication elements. It seems to me that is redundant and that:
1. ProtocolParameters should be only associated with Protocol elements.
2. Specifying protocol parameters is relevant only when authoring XAR files in the ExperimentLog format (which describes auto generation of Protocol Application objects).

Please confirm.

Thanks - Krishna.