WEBVTT Kind: captions Language: en 00:00:04.860 --> 00:00:13.850 align:start position:0% thank<00:00:04.980> you 00:00:13.850 --> 00:00:13.860 align:start position:0% 00:00:13.860 --> 00:00:16.250 align:start position:0% hello<00:00:14.340> everybody<00:00:14.580> I'm<00:00:15.120> Alexi<00:00:15.540> krabrov<00:00:16.080> the 00:00:16.250 --> 00:00:16.260 align:start position:0% hello everybody I'm Alexi krabrov the 00:00:16.260 --> 00:00:18.590 align:start position:0% hello everybody I'm Alexi krabrov the organizer<00:00:16.800> of<00:00:17.039> SF<00:00:17.400> text<00:00:17.640> and<00:00:18.060> here<00:00:18.240> we<00:00:18.359> are<00:00:18.480> on 00:00:18.590 --> 00:00:18.600 align:start position:0% organizer of SF text and here we are on 00:00:18.600 --> 00:00:20.990 align:start position:0% organizer of SF text and here we are on location<00:00:18.779> on<00:00:19.140> Groupon<00:00:19.560> we<00:00:20.520> have<00:00:20.640> a<00:00:20.760> Meetup 00:00:20.990 --> 00:00:21.000 align:start position:0% location on Groupon we have a Meetup 00:00:21.000 --> 00:00:23.689 align:start position:0% location on Groupon we have a Meetup about<00:00:21.180> ontologies<00:00:22.020> and<00:00:22.740> here<00:00:23.039> with<00:00:23.220> us<00:00:23.400> we 00:00:23.689 --> 00:00:23.699 align:start position:0% about ontologies and here with us we 00:00:23.699 --> 00:00:25.849 align:start position:0% about ontologies and here with us we have<00:00:23.880> Jeff<00:00:24.180> Lerman<00:00:24.600> staff<00:00:25.380> Anthology 00:00:25.849 --> 00:00:25.859 align:start position:0% have Jeff Lerman staff Anthology 00:00:25.859 --> 00:00:29.570 align:start position:0% have Jeff Lerman staff Anthology engineer<00:00:26.400> at<00:00:26.640> Kaya<00:00:27.060> gym<00:00:27.720> uh<00:00:28.439> who<00:00:28.619> works<00:00:28.980> on<00:00:29.099> uh 00:00:29.570 --> 00:00:29.580 align:start position:0% engineer at Kaya gym uh who works on uh 00:00:29.580 --> 00:00:33.250 align:start position:0% engineer at Kaya gym uh who works on uh biological<00:00:30.180> uh<00:00:30.900> knowledge<00:00:31.399> organization<00:00:32.399> and 00:00:33.250 --> 00:00:33.260 align:start position:0% biological uh knowledge organization and 00:00:33.260 --> 00:00:35.870 align:start position:0% biological uh knowledge organization and I'm<00:00:34.260> first<00:00:34.500> curious<00:00:34.920> can<00:00:35.219> you<00:00:35.399> tell<00:00:35.579> us<00:00:35.760> a 00:00:35.870 --> 00:00:35.880 align:start position:0% I'm first curious can you tell us a 00:00:35.880 --> 00:00:38.810 align:start position:0% I'm first curious can you tell us a little<00:00:35.940> bit<00:00:36.059> uh<00:00:36.899> what<00:00:37.200> is<00:00:37.440> the<00:00:37.860> knowledge 00:00:38.810 --> 00:00:38.820 align:start position:0% little bit uh what is the knowledge 00:00:38.820 --> 00:00:40.670 align:start position:0% little bit uh what is the knowledge domain<00:00:39.239> which<00:00:39.540> where<00:00:39.960> you're<00:00:40.140> building<00:00:40.379> this 00:00:40.670 --> 00:00:40.680 align:start position:0% domain which where you're building this 00:00:40.680 --> 00:00:43.970 align:start position:0% domain which where you're building this ontologies<00:00:41.219> okay<00:00:41.820> so<00:00:42.600> the<00:00:43.140> kyogen<00:00:43.620> ontology 00:00:43.970 --> 00:00:43.980 align:start position:0% ontologies okay so the kyogen ontology 00:00:43.980 --> 00:00:45.830 align:start position:0% ontologies okay so the kyogen ontology which<00:00:44.579> formerly<00:00:45.180> I<00:00:45.360> should<00:00:45.480> say<00:00:45.600> the 00:00:45.830 --> 00:00:45.840 align:start position:0% which formerly I should say the 00:00:45.840 --> 00:00:47.810 align:start position:0% which formerly I should say the Ingenuity<00:00:46.260> ontology 00:00:47.810 --> 00:00:47.820 align:start position:0% Ingenuity ontology 00:00:47.820 --> 00:00:48.529 align:start position:0% Ingenuity ontology um 00:00:48.529 --> 00:00:48.539 align:start position:0% um 00:00:48.539 --> 00:00:52.130 align:start position:0% um covers<00:00:49.320> uh<00:00:50.219> biology<00:00:51.000> broadly<00:00:51.660> is 00:00:52.130 --> 00:00:52.140 align:start position:0% covers uh biology broadly is 00:00:52.140 --> 00:00:55.430 align:start position:0% covers uh biology broadly is specifically<00:00:52.860> for<00:00:53.219> use<00:00:53.840> in<00:00:54.840> analyzing 00:00:55.430 --> 00:00:55.440 align:start position:0% specifically for use in analyzing 00:00:55.440 --> 00:00:59.529 align:start position:0% specifically for use in analyzing genomic<00:00:56.480> data<00:00:57.480> clinical<00:00:57.899> and<00:00:58.440> research<00:00:58.800> data 00:00:59.529 --> 00:00:59.539 align:start position:0% genomic data clinical and research data 00:00:59.539 --> 00:01:03.070 align:start position:0% genomic data clinical and research data as<00:01:00.539> well<00:01:00.780> as<00:01:00.960> more<00:01:01.739> broadly<00:01:02.100> molecular 00:01:03.070 --> 00:01:03.080 align:start position:0% as well as more broadly molecular 00:01:03.080 --> 00:01:07.990 align:start position:0% as well as more broadly molecular biology<00:01:04.080> related<00:01:04.559> data<00:01:05.220> so<00:01:05.780> and<00:01:06.780> the<00:01:07.680> original 00:01:07.990 --> 00:01:08.000 align:start position:0% biology related data so and the original 00:01:08.000 --> 00:01:10.370 align:start position:0% biology related data so and the original impetus<00:01:09.000> for<00:01:09.360> setting<00:01:09.780> something<00:01:09.960> like<00:01:10.200> this 00:01:10.370 --> 00:01:10.380 align:start position:0% impetus for setting something like this 00:01:10.380 --> 00:01:11.289 align:start position:0% impetus for setting something like this up 00:01:11.289 --> 00:01:11.299 align:start position:0% up 00:01:11.299 --> 00:01:14.950 align:start position:0% up was<00:01:12.299> probably<00:01:13.080> you<00:01:13.320> know<00:01:13.439> 15<00:01:13.680> years<00:01:14.040> ago 00:01:14.950 --> 00:01:14.960 align:start position:0% was probably you know 15 years ago 00:01:14.960 --> 00:01:19.670 align:start position:0% was probably you know 15 years ago as<00:01:15.960> the<00:01:16.920> just<00:01:17.580> the<00:01:17.760> volume<00:01:18.240> of<00:01:18.600> data<00:01:18.960> started 00:01:19.670 --> 00:01:19.680 align:start position:0% as the just the volume of data started 00:01:19.680 --> 00:01:21.890 align:start position:0% as the just the volume of data started to<00:01:19.860> get<00:01:20.100> really<00:01:20.700> large<00:01:21.000> people<00:01:21.299> started<00:01:21.720> to<00:01:21.780> be 00:01:21.890 --> 00:01:21.900 align:start position:0% to get really large people started to be 00:01:21.900 --> 00:01:23.950 align:start position:0% to get really large people started to be able<00:01:22.020> to<00:01:22.140> do<00:01:22.320> experiments<00:01:22.860> in<00:01:22.920> parallel 00:01:23.950 --> 00:01:23.960 align:start position:0% able to do experiments in parallel 00:01:23.960 --> 00:01:26.749 align:start position:0% able to do experiments in parallel where<00:01:24.960> they<00:01:25.259> could<00:01:25.439> acquire<00:01:26.100> a<00:01:26.280> large<00:01:26.400> amount 00:01:26.749 --> 00:01:26.759 align:start position:0% where they could acquire a large amount 00:01:26.759 --> 00:01:29.749 align:start position:0% where they could acquire a large amount of<00:01:26.939> data<00:01:27.360> in<00:01:28.140> a<00:01:28.860> short<00:01:29.040> amount<00:01:29.280> of<00:01:29.400> time<00:01:29.520> very 00:01:29.749 --> 00:01:29.759 align:start position:0% of data in a short amount of time very 00:01:29.759 --> 00:01:30.789 align:start position:0% of data in a short amount of time very easily 00:01:30.789 --> 00:01:30.799 align:start position:0% easily 00:01:30.799 --> 00:01:33.710 align:start position:0% easily and<00:01:31.799> the<00:01:32.040> challenge<00:01:32.280> then<00:01:32.759> becomes<00:01:33.119> analysis 00:01:33.710 --> 00:01:33.720 align:start position:0% and the challenge then becomes analysis 00:01:33.720 --> 00:01:35.810 align:start position:0% and the challenge then becomes analysis and<00:01:34.259> so<00:01:34.439> obviously<00:01:34.799> we're<00:01:35.100> still<00:01:35.340> in<00:01:35.700> that 00:01:35.810 --> 00:01:35.820 align:start position:0% and so obviously we're still in that 00:01:35.820 --> 00:01:37.730 align:start position:0% and so obviously we're still in that space<00:01:36.119> today<00:01:36.420> where<00:01:36.780> we<00:01:36.960> have<00:01:37.079> a<00:01:37.200> lot<00:01:37.320> of<00:01:37.439> data 00:01:37.730 --> 00:01:37.740 align:start position:0% space today where we have a lot of data 00:01:37.740 --> 00:01:41.630 align:start position:0% space today where we have a lot of data and<00:01:37.920> Analysis<00:01:38.400> is<00:01:38.900> is<00:01:39.900> the<00:01:40.079> bottleneck<00:01:40.640> the 00:01:41.630 --> 00:01:41.640 align:start position:0% and Analysis is is the bottleneck the 00:01:41.640 --> 00:01:42.950 align:start position:0% and Analysis is is the bottleneck the sources<00:01:41.939> of<00:01:42.060> the<00:01:42.180> data<00:01:42.420> are<00:01:42.479> different<00:01:42.659> and 00:01:42.950 --> 00:01:42.960 align:start position:0% sources of the data are different and 00:01:42.960 --> 00:01:44.090 align:start position:0% sources of the data are different and the<00:01:43.079> volume<00:01:43.200> and<00:01:43.439> the<00:01:43.560> data<00:01:43.740> are<00:01:43.860> different 00:01:44.090 --> 00:01:44.100 align:start position:0% the volume and the data are different 00:01:44.100 --> 00:01:46.130 align:start position:0% the volume and the data are different but 00:01:46.130 --> 00:01:46.140 align:start position:0% but 00:01:46.140 --> 00:01:48.289 align:start position:0% but that's<00:01:46.680> that's<00:01:46.680> why<00:01:47.040> we<00:01:47.159> do<00:01:47.280> what<00:01:47.400> we<00:01:47.520> do<00:01:47.640> so<00:01:48.180> is 00:01:48.289 --> 00:01:48.299 align:start position:0% that's that's why we do what we do so is 00:01:48.299 --> 00:01:50.389 align:start position:0% that's that's why we do what we do so is this<00:01:48.479> anthology<00:01:48.840> of<00:01:49.140> mainly<00:01:49.439> for<00:01:49.619> humans<00:01:50.040> so 00:01:50.389 --> 00:01:50.399 align:start position:0% this anthology of mainly for humans so 00:01:50.399 --> 00:01:52.190 align:start position:0% this anthology of mainly for humans so is<00:01:50.579> it<00:01:50.759> basically<00:01:51.060> organizational<00:01:51.899> this 00:01:52.190 --> 00:01:52.200 align:start position:0% is it basically organizational this 00:01:52.200 --> 00:01:54.010 align:start position:0% is it basically organizational this knowledge<00:01:52.439> in<00:01:52.619> a<00:01:52.740> human<00:01:52.860> readable<00:01:53.280> form 00:01:54.010 --> 00:01:54.020 align:start position:0% knowledge in a human readable form 00:01:54.020 --> 00:01:57.050 align:start position:0% knowledge in a human readable form uh<00:01:55.020> he<00:01:55.680> was<00:01:55.860> supposed<00:01:55.979> to<00:01:56.159> computers<00:01:56.579> right 00:01:57.050 --> 00:01:57.060 align:start position:0% uh he was supposed to computers right 00:01:57.060 --> 00:01:58.670 align:start position:0% uh he was supposed to computers right but<00:01:57.240> because<00:01:57.600> you<00:01:57.840> can<00:01:57.899> use<00:01:58.020> indulges<00:01:58.500> in 00:01:58.670 --> 00:01:58.680 align:start position:0% but because you can use indulges in 00:01:58.680 --> 00:02:01.130 align:start position:0% but because you can use indulges in different<00:01:58.740> ways<00:01:59.159> sure<00:01:59.820> uh<00:02:00.360> so<00:02:00.600> the<00:02:00.720> ontology 00:02:01.130 --> 00:02:01.140 align:start position:0% different ways sure uh so the ontology 00:02:01.140 --> 00:02:03.889 align:start position:0% different ways sure uh so the ontology is<00:02:01.619> rarely<00:02:02.100> used<00:02:02.399> directly<00:02:03.000> we<00:02:03.659> don't<00:02:03.720> make 00:02:03.889 --> 00:02:03.899 align:start position:0% is rarely used directly we don't make 00:02:03.899 --> 00:02:05.749 align:start position:0% is rarely used directly we don't make the<00:02:04.020> ontology<00:02:04.439> available<00:02:04.920> we<00:02:05.460> aren't 00:02:05.749 --> 00:02:05.759 align:start position:0% the ontology available we aren't 00:02:05.759 --> 00:02:06.649 align:start position:0% the ontology available we aren't currently 00:02:06.649 --> 00:02:06.659 align:start position:0% currently 00:02:06.659 --> 00:02:08.029 align:start position:0% currently um<00:02:06.719> uh<00:02:07.320> we<00:02:07.500> don't<00:02:07.619> currently<00:02:07.860> have<00:02:07.920> any 00:02:08.029 --> 00:02:08.039 align:start position:0% um uh we don't currently have any 00:02:08.039 --> 00:02:09.050 align:start position:0% um uh we don't currently have any business<00:02:08.220> models<00:02:08.580> we're<00:02:08.700> making<00:02:08.880> the 00:02:09.050 --> 00:02:09.060 align:start position:0% business models we're making the 00:02:09.060 --> 00:02:11.390 align:start position:0% business models we're making the ontology<00:02:09.479> we're<00:02:10.080> directly<00:02:10.800> available<00:02:11.039> to 00:02:11.390 --> 00:02:11.400 align:start position:0% ontology we're directly available to 00:02:11.400 --> 00:02:15.050 align:start position:0% ontology we're directly available to customers<00:02:11.879> uh<00:02:12.720> we<00:02:13.020> do<00:02:13.200> have<00:02:13.620> internally<00:02:14.459> ways 00:02:15.050 --> 00:02:15.060 align:start position:0% customers uh we do have internally ways 00:02:15.060 --> 00:02:18.290 align:start position:0% customers uh we do have internally ways to<00:02:15.360> visualize<00:02:16.319> what<00:02:16.620> we<00:02:16.739> have<00:02:16.920> and<00:02:17.340> to<00:02:17.580> we<00:02:18.120> have 00:02:18.290 --> 00:02:18.300 align:start position:0% to visualize what we have and to we have 00:02:18.300 --> 00:02:19.430 align:start position:0% to visualize what we have and to we have our<00:02:18.360> own<00:02:18.480> query<00:02:18.660> language<00:02:18.900> and<00:02:19.200> our 00:02:19.430 --> 00:02:19.440 align:start position:0% our own query language and our 00:02:19.440 --> 00:02:22.010 align:start position:0% our own query language and our manipulation<00:02:20.160> language<00:02:20.420> but<00:02:21.420> the<00:02:21.599> ontology 00:02:22.010 --> 00:02:22.020 align:start position:0% manipulation language but the ontology 00:02:22.020 --> 00:02:25.430 align:start position:0% manipulation language but the ontology is<00:02:22.860> really<00:02:23.280> serves<00:02:23.760> as<00:02:23.879> the<00:02:24.060> underpinning<00:02:24.480> uh 00:02:25.430 --> 00:02:25.440 align:start position:0% is really serves as the underpinning uh 00:02:25.440 --> 00:02:28.610 align:start position:0% is really serves as the underpinning uh to<00:02:25.920> other<00:02:26.400> application<00:02:26.879> software<00:02:27.480> that<00:02:28.440> we 00:02:28.610 --> 00:02:28.620 align:start position:0% to other application software that we 00:02:28.620 --> 00:02:32.690 align:start position:0% to other application software that we sell<00:02:28.800> and<00:02:29.099> so<00:02:29.400> uh<00:02:30.379> we<00:02:31.379> need<00:02:31.500> it<00:02:31.680> to<00:02:31.860> be<00:02:32.099> computer 00:02:32.690 --> 00:02:32.700 align:start position:0% sell and so uh we need it to be computer 00:02:32.700 --> 00:02:35.589 align:start position:0% sell and so uh we need it to be computer readable<00:02:33.239> certainly<00:02:33.720> computer<00:02:34.500> usable 00:02:35.589 --> 00:02:35.599 align:start position:0% readable certainly computer usable 00:02:35.599 --> 00:02:39.170 align:start position:0% readable certainly computer usable but<00:02:36.599> at<00:02:36.780> the<00:02:36.900> same<00:02:37.080> time<00:02:37.319> it's<00:02:37.800> serving<00:02:38.280> uh 00:02:39.170 --> 00:02:39.180 align:start position:0% but at the same time it's serving uh 00:02:39.180 --> 00:02:41.869 align:start position:0% but at the same time it's serving uh it's<00:02:39.540> not<00:02:39.660> very<00:02:39.840> far<00:02:40.020> removed<00:02:40.700> from<00:02:41.700> different 00:02:41.869 --> 00:02:41.879 align:start position:0% it's not very far removed from different 00:02:41.879 --> 00:02:43.970 align:start position:0% it's not very far removed from different applications<00:02:42.480> where<00:02:42.900> it<00:02:43.019> has<00:02:43.200> to<00:02:43.319> be 00:02:43.970 --> 00:02:43.980 align:start position:0% applications where it has to be 00:02:43.980 --> 00:02:46.850 align:start position:0% applications where it has to be human<00:02:44.459> readable<00:02:44.879> okay<00:02:45.239> okay<00:02:45.660> and<00:02:46.200> so<00:02:46.379> the<00:02:46.739> the 00:02:46.850 --> 00:02:46.860 align:start position:0% human readable okay okay and so the the 00:02:46.860 --> 00:02:49.009 align:start position:0% human readable okay okay and so the the so<00:02:47.220> the<00:02:47.459> end<00:02:47.580> user<00:02:47.940> is<00:02:48.060> still<00:02:48.239> human<00:02:48.480> it's<00:02:48.780> not 00:02:49.009 --> 00:02:49.019 align:start position:0% so the end user is still human it's not 00:02:49.019 --> 00:02:50.990 align:start position:0% so the end user is still human it's not as<00:02:49.379> you<00:02:49.620> know<00:02:49.739> like<00:02:50.160> it's<00:02:50.340> not<00:02:50.580> like<00:02:50.700> you<00:02:50.819> use 00:02:50.990 --> 00:02:51.000 align:start position:0% as you know like it's not like you use 00:02:51.000 --> 00:02:52.850 align:start position:0% as you know like it's not like you use this<00:02:51.180> Anthology<00:02:51.540> as<00:02:51.840> a<00:02:51.959> way<00:02:52.319> to<00:02:52.440> automatically 00:02:52.850 --> 00:02:52.860 align:start position:0% this Anthology as a way to automatically 00:02:52.860 --> 00:02:55.850 align:start position:0% this Anthology as a way to automatically cluster<00:02:53.480> things<00:02:54.480> necessarily<00:02:55.319> like<00:02:55.560> you<00:02:55.739> you 00:02:55.850 --> 00:02:55.860 align:start position:0% cluster things necessarily like you you 00:02:55.860 --> 00:02:57.949 align:start position:0% cluster things necessarily like you you have<00:02:56.040> a<00:02:56.220> human<00:02:56.400> asking<00:02:56.879> queries 00:02:57.949 --> 00:02:57.959 align:start position:0% have a human asking queries 00:02:57.959 --> 00:03:00.530 align:start position:0% have a human asking queries right<00:02:58.319> and<00:02:58.620> receiving<00:02:59.099> the<00:02:59.459> data<00:02:59.879> back<00:03:00.060> that's 00:03:00.530 --> 00:03:00.540 align:start position:0% right and receiving the data back that's 00:03:00.540 --> 00:03:03.410 align:start position:0% right and receiving the data back that's right<00:03:00.840> sort<00:03:01.200> of<00:03:01.319> yes<00:03:01.620> I<00:03:01.920> mean<00:03:02.420> it's 00:03:03.410 --> 00:03:03.420 align:start position:0% right sort of yes I mean it's 00:03:03.420 --> 00:03:05.809 align:start position:0% right sort of yes I mean it's interesting<00:03:03.780> the<00:03:03.900> ontology<00:03:04.260> sort<00:03:04.680> of<00:03:05.099> um 00:03:05.809 --> 00:03:05.819 align:start position:0% interesting the ontology sort of um 00:03:05.819 --> 00:03:08.089 align:start position:0% interesting the ontology sort of um kind<00:03:06.420> of<00:03:06.540> sits<00:03:06.840> at<00:03:06.959> the<00:03:07.080> core<00:03:07.200> of<00:03:07.440> the<00:03:07.560> Hub<00:03:07.739> of 00:03:08.089 --> 00:03:08.099 align:start position:0% kind of sits at the core of the Hub of 00:03:08.099 --> 00:03:10.070 align:start position:0% kind of sits at the core of the Hub of of<00:03:08.160> what<00:03:08.459> we<00:03:08.640> do<00:03:08.760> because<00:03:09.000> on<00:03:09.420> the<00:03:09.599> one<00:03:09.720> on<00:03:09.900> the 00:03:10.070 --> 00:03:10.080 align:start position:0% of what we do because on the one on the 00:03:10.080 --> 00:03:11.869 align:start position:0% of what we do because on the one on the one<00:03:10.260> side<00:03:10.440> we're<00:03:11.220> in<00:03:11.340> the<00:03:11.459> business<00:03:11.580> of 00:03:11.869 --> 00:03:11.879 align:start position:0% one side we're in the business of 00:03:11.879 --> 00:03:15.649 align:start position:0% one side we're in the business of curating<00:03:12.300> data<00:03:13.140> from<00:03:13.500> uh<00:03:14.400> disparate<00:03:15.180> sources 00:03:15.649 --> 00:03:15.659 align:start position:0% curating data from uh disparate sources 00:03:15.659 --> 00:03:17.509 align:start position:0% curating data from uh disparate sources from<00:03:16.080> databases<00:03:16.860> they<00:03:17.040> may<00:03:17.159> have<00:03:17.280> a<00:03:17.400> different 00:03:17.509 --> 00:03:17.519 align:start position:0% from databases they may have a different 00:03:17.519 --> 00:03:20.089 align:start position:0% from databases they may have a different organizational<00:03:18.060> instruction<00:03:18.300> and<00:03:18.780> we've<00:03:19.019> got 00:03:20.089 --> 00:03:20.099 align:start position:0% organizational instruction and we've got 00:03:20.099 --> 00:03:22.550 align:start position:0% organizational instruction and we've got um all<00:03:20.819> the<00:03:21.060> which<00:03:21.300> are<00:03:21.540> you<00:03:22.080> know<00:03:22.260> but<00:03:22.379> they 00:03:22.550 --> 00:03:22.560 align:start position:0% um all the which are you know but they 00:03:22.560 --> 00:03:23.750 align:start position:0% um all the which are you know but they still<00:03:22.680> have<00:03:22.800> an<00:03:22.920> organizational<00:03:23.280> structure 00:03:23.750 --> 00:03:23.760 align:start position:0% still have an organizational structure 00:03:23.760 --> 00:03:25.430 align:start position:0% still have an organizational structure to<00:03:24.120> fully 00:03:25.430 --> 00:03:25.440 align:start position:0% to fully 00:03:25.440 --> 00:03:28.910 align:start position:0% to fully um<00:03:25.560> a<00:03:25.980> sort<00:03:26.159> of<00:03:26.220> open-ended<00:03:26.959> text<00:03:27.959> from<00:03:28.620> from 00:03:28.910 --> 00:03:28.920 align:start position:0% um a sort of open-ended text from from 00:03:28.920 --> 00:03:32.330 align:start position:0% um a sort of open-ended text from from the<00:03:29.159> literature<00:03:29.580> and<00:03:30.420> so<00:03:30.800> we<00:03:31.800> do<00:03:31.920> need<00:03:32.099> the 00:03:32.330 --> 00:03:32.340 align:start position:0% the literature and so we do need the 00:03:32.340 --> 00:03:35.030 align:start position:0% the literature and so we do need the ontology<00:03:32.760> to<00:03:33.420> help<00:03:33.659> the<00:03:34.200> people<00:03:34.319> who<00:03:34.800> are 00:03:35.030 --> 00:03:35.040 align:start position:0% ontology to help the people who are 00:03:35.040 --> 00:03:37.190 align:start position:0% ontology to help the people who are importing<00:03:35.640> that<00:03:35.819> data 00:03:37.190 --> 00:03:37.200 align:start position:0% importing that data 00:03:37.200 --> 00:03:39.589 align:start position:0% importing that data um<00:03:37.319> to<00:03:37.980> to<00:03:38.280> assist<00:03:38.519> them<00:03:38.760> in<00:03:39.000> the<00:03:39.120> process<00:03:39.360> of 00:03:39.589 --> 00:03:39.599 align:start position:0% um to to assist them in the process of 00:03:39.599 --> 00:03:42.110 align:start position:0% um to to assist them in the process of classification<00:03:40.080> and<00:03:40.319> organization<00:03:40.860> right<00:03:41.640> so 00:03:42.110 --> 00:03:42.120 align:start position:0% classification and organization right so 00:03:42.120 --> 00:03:44.330 align:start position:0% classification and organization right so the<00:03:42.239> ontology<00:03:42.659> is<00:03:43.319> both<00:03:43.500> the<00:03:43.739> system<00:03:43.920> by<00:03:44.220> which 00:03:44.330 --> 00:03:44.340 align:start position:0% the ontology is both the system by which 00:03:44.340 --> 00:03:47.990 align:start position:0% the ontology is both the system by which we<00:03:44.519> organize<00:03:44.879> data<00:03:45.299> and<00:03:45.959> it<00:03:46.920> informs<00:03:47.819> the 00:03:47.990 --> 00:03:48.000 align:start position:0% we organize data and it informs the 00:03:48.000 --> 00:03:49.930 align:start position:0% we organize data and it informs the tools<00:03:48.299> that<00:03:48.480> we<00:03:48.659> use 00:03:49.930 --> 00:03:49.940 align:start position:0% tools that we use 00:03:49.940 --> 00:03:53.390 align:start position:0% tools that we use to<00:03:50.940> allow<00:03:51.480> us<00:03:51.720> to<00:03:52.019> have<00:03:52.200> that<00:03:52.440> organized<00:03:53.099> data 00:03:53.390 --> 00:03:53.400 align:start position:0% to allow us to have that organized data 00:03:53.400 --> 00:03:56.330 align:start position:0% to allow us to have that organized data and<00:03:54.360> acquire<00:03:54.840> that<00:03:55.080> data<00:03:55.379> on<00:03:55.920> the<00:03:56.040> other<00:03:56.159> side 00:03:56.330 --> 00:03:56.340 align:start position:0% and acquire that data on the other side 00:03:56.340 --> 00:03:59.149 align:start position:0% and acquire that data on the other side of<00:03:56.700> course<00:03:56.900> we<00:03:57.900> want<00:03:58.019> to<00:03:58.140> expose<00:03:58.440> that<00:03:58.739> data<00:03:59.040> in 00:03:59.149 --> 00:03:59.159 align:start position:0% of course we want to expose that data in 00:03:59.159 --> 00:04:00.789 align:start position:0% of course we want to expose that data in various<00:03:59.459> forms<00:03:59.879> and 00:04:00.789 --> 00:04:00.799 align:start position:0% various forms and 00:04:00.799 --> 00:04:03.890 align:start position:0% various forms and various<00:04:01.799> circumstances<00:04:02.720> through<00:04:03.720> our 00:04:03.890 --> 00:04:03.900 align:start position:0% various circumstances through our 00:04:03.900 --> 00:04:07.550 align:start position:0% various circumstances through our application<00:04:04.260> software<00:04:04.799> to<00:04:05.099> users<00:04:05.819> and<00:04:06.480> so<00:04:07.200> of 00:04:07.550 --> 00:04:07.560 align:start position:0% application software to users and so of 00:04:07.560 --> 00:04:10.369 align:start position:0% application software to users and so of course<00:04:07.680> you<00:04:07.860> know<00:04:08.040> we<00:04:08.700> have<00:04:08.819> human<00:04:09.120> users<00:04:09.599> at 00:04:10.369 --> 00:04:10.379 align:start position:0% course you know we have human users at 00:04:10.379 --> 00:04:12.289 align:start position:0% course you know we have human users at some<00:04:10.500> point<00:04:10.620> right 00:04:12.289 --> 00:04:12.299 align:start position:0% some point right 00:04:12.299 --> 00:04:15.589 align:start position:0% some point right but<00:04:12.840> the<00:04:13.500> ontology<00:04:13.920> is<00:04:14.640> non-accessed 00:04:15.589 --> 00:04:15.599 align:start position:0% but the ontology is non-accessed 00:04:15.599 --> 00:04:18.530 align:start position:0% but the ontology is non-accessed directly<00:04:15.900> even<00:04:16.079> by<00:04:16.320> the<00:04:16.560> applications<00:04:17.120> uh<00:04:18.120> we 00:04:18.530 --> 00:04:18.540 align:start position:0% directly even by the applications uh we 00:04:18.540 --> 00:04:20.750 align:start position:0% directly even by the applications uh we we<00:04:18.780> take<00:04:19.019> its<00:04:19.380> organizational 00:04:20.750 --> 00:04:20.760 align:start position:0% we take its organizational 00:04:20.760 --> 00:04:24.770 align:start position:0% we take its organizational structure<00:04:21.479> or<00:04:21.600> output<00:04:22.160> we<00:04:23.160> export<00:04:23.520> that<00:04:23.940> in 00:04:24.770 --> 00:04:24.780 align:start position:0% structure or output we export that in 00:04:24.780 --> 00:04:27.590 align:start position:0% structure or output we export that in some<00:04:25.139> format<00:04:25.979> that<00:04:26.220> is<00:04:26.460> then<00:04:26.699> in<00:04:27.000> turn<00:04:27.180> used<00:04:27.419> by 00:04:27.590 --> 00:04:27.600 align:start position:0% some format that is then in turn used by 00:04:27.600 --> 00:04:28.909 align:start position:0% some format that is then in turn used by the<00:04:27.780> application<00:04:28.080> so<00:04:28.320> there's<00:04:28.500> some<00:04:28.680> layers 00:04:28.909 --> 00:04:28.919 align:start position:0% the application so there's some layers 00:04:28.919 --> 00:04:30.010 align:start position:0% the application so there's some layers in<00:04:29.160> between 00:04:30.010 --> 00:04:30.020 align:start position:0% in between 00:04:30.020 --> 00:04:32.689 align:start position:0% in between a<00:04:31.020> few<00:04:31.139> layers<00:04:31.440> in<00:04:31.620> between<00:04:31.740> the<00:04:32.100> end<00:04:32.280> users 00:04:32.689 --> 00:04:32.699 align:start position:0% a few layers in between the end users 00:04:32.699 --> 00:04:34.969 align:start position:0% a few layers in between the end users and<00:04:33.060> the<00:04:33.180> ontology<00:04:33.600> itself<00:04:34.139> but<00:04:34.560> it's<00:04:34.740> still 00:04:34.969 --> 00:04:34.979 align:start position:0% and the ontology itself but it's still 00:04:34.979 --> 00:04:37.370 align:start position:0% and the ontology itself but it's still you<00:04:35.639> know<00:04:35.699> very<00:04:35.940> strongly<00:04:36.300> determined<00:04:36.960> what 00:04:37.370 --> 00:04:37.380 align:start position:0% you know very strongly determined what 00:04:37.380 --> 00:04:39.890 align:start position:0% you know very strongly determined what our<00:04:37.500> applications<00:04:37.860> can<00:04:38.160> do<00:04:38.340> got<00:04:38.759> it<00:04:39.000> so<00:04:39.360> there 00:04:39.890 --> 00:04:39.900 align:start position:0% our applications can do got it so there 00:04:39.900 --> 00:04:43.370 align:start position:0% our applications can do got it so there is<00:04:40.020> a<00:04:40.320> lot<00:04:40.440> of<00:04:40.680> data<00:04:41.400> in<00:04:41.820> in<00:04:42.120> you<00:04:42.840> know<00:04:42.960> the 00:04:43.370 --> 00:04:43.380 align:start position:0% is a lot of data in in you know the 00:04:43.380 --> 00:04:45.469 align:start position:0% is a lot of data in in you know the people<00:04:43.620> called<00:04:43.860> bioinformatics<00:04:44.759> or<00:04:44.940> genomics 00:04:45.469 --> 00:04:45.479 align:start position:0% people called bioinformatics or genomics 00:04:45.479 --> 00:04:48.170 align:start position:0% people called bioinformatics or genomics and<00:04:45.780> we<00:04:46.259> have<00:04:46.440> actually<00:04:46.620> several<00:04:46.979> startups<00:04:47.639> uh 00:04:48.170 --> 00:04:48.180 align:start position:0% and we have actually several startups uh 00:04:48.180 --> 00:04:50.930 align:start position:0% and we have actually several startups uh even<00:04:48.479> as<00:04:48.720> a<00:04:48.900> scholar<00:04:49.139> which<00:04:49.259> I<00:04:49.500> also<00:04:49.680> run<00:04:49.940> and 00:04:50.930 --> 00:04:50.940 align:start position:0% even as a scholar which I also run and 00:04:50.940 --> 00:04:54.050 align:start position:0% even as a scholar which I also run and uh<00:04:51.540> I<00:04:52.080> was<00:04:52.259> amazed<00:04:52.860> by<00:04:53.280> looking<00:04:53.460> at<00:04:53.699> you<00:04:54.000> know 00:04:54.050 --> 00:04:54.060 align:start position:0% uh I was amazed by looking at you know 00:04:54.060 --> 00:04:57.710 align:start position:0% uh I was amazed by looking at you know genomics<00:04:54.620> databases<00:04:55.639> how<00:04:56.639> much<00:04:56.759> text<00:04:57.479> is 00:04:57.710 --> 00:04:57.720 align:start position:0% genomics databases how much text is 00:04:57.720 --> 00:04:59.510 align:start position:0% genomics databases how much text is there<00:04:57.900> how<00:04:58.259> much<00:04:58.380> artifacts<00:04:59.100> so<00:04:59.220> you<00:04:59.400> know 00:04:59.510 --> 00:04:59.520 align:start position:0% there how much artifacts so you know 00:04:59.520 --> 00:05:02.150 align:start position:0% there how much artifacts so you know genomic<00:04:59.940> sequences<00:05:00.300> themselves<00:05:01.160> various 00:05:02.150 --> 00:05:02.160 align:start position:0% genomic sequences themselves various 00:05:02.160 --> 00:05:04.790 align:start position:0% genomic sequences themselves various papers<00:05:02.580> talking<00:05:03.060> about<00:05:03.300> them<00:05:03.660> various<00:05:04.440> calls 00:05:04.790 --> 00:05:04.800 align:start position:0% papers talking about them various calls 00:05:04.800 --> 00:05:07.070 align:start position:0% papers talking about them various calls right<00:05:04.979> like<00:05:05.220> this<00:05:05.400> paper<00:05:05.639> so<00:05:06.060> and<00:05:06.419> I<00:05:06.660> used<00:05:06.960> to 00:05:07.070 --> 00:05:07.080 align:start position:0% right like this paper so and I used to 00:05:07.080 --> 00:05:08.749 align:start position:0% right like this paper so and I used to work<00:05:07.139> at<00:05:07.320> present<00:05:07.620> at<00:05:07.740> the<00:05:07.919> bank<00:05:07.979> a<00:05:08.340> long<00:05:08.580> time 00:05:08.749 --> 00:05:08.759 align:start position:0% work at present at the bank a long time 00:05:08.759 --> 00:05:10.790 align:start position:0% work at present at the bank a long time ago<00:05:08.940> and<00:05:09.180> you<00:05:09.360> know<00:05:09.479> they<00:05:09.660> had<00:05:09.840> their<00:05:09.960> own<00:05:10.199> you 00:05:10.790 --> 00:05:10.800 align:start position:0% ago and you know they had their own you 00:05:10.800 --> 00:05:12.590 align:start position:0% ago and you know they had their own you know<00:05:10.919> and<00:05:11.340> I<00:05:11.699> looked<00:05:11.880> at<00:05:11.940> Medline<00:05:12.300> and<00:05:12.479> so 00:05:12.590 --> 00:05:12.600 align:start position:0% know and I looked at Medline and so 00:05:12.600 --> 00:05:14.629 align:start position:0% know and I looked at Medline and so forth<00:05:12.780> and<00:05:12.960> I<00:05:13.139> was<00:05:13.259> really<00:05:13.380> Amazed<00:05:13.800> by<00:05:14.040> the<00:05:14.280> by 00:05:14.629 --> 00:05:14.639 align:start position:0% forth and I was really Amazed by the by 00:05:14.639 --> 00:05:16.909 align:start position:0% forth and I was really Amazed by the by the<00:05:14.820> sheer<00:05:15.120> volume<00:05:15.300> of<00:05:15.960> all<00:05:16.080> this<00:05:16.259> data<00:05:16.680> and 00:05:16.909 --> 00:05:16.919 align:start position:0% the sheer volume of all this data and 00:05:16.919 --> 00:05:18.650 align:start position:0% the sheer volume of all this data and and<00:05:17.100> and<00:05:17.220> so<00:05:17.580> it<00:05:17.759> seems<00:05:17.940> that<00:05:18.060> everybody<00:05:18.300> has 00:05:18.650 --> 00:05:18.660 align:start position:0% and and so it seems that everybody has 00:05:18.660 --> 00:05:20.150 align:start position:0% and and so it seems that everybody has their<00:05:18.840> own<00:05:19.020> databases<00:05:19.500> their<00:05:19.740> European 00:05:20.150 --> 00:05:20.160 align:start position:0% their own databases their European 00:05:20.160 --> 00:05:22.610 align:start position:0% their own databases their European database<00:05:20.460> that<00:05:20.759> OS<00:05:21.300> databases<00:05:21.780> there<00:05:22.259> are<00:05:22.440> all 00:05:22.610 --> 00:05:22.620 align:start position:0% database that OS databases there are all 00:05:22.620 --> 00:05:25.310 align:start position:0% database that OS databases there are all kinds<00:05:22.860> of<00:05:22.979> uh<00:05:23.699> of<00:05:24.000> things<00:05:24.180> so 00:05:25.310 --> 00:05:25.320 align:start position:0% kinds of uh of things so 00:05:25.320 --> 00:05:27.409 align:start position:0% kinds of uh of things so have<00:05:25.800> this<00:05:26.039> uh<00:05:26.280> that<00:05:26.940> you're<00:05:27.120> talking<00:05:27.240> about 00:05:27.409 --> 00:05:27.419 align:start position:0% have this uh that you're talking about 00:05:27.419 --> 00:05:30.170 align:start position:0% have this uh that you're talking about are<00:05:27.780> they<00:05:28.340> unifying<00:05:29.340> all<00:05:29.400> these<00:05:29.699> data<00:05:29.940> sources 00:05:30.170 --> 00:05:30.180 align:start position:0% are they unifying all these data sources 00:05:30.180 --> 00:05:31.810 align:start position:0% are they unifying all these data sources for<00:05:30.419> instance<00:05:30.539> you<00:05:30.780> know<00:05:30.960> sequences 00:05:31.810 --> 00:05:31.820 align:start position:0% for instance you know sequences 00:05:31.820 --> 00:05:34.610 align:start position:0% for instance you know sequences themselves<00:05:32.820> and<00:05:33.479> and<00:05:33.840> papers<00:05:34.440> about 00:05:34.610 --> 00:05:34.620 align:start position:0% themselves and and papers about 00:05:34.620 --> 00:05:35.870 align:start position:0% themselves and and papers about sequences 00:05:35.870 --> 00:05:35.880 align:start position:0% sequences 00:05:35.880 --> 00:05:38.090 align:start position:0% sequences can<00:05:36.360> he<00:05:36.600> plays<00:05:36.840> both<00:05:36.960> things<00:05:37.199> and<00:05:37.440> you<00:05:37.740> know<00:05:37.800> on 00:05:38.090 --> 00:05:38.100 align:start position:0% can he plays both things and you know on 00:05:38.100 --> 00:05:41.510 align:start position:0% can he plays both things and you know on the<00:05:38.280> same<00:05:38.340> Anthology<00:05:38.759> sure<00:05:39.600> so<00:05:40.259> uh<00:05:41.039> you<00:05:41.400> know 00:05:41.510 --> 00:05:41.520 align:start position:0% the same Anthology sure so uh you know 00:05:41.520 --> 00:05:42.890 align:start position:0% the same Anthology sure so uh you know we<00:05:41.639> we<00:05:41.820> certainly 00:05:42.890 --> 00:05:42.900 align:start position:0% we we certainly 00:05:42.900 --> 00:05:44.629 align:start position:0% we we certainly um<00:05:42.960> Define<00:05:43.320> our<00:05:43.680> limits<00:05:44.039> and<00:05:44.160> and<00:05:44.280> so<00:05:44.520> that's 00:05:44.629 --> 00:05:44.639 align:start position:0% um Define our limits and and so that's 00:05:44.639 --> 00:05:46.490 align:start position:0% um Define our limits and and so that's one<00:05:44.880> thing<00:05:45.060> actually<00:05:45.180> that<00:05:45.539> we<00:05:45.720> don't<00:05:45.840> do<00:05:46.080> in 00:05:46.490 --> 00:05:46.500 align:start position:0% one thing actually that we don't do in 00:05:46.500 --> 00:05:49.070 align:start position:0% one thing actually that we don't do in the<00:05:46.740> ontology<00:05:47.100> itself<00:05:47.580> is<00:05:47.880> to<00:05:48.120> deal<00:05:48.300> uh<00:05:48.900> with 00:05:49.070 --> 00:05:49.080 align:start position:0% the ontology itself is to deal uh with 00:05:49.080 --> 00:05:50.390 align:start position:0% the ontology itself is to deal uh with sequence<00:05:49.440> data 00:05:50.390 --> 00:05:50.400 align:start position:0% sequence data 00:05:50.400 --> 00:05:52.550 align:start position:0% sequence data um<00:05:50.460> we<00:05:50.820> do<00:05:50.940> deal<00:05:51.180> with<00:05:51.419> variant<00:05:51.900> data<00:05:52.259> quite<00:05:52.440> a 00:05:52.550 --> 00:05:52.560 align:start position:0% um we do deal with variant data quite a 00:05:52.560 --> 00:05:54.230 align:start position:0% um we do deal with variant data quite a lot<00:05:52.680> and<00:05:52.979> so<00:05:53.160> that's<00:05:53.340> becoming<00:05:53.759> a<00:05:53.940> more<00:05:54.180> and 00:05:54.230 --> 00:05:54.240 align:start position:0% lot and so that's becoming a more and 00:05:54.240 --> 00:05:56.210 align:start position:0% lot and so that's becoming a more and more<00:05:54.479> important<00:05:54.900> as<00:05:55.139> it's<00:05:55.320> become<00:05:55.620> cheaper 00:05:56.210 --> 00:05:56.220 align:start position:0% more important as it's become cheaper 00:05:56.220 --> 00:05:59.270 align:start position:0% more important as it's become cheaper and<00:05:56.340> cheaper<00:05:56.580> to<00:05:56.699> sequence<00:05:57.180> uh<00:05:58.080> you<00:05:58.500> know 00:05:59.270 --> 00:05:59.280 align:start position:0% and cheaper to sequence uh you know 00:05:59.280 --> 00:06:02.270 align:start position:0% and cheaper to sequence uh you know DNA<00:06:00.060> and<00:06:00.360> and<00:06:00.539> even<00:06:00.840> sequence<00:06:01.199> whole<00:06:01.380> genomes 00:06:02.270 --> 00:06:02.280 align:start position:0% DNA and and even sequence whole genomes 00:06:02.280 --> 00:06:05.749 align:start position:0% DNA and and even sequence whole genomes um<00:06:02.479> which<00:06:03.479> is<00:06:03.720> sort<00:06:03.900> of<00:06:04.020> just<00:06:04.800> ridiculous<00:06:05.460> that 00:06:05.749 --> 00:06:05.759 align:start position:0% um which is sort of just ridiculous that 00:06:05.759 --> 00:06:07.010 align:start position:0% um which is sort of just ridiculous that we're<00:06:05.880> at<00:06:06.120> the<00:06:06.240> point<00:06:06.360> where<00:06:06.479> we<00:06:06.660> can<00:06:06.780> do<00:06:06.900> that 00:06:07.010 --> 00:06:07.020 align:start position:0% we're at the point where we can do that 00:06:07.020 --> 00:06:10.310 align:start position:0% we're at the point where we can do that yes<00:06:07.440> uh<00:06:07.919> but<00:06:08.699> uh<00:06:09.419> you<00:06:09.600> know<00:06:09.660> even<00:06:09.780> a<00:06:10.020> single 00:06:10.310 --> 00:06:10.320 align:start position:0% yes uh but uh you know even a single 00:06:10.320 --> 00:06:13.010 align:start position:0% yes uh but uh you know even a single genome<00:06:10.680> results<00:06:11.100> in<00:06:11.460> an<00:06:11.699> enormous<00:06:12.360> amount<00:06:12.840> of 00:06:13.010 --> 00:06:13.020 align:start position:0% genome results in an enormous amount of 00:06:13.020 --> 00:06:16.550 align:start position:0% genome results in an enormous amount of data<00:06:13.800> even<00:06:13.979> after<00:06:14.220> it's<00:06:14.580> Consolidated<00:06:15.560> and 00:06:16.550 --> 00:06:16.560 align:start position:0% data even after it's Consolidated and 00:06:16.560 --> 00:06:20.390 align:start position:0% data even after it's Consolidated and the<00:06:16.680> raw<00:06:16.919> data<00:06:17.280> you<00:06:17.880> know<00:06:17.940> much<00:06:18.120> more<00:06:18.360> so<00:06:18.620> uh<00:06:19.620> so 00:06:20.390 --> 00:06:20.400 align:start position:0% the raw data you know much more so uh so 00:06:20.400 --> 00:06:22.850 align:start position:0% the raw data you know much more so uh so uh<00:06:21.120> what's<00:06:21.419> of<00:06:21.600> interest<00:06:21.780> is<00:06:22.139> to<00:06:22.319> be<00:06:22.440> able<00:06:22.560> to 00:06:22.850 --> 00:06:22.860 align:start position:0% uh what's of interest is to be able to 00:06:22.860 --> 00:06:26.930 align:start position:0% uh what's of interest is to be able to look<00:06:23.100> at<00:06:23.900> the<00:06:24.900> differences<00:06:25.319> the<00:06:26.100> the<00:06:26.400> variance 00:06:26.930 --> 00:06:26.940 align:start position:0% look at the differences the the variance 00:06:26.940 --> 00:06:30.110 align:start position:0% look at the differences the the variance uh<00:06:27.479> the<00:06:27.660> genetic<00:06:28.259> variants<00:06:28.699> and<00:06:29.699> to<00:06:29.819> be<00:06:29.940> able 00:06:30.110 --> 00:06:30.120 align:start position:0% uh the genetic variants and to be able 00:06:30.120 --> 00:06:33.710 align:start position:0% uh the genetic variants and to be able to<00:06:30.539> learn<00:06:31.139> something<00:06:31.460> from<00:06:32.460> uh<00:06:33.300> the<00:06:33.539> presence 00:06:33.710 --> 00:06:33.720 align:start position:0% to learn something from uh the presence 00:06:33.720 --> 00:06:36.409 align:start position:0% to learn something from uh the presence or<00:06:33.960> absence<00:06:34.259> of<00:06:34.500> different<00:06:34.800> variants<00:06:35.220> so<00:06:35.759> so 00:06:36.409 --> 00:06:36.419 align:start position:0% or absence of different variants so so 00:06:36.419 --> 00:06:38.870 align:start position:0% or absence of different variants so so we<00:06:36.960> don't<00:06:37.199> process<00:06:37.740> whole<00:06:38.039> sequence<00:06:38.460> data<00:06:38.759> we 00:06:38.870 --> 00:06:38.880 align:start position:0% we don't process whole sequence data we 00:06:38.880 --> 00:06:40.850 align:start position:0% we don't process whole sequence data we don't<00:06:39.060> and<00:06:39.300> we<00:06:39.720> certainly<00:06:40.080> don't<00:06:40.319> store<00:06:40.620> whole 00:06:40.850 --> 00:06:40.860 align:start position:0% don't and we certainly don't store whole 00:06:40.860 --> 00:06:43.850 align:start position:0% don't and we certainly don't store whole papers<00:06:41.479> but<00:06:42.479> we<00:06:42.720> extract 00:06:43.850 --> 00:06:43.860 align:start position:0% papers but we extract 00:06:43.860 --> 00:06:45.890 align:start position:0% papers but we extract um<00:06:43.919> I<00:06:44.160> would<00:06:44.220> say<00:06:44.400> useful<00:06:45.300> information<00:06:45.479> what 00:06:45.890 --> 00:06:45.900 align:start position:0% um I would say useful information what 00:06:45.900 --> 00:06:48.050 align:start position:0% um I would say useful information what we<00:06:46.080> consider<00:06:46.319> to<00:06:46.500> be<00:06:46.560> useful<00:06:46.800> information 00:06:48.050 --> 00:06:48.060 align:start position:0% we consider to be useful information 00:06:48.060 --> 00:06:50.029 align:start position:0% we consider to be useful information um<00:06:48.199> statements 00:06:50.029 --> 00:06:50.039 align:start position:0% um statements 00:06:50.039 --> 00:06:52.790 align:start position:0% um statements um more<00:06:50.819> than<00:06:51.180> so<00:06:51.840> qualitative<00:06:52.380> more<00:06:52.680> than 00:06:52.790 --> 00:06:52.800 align:start position:0% um more than so qualitative more than 00:06:52.800 --> 00:06:55.790 align:start position:0% um more than so qualitative more than quantitative<00:06:53.479> data<00:06:54.680> statements<00:06:55.680> and 00:06:55.790 --> 00:06:55.800 align:start position:0% quantitative data statements and 00:06:55.800 --> 00:06:58.010 align:start position:0% quantitative data statements and relationships<00:06:56.460> from 00:06:58.010 --> 00:06:58.020 align:start position:0% relationships from 00:06:58.020 --> 00:07:00.409 align:start position:0% relationships from all<00:06:58.500> these<00:06:58.680> sources<00:06:59.039> so<00:06:59.400> from<00:06:59.759> from<00:07:00.180> the 00:07:00.409 --> 00:07:00.419 align:start position:0% all these sources so from from the 00:07:00.419 --> 00:07:02.270 align:start position:0% all these sources so from from the literature<00:07:00.780> certainly<00:07:01.740> um<00:07:01.740> and<00:07:01.979> there<00:07:02.160> are 00:07:02.270 --> 00:07:02.280 align:start position:0% literature certainly um and there are 00:07:02.280 --> 00:07:03.469 align:start position:0% literature certainly um and there are parts<00:07:02.400> of<00:07:02.520> the<00:07:02.580> literature<00:07:02.880> that<00:07:03.000> we<00:07:03.120> focus<00:07:03.300> on 00:07:03.469 --> 00:07:03.479 align:start position:0% parts of the literature that we focus on 00:07:03.479 --> 00:07:05.330 align:start position:0% parts of the literature that we focus on very<00:07:03.780> intently 00:07:05.330 --> 00:07:05.340 align:start position:0% very intently 00:07:05.340 --> 00:07:06.050 align:start position:0% very intently um 00:07:06.050 --> 00:07:06.060 align:start position:0% um 00:07:06.060 --> 00:07:08.990 align:start position:0% um and<00:07:06.660> then<00:07:06.840> uh<00:07:07.680> there<00:07:08.160> may<00:07:08.340> be<00:07:08.400> there<00:07:08.580> are<00:07:08.819> for 00:07:08.990 --> 00:07:09.000 align:start position:0% and then uh there may be there are for 00:07:09.000 --> 00:07:11.809 align:start position:0% and then uh there may be there are for example<00:07:09.180> databases<00:07:09.840> that<00:07:10.080> focus<00:07:10.380> on<00:07:10.819> genetic 00:07:11.809 --> 00:07:11.819 align:start position:0% example databases that focus on genetic 00:07:11.819 --> 00:07:14.150 align:start position:0% example databases that focus on genetic variants<00:07:12.180> and<00:07:12.960> we'll<00:07:13.139> import<00:07:13.440> those<00:07:13.740> and<00:07:13.979> what 00:07:14.150 --> 00:07:14.160 align:start position:0% variants and we'll import those and what 00:07:14.160 --> 00:07:18.770 align:start position:0% variants and we'll import those and what and<00:07:14.639> so<00:07:14.880> we<00:07:15.539> do<00:07:15.720> have<00:07:16.500> a<00:07:16.680> task<00:07:16.800> of<00:07:17.100> unifying 00:07:18.770 --> 00:07:18.780 align:start position:0% and so we do have a task of unifying 00:07:18.780 --> 00:07:20.870 align:start position:0% and so we do have a task of unifying um 00:07:20.870 --> 00:07:20.880 align:start position:0% 00:07:20.880 --> 00:07:23.029 align:start position:0% a<00:07:21.360> variety<00:07:21.599> of<00:07:21.840> different<00:07:22.080> data<00:07:22.560> sources<00:07:22.800> so 00:07:23.029 --> 00:07:23.039 align:start position:0% a variety of different data sources so 00:07:23.039 --> 00:07:26.029 align:start position:0% a variety of different data sources so as<00:07:23.340> you<00:07:23.460> mentioned<00:07:23.759> there<00:07:24.240> are<00:07:24.560> American<00:07:25.560> and 00:07:26.029 --> 00:07:26.039 align:start position:0% as you mentioned there are American and 00:07:26.039 --> 00:07:30.529 align:start position:0% as you mentioned there are American and European<00:07:27.020> databases<00:07:28.020> for<00:07:28.620> uh<00:07:29.460> for<00:07:29.819> genes<00:07:30.180> and 00:07:30.529 --> 00:07:30.539 align:start position:0% European databases for uh for genes and 00:07:30.539 --> 00:07:32.930 align:start position:0% European databases for uh for genes and and<00:07:30.720> other<00:07:31.259> genetic<00:07:31.680> information 00:07:32.930 --> 00:07:32.940 align:start position:0% and other genetic information 00:07:32.940 --> 00:07:34.909 align:start position:0% and other genetic information um<00:07:33.000> I<00:07:33.419> don't<00:07:33.539> know<00:07:33.720> about<00:07:34.080> a<00:07:34.319> competitor<00:07:34.740> to 00:07:34.909 --> 00:07:34.919 align:start position:0% um I don't know about a competitor to 00:07:34.919 --> 00:07:37.309 align:start position:0% um I don't know about a competitor to the<00:07:35.160> pdb<00:07:35.639> to<00:07:36.060> the<00:07:36.180> protein<00:07:36.479> Data<00:07:36.780> Bank<00:07:36.900> I<00:07:37.139> think 00:07:37.309 --> 00:07:37.319 align:start position:0% the pdb to the protein Data Bank I think 00:07:37.319 --> 00:07:39.710 align:start position:0% the pdb to the protein Data Bank I think that's<00:07:37.560> a<00:07:37.740> fortunately<00:07:38.160> centralized<00:07:39.120> I<00:07:39.539> mean 00:07:39.710 --> 00:07:39.720 align:start position:0% that's a fortunately centralized I mean 00:07:39.720 --> 00:07:42.110 align:start position:0% that's a fortunately centralized I mean based<00:07:40.560> on<00:07:40.620> my<00:07:40.740> knowledge<00:07:41.039> from<00:07:41.280> 10<00:07:41.580> years<00:07:41.819> ago 00:07:42.110 --> 00:07:42.120 align:start position:0% based on my knowledge from 10 years ago 00:07:42.120 --> 00:07:43.909 align:start position:0% based on my knowledge from 10 years ago right<00:07:42.660> and<00:07:42.840> it's<00:07:43.020> been<00:07:43.139> a<00:07:43.259> while<00:07:43.319> so<00:07:43.500> I<00:07:43.680> also 00:07:43.909 --> 00:07:43.919 align:start position:0% right and it's been a while so I also 00:07:43.919 --> 00:07:45.230 align:start position:0% right and it's been a while so I also used<00:07:44.039> to<00:07:44.220> be<00:07:44.280> a<00:07:44.400> protein<00:07:44.759> structural 00:07:45.230 --> 00:07:45.240 align:start position:0% used to be a protein structural 00:07:45.240 --> 00:07:47.150 align:start position:0% used to be a protein structural biologist<00:07:45.599> and 00:07:47.150 --> 00:07:47.160 align:start position:0% biologist and 00:07:47.160 --> 00:07:48.710 align:start position:0% biologist and um<00:07:47.220> but<00:07:47.639> I<00:07:47.759> also<00:07:48.000> haven't<00:07:48.060> thought<00:07:48.360> too<00:07:48.599> much 00:07:48.710 --> 00:07:48.720 align:start position:0% um but I also haven't thought too much 00:07:48.720 --> 00:07:51.830 align:start position:0% um but I also haven't thought too much about<00:07:48.960> the<00:07:49.199> pdb<00:07:49.620> for<00:07:50.280> a<00:07:50.400> while<00:07:50.520> now<00:07:50.759> but<00:07:51.720> anyway 00:07:51.830 --> 00:07:51.840 align:start position:0% about the pdb for a while now but anyway 00:07:51.840 --> 00:07:54.170 align:start position:0% about the pdb for a while now but anyway there<00:07:52.680> are<00:07:52.860> obviously<00:07:53.280> different<00:07:53.520> databases 00:07:54.170 --> 00:07:54.180 align:start position:0% there are obviously different databases 00:07:54.180 --> 00:07:55.390 align:start position:0% there are obviously different databases covering<00:07:54.479> some<00:07:54.660> of<00:07:54.780> the<00:07:54.840> same<00:07:54.960> information 00:07:55.390 --> 00:07:55.400 align:start position:0% covering some of the same information 00:07:55.400 --> 00:07:57.469 align:start position:0% covering some of the same information they<00:07:56.400> complement<00:07:56.759> each<00:07:56.940> other<00:07:57.120> to<00:07:57.300> some 00:07:57.469 --> 00:07:57.479 align:start position:0% they complement each other to some 00:07:57.479 --> 00:08:00.650 align:start position:0% they complement each other to some extent<00:07:57.840> and<00:07:58.620> we<00:07:59.099> do<00:07:59.580> our<00:07:59.759> best<00:07:59.880> to<00:08:00.180> unify 00:08:00.650 --> 00:08:00.660 align:start position:0% extent and we do our best to unify 00:08:00.660 --> 00:08:04.070 align:start position:0% extent and we do our best to unify information<00:08:01.020> from<00:08:01.500> those<00:08:01.680> databases<00:08:02.220> we<00:08:03.000> want 00:08:04.070 --> 00:08:04.080 align:start position:0% information from those databases we want 00:08:04.080 --> 00:08:06.529 align:start position:0% information from those databases we want um<00:08:04.139> you<00:08:04.440> know<00:08:04.560> we<00:08:04.680> can't<00:08:04.800> stand<00:08:05.099> alone<00:08:05.539> uh 00:08:06.529 --> 00:08:06.539 align:start position:0% um you know we can't stand alone uh 00:08:06.539 --> 00:08:08.570 align:start position:0% um you know we can't stand alone uh people<00:08:06.780> coming<00:08:07.139> to<00:08:07.440> us<00:08:07.560> with<00:08:07.860> their<00:08:08.039> data<00:08:08.400> are 00:08:08.570 --> 00:08:08.580 align:start position:0% people coming to us with their data are 00:08:08.580 --> 00:08:10.189 align:start position:0% people coming to us with their data are their<00:08:09.240> data<00:08:09.539> are<00:08:09.660> speaking<00:08:09.960> a<00:08:10.080> certain 00:08:10.189 --> 00:08:10.199 align:start position:0% their data are speaking a certain 00:08:10.199 --> 00:08:11.629 align:start position:0% their data are speaking a certain language<00:08:10.380> right<00:08:10.740> they're<00:08:10.919> using<00:08:11.340> certain 00:08:11.629 --> 00:08:11.639 align:start position:0% language right they're using certain 00:08:11.639 --> 00:08:14.629 align:start position:0% language right they're using certain identifiers<00:08:12.360> to<00:08:13.020> refer<00:08:13.380> to<00:08:13.620> Concepts<00:08:14.099> we<00:08:14.520> need 00:08:14.629 --> 00:08:14.639 align:start position:0% identifiers to refer to Concepts we need 00:08:14.639 --> 00:08:16.930 align:start position:0% identifiers to refer to Concepts we need to<00:08:14.759> be<00:08:14.880> able<00:08:15.000> to<00:08:15.120> map<00:08:15.300> those<00:08:15.660> identifiers 00:08:16.930 --> 00:08:16.940 align:start position:0% to be able to map those identifiers 00:08:16.940 --> 00:08:20.570 align:start position:0% to be able to map those identifiers to<00:08:17.940> those<00:08:18.479> same<00:08:18.660> Concepts<00:08:19.199> so<00:08:20.039> we<00:08:20.220> need<00:08:20.340> to<00:08:20.460> be 00:08:20.570 --> 00:08:20.580 align:start position:0% to those same Concepts so we need to be 00:08:20.580 --> 00:08:22.790 align:start position:0% to those same Concepts so we need to be able<00:08:20.639> to<00:08:20.819> take<00:08:21.300> the<00:08:21.419> refseq<00:08:21.960> for<00:08:22.259> example<00:08:22.440> for 00:08:22.790 --> 00:08:22.800 align:start position:0% able to take the refseq for example for 00:08:22.800 --> 00:08:24.830 align:start position:0% able to take the refseq for example for one<00:08:23.099> of<00:08:23.220> the<00:08:23.340> uh<00:08:23.879> one<00:08:24.539> of<00:08:24.660> the<00:08:24.720> American 00:08:24.830 --> 00:08:24.840 align:start position:0% one of the uh one of the American 00:08:24.840 --> 00:08:27.189 align:start position:0% one of the uh one of the American database<00:08:25.639> identifiers 00:08:27.189 --> 00:08:27.199 align:start position:0% database identifiers 00:08:27.199 --> 00:08:29.809 align:start position:0% database identifiers those<00:08:28.199> those<00:08:28.440> IDs<00:08:28.979> and<00:08:29.160> we<00:08:29.280> need<00:08:29.699> to 00:08:29.809 --> 00:08:29.819 align:start position:0% those those IDs and we need to 00:08:29.819 --> 00:08:31.490 align:start position:0% those those IDs and we need to understand<00:08:29.940> those<00:08:30.419> but<00:08:30.720> ditto<00:08:31.199> for<00:08:31.319> the 00:08:31.490 --> 00:08:31.500 align:start position:0% understand those but ditto for the 00:08:31.500 --> 00:08:33.230 align:start position:0% understand those but ditto for the European<00:08:31.860> ones 00:08:33.230 --> 00:08:33.240 align:start position:0% European ones 00:08:33.240 --> 00:08:35.690 align:start position:0% European ones um<00:08:33.360> and<00:08:33.719> that's<00:08:33.839> just<00:08:34.080> for<00:08:34.380> for<00:08:34.919> genes<00:08:35.399> and<00:08:35.580> for 00:08:35.690 --> 00:08:35.700 align:start position:0% um and that's just for for genes and for 00:08:35.700 --> 00:08:37.310 align:start position:0% um and that's just for for genes and for genetic<00:08:36.180> sequences<00:08:36.599> there's<00:08:36.839> a<00:08:37.020> variety<00:08:37.200> of 00:08:37.310 --> 00:08:37.320 align:start position:0% genetic sequences there's a variety of 00:08:37.320 --> 00:08:38.769 align:start position:0% genetic sequences there's a variety of other<00:08:37.500> things<00:08:37.740> like<00:08:38.039> that 00:08:38.769 --> 00:08:38.779 align:start position:0% other things like that 00:08:38.779 --> 00:08:42.110 align:start position:0% other things like that interesting<00:08:39.779> so<00:08:40.380> uh<00:08:40.680> let<00:08:40.800> me<00:08:40.919> give<00:08:41.159> me<00:08:41.159> if<00:08:41.459> uh 00:08:42.110 --> 00:08:42.120 align:start position:0% interesting so uh let me give me if uh 00:08:42.120 --> 00:08:44.750 align:start position:0% interesting so uh let me give me if uh throw<00:08:42.599> some<00:08:42.899> idea<00:08:43.260> on<00:08:43.979> the<00:08:44.099> table<00:08:44.219> which<00:08:44.580> I 00:08:44.750 --> 00:08:44.760 align:start position:0% throw some idea on the table which I 00:08:44.760 --> 00:08:47.570 align:start position:0% throw some idea on the table which I discussed<00:08:45.180> recently<00:08:45.540> with<00:08:45.959> uh<00:08:46.320> several<00:08:46.860> folks 00:08:47.570 --> 00:08:47.580 align:start position:0% discussed recently with uh several folks 00:08:47.580 --> 00:08:49.070 align:start position:0% discussed recently with uh several folks in<00:08:47.640> the<00:08:47.760> space<00:08:47.940> so<00:08:48.120> we<00:08:48.300> have<00:08:48.480> you<00:08:48.720> know<00:08:48.779> several 00:08:49.070 --> 00:08:49.080 align:start position:0% in the space so we have you know several 00:08:49.080 --> 00:08:52.190 align:start position:0% in the space so we have you know several startups<00:08:49.560> doing<00:08:49.680> genomics<00:08:50.300> and<00:08:51.300> also<00:08:51.600> amp<00:08:52.080> Lab 00:08:52.190 --> 00:08:52.200 align:start position:0% startups doing genomics and also amp Lab 00:08:52.200 --> 00:08:56.930 align:start position:0% startups doing genomics and also amp Lab at<00:08:52.560> Berkeley<00:08:52.920> is<00:08:53.820> using<00:08:54.180> spark<00:08:54.980> to<00:08:55.980> to<00:08:56.279> help 00:08:56.930 --> 00:08:56.940 align:start position:0% at Berkeley is using spark to to help 00:08:56.940 --> 00:08:59.930 align:start position:0% at Berkeley is using spark to to help basically<00:08:57.600> with<00:08:58.500> sequencing<00:08:59.339> and<00:08:59.700> and 00:08:59.930 --> 00:08:59.940 align:start position:0% basically with sequencing and and 00:08:59.940 --> 00:09:01.610 align:start position:0% basically with sequencing and and essentially<00:09:00.480> there's<00:09:00.779> several<00:09:01.200> there<00:09:01.500> are 00:09:01.610 --> 00:09:01.620 align:start position:0% essentially there's several there are 00:09:01.620 --> 00:09:04.790 align:start position:0% essentially there's several there are several<00:09:01.860> communities<00:09:02.540> both<00:09:03.540> industrial<00:09:04.500> and 00:09:04.790 --> 00:09:04.800 align:start position:0% several communities both industrial and 00:09:04.800 --> 00:09:08.509 align:start position:0% several communities both industrial and academic<00:09:05.339> which<00:09:06.740> unite<00:09:07.740> to<00:09:07.980> fight<00:09:08.100> cancer 00:09:08.509 --> 00:09:08.519 align:start position:0% academic which unite to fight cancer 00:09:08.519 --> 00:09:10.610 align:start position:0% academic which unite to fight cancer through<00:09:09.420> this<00:09:09.660> kind<00:09:09.839> of<00:09:09.959> open<00:09:10.080> genomic 00:09:10.610 --> 00:09:10.620 align:start position:0% through this kind of open genomic 00:09:10.620 --> 00:09:12.110 align:start position:0% through this kind of open genomic research<00:09:10.980> and<00:09:11.100> there<00:09:11.279> is<00:09:11.399> a<00:09:11.519> Global<00:09:11.760> Alliance 00:09:12.110 --> 00:09:12.120 align:start position:0% research and there is a Global Alliance 00:09:12.120 --> 00:09:14.269 align:start position:0% research and there is a Global Alliance of<00:09:12.300> several<00:09:12.600> forces<00:09:12.959> and<00:09:13.500> so<00:09:13.620> you<00:09:13.920> know<00:09:13.980> being 00:09:14.269 --> 00:09:14.279 align:start position:0% of several forces and so you know being 00:09:14.279 --> 00:09:15.949 align:start position:0% of several forces and so you know being a<00:09:14.519> software<00:09:14.760> engineer<00:09:14.880> myself<00:09:15.300> I'm<00:09:15.779> always 00:09:15.949 --> 00:09:15.959 align:start position:0% a software engineer myself I'm always 00:09:15.959 --> 00:09:18.110 align:start position:0% a software engineer myself I'm always thinking<00:09:16.320> that<00:09:16.440> you<00:09:16.620> know<00:09:16.680> open<00:09:16.800> source<00:09:17.279> uh 00:09:18.110 --> 00:09:18.120 align:start position:0% thinking that you know open source uh 00:09:18.120 --> 00:09:20.570 align:start position:0% thinking that you know open source uh approach<00:09:18.420> is<00:09:18.660> superior<00:09:19.140> because<00:09:19.500> you<00:09:19.860> can<00:09:19.980> you 00:09:20.570 --> 00:09:20.580 align:start position:0% approach is superior because you can you 00:09:20.580 --> 00:09:22.730 align:start position:0% approach is superior because you can you know<00:09:20.640> put<00:09:20.880> something<00:09:21.180> on<00:09:21.660> GitHub<00:09:22.080> and<00:09:22.440> kind<00:09:22.680> of 00:09:22.730 --> 00:09:22.740 align:start position:0% know put something on GitHub and kind of 00:09:22.740 --> 00:09:25.550 align:start position:0% know put something on GitHub and kind of you<00:09:22.920> have<00:09:23.160> a<00:09:23.339> good<00:09:23.459> readme<00:09:23.880> file<00:09:24.240> and<00:09:25.200> good 00:09:25.550 --> 00:09:25.560 align:start position:0% you have a good readme file and good 00:09:25.560 --> 00:09:29.090 align:start position:0% you have a good readme file and good example<00:09:26.040> and<00:09:26.580> test<00:09:26.820> you<00:09:27.600> know<00:09:27.720> uh<00:09:28.620> then<00:09:28.920> then 00:09:29.090 --> 00:09:29.100 align:start position:0% example and test you know uh then then 00:09:29.100 --> 00:09:30.590 align:start position:0% example and test you know uh then then you<00:09:29.339> will<00:09:29.459> have<00:09:29.580> a<00:09:29.700> lot<00:09:29.760> of<00:09:29.880> developers<00:09:30.300> who 00:09:30.590 --> 00:09:30.600 align:start position:0% you will have a lot of developers who 00:09:30.600 --> 00:09:32.630 align:start position:0% you will have a lot of developers who will<00:09:30.720> Who<00:09:30.899> will<00:09:31.019> jump<00:09:31.140> on<00:09:31.320> it<00:09:31.440> so<00:09:31.620> so<00:09:32.040> we<00:09:32.459> have 00:09:32.630 --> 00:09:32.640 align:start position:0% will Who will jump on it so so we have 00:09:32.640 --> 00:09:34.490 align:start position:0% will Who will jump on it so so we have these<00:09:32.880> conversations<00:09:33.240> where<00:09:33.600> we<00:09:33.839> can<00:09:34.019> you 00:09:34.490 --> 00:09:34.500 align:start position:0% these conversations where we can you 00:09:34.500 --> 00:09:36.530 align:start position:0% these conversations where we can you know<00:09:34.620> we're<00:09:34.740> thinking<00:09:35.100> uh<00:09:35.940> how<00:09:36.240> can<00:09:36.360> we 00:09:36.530 --> 00:09:36.540 align:start position:0% know we're thinking uh how can we 00:09:36.540 --> 00:09:39.350 align:start position:0% know we're thinking uh how can we package<00:09:37.140> this<00:09:37.380> knowledge<00:09:38.180> genomics<00:09:39.180> for 00:09:39.350 --> 00:09:39.360 align:start position:0% package this knowledge genomics for 00:09:39.360 --> 00:09:41.030 align:start position:0% package this knowledge genomics for computer<00:09:39.480> scientists<00:09:40.200> and<00:09:40.620> what<00:09:40.800> kind<00:09:40.920> of 00:09:41.030 --> 00:09:41.040 align:start position:0% computer scientists and what kind of 00:09:41.040 --> 00:09:43.610 align:start position:0% computer scientists and what kind of resources<00:09:41.399> we<00:09:41.640> need<00:09:42.060> to<00:09:42.720> enable<00:09:42.959> open<00:09:43.260> source 00:09:43.610 --> 00:09:43.620 align:start position:0% resources we need to enable open source 00:09:43.620 --> 00:09:45.110 align:start position:0% resources we need to enable open source collaboration<00:09:44.100> right<00:09:44.339> so<00:09:44.580> we<00:09:44.700> need<00:09:44.820> some<00:09:44.940> kind 00:09:45.110 --> 00:09:45.120 align:start position:0% collaboration right so we need some kind 00:09:45.120 --> 00:09:47.810 align:start position:0% collaboration right so we need some kind of<00:09:45.240> data<00:09:45.839> which<00:09:45.959> is<00:09:46.140> referenceable<00:09:46.740> and<00:09:47.519> some 00:09:47.810 --> 00:09:47.820 align:start position:0% of data which is referenceable and some 00:09:47.820 --> 00:09:49.910 align:start position:0% of data which is referenceable and some common<00:09:48.000> understood<00:09:48.600> format<00:09:49.019> and<00:09:49.440> we<00:09:49.680> also 00:09:49.910 --> 00:09:49.920 align:start position:0% common understood format and we also 00:09:49.920 --> 00:09:52.970 align:start position:0% common understood format and we also need<00:09:50.040> to<00:09:50.220> explain<00:09:50.399> the<00:09:51.180> problems<00:09:51.839> uh<00:09:52.740> in 00:09:52.970 --> 00:09:52.980 align:start position:0% need to explain the problems uh in 00:09:52.980 --> 00:09:55.310 align:start position:0% need to explain the problems uh in genomics<00:09:53.399> to<00:09:53.700> to<00:09:53.940> developers<00:09:54.480> but<00:09:54.720> because<00:09:54.899> we 00:09:55.310 --> 00:09:55.320 align:start position:0% genomics to to developers but because we 00:09:55.320 --> 00:09:56.930 align:start position:0% genomics to to developers but because we have<00:09:55.500> a<00:09:55.620> lot<00:09:55.680> of<00:09:55.800> smart<00:09:56.040> developers<00:09:56.519> in<00:09:56.760> the 00:09:56.930 --> 00:09:56.940 align:start position:0% have a lot of smart developers in the 00:09:56.940 --> 00:09:59.930 align:start position:0% have a lot of smart developers in the space<00:09:57.120> they<00:09:57.899> prop<00:09:58.080> can<00:09:58.500> probably<00:09:58.680> uh<00:09:59.580> do<00:09:59.760> a<00:09:59.880> lot 00:09:59.930 --> 00:09:59.940 align:start position:0% space they prop can probably uh do a lot 00:09:59.940 --> 00:10:02.630 align:start position:0% space they prop can probably uh do a lot of<00:10:00.060> advances<00:10:00.480> so<00:10:00.660> I'm<00:10:00.779> wondering<00:10:01.140> so<00:10:01.800> you're 00:10:02.630 --> 00:10:02.640 align:start position:0% of advances so I'm wondering so you're 00:10:02.640 --> 00:10:04.009 align:start position:0% of advances so I'm wondering so you're kind<00:10:02.880> of<00:10:02.940> you're<00:10:03.240> organizing<00:10:03.720> all<00:10:03.839> this 00:10:04.009 --> 00:10:04.019 align:start position:0% kind of you're organizing all this 00:10:04.019 --> 00:10:07.190 align:start position:0% kind of you're organizing all this knowledge<00:10:04.380> right<00:10:05.220> and<00:10:06.420> um<00:10:06.420> are<00:10:07.019> there<00:10:07.080> any 00:10:07.190 --> 00:10:07.200 align:start position:0% knowledge right and um are there any 00:10:07.200 --> 00:10:09.769 align:start position:0% knowledge right and um are there any insights<00:10:07.680> you<00:10:07.800> can<00:10:07.920> share<00:10:08.220> is<00:10:08.700> the<00:10:08.880> rename 00:10:09.769 --> 00:10:09.779 align:start position:0% insights you can share is the rename 00:10:09.779 --> 00:10:12.050 align:start position:0% insights you can share is the rename and<00:10:10.140> there<00:10:10.380> are<00:10:10.440> any<00:10:10.560> ways<00:10:11.040> for<00:10:11.580> the<00:10:11.820> community 00:10:12.050 --> 00:10:12.060 align:start position:0% and there are any ways for the community 00:10:12.060 --> 00:10:16.009 align:start position:0% and there are any ways for the community to<00:10:12.779> leverage<00:10:13.160> this<00:10:14.160> information<00:10:14.420> and<00:10:15.420> kind<00:10:15.899> of 00:10:16.009 --> 00:10:16.019 align:start position:0% to leverage this information and kind of 00:10:16.019 --> 00:10:18.110 align:start position:0% to leverage this information and kind of quickly<00:10:16.680> understand<00:10:16.920> or<00:10:17.399> Point<00:10:17.640> people<00:10:17.820> to 00:10:18.110 --> 00:10:18.120 align:start position:0% quickly understand or Point people to 00:10:18.120 --> 00:10:21.110 align:start position:0% quickly understand or Point people to the<00:10:18.360> right<00:10:18.480> pieces<00:10:19.140> right<00:10:19.980> so<00:10:20.700> is<00:10:20.940> this 00:10:21.110 --> 00:10:21.120 align:start position:0% the right pieces right so is this 00:10:21.120 --> 00:10:23.630 align:start position:0% the right pieces right so is this something<00:10:21.360> which<00:10:21.779> which<00:10:22.140> you<00:10:23.040> know<00:10:23.100> software 00:10:23.630 --> 00:10:23.640 align:start position:0% something which which you know software 00:10:23.640 --> 00:10:26.690 align:start position:0% something which which you know software engineer<00:10:24.120> can<00:10:24.779> do<00:10:25.140> as<00:10:25.800> a<00:10:25.980> hobby<00:10:26.160> in<00:10:26.580> their 00:10:26.690 --> 00:10:26.700 align:start position:0% engineer can do as a hobby in their 00:10:26.700 --> 00:10:28.250 align:start position:0% engineer can do as a hobby in their spare<00:10:27.060> time<00:10:27.180> or<00:10:27.420> is<00:10:27.600> this<00:10:27.720> something<00:10:27.899> you<00:10:28.200> know 00:10:28.250 --> 00:10:28.260 align:start position:0% spare time or is this something you know 00:10:28.260 --> 00:10:31.009 align:start position:0% spare time or is this something you know on<00:10:28.440> the<00:10:28.560> professional<00:10:29.060> researcher<00:10:30.060> can<00:10:30.240> do<00:10:30.480> uh 00:10:31.009 --> 00:10:31.019 align:start position:0% on the professional researcher can do uh 00:10:31.019 --> 00:10:33.650 align:start position:0% on the professional researcher can do uh what<00:10:31.560> is<00:10:31.680> you<00:10:31.800> thinking<00:10:32.100> about<00:10:32.160> this<00:10:32.459> so<00:10:33.180> the 00:10:33.650 --> 00:10:33.660 align:start position:0% what is you thinking about this so the 00:10:33.660 --> 00:10:35.630 align:start position:0% what is you thinking about this so the idea<00:10:33.899> here<00:10:34.200> is<00:10:34.380> is<00:10:34.620> you<00:10:34.860> know<00:10:34.920> how<00:10:35.279> much<00:10:35.399> of 00:10:35.630 --> 00:10:35.640 align:start position:0% idea here is is you know how much of 00:10:35.640 --> 00:10:37.790 align:start position:0% idea here is is you know how much of what<00:10:36.240> we<00:10:36.420> learn<00:10:36.660> or<00:10:36.959> what<00:10:37.140> we<00:10:37.320> what<00:10:37.560> we 00:10:37.790 --> 00:10:37.800 align:start position:0% what we learn or what we what we 00:10:37.800 --> 00:10:40.070 align:start position:0% what we learn or what we what we organize<00:10:38.100> can<00:10:38.399> be<00:10:38.880> um<00:10:39.000> made<00:10:39.420> available<00:10:39.600> so 00:10:40.070 --> 00:10:40.080 align:start position:0% organize can be um made available so 00:10:40.080 --> 00:10:42.590 align:start position:0% organize can be um made available so that<00:10:40.320> in<00:10:40.980> a<00:10:41.399> public<00:10:41.580> domain<00:10:42.240> in<00:10:42.420> the<00:10:42.540> public 00:10:42.590 --> 00:10:42.600 align:start position:0% that in a public domain in the public 00:10:42.600 --> 00:10:44.030 align:start position:0% that in a public domain in the public domain<00:10:42.959> or<00:10:43.080> if<00:10:43.200> you<00:10:43.380> know<00:10:43.560> I<00:10:43.680> understand<00:10:43.800> you 00:10:44.030 --> 00:10:44.040 align:start position:0% domain or if you know I understand you 00:10:44.040 --> 00:10:45.470 align:start position:0% domain or if you know I understand you guys<00:10:44.160> have<00:10:44.279> a<00:10:44.399> business<00:10:44.519> model<00:10:44.820> and<00:10:45.180> you<00:10:45.360> know 00:10:45.470 --> 00:10:45.480 align:start position:0% guys have a business model and you know 00:10:45.480 --> 00:10:47.329 align:start position:0% guys have a business model and you know we<00:10:45.600> make<00:10:45.779> these<00:10:45.959> products<00:10:46.200> available<00:10:46.380> but<00:10:46.920> how 00:10:47.329 --> 00:10:47.339 align:start position:0% we make these products available but how 00:10:47.339 --> 00:10:50.870 align:start position:0% we make these products available but how much<00:10:47.459> of<00:10:47.640> this<00:10:47.820> can<00:10:48.060> be<00:10:48.600> uh<00:10:49.440> can<00:10:49.620> be<00:10:49.740> you<00:10:49.860> know 00:10:50.870 --> 00:10:50.880 align:start position:0% much of this can be uh can be you know 00:10:50.880 --> 00:10:52.670 align:start position:0% much of this can be uh can be you know you<00:10:51.000> know<00:10:51.180> why<00:10:51.300> by<00:10:51.660> open<00:10:52.079> source<00:10:52.440> Community 00:10:52.670 --> 00:10:52.680 align:start position:0% you know why by open source Community 00:10:52.680 --> 00:10:54.350 align:start position:0% you know why by open source Community for<00:10:53.040> instance<00:10:53.220> looking<00:10:53.579> at<00:10:53.820> the<00:10:54.000> open 00:10:54.350 --> 00:10:54.360 align:start position:0% for instance looking at the open 00:10:54.360 --> 00:10:56.329 align:start position:0% for instance looking at the open available<00:10:54.720> date<00:10:55.140> this<00:10:55.440> is<00:10:55.680> something<00:10:55.920> which 00:10:56.329 --> 00:10:56.339 align:start position:0% available date this is something which 00:10:56.339 --> 00:10:59.389 align:start position:0% available date this is something which which<00:10:56.880> Community<00:10:57.300> needs<00:10:58.019> to<00:10:58.079> do<00:10:58.380> uh<00:10:58.980> is<00:10:59.160> this 00:10:59.389 --> 00:10:59.399 align:start position:0% which Community needs to do uh is this 00:10:59.399 --> 00:11:00.710 align:start position:0% which Community needs to do uh is this you<00:10:59.579> know<00:10:59.700> other<00:10:59.880> ways<00:11:00.180> for<00:11:00.300> Community<00:11:00.480> to 00:11:00.710 --> 00:11:00.720 align:start position:0% you know other ways for Community to 00:11:00.720 --> 00:11:01.970 align:start position:0% you know other ways for Community to organize<00:11:01.019> this<00:11:01.200> knowledge<00:11:01.500> and<00:11:01.740> make<00:11:01.860> it 00:11:01.970 --> 00:11:01.980 align:start position:0% organize this knowledge and make it 00:11:01.980 --> 00:11:03.769 align:start position:0% organize this knowledge and make it available<00:11:02.100> to<00:11:02.579> computer<00:11:02.940> scientists<00:11:03.540> kind<00:11:03.660> of 00:11:03.769 --> 00:11:03.779 align:start position:0% available to computer scientists kind of 00:11:03.779 --> 00:11:05.690 align:start position:0% available to computer scientists kind of to<00:11:03.899> quickly<00:11:04.079> educate<00:11:04.500> themselves<00:11:04.800> well<00:11:05.459> I 00:11:05.690 --> 00:11:05.700 align:start position:0% to quickly educate themselves well I 00:11:05.700 --> 00:11:07.130 align:start position:0% to quickly educate themselves well I think<00:11:05.880> yeah<00:11:06.180> I<00:11:06.360> think<00:11:06.480> there's<00:11:06.660> opportunities 00:11:07.130 --> 00:11:07.140 align:start position:0% think yeah I think there's opportunities 00:11:07.140 --> 00:11:07.970 align:start position:0% think yeah I think there's opportunities there 00:11:07.970 --> 00:11:07.980 align:start position:0% there 00:11:07.980 --> 00:11:09.410 align:start position:0% there um<00:11:08.040> and<00:11:08.399> frankly<00:11:08.760> I<00:11:08.940> don't<00:11:09.000> think<00:11:09.120> that<00:11:09.240> that's 00:11:09.410 --> 00:11:09.420 align:start position:0% um and frankly I don't think that that's 00:11:09.420 --> 00:11:11.030 align:start position:0% um and frankly I don't think that that's something<00:11:09.600> that<00:11:09.899> we<00:11:10.019> take<00:11:10.200> advantage<00:11:10.620> of<00:11:10.800> or 00:11:11.030 --> 00:11:11.040 align:start position:0% something that we take advantage of or 00:11:11.040 --> 00:11:12.710 align:start position:0% something that we take advantage of or we<00:11:11.220> really<00:11:11.459> promote<00:11:11.880> right<00:11:12.120> now<00:11:12.240> because<00:11:12.420> as 00:11:12.710 --> 00:11:12.720 align:start position:0% we really promote right now because as 00:11:12.720 --> 00:11:14.630 align:start position:0% we really promote right now because as you<00:11:13.019> pointed<00:11:13.740> out<00:11:13.800> and<00:11:13.980> you<00:11:14.220> know<00:11:14.279> we<00:11:14.459> have 00:11:14.630 --> 00:11:14.640 align:start position:0% you pointed out and you know we have 00:11:14.640 --> 00:11:15.949 align:start position:0% you pointed out and you know we have this<00:11:14.820> in<00:11:15.060> common<00:11:15.180> with<00:11:15.360> a<00:11:15.480> lot<00:11:15.600> of<00:11:15.660> people<00:11:15.779> I 00:11:15.949 --> 00:11:15.959 align:start position:0% this in common with a lot of people I 00:11:15.959 --> 00:11:17.449 align:start position:0% this in common with a lot of people I think<00:11:16.140> we're<00:11:16.320> a<00:11:16.560> private<00:11:16.800> company<00:11:16.980> and<00:11:17.279> the 00:11:17.449 --> 00:11:17.459 align:start position:0% think we're a private company and the 00:11:17.459 --> 00:11:20.690 align:start position:0% think we're a private company and the primary<00:11:17.959> uh<00:11:18.959> you<00:11:19.620> know<00:11:19.740> all<00:11:19.920> primary<00:11:20.279> energies 00:11:20.690 --> 00:11:20.700 align:start position:0% primary uh you know all primary energies 00:11:20.700 --> 00:11:22.910 align:start position:0% primary uh you know all primary energies are<00:11:20.880> devoted<00:11:21.300> towards<00:11:21.779> making<00:11:22.440> things<00:11:22.680> that 00:11:22.910 --> 00:11:22.920 align:start position:0% are devoted towards making things that 00:11:22.920 --> 00:11:24.889 align:start position:0% are devoted towards making things that we<00:11:23.040> can<00:11:23.100> sell<00:11:23.279> unfortunately 00:11:24.889 --> 00:11:24.899 align:start position:0% we can sell unfortunately 00:11:24.899 --> 00:11:29.090 align:start position:0% we can sell unfortunately um<00:11:24.959> on<00:11:25.620> the<00:11:25.680> other<00:11:25.740> hand<00:11:25.920> uh<00:11:26.820> we<00:11:27.600> benefit<00:11:28.320> from 00:11:29.090 --> 00:11:29.100 align:start position:0% um on the other hand uh we benefit from 00:11:29.100 --> 00:11:30.650 align:start position:0% um on the other hand uh we benefit from the<00:11:29.339> existence 00:11:30.650 --> 00:11:30.660 align:start position:0% the existence 00:11:30.660 --> 00:11:34.370 align:start position:0% the existence um<00:11:31.079> of<00:11:31.620> public<00:11:31.800> databases<00:11:32.459> of<00:11:33.360> genetic<00:11:34.019> data 00:11:34.370 --> 00:11:34.380 align:start position:0% um of public databases of genetic data 00:11:34.380 --> 00:11:36.290 align:start position:0% um of public databases of genetic data and<00:11:34.920> among<00:11:35.579> others<00:11:35.880> I<00:11:36.000> mentioned<00:11:36.180> the 00:11:36.290 --> 00:11:36.300 align:start position:0% and among others I mentioned the 00:11:36.300 --> 00:11:38.389 align:start position:0% and among others I mentioned the genetics<00:11:36.720> that's<00:11:37.260> a<00:11:37.440> big<00:11:37.500> Focus<00:11:37.800> lately<00:11:38.160> but 00:11:38.389 --> 00:11:38.399 align:start position:0% genetics that's a big Focus lately but 00:11:38.399 --> 00:11:40.190 align:start position:0% genetics that's a big Focus lately but there<00:11:38.640> are<00:11:38.820> certainly<00:11:39.060> other<00:11:39.300> public 00:11:40.190 --> 00:11:40.200 align:start position:0% there are certainly other public 00:11:40.200 --> 00:11:41.750 align:start position:0% there are certainly other public databases 00:11:41.750 --> 00:11:41.760 align:start position:0% databases 00:11:41.760 --> 00:11:44.269 align:start position:0% databases um that<00:11:42.120> that<00:11:42.360> we<00:11:42.720> use 00:11:44.269 --> 00:11:44.279 align:start position:0% um that that we use 00:11:44.279 --> 00:11:46.190 align:start position:0% um that that we use um<00:11:44.339> and 00:11:46.190 --> 00:11:46.200 align:start position:0% um and 00:11:46.200 --> 00:11:47.870 align:start position:0% um and um 00:11:47.870 --> 00:11:47.880 align:start position:0% um 00:11:47.880 --> 00:11:49.610 align:start position:0% um you<00:11:48.180> know<00:11:48.240> we<00:11:48.360> do<00:11:48.540> a<00:11:48.720> couple<00:11:48.839> of<00:11:48.959> things<00:11:49.200> so<00:11:49.380> we 00:11:49.610 --> 00:11:49.620 align:start position:0% you know we do a couple of things so we 00:11:49.620 --> 00:11:50.990 align:start position:0% you know we do a couple of things so we we<00:11:49.800> take<00:11:49.980> advantage<00:11:50.279> of<00:11:50.399> those<00:11:50.579> of<00:11:50.820> those 00:11:50.990 --> 00:11:51.000 align:start position:0% we take advantage of those of those 00:11:51.000 --> 00:11:52.430 align:start position:0% we take advantage of those of those databases<00:11:51.420> but<00:11:51.600> then<00:11:51.660> we<00:11:51.779> also<00:11:51.959> put<00:11:52.079> a<00:11:52.260> lot<00:11:52.320> of 00:11:52.430 --> 00:11:52.440 align:start position:0% databases but then we also put a lot of 00:11:52.440 --> 00:11:53.769 align:start position:0% databases but then we also put a lot of energy<00:11:52.560> into 00:11:53.769 --> 00:11:53.779 align:start position:0% energy into 00:11:53.779 --> 00:11:56.569 align:start position:0% energy into curating<00:11:54.779> like<00:11:55.620> I<00:11:55.740> said<00:11:55.800> unstructured 00:11:56.569 --> 00:11:56.579 align:start position:0% curating like I said unstructured 00:11:56.579 --> 00:12:00.110 align:start position:0% curating like I said unstructured knowledge<00:11:57.300> and<00:11:57.779> essentially<00:11:58.560> uh 00:12:00.110 --> 00:12:00.120 align:start position:0% knowledge and essentially uh 00:12:00.120 --> 00:12:02.810 align:start position:0% knowledge and essentially uh exposing<00:12:00.959> the<00:12:01.079> structure<00:12:01.440> right<00:12:02.220> or<00:12:02.399> exposing 00:12:02.810 --> 00:12:02.820 align:start position:0% exposing the structure right or exposing 00:12:02.820 --> 00:12:05.509 align:start position:0% exposing the structure right or exposing exposing<00:12:03.420> uh<00:12:04.320> putting<00:12:04.800> putting<00:12:05.100> a<00:12:05.160> structure 00:12:05.509 --> 00:12:05.519 align:start position:0% exposing uh putting putting a structure 00:12:05.519 --> 00:12:08.030 align:start position:0% exposing uh putting putting a structure around<00:12:05.760> the<00:12:06.180> the<00:12:06.420> meanings 00:12:08.030 --> 00:12:08.040 align:start position:0% around the the meanings 00:12:08.040 --> 00:12:08.990 align:start position:0% around the the meanings um 00:12:08.990 --> 00:12:09.000 align:start position:0% um 00:12:09.000 --> 00:12:11.449 align:start position:0% um so<00:12:09.480> that<00:12:09.660> ladder<00:12:10.079> stuff<00:12:10.320> is<00:12:10.740> I<00:12:11.100> would<00:12:11.220> say 00:12:11.449 --> 00:12:11.459 align:start position:0% so that ladder stuff is I would say 00:12:11.459 --> 00:12:12.949 align:start position:0% so that ladder stuff is I would say probably<00:12:11.940> going<00:12:12.240> to<00:12:12.360> continue<00:12:12.480> to<00:12:12.660> be<00:12:12.779> pretty 00:12:12.949 --> 00:12:12.959 align:start position:0% probably going to continue to be pretty 00:12:12.959 --> 00:12:15.530 align:start position:0% probably going to continue to be pretty proprietary<00:12:13.860> because<00:12:14.220> uh<00:12:14.820> that<00:12:15.120> labor 00:12:15.530 --> 00:12:15.540 align:start position:0% proprietary because uh that labor 00:12:15.540 --> 00:12:16.970 align:start position:0% proprietary because uh that labor intensive<00:12:16.019> kind<00:12:16.260> of<00:12:16.380> work<00:12:16.500> that<00:12:16.800> just 00:12:16.970 --> 00:12:16.980 align:start position:0% intensive kind of work that just 00:12:16.980 --> 00:12:19.910 align:start position:0% intensive kind of work that just requires<00:12:17.339> a<00:12:17.459> lot<00:12:17.579> of<00:12:17.700> money<00:12:17.880> that's<00:12:18.839> where<00:12:19.260> uh 00:12:19.910 --> 00:12:19.920 align:start position:0% requires a lot of money that's where uh 00:12:19.920 --> 00:12:22.250 align:start position:0% requires a lot of money that's where uh the<00:12:20.100> sort<00:12:20.279> of<00:12:20.399> private<00:12:20.760> domain<00:12:21.120> probably<00:12:21.480> has 00:12:22.250 --> 00:12:22.260 align:start position:0% the sort of private domain probably has 00:12:22.260 --> 00:12:25.370 align:start position:0% the sort of private domain probably has an<00:12:22.500> advantage<00:12:22.980> over<00:12:23.339> the<00:12:24.060> public<00:12:24.240> domain 00:12:25.370 --> 00:12:25.380 align:start position:0% an advantage over the public domain 00:12:25.380 --> 00:12:25.970 align:start position:0% an advantage over the public domain um 00:12:25.970 --> 00:12:25.980 align:start position:0% um 00:12:25.980 --> 00:12:28.009 align:start position:0% um meaning<00:12:26.459> we<00:12:26.820> know<00:12:26.940> we<00:12:27.060> need<00:12:27.420> a<00:12:27.660> large<00:12:27.779> number 00:12:28.009 --> 00:12:28.019 align:start position:0% meaning we know we need a large number 00:12:28.019 --> 00:12:31.009 align:start position:0% meaning we know we need a large number of<00:12:28.279> very<00:12:29.279> highly<00:12:29.700> trained<00:12:30.120> experts<00:12:30.540> doing 00:12:31.009 --> 00:12:31.019 align:start position:0% of very highly trained experts doing 00:12:31.019 --> 00:12:33.009 align:start position:0% of very highly trained experts doing this<00:12:31.320> stuff<00:12:31.500> and<00:12:31.740> it's<00:12:32.040> just<00:12:32.220> expensive<00:12:32.700> but 00:12:33.009 --> 00:12:33.019 align:start position:0% this stuff and it's just expensive but 00:12:33.019 --> 00:12:35.990 align:start position:0% this stuff and it's just expensive but uh<00:12:34.019> for<00:12:34.680> the<00:12:34.740> public<00:12:34.920> databases<00:12:35.459> that<00:12:35.640> we<00:12:35.820> use 00:12:35.990 --> 00:12:36.000 align:start position:0% uh for the public databases that we use 00:12:36.000 --> 00:12:38.630 align:start position:0% uh for the public databases that we use we<00:12:37.380> um<00:12:37.380> they're<00:12:37.860> more<00:12:37.980> useful<00:12:38.220> to<00:12:38.399> us<00:12:38.459> if 00:12:38.630 --> 00:12:38.640 align:start position:0% we um they're more useful to us if 00:12:38.640 --> 00:12:39.769 align:start position:0% we um they're more useful to us if they're<00:12:38.760> higher<00:12:39.060> quality<00:12:39.300> and<00:12:39.420> so<00:12:39.600> we 00:12:39.769 --> 00:12:39.779 align:start position:0% they're higher quality and so we 00:12:39.779 --> 00:12:41.750 align:start position:0% they're higher quality and so we regularly<00:12:40.260> provide<00:12:40.920> feedback<00:12:41.339> to<00:12:41.579> these 00:12:41.750 --> 00:12:41.760 align:start position:0% regularly provide feedback to these 00:12:41.760 --> 00:12:43.629 align:start position:0% regularly provide feedback to these databases<00:12:42.300> and<00:12:42.480> they<00:12:42.600> get<00:12:42.779> to<00:12:42.899> know<00:12:43.019> us 00:12:43.629 --> 00:12:43.639 align:start position:0% databases and they get to know us 00:12:43.639 --> 00:12:46.970 align:start position:0% databases and they get to know us because<00:12:44.639> we<00:12:45.360> because<00:12:45.660> we<00:12:46.019> are<00:12:46.200> so<00:12:46.440> focused<00:12:46.800> on 00:12:46.970 --> 00:12:46.980 align:start position:0% because we because we are so focused on 00:12:46.980 --> 00:12:49.250 align:start position:0% because we because we are so focused on on<00:12:47.339> quality<00:12:47.760> and<00:12:47.880> testing<00:12:48.360> and<00:12:48.779> integration 00:12:49.250 --> 00:12:49.260 align:start position:0% on quality and testing and integration 00:12:49.260 --> 00:12:52.190 align:start position:0% on quality and testing and integration we<00:12:49.920> notice<00:12:50.420> issues<00:12:51.420> that<00:12:51.660> they<00:12:51.779> frequently 00:12:52.190 --> 00:12:52.200 align:start position:0% we notice issues that they frequently 00:12:52.200 --> 00:12:54.949 align:start position:0% we notice issues that they frequently don't<00:12:52.380> have<00:12:52.560> the<00:12:52.800> resources<00:12:53.220> to<00:12:53.459> notice<00:12:53.959> and 00:12:54.949 --> 00:12:54.959 align:start position:0% don't have the resources to notice and 00:12:54.959 --> 00:12:57.970 align:start position:0% don't have the resources to notice and so<00:12:55.079> we<00:12:55.320> do<00:12:55.500> provide<00:12:56.160> feedback<00:12:56.579> in<00:12:57.180> that<00:12:57.360> way 00:12:57.970 --> 00:12:57.980 align:start position:0% so we do provide feedback in that way 00:12:57.980 --> 00:13:00.530 align:start position:0% so we do provide feedback in that way and<00:12:58.980> that<00:12:59.220> sort<00:12:59.459> of<00:12:59.519> thing<00:12:59.760> if<00:13:00.120> there<00:13:00.300> were<00:13:00.420> a 00:13:00.530 --> 00:13:00.540 align:start position:0% and that sort of thing if there were a 00:13:00.540 --> 00:13:03.290 align:start position:0% and that sort of thing if there were a form<00:13:00.720> for<00:13:01.019> it<00:13:01.200> might<00:13:01.500> be<00:13:01.700> even<00:13:02.700> more<00:13:02.940> valuable 00:13:03.290 --> 00:13:03.300 align:start position:0% form for it might be even more valuable 00:13:03.300 --> 00:13:05.389 align:start position:0% form for it might be even more valuable if<00:13:03.540> we<00:13:03.660> could<00:13:03.779> say<00:13:04.019> hey<00:13:04.260> we<00:13:04.980> have<00:13:05.100> some 00:13:05.389 --> 00:13:05.399 align:start position:0% if we could say hey we have some 00:13:05.399 --> 00:13:08.090 align:start position:0% if we could say hey we have some suggestions<00:13:06.000> as<00:13:06.720> to<00:13:06.959> how<00:13:07.200> data<00:13:07.620> could<00:13:07.800> be<00:13:07.920> and 00:13:08.090 --> 00:13:08.100 align:start position:0% suggestions as to how data could be and 00:13:08.100 --> 00:13:09.470 align:start position:0% suggestions as to how data could be and we're<00:13:08.339> happy<00:13:08.519> to<00:13:08.760> share<00:13:08.880> them<00:13:09.060> with<00:13:09.180> the<00:13:09.360> world 00:13:09.470 --> 00:13:09.480 align:start position:0% we're happy to share them with the world 00:13:09.480 --> 00:13:12.530 align:start position:0% we're happy to share them with the world because<00:13:09.779> everyone<00:13:10.019> benefits<00:13:10.740> right<00:13:11.339> uh<00:13:12.300> we 00:13:12.530 --> 00:13:12.540 align:start position:0% because everyone benefits right uh we 00:13:12.540 --> 00:13:14.210 align:start position:0% because everyone benefits right uh we have<00:13:12.660> some<00:13:12.779> suggestions<00:13:13.139> as<00:13:13.440> to 00:13:14.210 --> 00:13:14.220 align:start position:0% have some suggestions as to 00:13:14.220 --> 00:13:15.889 align:start position:0% have some suggestions as to what<00:13:14.820> people<00:13:15.000> should<00:13:15.240> be<00:13:15.360> paying<00:13:15.660> attention 00:13:15.889 --> 00:13:15.899 align:start position:0% what people should be paying attention 00:13:15.899 --> 00:13:18.470 align:start position:0% what people should be paying attention to<00:13:16.139> uh<00:13:17.100> when<00:13:17.519> they're<00:13:17.700> developing<00:13:18.060> databases 00:13:18.470 --> 00:13:18.480 align:start position:0% to uh when they're developing databases 00:13:18.480 --> 00:13:19.670 align:start position:0% to uh when they're developing databases when<00:13:18.720> they're<00:13:18.839> organizing<00:13:19.260> data<00:13:19.500> when 00:13:19.670 --> 00:13:19.680 align:start position:0% when they're organizing data when 00:13:19.680 --> 00:13:21.710 align:start position:0% when they're organizing data when they're<00:13:19.800> when<00:13:20.040> they're<00:13:20.160> collating<00:13:20.519> data 00:13:21.710 --> 00:13:21.720 align:start position:0% they're when they're collating data 00:13:21.720 --> 00:13:24.290 align:start position:0% they're when they're collating data um<00:13:21.779> and<00:13:22.500> uh<00:13:23.040> and<00:13:23.399> here<00:13:23.639> are<00:13:23.760> some<00:13:23.940> techniques 00:13:24.290 --> 00:13:24.300 align:start position:0% um and uh and here are some techniques 00:13:24.300 --> 00:13:27.470 align:start position:0% um and uh and here are some techniques that<00:13:24.420> people<00:13:24.600> could<00:13:24.779> use<00:13:25.040> uh<00:13:26.040> to 00:13:27.470 --> 00:13:27.480 align:start position:0% that people could use uh to 00:13:27.480 --> 00:13:28.910 align:start position:0% that people could use uh to um help<00:13:27.720> that<00:13:27.899> along<00:13:28.079> and<00:13:28.380> to<00:13:28.560> make<00:13:28.680> that 00:13:28.910 --> 00:13:28.920 align:start position:0% um help that along and to make that 00:13:28.920 --> 00:13:30.650 align:start position:0% um help that along and to make that feasible 00:13:30.650 --> 00:13:30.660 align:start position:0% feasible 00:13:30.660 --> 00:13:33.530 align:start position:0% feasible um<00:13:30.720> so<00:13:31.200> I<00:13:31.320> think<00:13:31.680> that<00:13:32.100> sort<00:13:32.339> of<00:13:32.540> uh 00:13:33.530 --> 00:13:33.540 align:start position:0% um so I think that sort of uh 00:13:33.540 --> 00:13:35.569 align:start position:0% um so I think that sort of uh interaction<00:13:33.959> uh<00:13:34.680> I<00:13:34.800> think<00:13:34.920> there's<00:13:35.040> room<00:13:35.399> for 00:13:35.569 --> 00:13:35.579 align:start position:0% interaction uh I think there's room for 00:13:35.579 --> 00:13:37.370 align:start position:0% interaction uh I think there's room for that<00:13:35.700> sort<00:13:35.880> of<00:13:35.940> thing<00:13:36.060> makes<00:13:36.600> sense<00:13:36.839> so<00:13:37.200> but 00:13:37.370 --> 00:13:37.380 align:start position:0% that sort of thing makes sense so but 00:13:37.380 --> 00:13:39.110 align:start position:0% that sort of thing makes sense so but I'm<00:13:37.800> also<00:13:37.980> curious<00:13:38.279> you<00:13:38.459> know<00:13:38.579> so<00:13:38.760> you<00:13:38.880> said 00:13:39.110 --> 00:13:39.120 align:start position:0% I'm also curious you know so you said 00:13:39.120 --> 00:13:42.170 align:start position:0% I'm also curious you know so you said you're<00:13:39.360> a<00:13:39.899> biologist<00:13:40.320> right<00:13:41.279> so<00:13:41.579> what<00:13:41.940> brought 00:13:42.170 --> 00:13:42.180 align:start position:0% you're a biologist right so what brought 00:13:42.180 --> 00:13:43.850 align:start position:0% you're a biologist right so what brought you<00:13:42.360> to<00:13:42.660> from<00:13:42.899> biology<00:13:43.200> to<00:13:43.440> basically 00:13:43.850 --> 00:13:43.860 align:start position:0% you to from biology to basically 00:13:43.860 --> 00:13:45.290 align:start position:0% you to from biology to basically knowledge<00:13:44.100> organization<00:13:44.700> which<00:13:45.120> is 00:13:45.290 --> 00:13:45.300 align:start position:0% knowledge organization which is 00:13:45.300 --> 00:13:46.430 align:start position:0% knowledge organization which is essentially<00:13:45.660> you<00:13:46.079> know<00:13:46.200> a<00:13:46.320> computer 00:13:46.430 --> 00:13:46.440 align:start position:0% essentially you know a computer 00:13:46.440 --> 00:13:49.370 align:start position:0% essentially you know a computer scientist<00:13:46.980> kind<00:13:47.160> of<00:13:47.339> domain<00:13:47.940> it<00:13:48.660> is<00:13:48.779> it<00:13:49.079> is<00:13:49.200> I 00:13:49.370 --> 00:13:49.380 align:start position:0% scientist kind of domain it is it is I 00:13:49.380 --> 00:13:50.930 align:start position:0% scientist kind of domain it is it is I mean<00:13:49.560> we're<00:13:49.800> we're<00:13:50.040> an<00:13:50.220> interesting<00:13:50.519> we're<00:13:50.760> an 00:13:50.930 --> 00:13:50.940 align:start position:0% mean we're we're an interesting we're an 00:13:50.940 --> 00:13:52.970 align:start position:0% mean we're we're an interesting we're an interesting<00:13:51.240> space<00:13:51.420> uh<00:13:52.260> you<00:13:52.500> know<00:13:52.620> in<00:13:52.860> my 00:13:52.970 --> 00:13:52.980 align:start position:0% interesting space uh you know in my 00:13:52.980 --> 00:13:56.930 align:start position:0% interesting space uh you know in my group<00:13:53.220> we<00:13:53.579> we<00:13:54.240> certainly<00:13:54.600> are<00:13:54.899> are<00:13:55.519> doing<00:13:56.519> data 00:13:56.930 --> 00:13:56.940 align:start position:0% group we we certainly are are doing data 00:13:56.940 --> 00:13:58.430 align:start position:0% group we we certainly are are doing data science<00:13:57.180> as<00:13:57.480> it<00:13:57.660> were<00:13:57.779> and<00:13:57.959> we<00:13:58.079> don't<00:13:58.200> have<00:13:58.320> a 00:13:58.430 --> 00:13:58.440 align:start position:0% science as it were and we don't have a 00:13:58.440 --> 00:13:59.990 align:start position:0% science as it were and we don't have a we<00:13:58.560> don't<00:13:58.680> use<00:13:58.800> that<00:13:58.980> name<00:13:59.160> but<00:13:59.459> people<00:13:59.639> people 00:13:59.990 --> 00:14:00.000 align:start position:0% we don't use that name but people people 00:14:00.000 --> 00:14:01.009 align:start position:0% we don't use that name but people people do 00:14:01.009 --> 00:14:01.019 align:start position:0% do 00:14:01.019 --> 00:14:02.030 align:start position:0% do um 00:14:02.030 --> 00:14:02.040 align:start position:0% um 00:14:02.040 --> 00:14:06.170 align:start position:0% um we<00:14:03.000> are<00:14:03.180> a<00:14:03.360> mix<00:14:03.600> of<00:14:04.139> people<00:14:04.980> with<00:14:05.519> a<00:14:05.760> strong 00:14:06.170 --> 00:14:06.180 align:start position:0% we are a mix of people with a strong 00:14:06.180 --> 00:14:07.910 align:start position:0% we are a mix of people with a strong computer<00:14:06.420> science<00:14:06.779> background<00:14:07.260> and<00:14:07.680> people 00:14:07.910 --> 00:14:07.920 align:start position:0% computer science background and people 00:14:07.920 --> 00:14:10.310 align:start position:0% computer science background and people with<00:14:08.160> a<00:14:08.519> strong<00:14:08.839> Sciences<00:14:09.839> background<00:14:10.139> I 00:14:10.310 --> 00:14:10.320 align:start position:0% with a strong Sciences background I 00:14:10.320 --> 00:14:11.389 align:start position:0% with a strong Sciences background I would<00:14:10.440> say<00:14:10.560> most<00:14:10.740> people<00:14:10.980> in<00:14:11.100> the<00:14:11.160> group<00:14:11.279> are 00:14:11.389 --> 00:14:11.399 align:start position:0% would say most people in the group are 00:14:11.399 --> 00:14:13.850 align:start position:0% would say most people in the group are PhD<00:14:11.880> level<00:14:12.120> uh<00:14:13.019> scientists<00:14:13.440> either<00:14:13.620> in 00:14:13.850 --> 00:14:13.860 align:start position:0% PhD level uh scientists either in 00:14:13.860 --> 00:14:15.650 align:start position:0% PhD level uh scientists either in chemistry<00:14:14.220> or<00:14:14.279> biology<00:14:14.639> okay 00:14:15.650 --> 00:14:15.660 align:start position:0% chemistry or biology okay 00:14:15.660 --> 00:14:19.269 align:start position:0% chemistry or biology okay um and<00:14:16.380> with<00:14:16.740> uh<00:14:17.459> varying<00:14:18.180> uh<00:14:18.600> levels<00:14:18.899> of 00:14:19.269 --> 00:14:19.279 align:start position:0% um and with uh varying uh levels of 00:14:19.279 --> 00:14:22.069 align:start position:0% um and with uh varying uh levels of exposure<00:14:20.279> to<00:14:20.760> the<00:14:20.880> clinical<00:14:21.180> side<00:14:21.420> but 00:14:22.069 --> 00:14:22.079 align:start position:0% exposure to the clinical side but 00:14:22.079 --> 00:14:24.410 align:start position:0% exposure to the clinical side but probably<00:14:22.320> more<00:14:22.620> on<00:14:22.860> the<00:14:22.920> research<00:14:23.279> side 00:14:24.410 --> 00:14:24.420 align:start position:0% probably more on the research side 00:14:24.420 --> 00:14:27.470 align:start position:0% probably more on the research side um<00:14:24.480> and<00:14:25.440> uh<00:14:26.160> it<00:14:26.459> we're<00:14:26.639> basically<00:14:27.000> we're<00:14:27.300> a 00:14:27.470 --> 00:14:27.480 align:start position:0% um and uh it we're basically we're a 00:14:27.480 --> 00:14:30.350 align:start position:0% um and uh it we're basically we're a group<00:14:27.660> of<00:14:27.779> people<00:14:27.959> who<00:14:28.320> are<00:14:28.380> interested<00:14:28.860> in 00:14:30.350 --> 00:14:30.360 align:start position:0% group of people who are interested in 00:14:30.360 --> 00:14:33.230 align:start position:0% group of people who are interested in um<00:14:30.420> maybe<00:14:30.600> stepping<00:14:31.079> back<00:14:31.139> from<00:14:31.500> the<00:14:31.800> uh<00:14:32.760> what 00:14:33.230 --> 00:14:33.240 align:start position:0% um maybe stepping back from the uh what 00:14:33.240 --> 00:14:34.730 align:start position:0% um maybe stepping back from the uh what you<00:14:33.480> might<00:14:33.660> call<00:14:33.839> in<00:14:33.959> the<00:14:34.139> business<00:14:34.320> world<00:14:34.500> the 00:14:34.730 --> 00:14:34.740 align:start position:0% you might call in the business world the 00:14:34.740 --> 00:14:36.470 align:start position:0% you might call in the business world the individual<00:14:35.040> contributor<00:14:35.639> level<00:14:36.060> when<00:14:36.360> it 00:14:36.470 --> 00:14:36.480 align:start position:0% individual contributor level when it 00:14:36.480 --> 00:14:39.829 align:start position:0% individual contributor level when it comes<00:14:36.660> to<00:14:36.920> uh<00:14:37.920> scientific<00:14:38.579> knowledge<00:14:39.060> and 00:14:39.829 --> 00:14:39.839 align:start position:0% comes to uh scientific knowledge and 00:14:39.839 --> 00:14:42.230 align:start position:0% comes to uh scientific knowledge and more<00:14:40.139> uh<00:14:40.980> sort<00:14:41.339> of<00:14:41.399> aware<00:14:41.639> and<00:14:41.760> interested<00:14:42.120> in 00:14:42.230 --> 00:14:42.240 align:start position:0% more uh sort of aware and interested in 00:14:42.240 --> 00:14:43.550 align:start position:0% more uh sort of aware and interested in the<00:14:42.360> idea<00:14:42.600> that<00:14:42.779> hey<00:14:42.959> there's<00:14:43.199> all<00:14:43.380> this 00:14:43.550 --> 00:14:43.560 align:start position:0% the idea that hey there's all this 00:14:43.560 --> 00:14:45.050 align:start position:0% the idea that hey there's all this knowledge<00:14:43.860> out<00:14:44.040> there<00:14:44.160> but<00:14:44.399> it's 00:14:45.050 --> 00:14:45.060 align:start position:0% knowledge out there but it's 00:14:45.060 --> 00:14:47.329 align:start position:0% knowledge out there but it's not<00:14:45.540> that<00:14:45.720> useful<00:14:46.079> if<00:14:46.320> it's<00:14:46.500> not<00:14:46.860> accessible 00:14:47.329 --> 00:14:47.339 align:start position:0% not that useful if it's not accessible 00:14:47.339 --> 00:14:50.150 align:start position:0% not that useful if it's not accessible and<00:14:47.699> so<00:14:47.940> much<00:14:48.060> of<00:14:48.240> it<00:14:48.360> is<00:14:48.480> inaccessible 00:14:50.150 --> 00:14:50.160 align:start position:0% and so much of it is inaccessible 00:14:50.160 --> 00:14:53.750 align:start position:0% and so much of it is inaccessible um<00:14:50.279> either<00:14:50.699> because<00:14:51.000> it's<00:14:51.839> not<00:14:52.680> well 00:14:53.750 --> 00:14:53.760 align:start position:0% um either because it's not well 00:14:53.760 --> 00:14:54.410 align:start position:0% um either because it's not well um 00:14:54.410 --> 00:14:54.420 align:start position:0% um 00:14:54.420 --> 00:14:56.210 align:start position:0% um organized<00:14:54.959> to<00:14:55.079> begin<00:14:55.199> with<00:14:55.380> and<00:14:55.740> that's<00:14:55.980> how<00:14:56.100> a 00:14:56.210 --> 00:14:56.220 align:start position:0% organized to begin with and that's how a 00:14:56.220 --> 00:14:57.530 align:start position:0% organized to begin with and that's how a structure<00:14:56.459> to<00:14:56.579> begin<00:14:56.639> with<00:14:56.820> OR<00:14:57.060> because<00:14:57.300> it's 00:14:57.530 --> 00:14:57.540 align:start position:0% structure to begin with OR because it's 00:14:57.540 --> 00:14:58.550 align:start position:0% structure to begin with OR because it's just<00:14:57.779> not 00:14:58.550 --> 00:14:58.560 align:start position:0% just not 00:14:58.560 --> 00:15:00.530 align:start position:0% just not um<00:14:58.620> integrated<00:14:59.279> into<00:14:59.519> a<00:14:59.760> unified<00:15:00.000> system<00:15:00.300> or 00:15:00.530 --> 00:15:00.540 align:start position:0% um integrated into a unified system or 00:15:00.540 --> 00:15:02.170 align:start position:0% um integrated into a unified system or any<00:15:00.720> kind<00:15:00.839> of<00:15:00.959> unified<00:15:01.199> system 00:15:02.170 --> 00:15:02.180 align:start position:0% any kind of unified system 00:15:02.180 --> 00:15:04.750 align:start position:0% any kind of unified system and<00:15:03.180> so<00:15:03.360> there's<00:15:03.779> knowledge<00:15:04.139> that<00:15:04.320> can<00:15:04.500> be 00:15:04.750 --> 00:15:04.760 align:start position:0% and so there's knowledge that can be 00:15:04.760 --> 00:15:07.370 align:start position:0% and so there's knowledge that can be exposed<00:15:05.760> without<00:15:06.240> doing<00:15:06.660> anything<00:15:06.899> in<00:15:07.260> the 00:15:07.370 --> 00:15:07.380 align:start position:0% exposed without doing anything in the 00:15:07.380 --> 00:15:08.170 align:start position:0% exposed without doing anything in the lab 00:15:08.170 --> 00:15:08.180 align:start position:0% lab 00:15:08.180 --> 00:15:10.850 align:start position:0% lab just<00:15:09.180> by<00:15:09.660> sort<00:15:10.019> of<00:15:10.139> putting<00:15:10.500> the<00:15:10.560> pieces 00:15:10.850 --> 00:15:10.860 align:start position:0% just by sort of putting the pieces 00:15:10.860 --> 00:15:12.410 align:start position:0% just by sort of putting the pieces together<00:15:11.040> that<00:15:11.639> are<00:15:11.820> already<00:15:11.880> out<00:15:12.120> there<00:15:12.240> if 00:15:12.410 --> 00:15:12.420 align:start position:0% together that are already out there if 00:15:12.420 --> 00:15:14.150 align:start position:0% together that are already out there if you<00:15:12.540> can<00:15:12.660> reveal<00:15:13.019> those<00:15:13.199> pieces<00:15:13.560> and<00:15:13.860> get<00:15:14.040> them 00:15:14.150 --> 00:15:14.160 align:start position:0% you can reveal those pieces and get them 00:15:14.160 --> 00:15:17.449 align:start position:0% you can reveal those pieces and get them into<00:15:14.339> one<00:15:14.519> system<00:15:14.760> so<00:15:15.199> uh<00:15:16.199> that<00:15:17.040> that's 00:15:17.449 --> 00:15:17.459 align:start position:0% into one system so uh that that's 00:15:17.459 --> 00:15:19.610 align:start position:0% into one system so uh that that's intriguing<00:15:18.180> to<00:15:18.300> me<00:15:18.480> I<00:15:18.779> mean<00:15:18.839> I<00:15:19.139> came<00:15:19.260> from<00:15:19.440> a 00:15:19.610 --> 00:15:19.620 align:start position:0% intriguing to me I mean I came from a 00:15:19.620 --> 00:15:22.189 align:start position:0% intriguing to me I mean I came from a place<00:15:19.800> where<00:15:20.100> I<00:15:20.279> was<00:15:20.540> a<00:15:21.540> graduate<00:15:21.899> student<00:15:22.019> and 00:15:22.189 --> 00:15:22.199 align:start position:0% place where I was a graduate student and 00:15:22.199 --> 00:15:23.870 align:start position:0% place where I was a graduate student and then<00:15:22.320> a<00:15:22.440> postdoc<00:15:22.800> I<00:15:23.100> guess<00:15:23.220> like<00:15:23.519> we<00:15:23.699> said 00:15:23.870 --> 00:15:23.880 align:start position:0% then a postdoc I guess like we said 00:15:23.880 --> 00:15:26.090 align:start position:0% then a postdoc I guess like we said molecular<00:15:24.300> biology<00:15:24.920> specifically<00:15:25.920> in 00:15:26.090 --> 00:15:26.100 align:start position:0% molecular biology specifically in 00:15:26.100 --> 00:15:28.069 align:start position:0% molecular biology specifically in protein<00:15:26.459> structure<00:15:26.880> and<00:15:27.120> I<00:15:27.300> did<00:15:27.540> sort<00:15:27.959> of 00:15:28.069 --> 00:15:28.079 align:start position:0% protein structure and I did sort of 00:15:28.079 --> 00:15:30.410 align:start position:0% protein structure and I did sort of biophysics<00:15:28.560> biochemistry<00:15:29.160> which<00:15:29.339> is<00:15:29.519> a<00:15:29.760> lab<00:15:29.940> I 00:15:30.410 --> 00:15:30.420 align:start position:0% biophysics biochemistry which is a lab I 00:15:30.420 --> 00:15:33.470 align:start position:0% biophysics biochemistry which is a lab I was<00:15:30.540> in<00:15:30.660> the<00:15:30.779> lab<00:15:31.339> I've<00:15:32.339> also<00:15:32.639> but<00:15:33.000> for<00:15:33.240> a<00:15:33.360> long 00:15:33.470 --> 00:15:33.480 align:start position:0% was in the lab I've also but for a long 00:15:33.480 --> 00:15:34.850 align:start position:0% was in the lab I've also but for a long long<00:15:33.720> time<00:15:34.019> I've<00:15:34.260> been<00:15:34.440> interested<00:15:34.740> in 00:15:34.850 --> 00:15:34.860 align:start position:0% long time I've been interested in 00:15:34.860 --> 00:15:36.769 align:start position:0% long time I've been interested in computers<00:15:35.220> and<00:15:35.459> sort<00:15:35.639> of<00:15:35.820> playing<00:15:36.360> with<00:15:36.660> them 00:15:36.769 --> 00:15:36.779 align:start position:0% computers and sort of playing with them 00:15:36.779 --> 00:15:38.769 align:start position:0% computers and sort of playing with them and<00:15:36.959> so<00:15:37.139> that's<00:15:37.260> always<00:15:37.500> been<00:15:37.740> kind<00:15:37.920> of<00:15:38.040> a 00:15:38.769 --> 00:15:38.779 align:start position:0% and so that's always been kind of a 00:15:38.779 --> 00:15:42.310 align:start position:0% and so that's always been kind of a of<00:15:39.779> mine<00:15:40.620> and<00:15:41.220> at<00:15:41.399> some<00:15:41.639> point 00:15:42.310 --> 00:15:42.320 align:start position:0% of mine and at some point 00:15:42.320 --> 00:15:45.949 align:start position:0% of mine and at some point the<00:15:43.320> idea<00:15:43.680> of<00:15:44.100> using<00:15:44.459> computers<00:15:44.820> as<00:15:45.060> a<00:15:45.300> tool<00:15:45.540> to 00:15:45.949 --> 00:15:45.959 align:start position:0% the idea of using computers as a tool to 00:15:45.959 --> 00:15:48.650 align:start position:0% the idea of using computers as a tool to help<00:15:46.680> organize<00:15:47.160> knowledge<00:15:48.000> and<00:15:48.300> make<00:15:48.420> it<00:15:48.540> more 00:15:48.650 --> 00:15:48.660 align:start position:0% help organize knowledge and make it more 00:15:48.660 --> 00:15:50.030 align:start position:0% help organize knowledge and make it more accessible<00:15:49.019> and<00:15:49.260> sort<00:15:49.440> of<00:15:49.500> do<00:15:49.680> great<00:15:49.860> things 00:15:50.030 --> 00:15:50.040 align:start position:0% accessible and sort of do great things 00:15:50.040 --> 00:15:53.870 align:start position:0% accessible and sort of do great things with<00:15:50.279> it<00:15:50.959> became<00:15:51.959> more<00:15:52.320> appealing<00:15:52.740> maybe<00:15:53.399> than 00:15:53.870 --> 00:15:53.880 align:start position:0% with it became more appealing maybe than 00:15:53.880 --> 00:15:56.870 align:start position:0% with it became more appealing maybe than the<00:15:54.180> toiling<00:15:54.540> at<00:15:54.660> the<00:15:54.779> lab<00:15:54.899> bench<00:15:55.399> and<00:15:56.399> so<00:15:56.639> I 00:15:56.870 --> 00:15:56.880 align:start position:0% the toiling at the lab bench and so I 00:15:56.880 --> 00:15:59.090 align:start position:0% the toiling at the lab bench and so I kind<00:15:57.240> of<00:15:57.300> turned<00:15:57.600> that<00:15:57.720> corner<00:15:58.079> and<00:15:58.380> so<00:15:58.920> I 00:15:59.090 --> 00:15:59.100 align:start position:0% kind of turned that corner and so I 00:15:59.100 --> 00:16:01.430 align:start position:0% kind of turned that corner and so I haven't<00:15:59.339> it's<00:16:00.300> so<00:16:00.480> important<00:16:00.779> to<00:16:00.899> me<00:16:01.019> to<00:16:01.260> stay 00:16:01.430 --> 00:16:01.440 align:start position:0% haven't it's so important to me to stay 00:16:01.440 --> 00:16:03.710 align:start position:0% haven't it's so important to me to stay connected<00:16:01.860> to<00:16:01.980> the<00:16:02.100> sciences<00:16:02.519> and<00:16:02.940> and<00:16:03.180> to<00:16:03.540> the 00:16:03.710 --> 00:16:03.720 align:start position:0% connected to the sciences and and to the 00:16:03.720 --> 00:16:06.050 align:start position:0% connected to the sciences and and to the science<00:16:04.079> that<00:16:04.440> I<00:16:04.620> was<00:16:04.740> doing<00:16:04.920> and<00:16:05.279> I'm<00:16:05.459> and<00:16:05.820> I 00:16:06.050 --> 00:16:06.060 align:start position:0% science that I was doing and I'm and I 00:16:06.060 --> 00:16:07.129 align:start position:0% science that I was doing and I'm and I am 00:16:07.129 --> 00:16:07.139 align:start position:0% am 00:16:07.139 --> 00:16:08.990 align:start position:0% am um<00:16:07.260> in<00:16:07.620> the<00:16:07.740> you<00:16:08.160> know<00:16:08.220> where<00:16:08.399> we<00:16:08.519> are<00:16:08.699> we're 00:16:08.990 --> 00:16:09.000 align:start position:0% um in the you know where we are we're 00:16:09.000 --> 00:16:10.790 align:start position:0% um in the you know where we are we're still<00:16:09.240> thinking<00:16:09.540> very<00:16:09.779> much<00:16:09.959> about<00:16:10.260> the 00:16:10.790 --> 00:16:10.800 align:start position:0% still thinking very much about the 00:16:10.800 --> 00:16:12.889 align:start position:0% still thinking very much about the science<00:16:11.339> aspect<00:16:11.880> of<00:16:11.940> things 00:16:12.889 --> 00:16:12.899 align:start position:0% science aspect of things 00:16:12.899 --> 00:16:15.530 align:start position:0% science aspect of things um otherwise<00:16:13.740> there's<00:16:13.980> no<00:16:14.339> usefulness<00:16:15.180> to<00:16:15.420> it 00:16:15.530 --> 00:16:15.540 align:start position:0% um otherwise there's no usefulness to it 00:16:15.540 --> 00:16:16.910 align:start position:0% um otherwise there's no usefulness to it right<00:16:15.720> because<00:16:16.019> it's<00:16:16.320> not<00:16:16.500> abstract 00:16:16.910 --> 00:16:16.920 align:start position:0% right because it's not abstract 00:16:16.920 --> 00:16:18.290 align:start position:0% right because it's not abstract knowledge<00:16:17.399> like<00:16:17.699> you<00:16:17.820> need<00:16:18.120> to<00:16:18.240> understand 00:16:18.290 --> 00:16:18.300 align:start position:0% knowledge like you need to understand 00:16:18.300 --> 00:16:21.350 align:start position:0% knowledge like you need to understand the<00:16:18.660> domain<00:16:19.019> we<00:16:19.740> need<00:16:19.860> to<00:16:19.980> have<00:16:20.220> them<00:16:20.579> really 00:16:21.350 --> 00:16:21.360 align:start position:0% the domain we need to have them really 00:16:21.360 --> 00:16:23.689 align:start position:0% the domain we need to have them really good<00:16:21.839> domain<00:16:22.260> knowledge<00:16:22.560> I<00:16:22.800> mean<00:16:22.980> we<00:16:23.459> need<00:16:23.579> to 00:16:23.689 --> 00:16:23.699 align:start position:0% good domain knowledge I mean we need to 00:16:23.699 --> 00:16:25.129 align:start position:0% good domain knowledge I mean we need to understand<00:16:23.820> what<00:16:24.120> we're<00:16:24.240> doing<00:16:24.420> or<00:16:24.660> else<00:16:24.779> and 00:16:25.129 --> 00:16:25.139 align:start position:0% understand what we're doing or else and 00:16:25.139 --> 00:16:28.009 align:start position:0% understand what we're doing or else and that's<00:16:25.740> what<00:16:26.040> gives<00:16:26.339> us<00:16:26.639> you<00:16:27.180> know<00:16:27.360> some 00:16:28.009 --> 00:16:28.019 align:start position:0% that's what gives us you know some 00:16:28.019 --> 00:16:29.449 align:start position:0% that's what gives us you know some Advantage 00:16:29.449 --> 00:16:29.459 align:start position:0% Advantage 00:16:29.459 --> 00:16:32.269 align:start position:0% Advantage um<00:16:29.519> is<00:16:29.940> that<00:16:30.120> on<00:16:30.360> the<00:16:30.420> one<00:16:30.540> hand<00:16:30.720> we<00:16:30.959> understand 00:16:32.269 --> 00:16:32.279 align:start position:0% um is that on the one hand we understand 00:16:32.279 --> 00:16:34.250 align:start position:0% um is that on the one hand we understand um how<00:16:32.519> to<00:16:32.579> sort<00:16:32.699> of<00:16:32.820> reduce<00:16:32.940> data<00:16:33.540> and<00:16:33.899> how<00:16:34.079> to 00:16:34.250 --> 00:16:34.260 align:start position:0% um how to sort of reduce data and how to 00:16:34.260 --> 00:16:36.170 align:start position:0% um how to sort of reduce data and how to reduce<00:16:34.380> knowledge<00:16:34.980> and<00:16:35.160> model<00:16:35.579> it<00:16:35.880> in<00:16:36.000> a 00:16:36.170 --> 00:16:36.180 align:start position:0% reduce knowledge and model it in a 00:16:36.180 --> 00:16:37.910 align:start position:0% reduce knowledge and model it in a useful<00:16:36.480> way<00:16:36.720> and<00:16:37.079> it'll<00:16:37.380> allow<00:16:37.560> us<00:16:37.680> to<00:16:37.860> do 00:16:37.910 --> 00:16:37.920 align:start position:0% useful way and it'll allow us to do 00:16:37.920 --> 00:16:39.350 align:start position:0% useful way and it'll allow us to do inference<00:16:38.339> and<00:16:38.459> calculation<00:16:38.880> on<00:16:39.120> the<00:16:39.240> other 00:16:39.350 --> 00:16:39.360 align:start position:0% inference and calculation on the other 00:16:39.360 --> 00:16:41.269 align:start position:0% inference and calculation on the other hand<00:16:39.540> we<00:16:40.199> understand<00:16:40.320> the<00:16:40.680> knowledge<00:16:40.920> itself 00:16:41.269 --> 00:16:41.279 align:start position:0% hand we understand the knowledge itself 00:16:41.279 --> 00:16:44.810 align:start position:0% hand we understand the knowledge itself and<00:16:41.459> the<00:16:41.639> bits<00:16:41.880> and<00:16:42.000> pieces<00:16:42.620> and<00:16:43.620> so<00:16:43.920> uh<00:16:44.579> that 00:16:44.810 --> 00:16:44.820 align:start position:0% and the bits and pieces and so uh that 00:16:44.820 --> 00:16:47.090 align:start position:0% and the bits and pieces and so uh that hopefully<00:16:45.120> helps<00:16:45.480> us<00:16:45.540> not<00:16:45.839> to<00:16:46.079> make<00:16:46.259> silly 00:16:47.090 --> 00:16:47.100 align:start position:0% hopefully helps us not to make silly 00:16:47.100 --> 00:16:50.150 align:start position:0% hopefully helps us not to make silly mistakes<00:16:47.720> and<00:16:48.720> also<00:16:49.019> to<00:16:49.259> uh<00:16:49.860> sort<00:16:50.100> of 00:16:50.150 --> 00:16:50.160 align:start position:0% mistakes and also to uh sort of 00:16:50.160 --> 00:16:54.350 align:start position:0% mistakes and also to uh sort of recognize<00:16:50.839> the<00:16:51.839> opportunities<00:16:52.579> so<00:16:53.579> I'm<00:16:54.120> going 00:16:54.350 --> 00:16:54.360 align:start position:0% recognize the opportunities so I'm going 00:16:54.360 --> 00:16:56.569 align:start position:0% recognize the opportunities so I'm going to<00:16:54.540> kind<00:16:54.720> of<00:16:54.779> come<00:16:55.500> back<00:16:55.680> to<00:16:55.920> this<00:16:56.160> you<00:16:56.519> know 00:16:56.569 --> 00:16:56.579 align:start position:0% to kind of come back to this you know 00:16:56.579 --> 00:16:59.569 align:start position:0% to kind of come back to this you know open<00:16:56.759> source<00:16:57.440> uh<00:16:58.440> Community<00:16:58.740> to<00:16:59.160> fight<00:16:59.339> cancer 00:16:59.569 --> 00:16:59.579 align:start position:0% open source uh Community to fight cancer 00:16:59.579 --> 00:17:01.610 align:start position:0% open source uh Community to fight cancer because<00:16:59.880> I<00:17:00.120> was<00:17:00.300> really<00:17:00.480> you<00:17:01.019> know<00:17:01.139> struck<00:17:01.440> by 00:17:01.610 --> 00:17:01.620 align:start position:0% because I was really you know struck by 00:17:01.620 --> 00:17:04.549 align:start position:0% because I was really you know struck by how<00:17:02.040> much<00:17:02.279> uh<00:17:03.180> opportunity<00:17:03.540> is<00:17:03.839> there<00:17:04.020> and<00:17:04.319> how 00:17:04.549 --> 00:17:04.559 align:start position:0% how much uh opportunity is there and how 00:17:04.559 --> 00:17:07.250 align:start position:0% how much uh opportunity is there and how little<00:17:04.740> is<00:17:05.699> uh<00:17:06.299> of<00:17:06.660> this<00:17:06.900> you<00:17:07.199> know 00:17:07.250 --> 00:17:07.260 align:start position:0% little is uh of this you know 00:17:07.260 --> 00:17:09.049 align:start position:0% little is uh of this you know centralized<00:17:07.980> organization<00:17:08.459> there<00:17:08.760> is<00:17:08.880> a<00:17:09.000> lot 00:17:09.049 --> 00:17:09.059 align:start position:0% centralized organization there is a lot 00:17:09.059 --> 00:17:11.150 align:start position:0% centralized organization there is a lot of<00:17:09.120> organizations<00:17:09.600> trying<00:17:10.319> to<00:17:10.559> unify<00:17:10.980> this 00:17:11.150 --> 00:17:11.160 align:start position:0% of organizations trying to unify this 00:17:11.160 --> 00:17:12.949 align:start position:0% of organizations trying to unify this data<00:17:11.459> but<00:17:11.579> there<00:17:11.699> is<00:17:11.819> so<00:17:11.939> much<00:17:12.240> like<00:17:12.600> it<00:17:12.780> you 00:17:12.949 --> 00:17:12.959 align:start position:0% data but there is so much like it you 00:17:12.959 --> 00:17:14.510 align:start position:0% data but there is so much like it you know<00:17:13.079> from<00:17:13.199> a<00:17:13.319> computer<00:17:13.439> science<00:17:13.860> scientist 00:17:14.510 --> 00:17:14.520 align:start position:0% know from a computer science scientist 00:17:14.520 --> 00:17:16.970 align:start position:0% know from a computer science scientist point<00:17:14.699> of<00:17:14.819> view<00:17:14.939> is<00:17:15.299> extremely<00:17:15.900> fragmented<00:17:16.500> it 00:17:16.970 --> 00:17:16.980 align:start position:0% point of view is extremely fragmented it 00:17:16.980 --> 00:17:19.069 align:start position:0% point of view is extremely fragmented it also<00:17:17.220> seems<00:17:17.520> to<00:17:17.640> me<00:17:17.880> that<00:17:18.540> you<00:17:18.720> know<00:17:18.780> the 00:17:19.069 --> 00:17:19.079 align:start position:0% also seems to me that you know the 00:17:19.079 --> 00:17:20.449 align:start position:0% also seems to me that you know the result<00:17:19.199> of<00:17:19.439> great<00:17:19.559> Sciences<00:17:19.980> people<00:17:20.220> but 00:17:20.449 --> 00:17:20.459 align:start position:0% result of great Sciences people but 00:17:20.459 --> 00:17:22.309 align:start position:0% result of great Sciences people but they're<00:17:20.640> not<00:17:20.819> necessarily<00:17:21.419> Google<00:17:21.959> level 00:17:22.309 --> 00:17:22.319 align:start position:0% they're not necessarily Google level 00:17:22.319 --> 00:17:24.350 align:start position:0% they're not necessarily Google level computer<00:17:22.620> scientists<00:17:23.280> so<00:17:23.520> they<00:17:23.760> because<00:17:23.939> you 00:17:24.350 --> 00:17:24.360 align:start position:0% computer scientists so they because you 00:17:24.360 --> 00:17:25.970 align:start position:0% computer scientists so they because you know<00:17:24.480> they<00:17:24.660> devote<00:17:25.260> their<00:17:25.380> efforts<00:17:25.740> into 00:17:25.970 --> 00:17:25.980 align:start position:0% know they devote their efforts into 00:17:25.980 --> 00:17:27.530 align:start position:0% know they devote their efforts into discovering<00:17:26.339> the<00:17:26.520> primary<00:17:26.819> knowledge<00:17:27.179> and 00:17:27.530 --> 00:17:27.540 align:start position:0% discovering the primary knowledge and 00:17:27.540 --> 00:17:28.909 align:start position:0% discovering the primary knowledge and there<00:17:27.720> is<00:17:27.839> not<00:17:27.959> enough<00:17:28.079> folks<00:17:28.380> like<00:17:28.500> you<00:17:28.740> who 00:17:28.909 --> 00:17:28.919 align:start position:0% there is not enough folks like you who 00:17:28.919 --> 00:17:31.669 align:start position:0% there is not enough folks like you who you<00:17:29.220> know<00:17:29.280> piece<00:17:29.640> it<00:17:29.760> together<00:17:29.940> yet<00:17:30.840> right<00:17:31.320> and 00:17:31.669 --> 00:17:31.679 align:start position:0% you know piece it together yet right and 00:17:31.679 --> 00:17:34.190 align:start position:0% you know piece it together yet right and so<00:17:31.919> uh<00:17:32.700> so<00:17:33.120> I'm<00:17:33.419> wondering<00:17:33.780> is<00:17:33.900> it<00:17:34.140> even 00:17:34.190 --> 00:17:34.200 align:start position:0% so uh so I'm wondering is it even 00:17:34.200 --> 00:17:36.049 align:start position:0% so uh so I'm wondering is it even feasible<00:17:34.799> is<00:17:35.100> it<00:17:35.220> possible<00:17:35.520> for<00:17:35.760> a<00:17:35.880> computer 00:17:36.049 --> 00:17:36.059 align:start position:0% feasible is it possible for a computer 00:17:36.059 --> 00:17:38.450 align:start position:0% feasible is it possible for a computer scientists<00:17:36.660> like<00:17:36.900> me<00:17:37.080> who<00:17:37.320> does<00:17:37.500> not<00:17:37.620> have<00:17:37.919> a 00:17:38.450 --> 00:17:38.460 align:start position:0% scientists like me who does not have a 00:17:38.460 --> 00:17:40.549 align:start position:0% scientists like me who does not have a formal<00:17:38.940> you<00:17:39.360> know<00:17:39.539> molecular<00:17:40.140> biology 00:17:40.549 --> 00:17:40.559 align:start position:0% formal you know molecular biology 00:17:40.559 --> 00:17:42.230 align:start position:0% formal you know molecular biology training 00:17:42.230 --> 00:17:42.240 align:start position:0% training 00:17:42.240 --> 00:17:43.789 align:start position:0% training um<00:17:42.360> but<00:17:42.660> is<00:17:42.840> curious<00:17:43.200> and<00:17:43.440> kind<00:17:43.620> of<00:17:43.679> can 00:17:43.789 --> 00:17:43.799 align:start position:0% um but is curious and kind of can 00:17:43.799 --> 00:17:45.710 align:start position:0% um but is curious and kind of can understand<00:17:43.980> almost<00:17:44.460> everything<00:17:44.700> if<00:17:45.419> you<00:17:45.600> read 00:17:45.710 --> 00:17:45.720 align:start position:0% understand almost everything if you read 00:17:45.720 --> 00:17:47.029 align:start position:0% understand almost everything if you read it<00:17:45.900> many<00:17:46.080> times 00:17:47.029 --> 00:17:47.039 align:start position:0% it many times 00:17:47.039 --> 00:17:49.310 align:start position:0% it many times uh<00:17:47.700> presumably 00:17:49.310 --> 00:17:49.320 align:start position:0% uh presumably 00:17:49.320 --> 00:17:52.250 align:start position:0% uh presumably um<00:17:49.440> Can<00:17:50.039> can<00:17:50.400> we<00:17:50.880> can<00:17:51.360> we<00:17:51.660> present<00:17:52.020> the 00:17:52.250 --> 00:17:52.260 align:start position:0% um Can can we can we present the 00:17:52.260 --> 00:17:55.210 align:start position:0% um Can can we can we present the problems<00:17:52.919> of<00:17:53.640> fighting<00:17:54.179> cancer 00:17:55.210 --> 00:17:55.220 align:start position:0% problems of fighting cancer 00:17:55.220 --> 00:17:58.789 align:start position:0% problems of fighting cancer indigestible<00:17:56.240> pieces<00:17:57.240> can<00:17:57.840> we<00:17:58.080> decompose<00:17:58.500> a 00:17:58.789 --> 00:17:58.799 align:start position:0% indigestible pieces can we decompose a 00:17:58.799 --> 00:18:00.350 align:start position:0% indigestible pieces can we decompose a problem<00:17:58.980> and<00:17:59.340> can<00:17:59.580> we<00:17:59.700> also<00:17:59.940> you<00:18:00.059> know<00:18:00.179> take 00:18:00.350 --> 00:18:00.360 align:start position:0% problem and can we also you know take 00:18:00.360 --> 00:18:02.150 align:start position:0% problem and can we also you know take all<00:18:00.539> this<00:18:00.660> knowledge<00:18:00.960> social<00:18:01.200> mapping<00:18:01.740> and 00:18:02.150 --> 00:18:02.160 align:start position:0% all this knowledge social mapping and 00:18:02.160 --> 00:18:03.590 align:start position:0% all this knowledge social mapping and present<00:18:02.460> a<00:18:02.640> computer<00:18:02.820> scientists<00:18:03.419> and 00:18:03.590 --> 00:18:03.600 align:start position:0% present a computer scientists and 00:18:03.600 --> 00:18:05.750 align:start position:0% present a computer scientists and digestible<00:18:04.080> pieces<00:18:04.500> and<00:18:04.740> kind<00:18:04.980> of<00:18:05.039> map<00:18:05.520> a 00:18:05.750 --> 00:18:05.760 align:start position:0% digestible pieces and kind of map a 00:18:05.760 --> 00:18:07.909 align:start position:0% digestible pieces and kind of map a little<00:18:05.880> path<00:18:06.120> to<00:18:06.419> them<00:18:06.600> so<00:18:06.780> somebody<00:18:07.320> on<00:18:07.740> over 00:18:07.909 --> 00:18:07.919 align:start position:0% little path to them so somebody on over 00:18:07.919 --> 00:18:09.590 align:start position:0% little path to them so somebody on over over<00:18:08.160> a<00:18:08.340> course<00:18:08.400> of<00:18:08.580> time<00:18:08.760> a<00:18:09.000> community<00:18:09.120> can 00:18:09.590 --> 00:18:09.600 align:start position:0% over a course of time a community can 00:18:09.600 --> 00:18:12.590 align:start position:0% over a course of time a community can kind<00:18:09.780> of<00:18:09.900> make<00:18:10.740> different<00:18:11.280> uh<00:18:11.880> efforts<00:18:12.419> and 00:18:12.590 --> 00:18:12.600 align:start position:0% kind of make different uh efforts and 00:18:12.600 --> 00:18:15.470 align:start position:0% kind of make different uh efforts and kind<00:18:12.840> of<00:18:12.960> together<00:18:13.700> uh<00:18:14.700> write<00:18:14.940> a<00:18:15.120> lot<00:18:15.179> of<00:18:15.299> good 00:18:15.470 --> 00:18:15.480 align:start position:0% kind of together uh write a lot of good 00:18:15.480 --> 00:18:17.690 align:start position:0% kind of together uh write a lot of good call<00:18:15.720> to<00:18:16.080> eventually<00:18:16.440> you<00:18:17.160> know<00:18:17.280> defeat 00:18:17.690 --> 00:18:17.700 align:start position:0% call to eventually you know defeat 00:18:17.700 --> 00:18:20.150 align:start position:0% call to eventually you know defeat cancer<00:18:17.880> through<00:18:18.539> Community<00:18:19.260> you<00:18:20.100> know 00:18:20.150 --> 00:18:20.160 align:start position:0% cancer through Community you know 00:18:20.160 --> 00:18:22.310 align:start position:0% cancer through Community you know crowdsource<00:18:20.820> programming<00:18:21.240> is<00:18:21.419> it<00:18:21.720> is<00:18:22.020> it<00:18:22.200> a 00:18:22.310 --> 00:18:22.320 align:start position:0% crowdsource programming is it is it a 00:18:22.320 --> 00:18:26.210 align:start position:0% crowdsource programming is it is it a possible<00:18:22.679> possible<00:18:23.640> activity<00:18:24.480> uh<00:18:25.320> right<00:18:25.740> so<00:18:26.160> I 00:18:26.210 --> 00:18:26.220 align:start position:0% possible possible activity uh right so I 00:18:26.220 --> 00:18:27.890 align:start position:0% possible possible activity uh right so I mean<00:18:26.400> I<00:18:26.520> I<00:18:26.640> think<00:18:26.820> when<00:18:27.000> we<00:18:27.179> when<00:18:27.299> we<00:18:27.480> use<00:18:27.660> terms 00:18:27.890 --> 00:18:27.900 align:start position:0% mean I I think when we when we use terms 00:18:27.900 --> 00:18:30.049 align:start position:0% mean I I think when we when we use terms like<00:18:28.020> defeat<00:18:28.440> cancer<00:18:28.620> we<00:18:28.980> kind<00:18:29.160> of<00:18:29.220> we're<00:18:29.400> at<00:18:29.820> a 00:18:30.049 --> 00:18:30.059 align:start position:0% like defeat cancer we kind of we're at a 00:18:30.059 --> 00:18:32.029 align:start position:0% like defeat cancer we kind of we're at a very<00:18:30.120> high<00:18:30.480> level<00:18:30.660> and<00:18:31.080> and 00:18:32.029 --> 00:18:32.039 align:start position:0% very high level and and 00:18:32.039 --> 00:18:33.650 align:start position:0% very high level and and um<00:18:32.100> you<00:18:32.340> know<00:18:32.400> sometimes<00:18:32.700> that<00:18:32.880> can 00:18:33.650 --> 00:18:33.660 align:start position:0% um you know sometimes that can 00:18:33.660 --> 00:18:36.230 align:start position:0% um you know sometimes that can you<00:18:34.200> know<00:18:34.320> but<00:18:34.799> but<00:18:34.980> there<00:18:35.220> are<00:18:35.340> lots<00:18:35.700> of<00:18:35.760> uh 00:18:36.230 --> 00:18:36.240 align:start position:0% you know but but there are lots of uh 00:18:36.240 --> 00:18:38.830 align:start position:0% you know but but there are lots of uh foreign 00:18:38.830 --> 00:18:38.840 align:start position:0% 00:18:38.840 --> 00:18:40.610 align:start position:0% I<00:18:39.840> mean<00:18:39.900> you<00:18:40.020> know<00:18:40.140> so<00:18:40.260> one<00:18:40.380> of<00:18:40.500> the<00:18:40.559> things 00:18:40.610 --> 00:18:40.620 align:start position:0% I mean you know so one of the things 00:18:40.620 --> 00:18:41.810 align:start position:0% I mean you know so one of the things people<00:18:40.799> are<00:18:41.039> really<00:18:41.220> interested<00:18:41.580> in<00:18:41.640> doing 00:18:41.810 --> 00:18:41.820 align:start position:0% people are really interested in doing 00:18:41.820 --> 00:18:44.690 align:start position:0% people are really interested in doing now<00:18:42.059> is<00:18:42.600> uh<00:18:43.500> finding<00:18:43.860> ways<00:18:44.160> to<00:18:44.400> leverage 00:18:44.690 --> 00:18:44.700 align:start position:0% now is uh finding ways to leverage 00:18:44.700 --> 00:18:47.570 align:start position:0% now is uh finding ways to leverage genomic<00:18:45.480> data<00:18:45.720> genetic<00:18:46.200> data<00:18:46.500> uh<00:18:47.280> to 00:18:47.570 --> 00:18:47.580 align:start position:0% genomic data genetic data uh to 00:18:47.580 --> 00:18:49.669 align:start position:0% genomic data genetic data uh to determine<00:18:48.059> what<00:18:48.660> the<00:18:48.900> best<00:18:49.080> what<00:18:49.380> the<00:18:49.559> most 00:18:49.669 --> 00:18:49.679 align:start position:0% determine what the best what the most 00:18:49.679 --> 00:18:52.130 align:start position:0% determine what the best what the most likely<00:18:50.160> uh<00:18:50.880> good<00:18:51.360> treatments<00:18:51.780> are<00:18:51.900> for 00:18:52.130 --> 00:18:52.140 align:start position:0% likely uh good treatments are for 00:18:52.140 --> 00:18:53.870 align:start position:0% likely uh good treatments are for individual<00:18:52.559> patients<00:18:52.919> yes<00:18:53.160> right<00:18:53.400> so<00:18:53.640> we<00:18:53.760> talk 00:18:53.870 --> 00:18:53.880 align:start position:0% individual patients yes right so we talk 00:18:53.880 --> 00:18:55.370 align:start position:0% individual patients yes right so we talk about<00:18:54.000> personalized<00:18:54.600> medicine<00:18:54.780> that's<00:18:55.140> a<00:18:55.320> lot 00:18:55.370 --> 00:18:55.380 align:start position:0% about personalized medicine that's a lot 00:18:55.380 --> 00:18:57.169 align:start position:0% about personalized medicine that's a lot of<00:18:55.500> what<00:18:55.620> people<00:18:55.740> are<00:18:55.919> talking<00:18:56.100> about<00:18:56.280> yes 00:18:57.169 --> 00:18:57.179 align:start position:0% of what people are talking about yes 00:18:57.179 --> 00:18:58.850 align:start position:0% of what people are talking about yes um<00:18:57.240> so<00:18:57.600> in<00:18:57.720> order<00:18:57.900> to<00:18:58.020> do<00:18:58.200> that<00:18:58.320> we<00:18:58.620> basically 00:18:58.850 --> 00:18:58.860 align:start position:0% um so in order to do that we basically 00:18:58.860 --> 00:19:00.049 align:start position:0% um so in order to do that we basically want<00:18:59.039> to<00:18:59.160> be<00:18:59.220> able<00:18:59.280> to<00:18:59.400> take<00:18:59.580> advantage<00:18:59.940> of 00:19:00.049 --> 00:19:00.059 align:start position:0% want to be able to take advantage of 00:19:00.059 --> 00:19:02.049 align:start position:0% want to be able to take advantage of everything<00:19:00.539> that's<00:19:00.780> come<00:19:01.020> before 00:19:02.049 --> 00:19:02.059 align:start position:0% everything that's come before 00:19:02.059 --> 00:19:05.690 align:start position:0% everything that's come before has<00:19:03.059> this<00:19:03.660> variant<00:19:04.080> been<00:19:04.320> seen<00:19:04.620> before<00:19:04.860> if<00:19:05.520> it 00:19:05.690 --> 00:19:05.700 align:start position:0% has this variant been seen before if it 00:19:05.700 --> 00:19:07.190 align:start position:0% has this variant been seen before if it hasn't<00:19:05.880> been<00:19:06.000> seen<00:19:06.179> before<00:19:06.360> can<00:19:06.720> we<00:19:06.840> infer 00:19:07.190 --> 00:19:07.200 align:start position:0% hasn't been seen before can we infer 00:19:07.200 --> 00:19:09.230 align:start position:0% hasn't been seen before can we infer things<00:19:07.440> about<00:19:07.620> it<00:19:07.860> based<00:19:08.220> on<00:19:08.280> where<00:19:08.580> it<00:19:08.760> is<00:19:08.940> or 00:19:09.230 --> 00:19:09.240 align:start position:0% things about it based on where it is or 00:19:09.240 --> 00:19:12.830 align:start position:0% things about it based on where it is or or<00:19:09.600> other<00:19:10.200> things<00:19:10.380> that<00:19:10.620> we<00:19:10.740> know<00:19:10.919> so 00:19:12.830 --> 00:19:12.840 align:start position:0% or other things that we know so 00:19:12.840 --> 00:19:14.690 align:start position:0% or other things that we know so um I<00:19:13.380> mean<00:19:13.500> there's<00:19:13.620> a<00:19:13.799> few<00:19:13.919> things<00:19:14.160> that 00:19:14.690 --> 00:19:14.700 align:start position:0% um I mean there's a few things that 00:19:14.700 --> 00:19:17.390 align:start position:0% um I mean there's a few things that would<00:19:14.820> that<00:19:15.000> would<00:19:15.179> help<00:19:15.360> one<00:19:16.799> um<00:19:16.919> and<00:19:17.280> and 00:19:17.390 --> 00:19:17.400 align:start position:0% would that would help one um and and 00:19:17.400 --> 00:19:20.150 align:start position:0% would that would help one um and and this<00:19:17.940> is<00:19:18.120> an<00:19:18.299> ongoing<00:19:18.840> Challenge<00:19:19.140> and<00:19:19.620> it's<00:19:19.980> a 00:19:20.150 --> 00:19:20.160 align:start position:0% this is an ongoing Challenge and it's a 00:19:20.160 --> 00:19:21.250 align:start position:0% this is an ongoing Challenge and it's a moving<00:19:20.400> Target 00:19:21.250 --> 00:19:21.260 align:start position:0% moving Target 00:19:21.260 --> 00:19:24.350 align:start position:0% moving Target over<00:19:22.260> time<00:19:22.620> we've 00:19:24.350 --> 00:19:24.360 align:start position:0% over time we've 00:19:24.360 --> 00:19:27.770 align:start position:0% over time we've we<00:19:25.080> realize<00:19:25.559> and<00:19:25.919> and<00:19:26.100> we<00:19:26.400> when<00:19:27.000> I<00:19:27.179> say<00:19:27.299> we<00:19:27.600> not 00:19:27.770 --> 00:19:27.780 align:start position:0% we realize and and we when I say we not 00:19:27.780 --> 00:19:29.330 align:start position:0% we realize and and we when I say we not the<00:19:27.900> company<00:19:28.020> but<00:19:28.260> the<00:19:28.440> community<00:19:28.559> realizes 00:19:29.330 --> 00:19:29.340 align:start position:0% the company but the community realizes 00:19:29.340 --> 00:19:33.470 align:start position:0% the company but the community realizes that<00:19:30.380> uh<00:19:31.380> there<00:19:31.919> might<00:19:32.100> be<00:19:32.280> additional<00:19:32.940> pieces 00:19:33.470 --> 00:19:33.480 align:start position:0% that uh there might be additional pieces 00:19:33.480 --> 00:19:35.930 align:start position:0% that uh there might be additional pieces of<00:19:33.720> information<00:19:34.039> about<00:19:35.039> a<00:19:35.280> given<00:19:35.520> observation 00:19:35.930 --> 00:19:35.940 align:start position:0% of information about a given observation 00:19:35.940 --> 00:19:37.669 align:start position:0% of information about a given observation that<00:19:36.240> are<00:19:36.360> important<00:19:36.720> for<00:19:36.960> us<00:19:37.020> to<00:19:37.260> be<00:19:37.380> able<00:19:37.500> to 00:19:37.669 --> 00:19:37.679 align:start position:0% that are important for us to be able to 00:19:37.679 --> 00:19:39.529 align:start position:0% that are important for us to be able to take<00:19:37.799> full<00:19:38.039> advantage<00:19:38.280> of<00:19:38.400> it<00:19:38.700> but<00:19:39.240> of<00:19:39.419> course 00:19:39.529 --> 00:19:39.539 align:start position:0% take full advantage of it but of course 00:19:39.539 --> 00:19:41.510 align:start position:0% take full advantage of it but of course you<00:19:40.080> know<00:19:40.140> if<00:19:40.260> that<00:19:40.440> happens 00:19:41.510 --> 00:19:41.520 align:start position:0% you know if that happens 00:19:41.520 --> 00:19:43.549 align:start position:0% you know if that happens in<00:19:42.059> some<00:19:42.240> year 00:19:43.549 --> 00:19:43.559 align:start position:0% in some year 00:19:43.559 --> 00:19:46.130 align:start position:0% in some year the<00:19:44.460> years<00:19:44.820> you<00:19:45.240> know<00:19:45.299> before<00:19:45.539> that<00:19:45.840> you<00:19:46.080> know 00:19:46.130 --> 00:19:46.140 align:start position:0% the years you know before that you know 00:19:46.140 --> 00:19:47.450 align:start position:0% the years you know before that you know when<00:19:46.260> people<00:19:46.500> were<00:19:46.679> collecting<00:19:47.100> all<00:19:47.280> that 00:19:47.450 --> 00:19:47.460 align:start position:0% when people were collecting all that 00:19:47.460 --> 00:19:51.049 align:start position:0% when people were collecting all that data<00:19:47.760> might<00:19:48.660> be<00:19:48.840> missing<00:19:49.260> those<00:19:49.799> pieces 00:19:51.049 --> 00:19:51.059 align:start position:0% data might be missing those pieces 00:19:51.059 --> 00:19:51.830 align:start position:0% data might be missing those pieces um 00:19:51.830 --> 00:19:51.840 align:start position:0% um 00:19:51.840 --> 00:19:55.730 align:start position:0% um so<00:19:52.679> there<00:19:53.280> is<00:19:53.400> a<00:19:53.640> certain<00:19:53.820> I<00:19:54.380> think<00:19:55.380> it'll<00:19:55.620> be 00:19:55.730 --> 00:19:55.740 align:start position:0% so there is a certain I think it'll be 00:19:55.740 --> 00:19:59.750 align:start position:0% so there is a certain I think it'll be hard<00:19:55.919> to<00:19:56.220> make<00:19:56.580> a<00:19:56.880> a<00:19:57.600> single<00:19:58.020> unified<00:19:58.860> sort<00:19:59.700> of 00:19:59.750 --> 00:19:59.760 align:start position:0% hard to make a a single unified sort of 00:19:59.760 --> 00:20:01.730 align:start position:0% hard to make a a single unified sort of data<00:20:00.059> format<00:20:00.360> even<00:20:00.840> if<00:20:01.080> you 00:20:01.730 --> 00:20:01.740 align:start position:0% data format even if you 00:20:01.740 --> 00:20:04.610 align:start position:0% data format even if you which<00:20:02.160> would<00:20:02.400> be<00:20:02.520> great<00:20:03.000> right<00:20:03.840> I<00:20:04.200> mean<00:20:04.320> so<00:20:04.440> one 00:20:04.610 --> 00:20:04.620 align:start position:0% which would be great right I mean so one 00:20:04.620 --> 00:20:06.950 align:start position:0% which would be great right I mean so one if<00:20:04.860> we<00:20:04.980> had<00:20:05.100> a<00:20:05.220> public<00:20:05.400> database<00:20:05.880> of<00:20:06.600> all<00:20:06.780> of 00:20:06.950 --> 00:20:06.960 align:start position:0% if we had a public database of all of 00:20:06.960 --> 00:20:09.169 align:start position:0% if we had a public database of all of the<00:20:07.140> relevant<00:20:07.500> observations 00:20:09.169 --> 00:20:09.179 align:start position:0% the relevant observations 00:20:09.179 --> 00:20:10.970 align:start position:0% the relevant observations um<00:20:09.240> that<00:20:09.780> would<00:20:09.900> be<00:20:10.080> a<00:20:10.260> huge<00:20:10.440> step<00:20:10.620> in<00:20:10.799> the 00:20:10.970 --> 00:20:10.980 align:start position:0% um that would be a huge step in the 00:20:10.980 --> 00:20:12.710 align:start position:0% um that would be a huge step in the right<00:20:11.100> direction<00:20:11.280> but<00:20:12.059> of<00:20:12.179> course<00:20:12.299> there's<00:20:12.480> a 00:20:12.710 --> 00:20:12.720 align:start position:0% right direction but of course there's a 00:20:12.720 --> 00:20:13.909 align:start position:0% right direction but of course there's a challenge<00:20:12.840> in<00:20:13.140> creating<00:20:13.440> such<00:20:13.620> a<00:20:13.799> thing 00:20:13.909 --> 00:20:13.919 align:start position:0% challenge in creating such a thing 00:20:13.919 --> 00:20:16.130 align:start position:0% challenge in creating such a thing because<00:20:14.160> we<00:20:14.460> don't<00:20:14.580> actually<00:20:14.760> know<00:20:15.179> all<00:20:15.960> of 00:20:16.130 --> 00:20:16.140 align:start position:0% because we don't actually know all of 00:20:16.140 --> 00:20:18.830 align:start position:0% because we don't actually know all of the<00:20:16.500> details<00:20:17.460> what<00:20:17.760> are<00:20:17.940> the<00:20:18.059> kinds<00:20:18.539> of<00:20:18.600> detail 00:20:18.830 --> 00:20:18.840 align:start position:0% the details what are the kinds of detail 00:20:18.840 --> 00:20:19.850 align:start position:0% the details what are the kinds of detail what<00:20:19.020> are<00:20:19.140> the<00:20:19.200> fields<00:20:19.440> I<00:20:19.559> don't<00:20:19.679> know<00:20:19.740> the 00:20:19.850 --> 00:20:19.860 align:start position:0% what are the fields I don't know the 00:20:19.860 --> 00:20:21.409 align:start position:0% what are the fields I don't know the kinds<00:20:20.039> of<00:20:20.039> details<00:20:20.460> that<00:20:20.580> we<00:20:20.700> want<00:20:20.880> to<00:20:21.059> we<00:20:21.299> want 00:20:21.409 --> 00:20:21.419 align:start position:0% kinds of details that we want to we want 00:20:21.419 --> 00:20:23.270 align:start position:0% kinds of details that we want to we want to<00:20:21.600> capture<00:20:21.840> and<00:20:22.679> that's<00:20:22.799> probably<00:20:23.039> going<00:20:23.160> to 00:20:23.270 --> 00:20:23.280 align:start position:0% to capture and that's probably going to 00:20:23.280 --> 00:20:24.710 align:start position:0% to capture and that's probably going to change<00:20:23.400> over<00:20:23.580> time<00:20:23.820> so<00:20:24.059> you<00:20:24.240> need<00:20:24.360> a<00:20:24.539> system 00:20:24.710 --> 00:20:24.720 align:start position:0% change over time so you need a system 00:20:24.720 --> 00:20:28.070 align:start position:0% change over time so you need a system that<00:20:25.440> allows<00:20:25.740> for<00:20:25.860> that<00:20:26.039> flexibility<00:20:26.900> and<00:20:27.900> you 00:20:28.070 --> 00:20:28.080 align:start position:0% that allows for that flexibility and you 00:20:28.080 --> 00:20:32.690 align:start position:0% that allows for that flexibility and you need<00:20:28.400> approaches<00:20:29.400> that<00:20:30.380> are<00:20:31.380> robust<00:20:31.740> to<00:20:32.460> those 00:20:32.690 --> 00:20:32.700 align:start position:0% need approaches that are robust to those 00:20:32.700 --> 00:20:34.669 align:start position:0% need approaches that are robust to those kinds<00:20:33.179> of<00:20:33.360> variations<00:20:33.780> like<00:20:34.200> all<00:20:34.380> right<00:20:34.500> so 00:20:34.669 --> 00:20:34.679 align:start position:0% kinds of variations like all right so 00:20:34.679 --> 00:20:36.350 align:start position:0% kinds of variations like all right so some<00:20:34.860> data<00:20:35.220> has<00:20:35.460> some<00:20:35.760> detail<00:20:36.059> and<00:20:36.179> some 00:20:36.350 --> 00:20:36.360 align:start position:0% some data has some detail and some 00:20:36.360 --> 00:20:37.789 align:start position:0% some data has some detail and some doesn't<00:20:36.600> but<00:20:36.840> we<00:20:36.960> can<00:20:37.080> we<00:20:37.260> still<00:20:37.440> need<00:20:37.559> to<00:20:37.679> be 00:20:37.789 --> 00:20:37.799 align:start position:0% doesn't but we can we still need to be 00:20:37.799 --> 00:20:40.490 align:start position:0% doesn't but we can we still need to be able<00:20:37.860> to<00:20:37.980> do<00:20:38.100> something<00:20:38.220> with<00:20:38.520> it<00:20:38.640> yes<00:20:39.059> uh<00:20:39.660> so 00:20:40.490 --> 00:20:40.500 align:start position:0% able to do something with it yes uh so 00:20:40.500 --> 00:20:42.590 align:start position:0% able to do something with it yes uh so there's<00:20:41.039> there's<00:20:41.280> those<00:20:41.520> kinds<00:20:41.820> of<00:20:41.880> things<00:20:42.059> I 00:20:42.590 --> 00:20:42.600 align:start position:0% there's there's those kinds of things I 00:20:42.600 --> 00:20:43.850 align:start position:0% there's there's those kinds of things I think<00:20:42.720> that 00:20:43.850 --> 00:20:43.860 align:start position:0% think that 00:20:43.860 --> 00:20:45.289 align:start position:0% think that um it's<00:20:44.280> interesting<00:20:44.640> because<00:20:44.760> in<00:20:45.000> a<00:20:45.179> group 00:20:45.289 --> 00:20:45.299 align:start position:0% um it's interesting because in a group 00:20:45.299 --> 00:20:48.350 align:start position:0% um it's interesting because in a group like<00:20:45.539> ours<00:20:46.340> uh<00:20:47.340> you<00:20:47.580> know<00:20:47.640> we<00:20:47.880> have<00:20:48.000> this 00:20:48.350 --> 00:20:48.360 align:start position:0% like ours uh you know we have this 00:20:48.360 --> 00:20:52.070 align:start position:0% like ours uh you know we have this overlap<00:20:48.900> of<00:20:49.200> expertise<00:20:50.000> between<00:20:51.080> the 00:20:52.070 --> 00:20:52.080 align:start position:0% overlap of expertise between the 00:20:52.080 --> 00:20:55.930 align:start position:0% overlap of expertise between the specific<00:20:52.440> uh<00:20:53.160> genomic<00:20:53.820> and<00:20:54.179> and<00:20:54.799> biological 00:20:55.930 --> 00:20:55.940 align:start position:0% specific uh genomic and and biological 00:20:55.940 --> 00:20:59.029 align:start position:0% specific uh genomic and and biological domain<00:20:56.940> knowledge<00:20:57.360> and<00:20:58.140> an<00:20:58.380> understanding<00:20:58.799> of 00:20:59.029 --> 00:20:59.039 align:start position:0% domain knowledge and an understanding of 00:20:59.039 --> 00:21:01.730 align:start position:0% domain knowledge and an understanding of data<00:20:59.400> reduction<00:20:59.700> and<00:20:59.940> data<00:21:00.299> organization 00:21:01.730 --> 00:21:01.740 align:start position:0% data reduction and data organization 00:21:01.740 --> 00:21:04.070 align:start position:0% data reduction and data organization but<00:21:02.340> we're<00:21:02.580> not<00:21:02.820> uh<00:21:03.240> you<00:21:03.419> know<00:21:03.539> world-class 00:21:04.070 --> 00:21:04.080 align:start position:0% but we're not uh you know world-class 00:21:04.080 --> 00:21:08.450 align:start position:0% but we're not uh you know world-class experts<00:21:04.620> on<00:21:05.400> either<00:21:05.580> side<00:21:05.820> right<00:21:06.780> so 00:21:08.450 --> 00:21:08.460 align:start position:0% experts on either side right so 00:21:08.460 --> 00:21:10.730 align:start position:0% experts on either side right so um it<00:21:09.120> would<00:21:09.240> certainly<00:21:09.539> be<00:21:09.720> interesting<00:21:10.140> uh 00:21:10.730 --> 00:21:10.740 align:start position:0% um it would certainly be interesting uh 00:21:10.740 --> 00:21:12.230 align:start position:0% um it would certainly be interesting uh for<00:21:10.919> there<00:21:11.039> to<00:21:11.220> be<00:21:11.340> communication<00:21:11.820> between 00:21:12.230 --> 00:21:12.240 align:start position:0% for there to be communication between 00:21:12.240 --> 00:21:14.450 align:start position:0% for there to be communication between groups<00:21:13.080> like<00:21:13.200> ours<00:21:13.620> that<00:21:13.799> are<00:21:13.919> so<00:21:14.039> and<00:21:14.280> there 00:21:14.450 --> 00:21:14.460 align:start position:0% groups like ours that are so and there 00:21:14.460 --> 00:21:15.650 align:start position:0% groups like ours that are so and there are<00:21:14.580> other<00:21:14.700> groups<00:21:15.059> that<00:21:15.299> are<00:21:15.480> working 00:21:15.650 --> 00:21:15.660 align:start position:0% are other groups that are working 00:21:15.660 --> 00:21:17.390 align:start position:0% are other groups that are working developing<00:21:16.200> biological<00:21:16.679> ontologies<00:21:17.220> or 00:21:17.390 --> 00:21:17.400 align:start position:0% developing biological ontologies or 00:21:17.400 --> 00:21:20.930 align:start position:0% developing biological ontologies or trying<00:21:17.580> to<00:21:17.760> do<00:21:17.940> things<00:21:18.179> like<00:21:19.080> this<00:21:19.640> and<00:21:20.640> people 00:21:20.930 --> 00:21:20.940 align:start position:0% trying to do things like this and people 00:21:20.940 --> 00:21:22.789 align:start position:0% trying to do things like this and people who<00:21:21.480> are 00:21:22.789 --> 00:21:22.799 align:start position:0% who are 00:21:22.799 --> 00:21:23.450 align:start position:0% who are um 00:21:23.450 --> 00:21:23.460 align:start position:0% um 00:21:23.460 --> 00:21:27.529 align:start position:0% um really<00:21:24.179> like<00:21:24.419> 100<00:21:24.679> data<00:21:25.679> scientists<00:21:26.360> may<00:21:27.360> be 00:21:27.529 --> 00:21:27.539 align:start position:0% really like 100 data scientists may be 00:21:27.539 --> 00:21:30.049 align:start position:0% really like 100 data scientists may be thinking<00:21:27.840> about<00:21:28.020> some<00:21:28.380> of<00:21:28.500> these<00:21:28.740> problems<00:21:29.700> um 00:21:30.049 --> 00:21:30.059 align:start position:0% thinking about some of these problems um 00:21:30.059 --> 00:21:32.870 align:start position:0% thinking about some of these problems um in<00:21:30.659> a<00:21:30.900> more<00:21:31.020> focused<00:21:31.620> way 00:21:32.870 --> 00:21:32.880 align:start position:0% in a more focused way 00:21:32.880 --> 00:21:33.590 align:start position:0% in a more focused way um 00:21:33.590 --> 00:21:33.600 align:start position:0% um 00:21:33.600 --> 00:21:35.750 align:start position:0% um and<00:21:34.679> um<00:21:34.679> and<00:21:35.280> sort<00:21:35.400> of<00:21:35.520> have<00:21:35.580> that 00:21:35.750 --> 00:21:35.760 align:start position:0% and um and sort of have that 00:21:35.760 --> 00:21:37.250 align:start position:0% and um and sort of have that conversation<00:21:36.179> because<00:21:36.419> yes<00:21:36.659> I<00:21:36.900> think<00:21:37.020> that 00:21:37.250 --> 00:21:37.260 align:start position:0% conversation because yes I think that 00:21:37.260 --> 00:21:39.049 align:start position:0% conversation because yes I think that there<00:21:37.440> probably<00:21:37.679> are 00:21:39.049 --> 00:21:39.059 align:start position:0% there probably are 00:21:39.059 --> 00:21:39.649 align:start position:0% there probably are um 00:21:39.649 --> 00:21:39.659 align:start position:0% um 00:21:39.659 --> 00:21:41.690 align:start position:0% um pieces<00:21:40.380> that<00:21:40.559> we<00:21:40.679> could<00:21:40.799> break<00:21:40.980> off<00:21:41.220> of<00:21:41.400> these 00:21:41.690 --> 00:21:41.700 align:start position:0% pieces that we could break off of these 00:21:41.700 --> 00:21:42.669 align:start position:0% pieces that we could break off of these problems 00:21:42.669 --> 00:21:42.679 align:start position:0% problems 00:21:42.679 --> 00:21:44.990 align:start position:0% problems and<00:21:43.679> have<00:21:43.799> the<00:21:43.980> community<00:21:44.159> sort<00:21:44.580> of<00:21:44.640> turning 00:21:44.990 --> 00:21:45.000 align:start position:0% and have the community sort of turning 00:21:45.000 --> 00:21:46.310 align:start position:0% and have the community sort of turning on<00:21:45.120> them<00:21:45.240> and<00:21:45.360> I<00:21:45.480> think<00:21:45.600> that<00:21:45.720> happens<00:21:45.900> to<00:21:46.140> some 00:21:46.310 --> 00:21:46.320 align:start position:0% on them and I think that happens to some 00:21:46.320 --> 00:21:47.870 align:start position:0% on them and I think that happens to some extent<00:21:46.679> but 00:21:47.870 --> 00:21:47.880 align:start position:0% extent but 00:21:47.880 --> 00:21:49.669 align:start position:0% extent but um<00:21:47.940> there<00:21:48.179> could<00:21:48.360> certainly<00:21:48.539> be<00:21:48.659> more<00:21:48.840> yeah<00:21:49.440> so 00:21:49.669 --> 00:21:49.679 align:start position:0% um there could certainly be more yeah so 00:21:49.679 --> 00:21:51.409 align:start position:0% um there could certainly be more yeah so that's<00:21:49.860> I<00:21:50.159> was<00:21:50.340> really<00:21:50.460> motivated<00:21:51.000> by 00:21:51.409 --> 00:21:51.419 align:start position:0% that's I was really motivated by 00:21:51.419 --> 00:21:53.570 align:start position:0% that's I was really motivated by observing<00:21:52.260> all<00:21:52.500> these<00:21:52.799> groups<00:21:53.100> working 00:21:53.570 --> 00:21:53.580 align:start position:0% observing all these groups working 00:21:53.580 --> 00:21:55.549 align:start position:0% observing all these groups working towards<00:21:54.059> the<00:21:54.179> same<00:21:54.299> goal<00:21:54.600> but<00:21:54.780> maybe<00:21:55.020> you<00:21:55.500> know 00:21:55.549 --> 00:21:55.559 align:start position:0% towards the same goal but maybe you know 00:21:55.559 --> 00:21:58.310 align:start position:0% towards the same goal but maybe you know as<00:21:55.740> software<00:21:56.039> developers<00:21:56.900> uh<00:21:57.900> we<00:21:58.200> can 00:21:58.310 --> 00:21:58.320 align:start position:0% as software developers uh we can 00:21:58.320 --> 00:21:59.570 align:start position:0% as software developers uh we can actually<00:21:58.500> facilitate<00:21:59.100> this<00:21:59.280> through<00:21:59.400> open 00:21:59.570 --> 00:21:59.580 align:start position:0% actually facilitate this through open 00:21:59.580 --> 00:22:02.390 align:start position:0% actually facilitate this through open source<00:22:00.000> and<00:22:00.179> it<00:22:00.659> actually<00:22:00.840> strives<00:22:01.400> are 00:22:02.390 --> 00:22:02.400 align:start position:0% source and it actually strives are 00:22:02.400 --> 00:22:04.570 align:start position:0% source and it actually strives are working<00:22:02.520> on<00:22:02.760> it's<00:22:02.940> probably<00:22:03.240> a<00:22:03.840> very<00:22:03.960> good<00:22:04.140> way 00:22:04.570 --> 00:22:04.580 align:start position:0% working on it's probably a very good way 00:22:04.580 --> 00:22:06.950 align:start position:0% working on it's probably a very good way to<00:22:05.580> bring<00:22:05.820> this<00:22:06.000> knowledge<00:22:06.299> together<00:22:06.539> right 00:22:06.950 --> 00:22:06.960 align:start position:0% to bring this knowledge together right 00:22:06.960 --> 00:22:08.510 align:start position:0% to bring this knowledge together right so<00:22:07.380> we<00:22:07.740> probably<00:22:07.919> need<00:22:08.159> good<00:22:08.340> public 00:22:08.510 --> 00:22:08.520 align:start position:0% so we probably need good public 00:22:08.520 --> 00:22:10.909 align:start position:0% so we probably need good public anthologies<00:22:09.179> as<00:22:09.360> well<00:22:09.480> because<00:22:09.720> if<00:22:10.679> this<00:22:10.860> is 00:22:10.909 --> 00:22:10.919 align:start position:0% anthologies as well because if this is 00:22:10.919 --> 00:22:12.230 align:start position:0% anthologies as well because if this is something<00:22:11.100> where<00:22:11.340> you're<00:22:11.460> hanging<00:22:11.760> all<00:22:11.940> these 00:22:12.230 --> 00:22:12.240 align:start position:0% something where you're hanging all these 00:22:12.240 --> 00:22:13.909 align:start position:0% something where you're hanging all these pieces<00:22:12.419> of<00:22:12.539> knowledge<00:22:12.780> onto<00:22:13.200> right<00:22:13.559> so<00:22:13.740> this 00:22:13.909 --> 00:22:13.919 align:start position:0% pieces of knowledge onto right so this 00:22:13.919 --> 00:22:15.830 align:start position:0% pieces of knowledge onto right so this is<00:22:14.039> kind<00:22:14.220> of<00:22:14.280> a<00:22:14.400> backbone<00:22:14.820> and<00:22:15.419> you<00:22:15.659> know<00:22:15.720> and 00:22:15.830 --> 00:22:15.840 align:start position:0% is kind of a backbone and you know and 00:22:15.840 --> 00:22:17.090 align:start position:0% is kind of a backbone and you know and so<00:22:16.020> this<00:22:16.260> is<00:22:16.380> something<00:22:16.500> which<00:22:16.740> you<00:22:16.980> know 00:22:17.090 --> 00:22:17.100 align:start position:0% so this is something which you know 00:22:17.100 --> 00:22:19.730 align:start position:0% so this is something which you know computer<00:22:17.400> science<00:22:17.700> understand<00:22:18.059> right<00:22:18.900> so<00:22:19.440> you 00:22:19.730 --> 00:22:19.740 align:start position:0% computer science understand right so you 00:22:19.740 --> 00:22:21.409 align:start position:0% computer science understand right so you know<00:22:19.799> if<00:22:20.159> we<00:22:20.340> have<00:22:20.460> a<00:22:20.640> good<00:22:20.700> public<00:22:20.880> Anthology 00:22:21.409 --> 00:22:21.419 align:start position:0% know if we have a good public Anthology 00:22:21.419 --> 00:22:23.690 align:start position:0% know if we have a good public Anthology which<00:22:22.260> we<00:22:22.500> all<00:22:22.620> can<00:22:22.799> agree<00:22:23.039> on<00:22:23.220> that<00:22:23.520> probably 00:22:23.690 --> 00:22:23.700 align:start position:0% which we all can agree on that probably 00:22:23.700 --> 00:22:25.549 align:start position:0% which we all can agree on that probably will<00:22:23.940> move<00:22:24.120> at<00:22:24.419> least<00:22:24.659> you<00:22:24.960> know<00:22:25.020> a<00:22:25.260> long<00:22:25.380> way 00:22:25.549 --> 00:22:25.559 align:start position:0% will move at least you know a long way 00:22:25.559 --> 00:22:27.770 align:start position:0% will move at least you know a long way so<00:22:26.039> so<00:22:26.520> now<00:22:26.760> I'm<00:22:26.940> really<00:22:27.120> interested<00:22:27.480> in<00:22:27.600> how 00:22:27.770 --> 00:22:27.780 align:start position:0% so so now I'm really interested in how 00:22:27.780 --> 00:22:30.590 align:start position:0% so so now I'm really interested in how to<00:22:27.960> make<00:22:28.080> that<00:22:28.260> happen<00:22:28.440> yeah<00:22:29.039> so<00:22:29.640> yeah<00:22:30.240> I<00:22:30.480> would 00:22:30.590 --> 00:22:30.600 align:start position:0% to make that happen yeah so yeah I would 00:22:30.600 --> 00:22:32.390 align:start position:0% to make that happen yeah so yeah I would say<00:22:30.780> that<00:22:30.960> there<00:22:31.200> are<00:22:31.679> um<00:22:31.740> there<00:22:31.980> are<00:22:32.100> attempts 00:22:32.390 --> 00:22:32.400 align:start position:0% say that there are um there are attempts 00:22:32.400 --> 00:22:33.950 align:start position:0% say that there are um there are attempts at<00:22:32.520> that<00:22:32.640> out<00:22:33.000> there 00:22:33.950 --> 00:22:33.960 align:start position:0% at that out there 00:22:33.960 --> 00:22:35.810 align:start position:0% at that out there um<00:22:34.080> one<00:22:34.620> of<00:22:34.740> the<00:22:34.980> sort<00:22:35.340> of<00:22:35.400> fundamental 00:22:35.810 --> 00:22:35.820 align:start position:0% um one of the sort of fundamental 00:22:35.820 --> 00:22:37.370 align:start position:0% um one of the sort of fundamental challenges<00:22:36.240> and<00:22:36.480> maybe<00:22:36.720> I'll<00:22:36.900> talk<00:22:37.080> about<00:22:37.200> it 00:22:37.370 --> 00:22:37.380 align:start position:0% challenges and maybe I'll talk about it 00:22:37.380 --> 00:22:39.350 align:start position:0% challenges and maybe I'll talk about it a<00:22:37.500> little<00:22:37.559> bit<00:22:37.679> later<00:22:37.980> as<00:22:38.280> well<00:22:38.460> of<00:22:39.000> building<00:22:39.240> a 00:22:39.350 --> 00:22:39.360 align:start position:0% a little bit later as well of building a 00:22:39.360 --> 00:22:41.450 align:start position:0% a little bit later as well of building a good<00:22:39.659> biology<00:22:40.020> is<00:22:40.500> that<00:22:40.620> it<00:22:40.740> turns<00:22:41.039> out<00:22:41.100> to<00:22:41.280> be 00:22:41.450 --> 00:22:41.460 align:start position:0% good biology is that it turns out to be 00:22:41.460 --> 00:22:43.669 align:start position:0% good biology is that it turns out to be fairly<00:22:41.880> labor<00:22:42.659> intensive<00:22:43.020> and<00:22:43.260> you<00:22:43.440> can 00:22:43.669 --> 00:22:43.679 align:start position:0% fairly labor intensive and you can 00:22:43.679 --> 00:22:45.830 align:start position:0% fairly labor intensive and you can certainly<00:22:44.039> with<00:22:45.000> software<00:22:45.419> develop 00:22:45.830 --> 00:22:45.840 align:start position:0% certainly with software develop 00:22:45.840 --> 00:22:50.270 align:start position:0% certainly with software develop techniques<00:22:46.580> uh<00:22:47.580> to<00:22:48.240> facilitate<00:22:49.280> maintaining 00:22:50.270 --> 00:22:50.280 align:start position:0% techniques uh to facilitate maintaining 00:22:50.280 --> 00:22:53.149 align:start position:0% techniques uh to facilitate maintaining uh<00:22:51.059> quality<00:22:51.539> and<00:22:52.080> especially<00:22:52.679> as<00:22:52.860> you<00:22:53.039> you 00:22:53.149 --> 00:22:53.159 align:start position:0% uh quality and especially as you you 00:22:53.159 --> 00:22:54.110 align:start position:0% uh quality and especially as you you know<00:22:53.280> increase<00:22:53.400> the<00:22:53.640> domain<00:22:53.820> and<00:22:53.940> increase 00:22:54.110 --> 00:22:54.120 align:start position:0% know increase the domain and increase 00:22:54.120 --> 00:22:55.250 align:start position:0% know increase the domain and increase the<00:22:54.360> coverage 00:22:55.250 --> 00:22:55.260 align:start position:0% the coverage 00:22:55.260 --> 00:22:55.930 align:start position:0% the coverage um 00:22:55.930 --> 00:22:55.940 align:start position:0% um 00:22:55.940 --> 00:22:57.470 align:start position:0% um but 00:22:57.470 --> 00:22:57.480 align:start position:0% but 00:22:57.480 --> 00:22:59.149 align:start position:0% but um the<00:22:57.960> you<00:22:58.140> know<00:22:58.260> the 00:22:59.149 --> 00:22:59.159 align:start position:0% um the you know the 00:22:59.159 --> 00:23:02.210 align:start position:0% um the you know the what<00:22:59.700> we<00:22:59.880> find<00:23:00.120> are<00:23:00.659> the<00:23:01.200> ontologies<00:23:01.799> that<00:23:02.039> are 00:23:02.210 --> 00:23:02.220 align:start position:0% what we find are the ontologies that are 00:23:02.220 --> 00:23:06.230 align:start position:0% what we find are the ontologies that are public<00:23:03.320> just<00:23:04.320> don't<00:23:04.500> have<00:23:04.860> that<00:23:05.400> amount<00:23:05.940> of 00:23:06.230 --> 00:23:06.240 align:start position:0% public just don't have that amount of 00:23:06.240 --> 00:23:08.630 align:start position:0% public just don't have that amount of attention<00:23:06.539> being<00:23:07.020> or<00:23:07.919> you<00:23:08.100> know<00:23:08.220> resources 00:23:08.630 --> 00:23:08.640 align:start position:0% attention being or you know resources 00:23:08.640 --> 00:23:10.370 align:start position:0% attention being or you know resources being<00:23:08.820> devoted<00:23:09.240> to<00:23:09.360> them 00:23:10.370 --> 00:23:10.380 align:start position:0% being devoted to them 00:23:10.380 --> 00:23:13.430 align:start position:0% being devoted to them um<00:23:10.980> either<00:23:11.460> to<00:23:12.000> uh<00:23:12.720> sort<00:23:12.900> of<00:23:13.020> maintain<00:23:13.260> the 00:23:13.430 --> 00:23:13.440 align:start position:0% um either to uh sort of maintain the 00:23:13.440 --> 00:23:16.310 align:start position:0% um either to uh sort of maintain the quality<00:23:13.799> or<00:23:14.760> even<00:23:15.120> to<00:23:15.419> maybe<00:23:15.600> even<00:23:15.840> to<00:23:16.140> test 00:23:16.310 --> 00:23:16.320 align:start position:0% quality or even to maybe even to test 00:23:16.320 --> 00:23:18.830 align:start position:0% quality or even to maybe even to test the<00:23:16.500> quality<00:23:16.860> right<00:23:17.520> and<00:23:18.179> so<00:23:18.299> at<00:23:18.419> least<00:23:18.600> if<00:23:18.720> we 00:23:18.830 --> 00:23:18.840 align:start position:0% the quality right and so at least if we 00:23:18.840 --> 00:23:20.630 align:start position:0% the quality right and so at least if we can<00:23:18.960> get<00:23:19.080> to<00:23:19.140> the<00:23:19.260> testing<00:23:19.559> part<00:23:19.740> we<00:23:20.340> can<00:23:20.520> say 00:23:20.630 --> 00:23:20.640 align:start position:0% can get to the testing part we can say 00:23:20.640 --> 00:23:22.130 align:start position:0% can get to the testing part we can say okay<00:23:20.760> here's<00:23:21.360> some<00:23:21.419> good<00:23:21.600> techniques<00:23:21.960> for 00:23:22.130 --> 00:23:22.140 align:start position:0% okay here's some good techniques for 00:23:22.140 --> 00:23:25.070 align:start position:0% okay here's some good techniques for testing<00:23:22.559> yes<00:23:22.980> then<00:23:23.460> there<00:23:23.760> could<00:23:23.940> be<00:23:24.120> you<00:23:24.900> know 00:23:25.070 --> 00:23:25.080 align:start position:0% testing yes then there could be you know 00:23:25.080 --> 00:23:27.110 align:start position:0% testing yes then there could be you know you<00:23:25.260> know<00:23:25.320> we<00:23:25.559> we<00:23:25.679> would<00:23:26.159> know<00:23:26.400> first<00:23:26.940> of<00:23:27.120> all 00:23:27.110 --> 00:23:27.120 align:start position:0% you know we we would know first of all 00:23:27.120 --> 00:23:28.430 align:start position:0% you know we we would know first of all we'd<00:23:27.299> have<00:23:27.480> a<00:23:27.539> metric<00:23:27.780> of<00:23:27.960> the<00:23:28.080> quality<00:23:28.260> right 00:23:28.430 --> 00:23:28.440 align:start position:0% we'd have a metric of the quality right 00:23:28.440 --> 00:23:29.870 align:start position:0% we'd have a metric of the quality right we<00:23:28.620> would<00:23:28.740> know<00:23:28.860> what<00:23:29.039> the<00:23:29.159> quality<00:23:29.460> was<00:23:29.640> in 00:23:29.870 --> 00:23:29.880 align:start position:0% we would know what the quality was in 00:23:29.880 --> 00:23:32.690 align:start position:0% we would know what the quality was in any<00:23:30.120> given<00:23:30.500> perspective<00:23:31.500> and<00:23:32.340> we<00:23:32.460> would<00:23:32.580> have 00:23:32.690 --> 00:23:32.700 align:start position:0% any given perspective and we would have 00:23:32.700 --> 00:23:33.950 align:start position:0% any given perspective and we would have and<00:23:32.940> people<00:23:33.059> would<00:23:33.240> have<00:23:33.360> things<00:23:33.480> to<00:23:33.659> work<00:23:33.780> on 00:23:33.950 --> 00:23:33.960 align:start position:0% and people would have things to work on 00:23:33.960 --> 00:23:35.570 align:start position:0% and people would have things to work on they<00:23:34.500> wanted<00:23:34.620> to<00:23:34.799> come<00:23:34.919> and<00:23:35.039> contribute<00:23:35.340> to<00:23:35.460> a 00:23:35.570 --> 00:23:35.580 align:start position:0% they wanted to come and contribute to a 00:23:35.580 --> 00:23:36.950 align:start position:0% they wanted to come and contribute to a project<00:23:35.700> like<00:23:35.940> that<00:23:36.120> it<00:23:36.299> was<00:23:36.419> like<00:23:36.600> well<00:23:36.720> here 00:23:36.950 --> 00:23:36.960 align:start position:0% project like that it was like well here 00:23:36.960 --> 00:23:39.230 align:start position:0% project like that it was like well here are<00:23:37.200> areas<00:23:37.559> that<00:23:37.799> we<00:23:37.980> know<00:23:38.100> the<00:23:38.280> tests<00:23:38.700> fail<00:23:39.000> in 00:23:39.230 --> 00:23:39.240 align:start position:0% are areas that we know the tests fail in 00:23:39.240 --> 00:23:40.669 align:start position:0% are areas that we know the tests fail in the<00:23:39.360> following<00:23:39.600> ways 00:23:40.669 --> 00:23:40.679 align:start position:0% the following ways 00:23:40.679 --> 00:23:43.789 align:start position:0% the following ways so<00:23:41.220> I<00:23:41.400> think<00:23:41.520> that<00:23:41.820> would<00:23:42.000> be<00:23:42.179> a<00:23:42.900> huge<00:23:43.500> step<00:23:43.620> in 00:23:43.789 --> 00:23:43.799 align:start position:0% so I think that would be a huge step in 00:23:43.799 --> 00:23:45.230 align:start position:0% so I think that would be a huge step in the<00:23:43.860> right<00:23:43.980> direction<00:23:44.100> this<00:23:44.640> I<00:23:44.880> think<00:23:45.000> this 00:23:45.230 --> 00:23:45.240 align:start position:0% the right direction this I think this 00:23:45.240 --> 00:23:46.610 align:start position:0% the right direction this I think this sounds<00:23:45.360> like<00:23:45.600> something<00:23:45.840> which<00:23:46.080> software 00:23:46.610 --> 00:23:46.620 align:start position:0% sounds like something which software 00:23:46.620 --> 00:23:48.350 align:start position:0% sounds like something which software Engineers<00:23:46.919> can<00:23:47.220> really<00:23:47.700> relate<00:23:48.059> to<00:23:48.179> through 00:23:48.350 --> 00:23:48.360 align:start position:0% Engineers can really relate to through 00:23:48.360 --> 00:23:49.850 align:start position:0% Engineers can really relate to through test<00:23:48.539> driven<00:23:48.780> development<00:23:49.200> like<00:23:49.380> if<00:23:49.620> first 00:23:49.850 --> 00:23:49.860 align:start position:0% test driven development like if first 00:23:49.860 --> 00:23:51.710 align:start position:0% test driven development like if first startable<00:23:50.280> writing<00:23:50.580> tests<00:23:50.940> which<00:23:51.419> is<00:23:51.539> your 00:23:51.710 --> 00:23:51.720 align:start position:0% startable writing tests which is your 00:23:51.720 --> 00:23:53.750 align:start position:0% startable writing tests which is your metric<00:23:51.960> of<00:23:52.140> quality<00:23:52.440> rather<00:23:53.159> than<00:23:53.280> you<00:23:53.520> start 00:23:53.750 --> 00:23:53.760 align:start position:0% metric of quality rather than you start 00:23:53.760 --> 00:23:55.490 align:start position:0% metric of quality rather than you start kind<00:23:54.120> of<00:23:54.240> populating<00:23:54.600> and<00:23:54.780> measuring<00:23:55.200> so 00:23:55.490 --> 00:23:55.500 align:start position:0% kind of populating and measuring so 00:23:55.500 --> 00:23:57.049 align:start position:0% kind of populating and measuring so that's<00:23:56.039> that<00:23:56.340> strikes<00:23:56.700> me<00:23:56.820> as<00:23:56.940> something 00:23:57.049 --> 00:23:57.059 align:start position:0% that's that strikes me as something 00:23:57.059 --> 00:23:58.850 align:start position:0% that's that strikes me as something issue<00:23:57.480> as<00:23:57.900> a<00:23:58.020> community<00:23:58.140> can<00:23:58.440> probably<00:23:58.559> try 00:23:58.850 --> 00:23:58.860 align:start position:0% issue as a community can probably try 00:23:58.860 --> 00:24:00.230 align:start position:0% issue as a community can probably try but<00:23:59.340> you<00:23:59.520> know<00:23:59.580> thank<00:23:59.760> you<00:23:59.880> very<00:23:59.940> much<00:24:00.000> Jeff 00:24:00.230 --> 00:24:00.240 align:start position:0% but you know thank you very much Jeff 00:24:00.240 --> 00:24:01.490 align:start position:0% but you know thank you very much Jeff it's<00:24:00.539> really<00:24:00.900> interesting<00:24:01.200> and<00:24:01.380> we're 00:24:01.490 --> 00:24:01.500 align:start position:0% it's really interesting and we're 00:24:01.500 --> 00:24:03.169 align:start position:0% it's really interesting and we're looking<00:24:01.740> forward<00:24:01.919> to<00:24:02.159> your<00:24:02.340> talk<00:24:02.520> thank<00:24:03.000> you 00:24:03.169 --> 00:24:03.179 align:start position:0% looking forward to your talk thank you 00:24:03.179 --> 00:24:05.419 align:start position:0% looking forward to your talk thank you thanks