RoadMap » History » Version 1
Anonymous, 05/13/2015 01:29 PM
| 1 | 1 | Anonymous | Road Map |
|---|---|---|---|
| 2 | ======== |
||
| 3 | |||
| 4 | * TODO items |
||
| 5 | * modify frontend <-> catalog query protocol to support union and limited search language |
||
| 6 | * improve database schema to avoid regexes (implies catalog changes to generate appropriate SQL queries) |
||
| 7 | |||
| 8 | |||
| 9 | Current Catalog Status |
||
| 10 | ----------------------- |
||
| 11 | |||
| 12 | - We have an initial catalog implementation that supports menu (component type) and auto-complete NDN name queries against a MySQL database. |
||
| 13 | - Catalog is crashing on receipt of query Interests. Chengyu has some ideas and is working on fixes. |
||
| 14 | - Chengyu is writing unit tests (and refactoring catalog to be easier to test). |
||
| 15 | |||
| 16 | Catalog Milestone Summary |
||
| 17 | -------------------------- |
||
| 18 | |||
| 19 | The catalog implementation should be prioritize to present increasingly interesting concepts. We've started off simple: we can query a single catalog without specifying any particular host. This starting point can be evolved to demonstrate synchronization, data publication/retrieval, and security. |
||
| 20 | |||
| 21 | Security is currently a low priority milestone because we can demonstrate synchronization and data movement without it. Provenance is an important topic for scientists, but adds little on its own in terms of demo value (i.e. something is accepted or rejected). In the meantime, we can use an "anything goes" security policy. |
||
| 22 | |||
| 23 | Catalog Milestones by Priority |
||
| 24 | ------------------------------- |
||
| 25 | |||
| 26 | 1. Synchronize catalogs using ChronoSync |
||
| 27 | |||
| 28 | - Our last demo focused on querying and displaying results from a single catalog. |
||
| 29 | - Allows us to start talking about catalogs as a system with a consistent view rather than independent hosts/databases. |
||
| 30 | - Next demo could demonstrate NDN names being inserted from any catalog and the catalog system synchronizing. |
||
| 31 | |||
| 32 | 2. Add dataset publication |
||
| 33 | |||
| 34 | 3. Validate data publication and synchronization messages |
||
| 35 | |||
| 36 | 4. Serve datasets directly from disk with a new NDN repo |