Documentation of the Expected Json for visualisation

[adhamhashibon]

It is quite difficult to get the jsonld in the right dformat that Medusa expects, so it would be great to have a documentation (e.g., in Readme, or better in a docs folder) that shows the format expected, and how it is handled in MEdusaVis. @robertobendi @chichiariscelavia could you please check and provide this information please?

[robertobendi]

here's a quick summary!

@graph: Contains an array of objects representing nodes in the graph. Each object represents an entity or node with properties. @id: Unique identifier for the entity. @type: Specifies the type of entity (e.g., Person, Organization). Other properties such as name, knows, etc., provide additional information about the entity.

an example:

{
  "@context": {
    "@vocab": "http://schema.org/"
  },
  "@graph": [
    {
      "@id": "http://example.org/entity1",
      "@type": "Person",
      "name": "John Doe",
      "knows": [
        {
          "@id": "http://example.org/entity2"
        },
        {
          "@id": "http://example.org/entity3"
        }
      ]
    },
    {
      "@id": "http://example.org/entity2",
      "@type": "Person",
      "name": "Jane Smith"
    },
    {
      "@id": "http://example.org/entity3",
      "@type": "Organization",
      "name": "Example Corp"
    }
  ]
}

this is just what i came up with looking at the example file i was give, i can easily change the keywords the script looks for

hope this helps,

Roberto

[adhamhashibon]

great, thanks for this useful information.

does Medusa make use of the information under context, or is it always ignored?