Every component has a globally unique name. Component names are structured hierarchically and contain a unique vendor ID. You must define the name when you create the component; the name cannot be changed later.
The segments of a name are separated by slashes (“/”), and must start with the unique vendor identifier, followed by at least one more segment.
The syntax for component names is defined by the following rules:
component_name = vendor_id "/" name_segments
vendor_id = *( domainlabel "." ) toplabel
domainlabel = alphanum | alphanum *( alphanum | "-" ) alphanum
toplabel = alpha | alpha *( alphanum | "-" ) alphanum
name_segments = segment *( "/" segment )
segment = *pchar
pchar = alphanum | mark
mark = "-" | "_" | "." | "!" | "$"
alpha = "a" .. "z"
alphanum = alpha | "0" .. "9"
According to this pattern, allowed names are:
· sap.com/technology/logging, example.org/component_1.0
In this case, sap.com and example.org are vendor IDs derived from Internet domains.
The following names are not allowed:
· accounting(vendor ID is missing)
· example.org/component~accounting („~“ is not allowed)
· example.org/Component/ACCOUNTING (no uppercase)
The development infrastructure restricts the overall length of a component name to 40 characters. The requirements concerning the case, the character set to be used, and the maximum length of component names originate in the restrictions for paths and field names when the components are mapped to the file systems of certain operating systems.
Use only lowercase letters in component names.
Besides this technical name, a component should have a legible name intended for displaying and browsing. Define this display name when creating the component; it can contain any character from the Unicode character set.
For more information, see Tips for Naming Components.