Skip to content

need to clarify: should implementation ignore conflicting information in the input object? #808

@mr-c

Description

@mr-c

Conformance test 1 include an input object where one of the inputs, a File, has an incorrect size and checksum.

There appears to be no guidance in CWL v1.0 about this situation.

I feel that ignoring this is bad; what if the File was a remote resource and the user had specified the size and checksum as an indication of what they expected.

  • Clarify the intent
  • Document in v1.1
  • Adjust the conformance tests to implement this in a specific test or tests

Again, many thanks to @tom-tan for bringing this to my attention

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions