OMNA URI-List Usage Name Registry
OMNA maintains a registry for Usage Names of URI-Lists associated with datasets in the XML Document repository. These values are for known top-level lists and are conveyed in the name attribute to the top-level <list> element.
Section 5.1.8 of OMA-TS-XDM_Shared-V1_0 specification defines the naming convention for OMA generated names and makes the initial reservations.
The URI-List names follow a simple naming model that permits unambiguous usage of the names for the URI-List.
The following grammar:
{ListLabel} ::= {OMAlabel} | {ExtLabel}
{OMAlabel} ::= oma_{OMAListItem}
{ExtLabel} ::= ext_{EntityRevDomain}_{ExtListItem}Where:
- {OMAListItem} and {ExtListItem} are pure alphabetic strings made up of just lowercase alpha characters
- {EntityRevDomain} is a reverse domain string for any entity wishing to produce local lists: OMA URI-List Registered Usage Names
The following list is of values used for name attributes of top-level URI-Lists defined by OMA Enablers. For each registered name, a brief description and a specification reference is provided.
| OMA URI-List Usages |
| Name | Description | OMA Reference Specification |
| oma_allcontacts | This name SHALL be used by an XDMC that has a need to store all users URIs, that it knows about, in one list independent of how the URIs are used. | OMA-TS-XDM_Shared-V1_0 |
| oma_blockedcontacts | This name SHALL be used by a XDMC that has a need to store URIs to users, that it want to block/reject in a number of application usages, in one list. | OMA-TS-XDM_Shared-V1_0 |
| oma_buddylist | This name SHALL be used by an XDMC that has a need to store all users URIs, that it wants to use for all types of communication, in one list. | OMA-TS-XDM_Shared-V1_0 |
| oma_pocbuddylist | This name SHALL be used by an XDMC that has a need to store users URIs, that it wants to use for PoC communication, in one list. | OMA-TS-XDM_Shared-V1_0 |
Externally-defined URI-List Usage Names
OMNA does not register externally defined list usage name labels but does put in place a scheme by which such entities should not accidentally invoke the same name value. This scheme uses the reverse domain text as a part of the label.
Examples of permitted labels include:
ext_org.foo_barlist
ext_com.vendor_specialfunctionlist
There is no requirement to inform OMNA of such usage.