Data Service » History » Version 1
Anonymous, 07/24/2007 03:39 PM
1 | 1 | ||
---|---|---|---|
2 | # Data Services |
||
3 | |||
4 | This is a draft architecture for platform data services. |
||
5 | |||
6 | |||
7 | Currently, these are only notes of my first ideas. Should be followed. |
||
8 | |||
9 | |||
10 | |||
11 | |||
12 | |||
13 | ## Action flow for queries: |
||
14 | |||
15 | 1. Receive Request |
||
16 | |||
17 | 1. Analyse Query |
||
18 | |||
19 | 1. Retrieve Data |
||
20 | |||
21 | 1. Validate Data (optional) |
||
22 | |||
23 | 1. Convert Data format (optional) |
||
24 | |||
25 | 1. Return Response |
||
26 | |||
27 | |||
28 | ## Data Service Parameters: |
||
29 | |||
30 | * Kind of Data |
||
31 | |||
32 | * Adresses |
||
33 | |||
34 | * Taxon Data |
||
35 | |||
36 | * Literature (Bibliographic References) |
||
37 | |||
38 | * Images |
||
39 | |||
40 | * Documents |
||
41 | |||
42 | * List of acceptable response data formats |
||
43 | |||
44 | * e.g. LDAP, SyncML,... |
||
45 | |||
46 | * e.g. TCS,... |
||
47 | |||
48 | * e.g. BibTex, EndNote,... |
||
49 | |||
50 | * e.g. JPEG, PNG, ... |
||
51 | |||
52 | * Action or Function |
||
53 | |||
54 | * e.g. query, read, write, versioning, validate |
||
55 | |||
56 | * Input data format |
||
57 | |||
58 | * applies for modifying actions only, e.g. write, versioning, |
||
59 | |||
60 | * same as response data formats, but only one per data set |
||
61 | |||
62 | * List of data stores to apply action to |
||
63 | |||
64 | * URI-style description of data sources to be queried |
||
65 | |||
66 | * may be just a label or may be an URL |