NamespacesLocate this document in the navigation structure

Use

The World Wide Web Consortium (W3C) http://www.w3c.orgInformation published on non-SAP site defined the naming and addressing standards for Web development. The EPCF uses these standards for the client-side eventing and data sharing.

Addressing Internet Resources

A Uniform Resource Identifier (URI) addresses a resource in the Internet in the following forms:

  • By name - Uniform Resource Name (URN).

  • By location - Uniform Resource Locator (URL).

URNs are intended to serve as persistent, location-independent, resource identifiers. URN can also be used to define distinct entities without being associated with an existing resource. For more information about the syntax, see the Request for Comments (RFC) 2141 at http://www.ietf.orgInformation published on non-SAP site.

Namespace Syntax

The namespace syntax is compliant with the URN specification, which is available from the W3C. Namespaces used in JavaScript function calls must be compliant to this specification.

A namespace must start with the urn prefix:

urn:<Namespace_identifier>:<Namespace_Specific_String>

The <Namespace_identifier> and <Namespace_Specific_String> tokens must be compliant with the recommendations of RFC 2141 and RFC 1630. It is recommended to use only lowercase, uppercase and numerical characters in the namespaces.

Namespaces reserved by the portal for core portal development are com.sapportals.portal.* and com.sapportals.* .

Name Syntax

Some of the EPCF methods receive a name parameter of the string type. Valid characters for the name are a to z, A to Z, 0 to 9, underscore(_), dash (-).