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

Not possible to validate FlexSettlementType ISP boundaries #38

Open
radboudp opened this issue Jun 14, 2022 · 0 comments
Open

Not possible to validate FlexSettlementType ISP boundaries #38

radboudp opened this issue Jun 14, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@radboudp
Copy link

FlexSettlementType FlexOrderSettlementType does provide a Period, but no ISP-Duration or TimeZone that are needed to validate the provided ISP (start, duration) combinations. TimeZone is required to determine the length of the day in case of summer/winter time transition and ISP-Duration is required to determine the number of ISPs that fit in the day's length.

Same goes for FlexSettlementType ContractSettlementType ContractSettlementPeriodType ISP list.

For FlexSettlementType FlexOrderSettlementType one can argue that there must be a FlexOrder and the ISP provided must correspond the ISPs provided in the FlexOrder referred to by the OrderReference field (available according to the documentation, but not in the XSD). There also is no FlexOrderMessageID, which would be more useful then the OrderReference. But this validation which I think should take place between the FlexOrderType and the FlexOrderSettlementType that the list of ISPs match, is not described in the documentation that it should be performed.

I do not see any other means to validate the FlexSettlementType ContractSettlementType ContractSettlementPeriodType ISP lists.

@radboudp radboudp added the bug Something isn't working label Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant