You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more of a question and/or feature request. From reading some of the webinars regarding QIF, a lot of them advertise that QPIds are used to uniquely identify components within the QIF Document such as Results, Feature Items or Characteristic Items.
But from my understanding after using the QIF Python bindings and reading the XSD schemas for QIF 3.0, QPIds are only used to identify an instance of a QIF document, where child components such as Feature Items are IDed with plain integer numbers.
If I'm not mistaken, then why is this the case? Why not use UUIDs to identify everything?
The text was updated successfully, but these errors were encountered:
Hi,
This is more of a question and/or feature request. From reading some of the webinars regarding QIF, a lot of them advertise that QPIds are used to uniquely identify components within the QIF Document such as Results, Feature Items or Characteristic Items.
But from my understanding after using the QIF Python bindings and reading the XSD schemas for QIF 3.0, QPIds are only used to identify an instance of a QIF document, where child components such as Feature Items are IDed with plain integer numbers.
If I'm not mistaken, then why is this the case? Why not use UUIDs to identify everything?
The text was updated successfully, but these errors were encountered: