This provided unique identification for an element, across the specification artifact. Since an element can have multiple server as well as client identities, what is chosen for universal identification could vary for different platforms.

For dWebSpec specification the choices are between the "name" and "id" attributes of the corresponding HTML form elements. The earlier is preferable since it also represent the server side data identity for the element.

This corresponds to JSF component identifier.

This is the identifier for a component; although it could be used for linking all the specification artifacts, some caution need to be taken in attempting its' use in relation to client scripting.

As mentioned, this is the component identifier, although the client identifier is derived from it, they are not interchangeable. The client identified starts with the names of the parent naming container, in this form:

	naming-container-component-id:element-component-id

example

	myForm:myElement

This could be recursive: a parent could have a parent. As such, if the component-id is referenced in client scripting, it would not reflect the true client-id at runtime. If also used in the CSS style sheet, it would be imprecise, and the style sheet would not accommodate the full client-id because of the embedded colon.