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
More like tech-debt than a bug, but we shouldn't assume too much about the stability of prov-json. It's a serialization of a much more flexible datastructure, and while I don't expect it to change, tying ourselves too tightly too it is like parsing xml with regexes. The easiest thing to point at are the colon-prefixes: These could be changed, without changing the semantics... but it would break us.
Some options:
See if some other part of the response has the information we need. (best?)
Propose additions to response which would provide what we need.
More like tech-debt than a bug, but we shouldn't assume too much about the stability of prov-json. It's a serialization of a much more flexible datastructure, and while I don't expect it to change, tying ourselves too tightly too it is like parsing xml with regexes. The easiest thing to point at are the colon-prefixes: These could be changed, without changing the semantics... but it would break us.
Some options:
cc @john-conroy
The text was updated successfully, but these errors were encountered: