Although the PoC will only implement a few of the possible Java SPI methods it is important to have a good detailed view of the structure and naming of this interface going forward and document it.

Temporal DB as extension of 'Core' SPI?

How does core know about extensions? Runtime plugin?

Alternative : separate service, loose coupling via events?

How about queries? XPath and/or Query Builders

Take learnings from Ericsson ENM DPS SPI as detailed here : 

Acceptance Criteria for Proposed Persistence SPI

1. Documented on ONAP Wiki
2. Discussed and agreed within CPS Team
3. Discussed and agreed with Ericsson LMI architects
4. Discussed and agreed with wider community

Currently we are considering 3 'separated' SPIs or 'groups' of methods:

1. Models (add, list)
2. Data (CRUD)
3. Queries

Wiki Page already started here : https://wiki.onap.org/pages/viewpage.action?pageId=92999716