NCA defines the following framework identifiers (a “framework” identifier is an identifier that is used by the basic NCA framework, irrespective of application).
Uniquely identifies a class. Stored in property NcObject.classId
|NcClassId||NCA control model||Permanent|
Further information provided in Appendix A.
Compact read-only handle that uniquely identifies an object within its device. Stored in property NcObject.oid.
|NcOid||Device||Constant until reboot|
Static identifier of a property, method, or event of a control class.
Static, read-only text property that names an object within the block to which it belongs. Unique within the block. Stored in property NcObject.role.
Uniquely identifies the location of an object within a device model. Sequence of strings, consisting of the
role values of all the object’s containing blocks, starting from the root block and ending with the object’s own
Role paths are enabled by the existence of blocks in the device model.
Read/write string that users can set to identify an object’s operational purpose in a particular application context. Analogous to the texts written on mixing console scribble strips, labels, and bits of paper tape affixed to equipment in use. Stored in property NcObject.userLabel.
UUID that uniquely identifies the particular product that constitutes the Device. Stored in field
uuid of datatype NcProduct. In turn, product descriptor for a Device is stored in property NcDeviceManager.product.
NCA-NMOS identity mapping
NCA’s Touchpoint feature allows applications to attach a list of touchpoints to any control object. A touchpoint is a defined relation between an entity in NCA and an entity in a different namespace. Stored in property NcObject.touchpoints.
NCA discoverability in IS-04
Compliant NCA protocols are advertised through existing IS-04 practices inside the controls array of an NMOS Device.