Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard

Conal Tuohy <conal.tuohy@xxxxxxxxxxxx> · Tue, 08 Jan 2013 08:39:07 +1000



    On 07/01/13 13:23, Matthew Morley
      wrote:

    
      For me the deficiency is not in the pointer, but patch format
      being generated.

      
      One approach is to push that *one* test, structure conformity,
      into the pointer syntax. Another is via the type operation.

      
      If a vague patch is generated, vague results are to be expected.

    
    It seems to me, on the contrary, that the deficiency is in the
    pointer syntax, and I think it would be a mistake to try to work
    around that deficiency in JSON Patch. Because aren't there other
    things which one might do with JSON Pointer than use it with JSON
    Patch? There's been mention of having it registered as a URI
    fragment identifier syntax for JSON for example. JSON Pointers could
    then end up all over the place, outside of patches. IMHO JSON
    Pointer needs to be taken seriously as a technology in its own
    right. 

    
    -- 

      
        Conal Tuohy

        HuNI Technical
          Coordinator

        Victorian
          eResearch Strategic Initiative

        Skype: conal.tuohy

        Twitter: @conal_tuohy