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

Managing Product, it is reference data or instance data? #139

Open
dubnemo opened this issue Mar 4, 2024 · 1 comment
Open

Managing Product, it is reference data or instance data? #139

dubnemo opened this issue Mar 4, 2024 · 1 comment

Comments

@dubnemo
Copy link
Collaborator

dubnemo commented Mar 4, 2024

It is unclear if Product is intended to be reference data or instance data about the product.
Is it product.description that is displayed in the tractor MICS? Asking for a friend.

Similar with with Packaged Product:
https://adaptstandard.org/docs/packaged-product/
Here I see:
https://adaptstandard.org/docs/packaged-product-instance/

With the increased awareness and need for Traceability, key data element identifiers would be valuable to capture specific instances of a product. Or we burying them into Context Items?

What about seed size instance related information? Can there be a general Measument component that the various product attributes are mapped into instead of specific qualified types?

image

@knelson-farmbeltnorth
Copy link
Contributor

@dubnemo The documentation out on the site is out-of-date. We will be publishing an update shortly.

Short answer: Product is reference information. The PackagedProduct/Instance components are not included in the 1.0 scope. See #117

The intent is not to bury traceability/supply chain things in context items or to omit them permanently. Traceability and observations are two big topics we will be pivoting to following work to wrap up 1.0.

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

No branches or pull requests

2 participants