| | 1 | = Karen's Historical Notes = |
| | 2 | |
| | 3 | The link to Karen's notes is throwing a server error, so here's what I got from Archive.org's Wayback Machine. |
| | 4 | |
| | 5 | -Joe |
| | 6 | |
| | 7 | {{{ |
| | 8 | 2002-05-16 |
| | 9 | |
| | 10 | Rick and I talked about on what level we should describe data: e.g., a |
| | 11 | single data set or a collection of data set. |
| | 12 | |
| | 13 | Different data archives organize their data differently. The |
| | 14 | searchable unit can be either a single FITS data set or a collection |
| | 15 | of them. |
| | 16 | |
| | 17 | One possible senario is to describe data at a level searchable by its |
| | 18 | archive, with the archive specific information encaptulated as a field |
| | 19 | in the XML meta-data desription to facilitate query |
| | 20 | translation. Alternatively, the XML meta-data description can |
| | 21 | incorporate the organizational structure of different data archives. |
| | 22 | |
| | 23 | 2002-05-22 |
| | 24 | |
| | 25 | Report on DM from NVO project |
| | 26 | |
| | 27 | UML object-oriented data modeling language |
| | 28 | |
| | 29 | SOAP vs XML-RPC |
| | 30 | |
| | 31 | service model: |
| | 32 | resource registration |
| | 33 | resource discovery |
| | 34 | |
| | 35 | usage scenario |
| | 36 | 100 questions for the NVO |
| | 37 | |
| | 38 | 2002-05-23 |
| | 39 | |
| | 40 | GridPP the grid for uk particle physics, useful links to recommended |
| | 41 | readings |
| | 42 | |
| | 43 | AML (astromical markup language) Damien Guillaume |
| | 44 | |
| | 45 | Level of service registration: |
| | 46 | - entire data archive |
| | 47 | - individual data set |
| | 48 | |
| | 49 | What is the pros and cons of either approach? -- plan to read Ninja |
| | 50 | paper |
| | 51 | |
| | 52 | 2002-05-24 |
| | 53 | |
| | 54 | What can a data archive do? |
| | 55 | - storage |
| | 56 | - basic data search depending on database organization |
| | 57 | - data analysis? require computing resources |
| | 58 | the first two items already exist. the last item may not. |
| | 59 | |
| | 60 | from the original proposal: |
| | 61 | http://sun.stanford.edu/~rick/propose/vso |
| | 62 | ---------------------------------------------------------------------- |
| | 63 | data archive |
| | 64 | - geographically distributed |
| | 65 | - diversely organized |
| | 66 | - provide individually tailored access services |
| | 67 | |
| | 68 | data interoperability: translation among |
| | 69 | - data descriptions |
| | 70 | - data format |
| | 71 | -> determine the semantics of XML representation |
| | 72 | |
| | 73 | access interoperability: translation among |
| | 74 | - different search engines |
| | 75 | -> reformulate XML search into source-specific search |
| | 76 | |
| | 77 | ---------------------------------------------------------------------- |
| | 78 | The NVO approach: |
| | 79 | ask some questions and see what we need to solve these problems |
| | 80 | -> identify service units, perhaps also data models. |
| | 81 | |
| | 82 | |
| | 83 | Ninja |
| | 84 | Service Discover Service: |
| | 85 | hierarchical structure |
| | 86 | |
| | 87 | Related: |
| | 88 | query distributed video database |
| | 89 | |
| | 90 | }}} |
| | 91 | |
| | 92 | {{{ |
| | 93 | Fri, 24 May 2002 about 11 AM |
| | 94 | }}} |