| Div | ||
|---|---|---|
| ||
| Vocabulary Service Home |
| Note | ||
|---|---|---|
| ||
Much of the page structure and text below this point is boilerplate, copied in from the relevant New Service template. Further work is needed to complete this page. |
Entity Diagrams
Add a gliffy drawing to this page with the macro "{gliffy:name=your name entity|size=l}". Commit this and then edit the Gliffy drawing from the links on the page.
Note: if you want to import a drawing from another space, or copy a drawing, follow these steps:
...
There are only a few entities associated with the Vocabulary service, in principle. What makes things complex is that other services can behave like, but may extend, Vocabulary instances, and return objects that extend VocabularyItem instances.
Vocabulary Entity Diagrams
In the diagram below, only the Vocabulary and VocabularyItem will be stored in the Nuxeo repository. This is necessary to allow extensions to the respective schemas, as people work on the vocabulary functionality. The graph, which is represented and constrained by the other entities (types and relations), will be stored directly in tables that we manage, and are not directly accessible through the normal interfaces. Instead, graph logic will be supported that reflects the underlying model implicitly.