Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

timestamp issue #30

Open
tschmidtb51 opened this issue Jun 15, 2023 · 2 comments
Open

timestamp issue #30

tschmidtb51 opened this issue Jun 15, 2023 · 2 comments

Comments

@tschmidtb51
Copy link

The current (and proposed in #25) spec violates the rule

[doc_time_first_isued] MUST equal the oldest [statement_time_first_issued] of all included VEX statements.

in the second example given in section Updating Statements with Inherited Data.

See also #29

@puerco
Copy link
Member

puerco commented Jun 19, 2023

Mmh I think this is one to take back to the wide VEX-WG. In my opinion this assertion is wrong:

[doc_time_first_isued] MUST equal the oldest [statement_time_first_issued] of all included VEX
statements.

While cascading the date from the document to the statements allows for more compact statements and less redundancy, a document should be able to be created at anytime containing VEX statements formulated in the past.

@puerco
Copy link
Member

puerco commented Jun 19, 2023

Tagging @zmanion for some perspective here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants