Uploaded image for project: 'OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC'
  1. OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
  2. TOSCA-119

TOSCA should specify what to use in the accept Header for HTTP REST requests.

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: New
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Spec
    • Labels:
      None
    • Proposal:
      Hide

      application/xml may be a sufficient default since most frameworks and browsers understand natively, but additional accept headers may make sense like the below:

      application/tosca+xml;version=1.0

      When additional formats or versions come out then it might also allow:

      application/tosca+xml;version=1.1
      application/tosca+json;version=1.1

      Show
      application/xml may be a sufficient default since most frameworks and browsers understand natively, but additional accept headers may make sense like the below: application/tosca+xml;version=1.0 When additional formats or versions come out then it might also allow: application/tosca+xml;version=1.1 application/tosca+json;version=1.1

      Description

      TOSCA does not address wire protocols for making REST requests for TOSCA documents.

      For example, what should the accept type be in the following situations:

      • CSAR
      • Definitions Document
      • Schema documents

      One could infer that for the CSA it would be application/tosca-csar or application/csar
      For definitions documents, it could be application/xml.

      However, in the second case, this would be insufficient according to intended HTTP accept header usage.

      This issue perhaps should be linked to https://tools.oasis-open.org/issues/browse/TOSCA-7

      For some background on Accept type, the following article is interesting:

      http://www.informit.com/articles/article.aspx?p=1566460

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              travis.tripp Travis Tripp (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: