Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: added JSON content

...

  1. The vendor must supply an XML or JSON Schema fully describing their extended ODM format.
  2. Extended ODM files should reference the proper extension Schema.
  3. The extension may add new XML elements and attributes, but may not render any standard ODM elements or attributes obsolete. Vendor extensions cannot be used for information that is normally expressed using other ODM elements.
  4. All For extensions represented in XML, all new elements and attributes must use distinct XML namespaces to insure that there are no naming conflicts with other vendor extensions. Since JSON does not support namespaces, extensions represented in JSON must ensure no naming conflicts exist with the ODM standard as well as any other vendor extensions involved in the targeted use cases.
  5. Removing all vendor extensions from an extended ODM file must result in a meaningful and accurate standard ODM file.
  6. Vendors should be able to produce ODM files free of any vendor extensions upon request.

...