Skip to content

Need validation or parse error when message is VMF, but no message_standard_version is defined.  #37

Open

Description

@mbeckerle

We have test data where the header indicates VMF data, but the optional message_standard_version field is not present.

This is not well formed and should be a parse error, or a least a validation error.

Related ticket #26

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions