XML Naming Standards General Guidelines

29-2 Developers Guide for Oracle Application Integration Architecture Foundation Pack No special characters such as spaces, -, _, ., , , , [] ■ Indicate artifact type in the name to reduce ambiguity When the same name is used for different artifact types, append a suffix to indicate its type. It makes it easier to distinguish these artifacts by identifying their types: Artifact NameType Suffix Example: InvoiceEBO, InvoiceEBOType, InvoiceEBM, InvoiceEBMType. ■ The total path length to a named artifact must not exceed 17000 characters. Some operating systems such as Windows have a limit of 255 characters for file names. Some room is left for prefixing with complete network directory or URL.

29.1.1 XML Naming Standards

The following standards are based on UNCEFACT - XML Naming and Design Rules.

29.1.1.1 General Naming Standards

Follow these general naming standards: ■ Lower-Camel-case must be used for naming attributes. Example: xsd:attribute name=unitCode ■ Upper-Camel-case must be used for naming elements and types. Example: xsd:element name=UnitOfMeasure xsd:complexType name=InvoiceEBOType ■ Names must be singular unless the concept itself is plural. For example repeating elements must have a singular name. ■ Names must not contain special characters such as: space, -, _, ., , , , .... ■ Avoid having numeric characters in the name. There are cases were using a numeric character is required to convey some significance. ■ Complex type names should end with the Type suffix to make it easier to recognize types from elements. Example: xsd:complexType name=InvoiceEBOType ■ The name of a simple type definition should be the name of the root element with the ContentType suffix. Example: xsd:simpleType name=PhoneNumberContentType

29.1.1.2 General Namespace Naming Standards

These are the general namespace naming rules. More detailed rules are described in the following sections, especially naming rules for EBS and ABCS. ■ All namespaces must start with http:xmlns.oracle.com. ■ Namespaces used by Enterprise Business Objects EBOs and Enterprise Business Messages EBMs start with http:xmlns.oracle.comEnterpriseObjects. Example: http:xmlns.oracle.comEnterpriseObjectsCoreEBOInvoiceV1 Oracle AIA Naming Standards for AIA Development 29-3 ■ Namespaces used for externally facing services must start with http:xmlns.oracle.comEnterpriseServices . Examples: http:xmlns.oracle.comEnterpriseServicesCoreInvoiceV1 http:xmlns.oracle.com EnterpriseServicesIndustryTelcoInvoiceV1 ■ Namespaces for versioned artifacts must have the major version number as a suffix with V as an abbreviation for version. Example: http:xmlns.oracle.com EnterpriseObjectsCoreEBOInvoiceV1 ■ The namespace structure should closely map to the taxonomy of the types it encapsulates. Example: Horizontal: http:xmlns.oracle.comEnterpriseObjectsCoreEBOInvoiceV1. Telco: http:xmlns.oracle.comEnterpriseObjectsIndustryTelcoEBOInvoiceV1. ■ Namespaces for artifacts generated within ABCSs must start with: http:xmlns.oracle.comABCS . ■ When importing or including schema in a schema file, the schema location must always use relative path. Example: xsd:importnamespace=http:xmlns.oracle.comEnterpriseObjectsCoreEBOInvoiceV1 schemaLocation=........CoreEBOInvoiceInvoiceEBO .xsd ■ Namespace prefixes must be a minimum of six 6 lowercase characters abbreviation of the namespace. The abbreviation must be descriptive and unambiguous within the context where it is being used. ■ Namespace prefixes for EBOs and EBMs must adhere to the following standard wherever used regardless of the applications or technology used. Auto-generated prefixes such as ns1, ns2 must not be used. Auto-generated prefixes for standard namespaces such as xsd, xsi are acceptable. Table 29–1 provides details on the namespace patterns and files associated with namespace prefixes. Table 29–1 Namespace Prefixes Prefixes Namespace Pattern Files corecomcust http:xmlns.oracle.comEnter priseObjectsCoreCustomCo mmonV1 CustomCommonComponents, CustomReferenceComponents coreinvcust http:xmlns.oracle.comEnter priseObjectsCoreCustomEB O InvoiceV1 CustomInvoiceEBO corecom http:xmlns.oracle.comEnter priseObjectsCoreCommon V1 CommonComponents. Reference Components coreinv http:xmlns.oracle.comEnter priseObjectsCoreEBOInvoic eV1 InvoiceEBO coreinv http:xmlns.oracle.comEnter priseObjectsCoreEBOInvoic eV1 InvoiceEBM 29-4 Developers Guide for Oracle Application Integration Architecture Foundation Pack

29.1.1.3 Participating Applications Names

When participating application names are part of an artifact name, upper-camel-case short names should be used. For cases where an abbreviation is needed, an upper-case abbreviation should be used. Table 29–2 provides a list of short names and abbreviations used for participating applications. telcocomcust http:xmlns.oracle.comEnter prisObjectsIndustryTelcoC ustomCommonV1 CustomCommonComponents, CustomReferenceComponents telcoinvcust http:xmlns.oracle.comEnter priseObjectsIndustryTelcoC ustomEBOInvoiceV1 CustomInvoiceEBO telcocom http:xmlns.oracle.comEnter priseObjectsIndustryTelcoC ommonV1 CommonComponents. Reference Components telcoinv http:xmlns.oracle.comEnter priseObjectsIndustryTelcoE BOInvoiceV1 InvoiceEBO telcoinv http:xmlns.oracle.comEnter priseObjectsIndustryTelcoE BOInvoiceV1 InvoiceEBM Table 29–2 Short Names and Abbreviations for Participating Application Names Application Short Name Abbreviation Oracle E-Business Suite Ebiz EBIZ Oracle Siebel Siebel SEBL Oracle PeopleSoft PeopleSoft PSFT Oracle JD Edwards Enterprise One JDEOne JDE1 Oracle JD Edwards World JDEWorld JDEW Oracle Transportation Management Suite Logistics LOGIS Oracle Telephony Work Telephony TELE Oracle Demantra Demantra DMTR Oracle Communications Billing and Revenue Management Portal PORTAL Oracle Retail Applications Retek RETEK Table 29–1 Cont. Namespace Prefixes Prefixes Namespace Pattern Files Oracle AIA Naming Standards for AIA Development 29-5

29.2 Composites