Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

2        Database backend

2.

...

Old draft from early ENM study:

Image Removed

1 A Few considerations

  • If we can ignore mutability of key attributes the schema largely holds, an XPATH can be used as unique key for each data element (fragment) 
  • We should stick to an XPATH with equality operators on key attributes only (e.g. no access by list index).
  • 255 characters may not be enough for an XPATH.
  • Conditions on multiple key attributes in the XPATH will have to be ordered to work as a single string.
  • 'MO type' will require another definition since it is path dependent in Yang. Schema node identifier is as close as it gets.
  • Given the work done in Neo4J to flatten attributes the use of a JSON format (possibly binary) in another DB technology makes sense – it will be easier to store and retrieve (no need to flatten the whole structure).

...