Share via


Notational Convention

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

The following notation is used to specify attribute values and leaf element contents:

  • Element types begin with an uppercase letter.

  • Attribute names begin with a lowercase letter.

  • string indicates a string.

  • decimalindicates an integer using decimal notation. Only the ISO Latin-1 digits 0 to 9, +, and - are allowed.

  • timerepresents a date and time in (ISO 8601 extended) UTC format, yyyy-mm-ddThh:mm:ssZ. For example, 2006-01-10T00:04:00Z. The Z indicates UTC. All times in the API must be in UTC. Leap seconds are not supported. The behavior of times with years before the year 1990 is not defined.

  • The vertical bar (|) character is used to separate individual, noncontiguous values like those used for enumeration types, for example**[True|False],[ACL|Password]**

  • The notation [minimum to maximum] means the set of integers greater than or equal to minimum and less than or equal to maximum. This notation is used to specify the valid ranges of decimalattribute values.

Unless explicitly stated otherwise, the following defaults apply:

  • Elements are leaf elements, that is, they do not have children.

  • Elements have no attributes.

  • All attributes listed in the API Reference are required, unless specifically described as optional.

Maximum string lengths are often specified to be longer in replies than in requests. API client software must follow the shorter length restrictions when sending strings in requests, but must also be able to accept the longer strings in replies.

Remember that in XML, elements and attribute names are case-sensitive.

Most of the XML API examples included in this document use the same user name and password. It is recommended that application developers and conference center administrators use different user accounts and passwords to ensure the security of the conference center.

See Also

Concepts

Live Meeting service API Terms and Concepts