Page Comparison

...

1. import/export for creating, modifying, deleting, listing parts or whole of one or more Views
   1. export graph (actual upload csv schema might be different than this. upload is actually a UI component)
      1. Nodes tab
         1. <NodeName, additional fields> 
      2. Relations Tab
         1. <leftNode, rightNode, relationType, additional relationFields>
   2. import graph (same as above)
   3. edit graph (actual upload csv schema might be different than this. upload is actually a UI component)
      1. Add Nodes tab (most likely not needed)
         1. <NodeName, additional fields, PolicyName/ID> 
      2. Delete Nodes tab
         1. <NodeName, PolicyName/ID>
      3. Rename Nodes tab
         1. <OldNodeName, NewNodeName, PolicyName/ID>
      4. Split Nodes tab
         1. <OldNodeName, ListOfNewNodeName, PolicyName/ID>
      5. Merge Nodes tab
         1. <List of OldNodeNames, NewNode, PolicyName/ID>
      6. Add Links tab (most likely not needed)
         1. <leftNodeName, rightNode, linkType, PolicyName/ID> 
      7. Delete Links tab (most likely not needed)
         1. <leftNodeName, rightNode, linkType, PolicyName/ID>
2. APIs  for creating, modifying, deleting, listing parts or whole of one or more Views, and their management
   1. can parallel the import/export/edit syntax

Compound Policy

{
  "version": 0.1,
  "predicate": {
    "conjunction": "and",
    "predicate": [
      {
        "comparator": "equalTo",
        "policy": "pid_00",
        "value": 0
      },
      {
        "conjunction": "or",
        "predicate": [
          {
            "comparator": "in",
            "policy": "pid_01",
            "value": "[Spine]"
          },
          {
            "comparator": "not in",
            "policy": "pid_02",
            "value": "[Maths, English]"
          }
        ]
      }
    ]
  }
}

Comments

1. For better performance, making Framework, Vocabulary, etc as first entities may be necessary. Handling sets via set membership could result in verbose queries and higher latency
2. Node and Relationship (properties) are listed out here
3. Policies can also have RBAC-based behavior.

...