Doc plan

[congysu]

ODataLib: Use ODataLib to write an OData service: in-mem is fine
    EdmLib:
        Notions:
            Entity set
            Entity type
            Primitive type
            Entity container
        Model creating: Create an EdmModel with Edm API: imperetive
            Minimal Edm model: single entity set, singe entity type, primitive structral properties
            model with collection-valued properties
            model with nav-prop
            model with complex type
            with enum type
            with spatial types
            with action, and function
            with annotations
            with model ref
        Model search:
            search a type: by name, ns+name, instance ref?
            search a property: by name, ns+name, instance ref?
            search an operation: by name, ns+name, instance ref?
            case insentive, namespace free

    SpatialLib:
        Notions:
            Geometric
            Geographic
            Point, line, polygon, other?
            IOT?
        Model:
            Add a location property to a model, and with a distance function

    OData Core Lib:
        Reader/Writer
            Write an OData Entry (with only primitive properties) to a json payload
            Write an OData Entry: with collection-valued properties to a json payload
            Write an OData Entry: with a navigation properties to a json payload: minimal, full, none
            Write an OData Entry: with a complex-valued properties to a json payload
            Write an OData entry: with enum properties to a json payload
            Write an OData entry: with spatial properties to a json payload
            Write an instance annotation
            Write an OData feed: repeat above
            Write an OData raw value: primitive, collection-valued, nav prop (link?), complex-valued, enum
            Read an OData entry: repeat above
            Read an OData feed: repeat above
            Read an OData raw value: repeat above
        Parser:
            How does each output AST look like? describe it
            Parse path:
                service root, $metadata
                entity set
                entity_set(key)
                entity_set/key
                entity_set/key/structural_prop
                entity_set/key/nav_prop
                function|action
                entity_set/function|action
                entity_set/key/function|action
                entity_set/$count
                entity_set/key/nav_prop/$count
            Parse query options:
                $filter
                $select & $expand
                $skip & $top
                $orderby
                nested $filter in $expand
                nested $select in $expand
                $levels
                $format
        Builder:
            How to construct the input?
            Repeat each parser scenario

Client: Use client to send a request, and receive a response without and without T4

WebAPI: model builder, routing, parameter binding, input/output formatting
    Model builder
        Model builder:
            Declartive programming
            Fluent APIs
        Convention model builder:
            Convention over configuration
    Routing
        Convention route
        Attribute route
    Paremter binding

RESTier: