CONTENTS
[ Back ] [ Next ]
Click Here to visit the home page belonging to
the creator of DCP and get access to other downloads, including a
white paper on forward compatible
design for the Internet.
| |
|
Reserved objects are predefined structures that facilitate and
standardize the exposition and transfer of a core set of objects that apply to all
devices. An asterisk (*) in the request URI
indicates that
the token that follows is a DCP reserved object. The get method
is used to request reserved objects.
Syntax
Example: Get Request for the object model (*OM) reserved object
GET DCP://security.domain.com/*OM DCP/1.0
In the example above, the target device would return it's object model in the entity body of the
response.Reserved objects essentially define a way
to query any device (known or unknown) for basic information and data.
|
|
|
The DCP Object Model is a reserved object which
conforms to a hierarchical object-oriented structure that provides a facility
for retrieving an object’s (or device's) child
objects, methods, properties and events. It exposes everything necessary to
carry on DCP communication with the device. The object model is returned within the
response's entity body with content negotiated prior to transfer.
Although an XML document type definition has been
defined for the DCP reserved object model, use of the representation with DCP is
not required. The reserved object only
facilitates the exposition and transfer of the object model.
Syntax
Example: Get Request for the object model (*OM) reserved object
GET DCP://security.domain.com/*OM DCP/1.0
The reserved object model essentially defines a way to query any device
(known or unknown) for information regarding its objects, properites, methods
and events.
|
|
|
The DCP User Interface (UI) object is a reserved object which
provides the facility for embedding, exposing and delivering object-specific user
interfaces within objects (or devices) themselves. The UI object is returned within the response's
entity body
with content negotiated prior to transfer. The user interface object may be implemented
with whatever technology the developer chooses and does not specify the
behavior for user interfaces. The DCP UI object only facilitates the exposition and
transfer of the interface.
Syntax
Example: Get Request for the user interface (*UI) reserved object
GET DCP://security.domain.com/*UI DCP/1.0
|
|
|
The Documentation object is a reserved object
which provides the facility for embedding and delivering object-specific documentation
within objects (or devices) themselves. The document object
is returned within the response's entity
body with content negotiated prior to transfer.
Syntax
Example: Get Request for the documentation (*DOC) reserved object
GET DCP://security.domain.com/*DOC DCP/1.0
|
|
|
The Driver Object is a reserved object
which provides the
facility for embedding, exposing and delivering software and hardware drivers within
objects (or devices) themselves. The driver object is returned within the response's
entity body with content
negotiated prior to transfer. DCP does not specify the behavior for drivers; it only
specifies the exposition and transfer. The driver object may be used to implement plug-and-play behavior. Since content is negotiated prior to transfer, more than one driver may be
embedded in a single object allowing for multi-platform support.
Syntax
Example: Get Request for the driver (*DRV) reserved object
GET DCP://security.domain.com/*DRV DCP/1.0
|
|