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

Cannot find information about ICAR_ValidSampleFillingIndicator code list #108

Closed
thomasd-gea opened this issue May 22, 2020 · 2 comments · Fixed by #117
Closed

Cannot find information about ICAR_ValidSampleFillingIndicator code list #108

thomasd-gea opened this issue May 22, 2020 · 2 comments · Fixed by #117

Comments

@thomasd-gea
Copy link
Contributor

During implementation of milk sampling information we came across this type:

icarValidSampleFillingIndicatorType.json

The enum values are just "0", "1" and "2" and the file references the "ICAR_ValidSampleFillingIndicatorCode list" which I couldn't find anywhere.

I'd propose to use more descriptive enum values in a future version of the standard (as this would be a breaking change). Unit then, putting information about the existing enum values into the description of the type would be very helpful.

@cookeac
Copy link
Collaborator

cookeac commented Jun 4, 2020

In the old ICAR XML documentation, the enumerated values mean
0 - successful milking (>80% of expected milk)
1 - incomplete (<20% expected milk) or interrupted
2 - complete, measurement not complete (between 20% and 80% of expected milk)

Without introducing a breaking change, the solution for 1.1 would be to document this in the description of the type.

@cookeac
Copy link
Collaborator

cookeac commented Jun 5, 2020

We decided we would do a short term fix by improving the description for the type (#116). For ADE-2 (breaking change) we will propose a more self-explanatory enumeration.

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

Successfully merging a pull request may close this issue.

2 participants