Arthur Foster

Hillman House,  4, Madeira Road,

Parkstone,  Poole,  Dorset   BH14 9ET

UK

Description of GDMO
 Name Binding Example

e-mail:

arthur@arthurfoster.com

tel: 

+44 (01202) 469468

fax:

+44 (01202) 469861

  

Home Site Map Search

Home Up Action Example Attribute Example Attribute Group Example Behaviour Example Managed Object Example Name Binding Example Notification Example Package Example Parameter Example

 
Name Binding Template
Create Operation
Delete Operation

 

This NAME BINDING example illustrates the main features of the template. This template example is taken from the Network Management Forum OMNIPoint 1 specifications.

The example below is the upperTester-root name binding. It is named from root.

 

Name Binding Example

 
    upperTester-root NAME BINDING
         SUBORDINATE OBJECT CLASS 
             upperTester AND SUBCLASSES;
         NAMED BY
         SUPERIOR OBJECT CLASS 
             "Rec. X.660 | ISO/IEC 9834-1 : 1992":root;
         WITH ATTRIBUTE upperTesterTitle;
         BEHAVIOUR named-By-RootBehaviour;
         REGISTERED AS {forum-nameBinding 163};
 

The upperTesterTitle attribute identified by the WITH ATTRIBUTE clause indicates that the upperTesterTitle attribute is used to name instances of the upperTester managed object class identified in the SUBORDINATE OBJECT CLASS relative to the 'root' managed object class identified in the SUPERIOR OBJECT CLASS clause . 'root' is a special object class that is the start of this naming tree.

This name binding has no modifiers which indicates that it will not be deleted or created by a management operation.

 
 
Author: Arthur Foster
28 May 2002

Arthur Foster is a

founder member of

 
 

Hosted by