| At line 245 added 39 lines. |
| + !Provenance |
| + |
| + * Verification of experiment data; recipes for experiment designs; explanation for the impact of changes; ownership; performance; data quality |
| + * The "Provenance Pyramid" -- Knowledge level; Organisation Level; Data Level; Process Level |
| + ** Organisation Level at the bottom left of the pyramid, the same size as the right size, which contains the Data Level on top of the Process Level |
| + * myGrid approach |
| + ** LSIDs: to identify objects |
| + ** myGrid information model and mIR: to store lower levels of the pyramid |
| + ** sem web technologies (RDF, Ontologies): to store knowledge provenance |
| + ** Taverna workflow workbench and plugins: ensure automated recording |
| + * LSIDs |
| + ** each bioinf database on the web has: |
| + *** diff. policies for assigning and maintaining identifiers, dealing with versioning, etc. |
| + *** diff. mechanisms ... |
| + ** OMG standard |
| + *** urn:lsid:AuthorityID:NamespaceID:ObjectID:RevisionID |
| + *** urn:lsid:ncbi.nlm.nig.gov:GenBank:T48601:2 |
| + *** lsid designator -- the item being id'd is a lifes science-specific resource |
| + *** authority identifier -- internet domain owned by org that assigns an LSID to a resource |
| + *** namespace id -- name of the resource |
| + *** etc. |
| + ** how id data retrived with LSIDs? |
| + *** application -> 1. get me infor for id --> LSID client |
| + *** 2. where can i get data and metadata for ID |
| + **** returns wsdl doc giving information on where to get the data |
| + ** Authority commitments |
| + *** data returned for a given lsid must always be the same |
| + *** must always maintain an authority at e.g. pdb.org that can point to data and metadata resolvers |
| + ** lsid components |
| + *** IBM build client and server implementations in Perl, Java, C++ ... |
| + *** fairly straightforward to wrap an existing db as a source of data or metadata |
| + *** client also straightforward |
| + *** LSID launchpad ... within internet explorer (type in your lsid, returns metadata, etc) |
| + ** Use of LSIDs within myGrid |
| + *** needed an id for things such as workflows, experiments, new data results, etc. |
| + *** everything id'd with LSIDs |
| + *** build and deployed: LSID assigning server; lsid authority ([http://www.mygrid.org.uk]); metadata resolver; data resolver; (all based on IBM's open source implementation) |
| + ** |
| + |
