|PDI Tag to Class/Property Mappings|
The following topics define each of the vCard, vNote, and calendar objects and their properties. For each tag, the matching EWSoftware PDI class is given. PDI property classes may have several attributes in addition to their actual data value such as an encoding method, data type/location, etc. Refer to the BaseProperty class for the attributes common to all property classes. Refer to the derived classes for type-specific attributes.
The appropriate data value property name is also listed in the tables within each topic. For any property class regardless of the underlying data type, the Value property will return the data value in string form. For non-string property classes, there are also type-specific properties that return the property data in a more natural format (i.e. DateTimeValue for date/time properties or TimeSpanValue for properties that deal with time spans). Property classes with compound data values have multiple properties that let you access the individual parts of the data value (i.e. the parts of the AddressProperty or ProductIdProperty).
Several properties are specific to only one version of their related specification. This is indicated in the notes column. Property tags are listed in alphabetical order within the components. However, their actual order in the PDI data stream is not significant and the properties can appear in any order as can the components themselves.
Many of the property objects can appear more than once in a component. In those cases, a matching type-safe collection class also exists to contain them. As a convenience, the property collections contain an overloaded Add method that take an object of the underlying data type so that you can quickly add values to the collection without having to create an instance of the property type first, assign the value to it, and then add it to the collection.