Skip to content

Q re JSON-LD output structure #153

Description

@mih

Looking at the structure of the current output, I see that I get essentially three @graph, two of which are nested into the third:

{
  "@context: {...},
  "@graph": [
    {
      "@graph": [...]
    },
    {
      "@graph": [...]
    }
]
}

I wonder what the motivation is to use this particular structure over

  1. a single @graph with all the documents
  2. somehow named or identified nested graph that enable an easy decision which one has the prov info on nidmresult generation, and which one has the real thing

Regarding a semantic interpretation both modifications should not have an impact, but a simple script eating these data would have an easier time looping through a single list, than having to consider a possibly implicit structure in the node array of the top-level graph.

Thx!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions