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
How are you guys dealing with trade documents beyond the maximum 34 parameter limit? I suppose the only choice it to revert to online by-reference? If that's your recommendation, is this documented anywhere so we can follow your best practices?
Do you see a "graceful degradation" kind of approach, where issuers encode by value up to the parameter limit, and then encode by reference for larger documents? Curious about your thoughts on this...
The text was updated successfully, but these errors were encountered:
Hi @nissimsan, yes we are implementing via an online hosted solution (e.g. storage bucket) due to the size limitations of QR codes.
You may find a brief explanation documented under the Universal Actions section. Essentially, the hosted URL of the document is provided as a query parameter to the verifier.
We have also listed out a few distribution methods along with their pros & cons.
I'm looking with interest at https://github.com/Open-Attestation/open-attestation/tree/master/benchmarks/qr-code
How are you guys dealing with trade documents beyond the maximum 34 parameter limit? I suppose the only choice it to revert to online by-reference? If that's your recommendation, is this documented anywhere so we can follow your best practices?
Do you see a "graceful degradation" kind of approach, where issuers encode by value up to the parameter limit, and then encode by reference for larger documents? Curious about your thoughts on this...
The text was updated successfully, but these errors were encountered: