-
Notifications
You must be signed in to change notification settings - Fork 9
Conceptual architecture
der edited this page Nov 22, 2012
·
15 revisions
The diagram below shows the high level functional blocks needed for a registry service implementation. This is not a formal component architecture in that there is no requirement for the internal component structure to be divided into precisely these blocks. The only formal component interfaces are the external interfaces defined in the Api specification which in turn reference open standard specifications, particularly SPARQL 1.1.
- Dispatcher
- Request processor
- Auth
- Registry interface
- RDF store
- Text index
- Federation manager
- Renderer
- Access UI
- Admin UI
Component | Proof of Concept | Deployment |
Dispatcher | Required, non scalable | Scalable forwarding |
Request processor | Required | Required |
Auth | No | Required |
Registry interface | Partial, some operations may be stubbed out | Full |
RDF store | Required | Required |
Text index | Local index | Index external registers |
Federation manager | Stub | Full |
Renderer | Required | Required |
Access UI | Demonstration level | Full |
Admin UI | No | Required |