Page Comparison

...

note:
V1T2P8 -> DIAL code used to link the content

@context:

Context infomation information will be stored in the JSON file. Which can be configured/defined by the user specific to each context type. User can send the request of specific context, which will be validated against this JSON-LD context file.

note:
Here we are not using @graph object declaration in the context data/file.
Hence all the context information will be stored against single graph node of the dialcodeDIAL code.(if we use graph DB to store)

...

• All the properties are storing against the single node object(dialcodeDIAL code).

Context with @graph

Here we are using @graph declartion declaration in the context for JSON-LD declaration. Hence user has to send the request also in the graph format so that we can validate the request against the @context delcaration declaration.

We are taking he same examples of Textbook & Certificate explanied explained above.

Textbook: http://example.org/dialcode-textbook.json

Context file data to validation when textbook is linked to dialcodeDIAL code

{
  "@context": {
    "schema": "http://schema.org/",
    "dial": "https://example.org/dial"
  },
  "@graph": [
    {
      "@id": "framework",
      "@type": "schema:name",
      "rdfs:comment": "Class to represent a framework.",
      "rdfs:label": "framework",
      "rdfs:subClassOf": {
        "@id": "schema:CreativeWork"
      }
    },
    {
      "@id": "DIALCode",
      "@type": "schema:Code",
      "rdfs:comment": "Class to represent a DIAL code.",
      "rdfs:label": "DIALCode",
      "rdfs:subClassOf": {
        "@id": "schema:Code"
      }
    }
  ]
}

...

• Duplicate entries in the context column, if the DIAL codes at linked to the child nodes of the same collection.

• Any update on the context information on the parent node should update all the child node context(multiple entires in the DB)

Solution 2:

Separate dialcode DIAL code context information from dial-service metadata DB.

...

• Discovery by context is not possible. We can’t do any queries on DIAL code metadata/context.

• Easy to store any unstructured data as nodes & give the relation between nodes. This helps to store different types of context with respect to multiple use-cases.

• Any update of the root level context is just an a linking to different node.

...

• JSON-LD reference: https://linked.art/api/1.0/json-ld/

• DIAL spec: https://github.com/sunbird-specs/DIAL-specs

MOM:

March 1, 2022

• Decided to not using @graph object declaration in the context data/file.

• Decided to use schema instead on frame object for validation. Understanding the frame object is overhead for adopter.

• Action Item: Jayaprakash Narayanaswamy needs to build the POC for schema validation while accepting the request and return json-ld object in response.