RFC200: V23.
RFC213 Serial Device: Updated based on ML comments.
[RFC189] Update javadocs, add new property for defining the resource pattern, remove special cases for selecting a servlet context helper
[RFC189] Accept all changes
RFC200: add UML classes diagram in svg format.
Added contracts.json
RFC200: Update UML schema.
Initial version of Log Service Update RFP.
RFC200: UML diagram is now fully compliant with the OSGi requirements.
RFC 202 USB Information Device Category: Modified based on F2F meeting in Madrid.
RFC200: Update UML diag (1 todo remains).
RFC200: RFC is now in version V24.
RFC200: push RFC's .pdf in final format (all the modifications are
accepted).
RFC200: Update javadoc.
RFC200: V25.
RFC 208: Updates from bug 2725

1) The name is just a human readable string, so the spec does not need to
prescribe a specific algorithm here.

2) The javadoc describes that the default value can come from the annotated
element's default value.

3) The enum value's name will be used for both the option label and value.

4) Tools processing these annotations must always generate valid Meta Type
Resource XML documents. If this is not possible, then the tool must report an
error to enable the programmer to take corrective action.
RFC 208: OCD can be applied to annotations and interfaces

Clarify that ObjectClassDefinition annotation can be applied to
annotation types and interface types. Use on concrete and abstract class
types is not supported.
RFC 208: Update description of default type and cardinality values

Supporting applying ObjectClassDefinition to interfaces required some
more detail in the design.
RFC 208: Include List/...<Enum> in option values/labels defaults