See: Description
| Interface | Description |
|---|---|
| Component |
Implemented by types that can immediately nest inside a
<presence> element. |
| ComponentSwitch |
Visitor pattern interface for
Component classes. |
| Class | Description |
|---|---|
| Contact |
PIDF
<contact> element. |
| Device |
The
<dm:device> element as defined in RFC 4479. |
| LangContent |
Represents a string and a specified language.
|
| Person |
The
<dm:person> element as defined in RFC 4479. |
| PIDF |
Contants associated with the Presence Information Data Format (PIDF).
|
| Presence |
Top level element in the Presence Information Data Format (PIDF).
|
| Status |
PIDF
<status> element. |
| Tuple |
PIDF
<tuple> element. |
| Enum | Description |
|---|---|
| Basic |
PIDF
<basic> element values. |
This package includes several abstract JiBX mapping definitions for PIDF XML structures
and one concrete JiBX binding named "pidf" defining a mapping for the <pidf:presence> element.
The binding technically does not adhere to RFC 3863 because it doesn't allow arbitrary nested
elements from other namespaces in several locations where supporting that is required. This is
because JiBX doesn't support doing that.
Several re-usable abstract mappings are defined in this package, including:
pidf:presence<presence> element; represented by Presence.pidf:tuple<tuple> element; represented by Tuple.pidf:status<status> element; represented by Status.pidf:contact<contact> element; represented by Contact.
The type-names listed above use the following XML namespace prefixes:
pidfurn:ietf:params:xml:ns:pidf