meeting support for issue processing

Dear All,

    

    short before the meeting and in the hope it is helpful:

    

    A) an ordered listing of the 37 issue candidates and there tentative
    processing section as proposed by todays agenda:

    

    JIRA Issues:

    

    
      
ODATA–31 “Section 9.1.3: Describe call choreography for 202
        Accepted (Async responses)” 7.3.1.3

      
ODATA–34 “Control verbosity of $metadata response: include
        annotations or documentation” 7.1.1.1

      
ODATA–37 “UPSERT: allow PUT and PATCH to the URL of a not yet
        existing entity to create this entity ” 7.2.6.5

      
ODATA–42 “8.2.5 If-None-Match: clarify use of If-None-Match in
        data modification or action requests” 7.2.6.4

      
ODATA–68 “Describe representation of ReferenceTypes in
        responses” 7.2.4.1

      
ODATA–102 “5.4.1/2 Representing Actions/Functions Bound to
        Multiple Entities” 7.1.5.1

      
ODATA–111 “Define supported numeric promotions” 7.2.6.3

      
ODATA–124 “For round-tripping values, what precision must
        agents support for DateTime(Offset), and are leap seconds
        permitted?” 7.2.1.1

      
ODATA–139 “New system query option $search for free-text
        search within an entity set” 7.1.6.2

      
ODATA–159 “Handling inline attachments in requests/responses”
        7.1.6.1

      
ODATA–192 “Define vocabulary term as a replacement for
        StoreGeneratedPattern attribute” 7.2.9.1

      
ODATA–204 “Define namespace versioning policy for XML
        namespaces” 7.1.4.1

      
ODATA–222 “free-text search within a property” 7.1.7.1

      
ODATA–228 “Specify $search for free-text search within a OData
        Service and specify $search for free-text search within an
        entityContainer” 7.1.6.3

      
ODATA–230 “Support use of parameter aliases in $filter and
        $orderby” 7.2.2.2

      
ODATA–232 “Enhance description of normalization procedures
        (public comment c201301e00001)” 7.2.2.1

      
ODATA–244 “Support navigation properties on complex types”
        7.1.3.1

      
ODATA–246 “IDs should be dereferenceable URIs” 7.2.6.2

      
ODATA–260 “Make explicit that DELETE on an entity may
        implicitly change links to and from other entities” 7.1.1.3

      
ODATA–264 “Allow omitting parent key(s) in URLs to contained
        children” 7.1.8.1

      
ODATA–267 “Allow Qualifier attribute on Annotation elements
        within an Annotations element that does NOT specify a Qualifier
        attribute” 7.1.2.2

      
ODATA–270 “Collections of Edm.PrimitiveType are problematic in
        JSON” 7.2.5.4

      
ODATA–274 “OData clients should always use PATCH, deprecate
        PUT” 7.1.1.2

      
ODATA–275 “Clarify whether binding parameters for actions and
        functions can be nullable” 7.2.5.3

      
ODATA–276 “Fix issues with entity references and rationalize
        with $links” 7.1.9.1

      
ODATA–277 “Remove Collation attribute” 7.2.5.2

      
ODATA–279 “Define URL conventions for addressing functions and
        function imports” 7.2.3.1

      
ODATA–280 “Support cast segment in $expand” 7.1.6.4

      
ODATA–281 “Keep second() as integer, introduce
        FractionalSeconds” 7.1.6.5

      
ODATA–283 “Accept-Charset HTTP Request Header and charset
        content-type parameter” 7.3.2.1

      
ODATA–284 “Annotating an Annotation” 7.1.2.1

      
ODATA–285 “Section 4.7: explicitly mention which property
        types allow appending /$value” 7.2.8.1

      
ODATA–288 “Change default decimal Scale to variable” 7.2.5.1

      
ODATA–292 “Questions on POST, PATCH and merge/replace
        semantics with related entities in composite relationships”
        7.2.6.1

      
ODATA–300 “Valid Syntax in JSON samples” 7.2.7.1

      
ODATA–306 “Batch Request processing: Define server behavior,
        if one or more request(s) didn’t succeed” 7.3.1.2

      
ODATA–321 “Use consistent naming for headers” 7.3.1.1

    
    B) List of Issue-IDs as copy and paste candidates to ease assemblage
    of grouping motions ;-) empty rows indicate a subsection change.

    

    ##Section 7.1

    ODATA-34, ODATA-274, ODATA-260, 

    

    ODATA-284, ODATA-267, 

    

    ODATA-244, 

    

    ODATA-204, 

    

    ODATA-102, 

    

    ODATA-159, ODATA-139, ODATA-228, ODATA-280, ODATA-281, 

    

    ODATA-222, 

    

    ODATA-264, 

    

    ODATA-276, 

    

    ##Section 7.2

    ODATA-124, 

    

    ODATA-232, ODATA-230, 

    

    ODATA-279, 

    

    ODATA-68, 

    

    ODATA-288, ODATA-277, ODATA-275, ODATA-270, 

    

    ODATA-292, ODATA-246, ODATA-111, ODATA-42, ODATA-37, 

    

    ODATA-300, 

    

    ODATA-285, 

    

    ODATA-192, 

    

    ##Section 7.3

    ODATA-321, ODATA-306, ODATA-31, 

    

    ODATA-283, 

    

    All the best,

    Stefan.