Spec refining: Merkle-paths to an array's index

[TimDaub]

Hi,

it is likely that this already came up in some other repository. If so maybe just link there and I'll elaborate there. My question is:

Say I have the following ipld object:

{
  "someKey": "andValue",
  "listOfKeys": [
    {
      "someKey": "aValueIWouldLikeToRetrieve"
   },
   ...
  ]
}

Let's assume this object can be addressed using this hash: QmAAAA...AAA.
How can I address the x-th index of /QmAAAA...AAA/listOfKeys/?
Or to formulate a general question: How can specific indexes in a list/array in IPLD using merkle-paths be addressed?

[nicola]

Hey thanks @TimDaub for your question, we are going to write a better spec to include example and cases like this. The agreement has been to follow the json-pointers spec closely, so in this case:

hash/listOfKeys/0/someKey === "aValueIWouldLikeToRetrieve"

Let me know if there are other questions about this

[TimDaub]

Thanks to @sohkai I just found this example in the spec:

> ipld cat --json QmCCC...CCC/doge.jpg
{
  "subfiles": [
    {
      "/": "QmPHPs1P3JaWi53q5qqiNauPhiTqa3S1mbszcVPHKGNWRh"
    },
    {
      "/": "QmPCuqUTNb21VDqtp5b8VsNzKEMtUsZCCVsEUBrjhERRSR"
    },
    {
      "/": "QmS7zrNSHEt5GpcaKrwdbnv1nckBreUxWnLaV4qivjaNr3"
    }
  ]
}

> ipld cat --yml QmCCC...CCC/doge.jpg
---
subfiles:
  - /: QmPHPs1P3JaWi53q5qqiNauPhiTqa3S1mbszcVPHKGNWRh
  - /: QmPCuqUTNb21VDqtp5b8VsNzKEMtUsZCCVsEUBrjhERRSR
  - /: QmS7zrNSHEt5GpcaKrwdbnv1nckBreUxWnLaV4qivjaNr3

> ipld cat --json QmCCC...CCC/doge.jpg/subfiles/1/
{
  "data": "\u0008\u0002\u0012��\u0008����\u0000\u0010JFIF\u0000\u0001\u0001\u0001\u0000H\u0000H..."
}

All good :)

[nicola]

hey @RichardLitt, can we keep the need spec label? I think they aim at the new spec (which looks less like a tutorial, more like a spec). It's basically a way to keep track of what needs a better spec!

[RichardLitt]

Added back!

[nicola]

(sorry little change in the way we work in writing the spec, will leave this issue open until we are done with writing it)

[rvagg]

Closing due to staleness as per team agreement to clean up the issue tracker a bit (ipld/team-mgmt#28). This doesn't mean this issue is off the table entirely, it's just not on the current active stack but may be revisited in the near future. If you feel there is something pertinent here, please speak up, reopen, or open a new issue. [/boilerplate]