# GraphQL+- -\> Spec Compliant GraphQL

**URL:** <https://discuss.dgraph.io/t/graphql-spec-compliant-graphql/5891>\
**Category:** Dev\
**Tags:** graphql\
**Created:** [January 27, 2020, 1:15am UTC](https://discuss.dgraph.io/t/graphql-spec-compliant-graphql/5891 "2020-01-27T01:15:23Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![ajeet](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/ajeet/32/4161_2.png) [@ajeet](https://discuss.dgraph.io/u/ajeet)\
**Post date:** [August 31, 2020, 1:41pm UTC](https://discuss.dgraph.io/t/graphql-spec-compliant-graphql/5891/11 "2020-08-31T13:41:55Z")

</div>

> [@pawan](#):
>
> The spec does say that but it doesn’t define what that ordering should be.

Fair enough. Ordered doesn’t always mean “in the same order as the input”. In C++, a `std::set` is ordered, but stores items in sorted order. In Python, however, an `OrderedDict` retains the order of input.

I’ve looked at the spec and issues on GitHub and there is no indication of this there either, so perhaps we can move this from “GraphQL non-compliant” back to “nice-to-have”. Lists that retain their input order are definitely very useful - in the GraphQL survey forms app ([schema](https://github.com/dgraph-io/graphql-sample-apps/blob/master/surveyo/schema.graphql#L21)) we built, we needed an `order: Int` field containing the index of each item, just so that we could query them in order - which felt awkward.

I’m trying to get in touch with the GraphQL team via IRC/Slack/GitHub, I will update here if there is a reply.

---

_[View the full topic](https://discuss.dgraph.io/t/graphql-spec-compliant-graphql/5891)._