PaginationContainer inconsistent with connections spec

I recently added the PageInfo and Edge Type interfaces to my GraphQL schema in support of a relay PaginationContainer and noticed an inconsistency with the [connection spec](https://facebook.github.io/relay/graphql/connections.htm#sec-undefined.PageInfo). Relay requires both `startCursor` and `endCursor` fields in PageInfo, which are not mentioned in the spec. It also appears not to use the `cursor` field on Edge Types which is required by the spec (not needing this field actually simplifies things in my case, as my backing datastore has no native concept of a per-item cursor/token).

Should the spec be updated to reflect the type of connection Relay expects?

Start by reading the linked connection spec and comparing its PageInfo and Edge Type requirements with the behavior expected by Relay's PaginationContainer. The issue mentions no files or tests; done would require a decided resolution for the mismatch and a corresponding specification change if one is agreed.

Written by the indexing model from the issue text.