The name of the parameter. The enumerated type of the service. The name of type descriptor where additional data element information can be located. . An indication of the optionality of the parameter The encoding type of the parameter. For parameters offered by Node 1.1 services – this indicates in which order the parameter should be sent. The number of times the parameter should be repeated in the request. The type of the service request, it must be one of the web methods defined in the Node Function Specification 2.0, such as Query, Solicit ,Execute or Submit. The name of the dataflow for the service. This is required for Query and Solicit method. The name of the service request. This should be a unique identifier under a particular dataflow. A text description of the service A URL pointing to additional documentation of the service. A name-value pair for additional service properties. The element is optional and may occur multiple times. A default style-sheet which could be used to transform the results to a displayable format. The element is optional.. The StyleSheetType includes a string URL and an associated type identifier. The value of the type identifier is defined in the relevant Flow Configuration Document, but should generally indicate the output format of the instance document after the style sheet transformation. This is a list of parameters defined in the next section. The value of the element could contain a list of allowable values for the parameter separated by comma. The name of the node. Although this can be any string, it is recommended that the name is the same as the node name defined in the Network Authentication and Authorization Services (NAAS). A short name of the node. The SOAP address of the node. It should be a fully qualified URL. The name of the service provider. Email address and/or phone number of the technical contact person. The version number of the node. Valid version numbers are 1.1 and 2.0. The deployment environment of the node. It should be development, test or production. This determines which security service to be used. The current status of the node. It should be the same status string returned by the NodePing method. Other properties associated with the node, such as a string description. This is a name-value pair that could occur multiple times. A set of four lat/long coordinates that defines the geographic boundary of a Node’s data. A list of services offered by the Node.