Update to handle constraints?

[cbizon]

Where should constraints go? Is it an option on our fill/bind operations? Subclasses thereof? Does everybody have to match the constraint? What if the tool lacks the data (like a node property) on which to perform the constraint?

[cbizon]

After discussing on the O&W call, we agreed to add a post-condition to fill that constraints be honored in any result.

[dkoslicki]

Will need to write up code snippets here that validates all constraints are satisfied (properties, categories, etc.).
Patrick estimates doable, but not simple

[dkoslicki]

Perhaps just say: "Any constraints specified in the TRAPI must be respected by fill/lookup" in the description of the operation

[finnagin]

TODO: add "Any constraints specified in the TRAPI must be respected by fill/lookup" to the descriptions of fill, lookup, & lookup_and_score in a new PR