Open Data Tables schema forces order of some elements

The schema for Open Data Tables requires that elements within select bindings be ordered (urls, paging, inputs, execute). While I can see how this order may be helpful when reading the source of the Open Data Table, the documentation explains these elements with paging and inputs transposed - nowhere in the documentation is the required order explained. Furthermore, within the paging element the order of elements is also strictly enforced. It seems that the schema should be relaxed so that these elements can be arranged in any order - their source order seems to have no meaning. If for some reason the schema cannot be changed, the documentation needs to be updated.

2 Replies
  • Hi David,

    Thanks for taking the time to explain this issue. I've asked the YQL team to take a look at it.

    Please keep sending feedback.

    Best regards
  • I just committed a fix which relaxes the ordering of the sub-elements of <binding> and <paging>. The fix will become available with the 2.6.1 release. Thanks for the feedback!

Recent Posts

in YQL