Uploaded image for project: 'OASIS Content Management Interoperability Services (CMIS) TC'
  1. OASIS Content Management Interoperability Services (CMIS) TC
  2. CMIS-164

Usage of <content> across multiple implementations

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: REST/AtomPub Binding
    • Labels:
      None

      Description

      reported by Ugo Cei during the PlugFest in Basel in keywords, so my interpretation may be off.

      Currently there are various different ways on how the implementation refer to the "enclosed" binary.
      Some use the <content> element someuse various link relations, this became particularly apparent when testing
      with various server implementations.
      It seems that the specification could be clear about how to use <content> possibly with an example.

        Attachments

          Activity

            People

            • Assignee:
              albertcbrown Al Brown (Inactive)
              Reporter:
              david@day.com David Nuescheler (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: