Versions Compared

Old Version 4

changes.mady.by.user Richard Marshall

Saved on

compared with

New Version 5

changes.mady.by.user Richard Marshall

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Example
inlinetrue

For example, a general convention could be that all references are defined relative to the analysis that uses the method. Any metadata element name that is specified without any qualification is assumed to be a reference to the value of an attribute in the instance of the Analysis class that represents the analysis. In this case, references to metadata elements in instances of other classes would need some sort of qualifier (such as a "relative path" or a "search criterion") to indicate where the value for the parameter can be found.

However, if ARS metadata is shared, the provider should either:

        • Provide sufficient supporting information so that all metadata element reference can be unambiguously interpreted by the receiver, or
        • Record parameter values obtained from metadata references with each analysis.

Or:

      • The value attribute may be used to prespecify value(s) for use during execution of the analysis:
        • If a single value is specified, this would generally be interpreted as representing a "default" value to be applied in all analyses that use the method, unless the parameter is copied to the analysis and the prespecified value is replaced with another analysis-specific value.
        • If multiple values are specified (which is allowable in the TemplateCodeParameter specialization of the CodeParameter class), these would generally be interpreted as a list of allowable values. In this case, the parameter would need to be copied to the analysis so that the appropriate analysis-value can be selected from the list and recorded for the analysis).
        • If the value attribute has no value (or is not used in the instance of the TemplateCodeParameter class) and the valueSource is also not used, this would generally imply that the parameter should be copied to the analysis so that an analysis-specific value can be specified.

Sponsors may use other conventions for the population and use of the value attribute. However, any conventions used should be applied consistently throughout the reporting event and, if ARS metadata is shared, the provider should either:

        • Provide sufficient supporting information so that it is obvious to the receiver how template parameter values are applied during execution of analyses, or
        • Record all analysis-specific parameter values with.
Example


Pagenav