https://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362004-06-07T18:09:04ZEcoinformatics RedmineKepler - Bug #1546: dynamic data and actor views using ontologieshttps://projects.ecoinformatics.org/ecoinfo/issues/1546?journal_id=54662004-06-07T18:09:04ZChad Berkleyberkley@nceas.ucsb.edu
<ul></ul><p>Another major issue with this is how to tag atomic actors that have no xml<br />description. One option is to have some sort of LUT, possibly in a web service,<br />for linking components to their ontological description. also need to figure<br />out how to add this information to existing moml files without upsetting the<br />moml parser.</p> Kepler - Bug #1546: dynamic data and actor views using ontologieshttps://projects.ecoinformatics.org/ecoinfo/issues/1546?journal_id=54672004-06-07T18:10:33ZChad Berkleyberkley@nceas.ucsb.edu
<ul></ul><p>need to create screenshots and a possible prototype UI diagrams for the ontology<br />browser. need to identify changes to the data and actor tabs for choosing views.</p> Kepler - Bug #1546: dynamic data and actor views using ontologieshttps://projects.ecoinformatics.org/ecoinfo/issues/1546?journal_id=54682004-06-08T20:39:25ZShawn Bowersbowers@gonzaga.edu
<ul></ul><p>We need to clarify the "query language" that will be provided to allow a user to<br />dynamically view actors and datasets via ontological information.</p>
<p>The simplest "query language" would be to allow a user to select a single<br />concept to organize the view by. For example, by giving "AnalyticalModel", a<br />tree would be created with "AnalyticalModel" as the root node, the various<br />subtypes of "AnalyticalModel" as internal nodes, and the actual actors/workflows<br />as leaves of the tree. (Note that we prune internal nodes here if no<br />actors/workflows exist along the path.)</p>
<p>As more complex "query expressions" are permitted, how results should be<br />displayed becomes less clear. For example, we could permit single concept query<br />plus role restrictions such as "AnalyticalModel and uses StatisticalModel". In<br />this case, it isn't clear how the root node should be displayed, or how further<br />subtypes of the root are best displayed. We could permit multiple concepts in<br />query expressions (implying that each concept is "anded"). Multiple concepts<br />with role restrictions. And, arbitrary concept expressions (e.g.,<br />"AnalyticalModel using StatisticalModel or StatisticalRegressionModel"). Each of<br />these would seem to complicate the display.</p>
<p>As a first cut, I think we should stick to single-concept queries.</p> Kepler - Bug #1546: dynamic data and actor views using ontologieshttps://projects.ecoinformatics.org/ecoinfo/issues/1546?journal_id=54692004-06-14T23:14:31ZShawn Bowersbowers@gonzaga.edu
<ul></ul><p>This set of slides is a very early version of the sparrow api, including the<br />dynamic view operation. Note that the version is as of yet incomplete and<br />unimplemented. (I put it under this bug because at this point it is specific<br />for 1546.)</p> Kepler - Bug #1546: dynamic data and actor views using ontologieshttps://projects.ecoinformatics.org/ecoinfo/issues/1546?journal_id=54702004-07-14T18:39:37ZShawn Bowersbowers@gonzaga.edu
<ul></ul><p>Current design document for the sparrow java api (sparrow-api)</p> Kepler - Bug #1546: dynamic data and actor views using ontologieshttps://projects.ecoinformatics.org/ecoinfo/issues/1546?journal_id=54712004-10-12T18:06:02ZChad Berkleyberkley@nceas.ucsb.edu
<ul></ul><p>This is now working via Jena. Shawn and I have changed the kepler configuration<br />to only include a long moml list of actors and we have added an id property<br />which uses lsids for unique identification. Shawns code then takes the list of<br />actors and an ontology written in OWL and rebuilds the actor library based on<br />the ontology. This should be working by the alpha3 release.</p> Kepler - Bug #1546: dynamic data and actor views using ontologieshttps://projects.ecoinformatics.org/ecoinfo/issues/1546?journal_id=54722013-03-27T21:17:29ZRedmine Admin
<ul></ul><p>Original Bugzilla ID was 1546</p>