WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:16.320 align:start position:0% [Music] 00:00:16.320 --> 00:00:16.330 align:start position:0% [Music] 00:00:16.330 --> 00:00:20.080 align:start position:0% [Music] okay<00:00:17.330> here<00:00:17.600> we<00:00:17.660> go<00:00:18.160> my<00:00:19.160> name<00:00:19.190> is<00:00:19.460> James<00:00:19.730> Pitts 00:00:20.080 --> 00:00:20.090 align:start position:0% okay here we go my name is James Pitts 00:00:20.090 --> 00:00:24.150 align:start position:0% okay here we go my name is James Pitts and<00:00:20.360> this<00:00:20.930> is<00:00:21.080> about<00:00:21.290> semantic<00:00:21.980> aetherium<00:00:22.520> and 00:00:24.150 --> 00:00:24.160 align:start position:0% and this is about semantic aetherium and 00:00:24.160 --> 00:00:27.400 align:start position:0% and this is about semantic aetherium and when<00:00:25.160> you<00:00:25.250> talk<00:00:25.400> about<00:00:25.430> semantic<00:00:26.300> or<00:00:26.510> semantic 00:00:27.400 --> 00:00:27.410 align:start position:0% when you talk about semantic or semantic 00:00:27.410 --> 00:00:30.630 align:start position:0% when you talk about semantic or semantic technologies<00:00:28.040> like<00:00:28.280> the<00:00:28.430> Semantic<00:00:28.850> Web 00:00:30.630 --> 00:00:30.640 align:start position:0% technologies like the Semantic Web 00:00:30.640 --> 00:00:35.710 align:start position:0% technologies like the Semantic Web it<00:00:31.640> starts<00:00:32.029> with<00:00:32.090> metadata<00:00:33.550> so<00:00:34.550> so<00:00:35.450> what<00:00:35.600> is 00:00:35.710 --> 00:00:35.720 align:start position:0% it starts with metadata so so what is 00:00:35.720 --> 00:00:39.970 align:start position:0% it starts with metadata so so what is metadata<00:00:36.520> it<00:00:37.750> provides<00:00:38.750> context<00:00:39.500> to<00:00:39.680> the<00:00:39.800> data 00:00:39.970 --> 00:00:39.980 align:start position:0% metadata it provides context to the data 00:00:39.980 --> 00:00:42.010 align:start position:0% metadata it provides context to the data that<00:00:40.070> you<00:00:40.310> have<00:00:40.340> and<00:00:40.850> so<00:00:41.480> when<00:00:41.600> you're<00:00:41.720> marking 00:00:42.010 --> 00:00:42.020 align:start position:0% that you have and so when you're marking 00:00:42.020 --> 00:00:46.540 align:start position:0% that you have and so when you're marking up<00:00:42.140> HTML<00:00:42.710> you're<00:00:43.670> you're<00:00:45.130> creating<00:00:46.130> context 00:00:46.540 --> 00:00:46.550 align:start position:0% up HTML you're you're creating context 00:00:46.550 --> 00:00:47.889 align:start position:0% up HTML you're you're creating context for<00:00:46.670> the<00:00:46.790> data<00:00:47.000> that<00:00:47.210> you've<00:00:47.329> included<00:00:47.510> in 00:00:47.889 --> 00:00:47.899 align:start position:0% for the data that you've included in 00:00:47.899 --> 00:00:51.850 align:start position:0% for the data that you've included in your<00:00:47.930> webpage<00:00:48.440> and<00:00:49.190> it<00:00:50.000> in<00:00:50.899> that<00:00:51.020> context<00:00:51.649> can 00:00:51.850 --> 00:00:51.860 align:start position:0% your webpage and it in that context can 00:00:51.860 --> 00:00:55.270 align:start position:0% your webpage and it in that context can run<00:00:52.040> very<00:00:52.310> deep<00:00:52.370> and<00:00:53.530> regular<00:00:54.530> metadata<00:00:55.010> that 00:00:55.270 --> 00:00:55.280 align:start position:0% run very deep and regular metadata that 00:00:55.280 --> 00:00:58.170 align:start position:0% run very deep and regular metadata that we<00:00:55.399> usually<00:00:55.730> deal<00:00:56.120> with<00:00:56.149> as<00:00:56.420> HTML<00:00:56.899> developers 00:00:58.170 --> 00:00:58.180 align:start position:0% we usually deal with as HTML developers 00:00:58.180 --> 00:01:01.540 align:start position:0% we usually deal with as HTML developers it<00:00:59.180> it's<00:00:59.809> it's<00:01:00.200> a<00:01:00.350> bit<00:01:00.620> of<00:01:00.710> a<00:01:00.770> burden<00:01:01.100> when<00:01:01.430> you 00:01:01.540 --> 00:01:01.550 align:start position:0% it it's it's a bit of a burden when you 00:01:01.550 --> 00:01:04.030 align:start position:0% it it's it's a bit of a burden when you do<00:01:01.730> it<00:01:01.910> but<00:01:02.540> if<00:01:03.170> you<00:01:03.320> want<00:01:03.469> to<00:01:03.559> go<00:01:03.680> to<00:01:03.739> something 00:01:04.030 --> 00:01:04.040 align:start position:0% do it but if you want to go to something 00:01:04.040 --> 00:01:06.460 align:start position:0% do it but if you want to go to something like<00:01:04.159> the<00:01:04.369> Semantic<00:01:04.790> Web<00:01:04.820> it<00:01:05.690> has<00:01:05.900> it's<00:01:06.320> a 00:01:06.460 --> 00:01:06.470 align:start position:0% like the Semantic Web it has it's a 00:01:06.470 --> 00:01:10.780 align:start position:0% like the Semantic Web it has it's a quite<00:01:06.799> a<00:01:06.830> big<00:01:07.250> endeavor<00:01:09.220> so<00:01:10.220> the<00:01:10.370> Semantic<00:01:10.760> Web 00:01:10.780 --> 00:01:10.790 align:start position:0% quite a big endeavor so the Semantic Web 00:01:10.790 --> 00:01:12.340 align:start position:0% quite a big endeavor so the Semantic Web is<00:01:10.940> proposed<00:01:11.450> by<00:01:11.570> Tim<00:01:11.840> berners-lee 00:01:12.340 --> 00:01:12.350 align:start position:0% is proposed by Tim berners-lee 00:01:12.350 --> 00:01:15.310 align:start position:0% is proposed by Tim berners-lee who<00:01:12.920> created<00:01:13.250> the<00:01:13.370> web<00:01:13.549> and<00:01:13.900> when<00:01:14.900> the<00:01:15.020> person 00:01:15.310 --> 00:01:15.320 align:start position:0% who created the web and when the person 00:01:15.320 --> 00:01:17.560 align:start position:0% who created the web and when the person who<00:01:15.409> created<00:01:15.650> the<00:01:15.710> web<00:01:15.890> proposed<00:01:16.540> proposes<00:01:17.540> a 00:01:17.560 --> 00:01:17.570 align:start position:0% who created the web proposed proposes a 00:01:17.570 --> 00:01:20.080 align:start position:0% who created the web proposed proposes a new<00:01:17.840> idea<00:01:18.229> a<00:01:18.590> new<00:01:18.979> concept<00:01:19.670> a<00:01:19.729> new<00:01:19.850> set<00:01:20.060> of 00:01:20.080 --> 00:01:20.090 align:start position:0% new idea a new concept a new set of 00:01:20.090 --> 00:01:22.359 align:start position:0% new idea a new concept a new set of standards<00:01:20.380> were<00:01:21.380> inclined<00:01:21.799> to<00:01:21.950> pay<00:01:22.070> attention 00:01:22.359 --> 00:01:22.369 align:start position:0% standards were inclined to pay attention 00:01:22.369 --> 00:01:24.550 align:start position:0% standards were inclined to pay attention to<00:01:22.670> him<00:01:22.790> because<00:01:23.150> we're<00:01:23.479> grateful<00:01:24.049> and<00:01:24.380> it's 00:01:24.550 --> 00:01:24.560 align:start position:0% to him because we're grateful and it's 00:01:24.560 --> 00:01:28.030 align:start position:0% to him because we're grateful and it's he's<00:01:25.220> a<00:01:25.250> genius<00:01:25.610> so<00:01:26.090> a<00:01:27.020> lot<00:01:27.619> of<00:01:27.650> people<00:01:27.920> got 00:01:28.030 --> 00:01:28.040 align:start position:0% he's a genius so a lot of people got 00:01:28.040 --> 00:01:30.399 align:start position:0% he's a genius so a lot of people got very<00:01:28.280> excited<00:01:28.820> and<00:01:28.850> I<00:01:29.299> drunk<00:01:30.140> the<00:01:30.260> kool-aid 00:01:30.399 --> 00:01:30.409 align:start position:0% very excited and I drunk the kool-aid 00:01:30.409 --> 00:01:32.770 align:start position:0% very excited and I drunk the kool-aid myself<00:01:30.979> I<00:01:31.070> got<00:01:31.220> extremely<00:01:31.970> excited<00:01:32.420> about<00:01:32.450> it 00:01:32.770 --> 00:01:32.780 align:start position:0% myself I got extremely excited about it 00:01:32.780 --> 00:01:35.350 align:start position:0% myself I got extremely excited about it and<00:01:33.020> so<00:01:33.500> he<00:01:33.680> started<00:01:34.010> with<00:01:34.100> web<00:01:34.400> of<00:01:34.549> content 00:01:35.350 --> 00:01:35.360 align:start position:0% and so he started with web of content 00:01:35.360 --> 00:01:38.020 align:start position:0% and so he started with web of content which<00:01:35.869> is<00:01:36.020> the<00:01:36.140> current<00:01:36.470> web<00:01:36.650> and<00:01:36.950> then<00:01:37.880> he 00:01:38.020 --> 00:01:38.030 align:start position:0% which is the current web and then he 00:01:38.030 --> 00:01:41.020 align:start position:0% which is the current web and then he would<00:01:38.180> he<00:01:38.720> expanded<00:01:39.200> it<00:01:39.320> to<00:01:39.500> be<00:01:39.680> a<00:01:39.950> web<00:01:40.640> of<00:01:40.820> data 00:01:41.020 --> 00:01:41.030 align:start position:0% would he expanded it to be a web of data 00:01:41.030 --> 00:01:44.200 align:start position:0% would he expanded it to be a web of data and<00:01:41.450> a<00:01:41.869> web<00:01:42.080> of<00:01:42.229> trust<00:01:42.470> and<00:01:42.920> as<00:01:43.580> we<00:01:43.909> all<00:01:44.000> know 00:01:44.200 --> 00:01:44.210 align:start position:0% and a web of trust and as we all know 00:01:44.210 --> 00:01:47.249 align:start position:0% and a web of trust and as we all know we're<00:01:44.479> solving<00:01:45.020> the<00:01:45.350> trust<00:01:45.680> aspect<00:01:46.520> of<00:01:46.640> this 00:01:47.249 --> 00:01:47.259 align:start position:0% we're solving the trust aspect of this 00:01:47.259 --> 00:01:50.830 align:start position:0% we're solving the trust aspect of this and<00:01:48.460> the<00:01:49.460> deeper<00:01:49.820> sense<00:01:50.060> of<00:01:50.240> what<00:01:50.750> he's 00:01:50.830 --> 00:01:50.840 align:start position:0% and the deeper sense of what he's 00:01:50.840 --> 00:01:54.340 align:start position:0% and the deeper sense of what he's talking<00:01:51.020> about<00:01:51.259> is<00:01:51.530> that<00:01:52.490> once<00:01:53.210> you<00:01:53.420> establish 00:01:54.340 --> 00:01:54.350 align:start position:0% talking about is that once you establish 00:01:54.350 --> 00:01:57.520 align:start position:0% talking about is that once you establish all<00:01:54.560> this<00:01:54.710> context<00:01:55.549> and<00:01:56.060> once<00:01:56.240> you<00:01:56.390> know<00:01:56.530> the 00:01:57.520 --> 00:01:57.530 align:start position:0% all this context and once you know the 00:01:57.530 --> 00:02:02.469 align:start position:0% all this context and once you know the source<00:01:57.829> of<00:01:58.040> the<00:01:58.130> context<00:01:59.229> you<00:02:00.229> you<00:02:01.220> you<00:02:01.939> create 00:02:02.469 --> 00:02:02.479 align:start position:0% source of the context you you you create 00:02:02.479 --> 00:02:05.200 align:start position:0% source of the context you you you create something<00:02:03.229> that's<00:02:03.380> almost<00:02:03.740> not<00:02:04.549> so<00:02:04.850> much<00:02:05.000> of<00:02:05.119> a 00:02:05.200 --> 00:02:05.210 align:start position:0% something that's almost not so much of a 00:02:05.210 --> 00:02:07.300 align:start position:0% something that's almost not so much of a thinking<00:02:05.689> vein<00:02:05.990> but<00:02:06.320> something<00:02:06.740> that<00:02:06.770> is 00:02:07.300 --> 00:02:07.310 align:start position:0% thinking vein but something that is 00:02:07.310 --> 00:02:09.850 align:start position:0% thinking vein but something that is meaningful<00:02:08.269> that<00:02:08.569> that<00:02:09.019> all<00:02:09.379> the<00:02:09.709> information 00:02:09.850 --> 00:02:09.860 align:start position:0% meaningful that that all the information 00:02:09.860 --> 00:02:11.830 align:start position:0% meaningful that that all the information is<00:02:10.340> connected<00:02:10.849> together<00:02:10.970> in<00:02:11.180> a<00:02:11.300> very<00:02:11.480> formal 00:02:11.830 --> 00:02:11.840 align:start position:0% is connected together in a very formal 00:02:11.840 --> 00:02:15.160 align:start position:0% is connected together in a very formal way<00:02:12.670> and<00:02:13.670> that<00:02:14.000> can<00:02:14.030> make<00:02:14.270> that<00:02:14.810> made<00:02:14.930> a<00:02:14.959> lot<00:02:15.140> of 00:02:15.160 --> 00:02:15.170 align:start position:0% way and that can make that made a lot of 00:02:15.170 --> 00:02:15.790 align:start position:0% way and that can make that made a lot of people<00:02:15.319> very 00:02:15.790 --> 00:02:15.800 align:start position:0% people very 00:02:15.800 --> 00:02:19.780 align:start position:0% people very sited<00:02:16.160> and<00:02:16.340> a<00:02:16.670> w3c<00:02:17.060> which<00:02:18.310> which<00:02:19.310> maintains 00:02:19.780 --> 00:02:19.790 align:start position:0% sited and a w3c which which maintains 00:02:19.790 --> 00:02:21.670 align:start position:0% sited and a w3c which which maintains its<00:02:19.970> standards<00:02:20.390> of<00:02:20.540> the<00:02:20.630> web<00:02:20.810> developed<00:02:21.590> the 00:02:21.670 --> 00:02:21.680 align:start position:0% its standards of the web developed the 00:02:21.680 --> 00:02:23.320 align:start position:0% its standards of the web developed the standards<00:02:22.010> of<00:02:22.130> the<00:02:22.220> Semantic<00:02:22.610> Web<00:02:22.640> and<00:02:23.060> many 00:02:23.320 --> 00:02:23.330 align:start position:0% standards of the Semantic Web and many 00:02:23.330 --> 00:02:26.650 align:start position:0% standards of the Semantic Web and many many<00:02:23.600> tools<00:02:23.840> came<00:02:24.110> out<00:02:24.230> standards<00:02:25.540> lots<00:02:26.540> of 00:02:26.650 --> 00:02:26.660 align:start position:0% many tools came out standards lots of 00:02:26.660 --> 00:02:28.630 align:start position:0% many tools came out standards lots of interesting<00:02:27.440> diagrams<00:02:27.860> like<00:02:28.130> that 00:02:28.630 --> 00:02:28.640 align:start position:0% interesting diagrams like that 00:02:28.640 --> 00:02:31.860 align:start position:0% interesting diagrams like that to<00:02:28.880> describe<00:02:29.210> how<00:02:29.510> things<00:02:29.720> connect<00:02:30.200> together 00:02:31.860 --> 00:02:31.870 align:start position:0% to describe how things connect together 00:02:31.870 --> 00:02:35.950 align:start position:0% to describe how things connect together but<00:02:32.870> it<00:02:32.960> largely<00:02:33.260> failed<00:02:33.740> and<00:02:34.690> you'll<00:02:35.690> find 00:02:35.950 --> 00:02:35.960 align:start position:0% but it largely failed and you'll find 00:02:35.960 --> 00:02:37.900 align:start position:0% but it largely failed and you'll find many<00:02:36.440> articles<00:02:36.800> about<00:02:37.070> how<00:02:37.370> the<00:02:37.430> Semantic<00:02:37.880> Web 00:02:37.900 --> 00:02:37.910 align:start position:0% many articles about how the Semantic Web 00:02:37.910 --> 00:02:40.360 align:start position:0% many articles about how the Semantic Web was<00:02:38.120> a<00:02:38.180> complete<00:02:38.900> bust<00:02:39.140> but<00:02:40.070> the<00:02:40.160> thing<00:02:40.340> is 00:02:40.360 --> 00:02:40.370 align:start position:0% was a complete bust but the thing is 00:02:40.370 --> 00:02:43.150 align:start position:0% was a complete bust but the thing is there<00:02:41.090> there's<00:02:41.480> there's<00:02:42.410> a<00:02:42.470> lot<00:02:42.680> of<00:02:42.800> standards 00:02:43.150 --> 00:02:43.160 align:start position:0% there there's there's a lot of standards 00:02:43.160 --> 00:02:46.870 align:start position:0% there there's there's a lot of standards that<00:02:43.310> are<00:02:43.640> out<00:02:43.760> there<00:02:44.170> but<00:02:45.520> they<00:02:46.520> just<00:02:46.550> weren't 00:02:46.870 --> 00:02:46.880 align:start position:0% that are out there but they just weren't 00:02:46.880 --> 00:02:48.700 align:start position:0% that are out there but they just weren't useful<00:02:47.390> for<00:02:47.840> people<00:02:47.960> in<00:02:48.170> their<00:02:48.260> a<00:02:48.320> bit<00:02:48.560> of<00:02:48.650> a 00:02:48.700 --> 00:02:48.710 align:start position:0% useful for people in their a bit of a 00:02:48.710 --> 00:02:52.210 align:start position:0% useful for people in their a bit of a burden<00:02:48.890> to<00:02:49.160> work<00:02:49.340> with<00:02:50.050> and<00:02:51.050> famously<00:02:51.860> cory 00:02:52.210 --> 00:02:52.220 align:start position:0% burden to work with and famously cory 00:02:52.220 --> 00:02:52.690 align:start position:0% burden to work with and famously cory doctorow 00:02:52.690 --> 00:02:52.700 align:start position:0% doctorow 00:02:52.700 --> 00:02:54.460 align:start position:0% doctorow even<00:02:53.000> before<00:02:53.120> the<00:02:53.420> Semantic<00:02:53.840> Web<00:02:53.870> was<00:02:54.170> really 00:02:54.460 --> 00:02:54.470 align:start position:0% even before the Semantic Web was really 00:02:54.470 --> 00:02:57.130 align:start position:0% even before the Semantic Web was really formally<00:02:54.980> a<00:02:55.190> set<00:02:55.490> of<00:02:55.610> standards<00:02:56.060> he<00:02:56.750> actually 00:02:57.130 --> 00:02:57.140 align:start position:0% formally a set of standards he actually 00:02:57.140 --> 00:02:59.140 align:start position:0% formally a set of standards he actually took<00:02:57.500> on<00:02:57.620> just<00:02:57.860> metadata<00:02:58.340> itself<00:02:58.550> the<00:02:59.030> whole 00:02:59.140 --> 00:02:59.150 align:start position:0% took on just metadata itself the whole 00:02:59.150 --> 00:03:02.320 align:start position:0% took on just metadata itself the whole concept<00:02:59.570> he<00:02:59.720> said<00:02:59.900> it's<00:02:59.990> MIT<00:03:00.140> a<00:03:00.170> crap<00:03:00.530> and<00:03:01.330> it's 00:03:02.320 --> 00:03:02.330 align:start position:0% concept he said it's MIT a crap and it's 00:03:02.330 --> 00:03:04.330 align:start position:0% concept he said it's MIT a crap and it's very<00:03:02.540> snarky<00:03:02.930> but<00:03:03.230> it<00:03:03.470> was<00:03:03.590> very<00:03:03.920> insightful 00:03:04.330 --> 00:03:04.340 align:start position:0% very snarky but it was very insightful 00:03:04.340 --> 00:03:07.180 align:start position:0% very snarky but it was very insightful too<00:03:05.170> he<00:03:06.170> talked<00:03:06.410> about<00:03:06.620> insurmountable 00:03:07.180 --> 00:03:07.190 align:start position:0% too he talked about insurmountable 00:03:07.190 --> 00:03:11.220 align:start position:0% too he talked about insurmountable obstacles<00:03:08.290> lies<00:03:09.290> laziness<00:03:10.220> stupidity 00:03:11.220 --> 00:03:11.230 align:start position:0% obstacles lies laziness stupidity 00:03:11.230 --> 00:03:14.740 align:start position:0% obstacles lies laziness stupidity impracticality<00:03:12.550> and<00:03:13.580> it's<00:03:14.090> a<00:03:14.210> great<00:03:14.450> article 00:03:14.740 --> 00:03:14.750 align:start position:0% impracticality and it's a great article 00:03:14.750 --> 00:03:16.570 align:start position:0% impracticality and it's a great article if<00:03:14.930> you<00:03:15.020> look<00:03:15.170> it<00:03:15.290> up<00:03:15.380> the<00:03:15.620> seven<00:03:15.920> strongmen<00:03:16.400> of 00:03:16.570 --> 00:03:16.580 align:start position:0% if you look it up the seven strongmen of 00:03:16.580 --> 00:03:20.680 align:start position:0% if you look it up the seven strongmen of meta<00:03:16.940> utopia<00:03:18.010> we<00:03:19.010> ourselves<00:03:19.160> or<00:03:19.790> utopians<00:03:20.540> in 00:03:20.680 --> 00:03:20.690 align:start position:0% meta utopia we ourselves or utopians in 00:03:20.690 --> 00:03:23.080 align:start position:0% meta utopia we ourselves or utopians in a<00:03:20.750> way<00:03:20.900> so<00:03:20.959> we<00:03:21.230> can<00:03:21.440> learn<00:03:21.590> a<00:03:21.650> lot<00:03:21.860> from<00:03:22.090> people 00:03:23.080 --> 00:03:23.090 align:start position:0% a way so we can learn a lot from people 00:03:23.090 --> 00:03:25.470 align:start position:0% a way so we can learn a lot from people who<00:03:23.209> just<00:03:23.480> simply<00:03:23.870> say<00:03:24.380> things<00:03:24.650> like<00:03:24.830> that 00:03:25.470 --> 00:03:25.480 align:start position:0% who just simply say things like that 00:03:25.480 --> 00:03:27.520 align:start position:0% who just simply say things like that perhaps<00:03:26.480> Tim<00:03:26.780> berners-lee<00:03:27.050> should<00:03:27.440> have 00:03:27.520 --> 00:03:27.530 align:start position:0% perhaps Tim berners-lee should have 00:03:27.530 --> 00:03:30.370 align:start position:0% perhaps Tim berners-lee should have listened<00:03:27.890> to<00:03:27.950> that<00:03:28.160> a<00:03:28.190> little<00:03:28.430> bit<00:03:29.260> but<00:03:30.260> the 00:03:30.370 --> 00:03:30.380 align:start position:0% listened to that a little bit but the 00:03:30.380 --> 00:03:31.960 align:start position:0% listened to that a little bit but the thing<00:03:30.560> is<00:03:30.590> even<00:03:30.890> though<00:03:30.920> Semantic<00:03:31.370> Web<00:03:31.400> is<00:03:31.700> a 00:03:31.960 --> 00:03:31.970 align:start position:0% thing is even though Semantic Web is a 00:03:31.970 --> 00:03:34.540 align:start position:0% thing is even though Semantic Web is a failure<00:03:32.360> or<00:03:32.750> perhaps<00:03:33.470> not<00:03:33.800> two<00:03:34.070> people<00:03:34.459> are 00:03:34.540 --> 00:03:34.550 align:start position:0% failure or perhaps not two people are 00:03:34.550 --> 00:03:35.350 align:start position:0% failure or perhaps not two people are still<00:03:34.790> working<00:03:35.060> on<00:03:35.180> it 00:03:35.350 --> 00:03:35.360 align:start position:0% still working on it 00:03:35.360 --> 00:03:38.949 align:start position:0% still working on it um<00:03:35.980> metadata<00:03:36.980> is<00:03:37.160> ubiquitous<00:03:37.870> anyone<00:03:38.870> who's 00:03:38.949 --> 00:03:38.959 align:start position:0% um metadata is ubiquitous anyone who's 00:03:38.959 --> 00:03:43.750 align:start position:0% um metadata is ubiquitous anyone who's worked<00:03:39.140> with<00:03:39.260> webpages<00:03:39.770> knows<00:03:41.800> and<00:03:42.800> the 00:03:43.750 --> 00:03:43.760 align:start position:0% worked with webpages knows and the 00:03:43.760 --> 00:03:46.240 align:start position:0% worked with webpages knows and the simple<00:03:44.030> fact<00:03:44.209> is<00:03:44.300> apps<00:03:44.630> share<00:03:45.350> data<00:03:45.560> and<00:03:45.860> that 00:03:46.240 --> 00:03:46.250 align:start position:0% simple fact is apps share data and that 00:03:46.250 --> 00:03:50.710 align:start position:0% simple fact is apps share data and that data<00:03:46.310> has<00:03:46.790> important<00:03:47.600> context<00:03:48.290> and<00:03:49.690> much<00:03:50.690> of 00:03:50.710 --> 00:03:50.720 align:start position:0% data has important context and much of 00:03:50.720 --> 00:03:53.229 align:start position:0% data has important context and much of the<00:03:50.900> data<00:03:51.080> as<00:03:51.320> web<00:03:52.190> developers<00:03:52.640> know<00:03:52.850> is<00:03:53.060> is 00:03:53.229 --> 00:03:53.239 align:start position:0% the data as web developers know is is 00:03:53.239 --> 00:03:55.900 align:start position:0% the data as web developers know is is embedded<00:03:53.870> in<00:03:53.989> HTML<00:03:54.140> and<00:03:54.800> that's<00:03:55.280> the<00:03:55.580> standard 00:03:55.900 --> 00:03:55.910 align:start position:0% embedded in HTML and that's the standard 00:03:55.910 --> 00:03:59.770 align:start position:0% embedded in HTML and that's the standard Micro<00:03:56.600> data<00:03:57.700> API<00:03:58.700> calls<00:03:59.060> are<00:03:59.239> out<00:03:59.360> there<00:03:59.600> and 00:03:59.770 --> 00:03:59.780 align:start position:0% Micro data API calls are out there and 00:03:59.780 --> 00:04:01.960 align:start position:0% Micro data API calls are out there and the<00:03:59.900> documentation<00:04:00.560> behind<00:04:00.709> it<00:04:00.950> by<00:04:01.100> API<00:04:01.610> calls 00:04:01.960 --> 00:04:01.970 align:start position:0% the documentation behind it by API calls 00:04:01.970 --> 00:04:05.770 align:start position:0% the documentation behind it by API calls can<00:04:02.239> be<00:04:02.330> considered<00:04:02.900> metadata<00:04:04.150> and<00:04:05.150> that's<00:04:05.450> in 00:04:05.770 --> 00:04:05.780 align:start position:0% can be considered metadata and that's in 00:04:05.780 --> 00:04:07.390 align:start position:0% can be considered metadata and that's in its<00:04:06.140> one<00:04:06.290> of<00:04:06.320> the<00:04:06.440> reasons<00:04:06.709> why<00:04:06.830> we<00:04:07.040> must 00:04:07.390 --> 00:04:07.400 align:start position:0% its one of the reasons why we must 00:04:07.400 --> 00:04:11.170 align:start position:0% its one of the reasons why we must maintain<00:04:08.180> great<00:04:08.690> documentation<00:04:09.580> and<00:04:10.580> much<00:04:11.000> of 00:04:11.170 --> 00:04:11.180 align:start position:0% maintain great documentation and much of 00:04:11.180 --> 00:04:14.490 align:start position:0% maintain great documentation and much of this<00:04:11.390> of<00:04:11.769> the<00:04:12.769> Semantic<00:04:13.160> Web<00:04:13.190> is<00:04:13.580> out<00:04:14.000> there 00:04:14.490 --> 00:04:14.500 align:start position:0% this of the Semantic Web is out there 00:04:14.500 --> 00:04:17.080 align:start position:0% this of the Semantic Web is out there not<00:04:15.500> really<00:04:15.769> forming<00:04:16.190> a<00:04:16.280> full<00:04:16.519> semantic<00:04:17.000> web 00:04:17.080 --> 00:04:17.090 align:start position:0% not really forming a full semantic web 00:04:17.090 --> 00:04:18.699 align:start position:0% not really forming a full semantic web not<00:04:17.330> really<00:04:17.570> forming<00:04:18.019> something<00:04:18.590> that 00:04:18.699 --> 00:04:18.709 align:start position:0% not really forming something that 00:04:18.709 --> 00:04:20.759 align:start position:0% not really forming something that everyone<00:04:19.040> uses<00:04:19.220> but<00:04:19.519> it's<00:04:19.700> out<00:04:19.880> there<00:04:20.150> and<00:04:20.390> it 00:04:20.759 --> 00:04:20.769 align:start position:0% everyone uses but it's out there and it 00:04:20.769 --> 00:04:23.950 align:start position:0% everyone uses but it's out there and it it's<00:04:21.769> useful<00:04:22.220> for<00:04:22.460> example<00:04:23.240> wikipedia<00:04:23.900> has 00:04:23.950 --> 00:04:23.960 align:start position:0% it's useful for example wikipedia has 00:04:23.960 --> 00:04:24.690 align:start position:0% it's useful for example wikipedia has been<00:04:24.260> convert 00:04:24.690 --> 00:04:24.700 align:start position:0% been convert 00:04:24.700 --> 00:04:28.350 align:start position:0% been convert into<00:04:25.450> a<00:04:25.480> database<00:04:25.900> and<00:04:26.230> you<00:04:26.680> can<00:04:27.130> see<00:04:28.000> wiki 00:04:28.350 --> 00:04:28.360 align:start position:0% into a database and you can see wiki 00:04:28.360 --> 00:04:30.630 align:start position:0% into a database and you can see wiki data<00:04:28.600> you<00:04:28.870> can<00:04:29.050> go<00:04:29.230> in<00:04:29.380> there<00:04:29.500> and<00:04:29.560> pull<00:04:30.370> a<00:04:30.400> lot 00:04:30.630 --> 00:04:30.640 align:start position:0% data you can go in there and pull a lot 00:04:30.640 --> 00:04:32.130 align:start position:0% data you can go in there and pull a lot of<00:04:30.730> data<00:04:30.910> relate<00:04:31.240> things<00:04:31.390> together<00:04:31.630> it's<00:04:31.960> very 00:04:32.130 --> 00:04:32.140 align:start position:0% of data relate things together it's very 00:04:32.140 --> 00:04:37.020 align:start position:0% of data relate things together it's very useful<00:04:33.420> so<00:04:34.420> often<00:04:35.350> we<00:04:35.470> use<00:04:35.800> metadata<00:04:36.700> without 00:04:37.020 --> 00:04:37.030 align:start position:0% useful so often we use metadata without 00:04:37.030 --> 00:04:39.210 align:start position:0% useful so often we use metadata without really<00:04:37.240> realizing<00:04:37.510> it<00:04:38.350> for<00:04:38.770> example<00:04:39.130> the 00:04:39.210 --> 00:04:39.220 align:start position:0% really realizing it for example the 00:04:39.220 --> 00:04:43.080 align:start position:0% really realizing it for example the emails<00:04:39.670> that<00:04:39.910> you<00:04:40.180> receive<00:04:40.660> in<00:04:41.280> Gmail<00:04:42.280> about 00:04:43.080 --> 00:04:43.090 align:start position:0% emails that you receive in Gmail about 00:04:43.090 --> 00:04:46.440 align:start position:0% emails that you receive in Gmail about your<00:04:43.240> flight<00:04:43.570> actually<00:04:44.320> contain<00:04:45.450> tags 00:04:46.440 --> 00:04:46.450 align:start position:0% your flight actually contain tags 00:04:46.450 --> 00:04:48.660 align:start position:0% your flight actually contain tags metadata<00:04:47.320> microbe<00:04:47.770> data<00:04:47.980> in<00:04:48.220> there<00:04:48.460> and 00:04:48.660 --> 00:04:48.670 align:start position:0% metadata microbe data in there and 00:04:48.670 --> 00:04:50.040 align:start position:0% metadata microbe data in there and that's<00:04:48.850> what<00:04:49.060> Google<00:04:49.360> will<00:04:49.450> generate<00:04:49.810> from 00:04:50.040 --> 00:04:50.050 align:start position:0% that's what Google will generate from 00:04:50.050 --> 00:04:51.990 align:start position:0% that's what Google will generate from those<00:04:50.200> from<00:04:50.680> that<00:04:50.710> Micro<00:04:51.100> data<00:04:51.220> and<00:04:51.490> github 00:04:51.990 --> 00:04:52.000 align:start position:0% those from that Micro data and github 00:04:52.000 --> 00:04:54.900 align:start position:0% those from that Micro data and github actions<00:04:52.710> often<00:04:53.710> when<00:04:54.040> you<00:04:54.100> do<00:04:54.250> search<00:04:54.490> results 00:04:54.900 --> 00:04:54.910 align:start position:0% actions often when you do search results 00:04:54.910 --> 00:04:56.760 align:start position:0% actions often when you do search results you'll<00:04:55.060> see<00:04:55.120> these<00:04:55.450> little<00:04:55.510> info<00:04:56.050> boxes<00:04:56.560> which 00:04:56.760 --> 00:04:56.770 align:start position:0% you'll see these little info boxes which 00:04:56.770 --> 00:04:59.550 align:start position:0% you'll see these little info boxes which are<00:04:56.920> somewhat<00:04:57.250> controversial<00:04:57.930> Google<00:04:58.930> grabs 00:04:59.550 --> 00:04:59.560 align:start position:0% are somewhat controversial Google grabs 00:04:59.560 --> 00:05:01.230 align:start position:0% are somewhat controversial Google grabs this<00:04:59.860> data<00:05:00.070> from<00:05:00.280> various<00:05:00.430> places<00:05:01.030> and 00:05:01.230 --> 00:05:01.240 align:start position:0% this data from various places and 00:05:01.240 --> 00:05:02.970 align:start position:0% this data from various places and actually<00:05:01.780> creates<00:05:02.080> a<00:05:02.170> summary<00:05:02.560> much<00:05:02.800> like 00:05:02.970 --> 00:05:02.980 align:start position:0% actually creates a summary much like 00:05:02.980 --> 00:05:06.810 align:start position:0% actually creates a summary much like Wikipedia<00:05:03.960> and<00:05:05.190> yeah<00:05:06.190> those<00:05:06.310> are<00:05:06.460> called<00:05:06.610> info 00:05:06.810 --> 00:05:06.820 align:start position:0% Wikipedia and yeah those are called info 00:05:06.820 --> 00:05:10.830 align:start position:0% Wikipedia and yeah those are called info boxes<00:05:07.240> so<00:05:08.140> the<00:05:08.800> thing<00:05:09.010> about<00:05:09.180> there's<00:05:10.180> a<00:05:10.240> sort 00:05:10.830 --> 00:05:10.840 align:start position:0% boxes so the thing about there's a sort 00:05:10.840 --> 00:05:13.500 align:start position:0% boxes so the thing about there's a sort of<00:05:10.870> a<00:05:10.960> conundrum<00:05:11.260> about<00:05:11.940> metadata<00:05:12.940> in<00:05:13.120> general 00:05:13.500 --> 00:05:13.510 align:start position:0% of a conundrum about metadata in general 00:05:13.510 --> 00:05:17.250 align:start position:0% of a conundrum about metadata in general is<00:05:13.740> if<00:05:14.740> if<00:05:15.130> you're<00:05:15.660> if<00:05:16.660> you're<00:05:16.720> too<00:05:17.020> loose 00:05:17.250 --> 00:05:17.260 align:start position:0% is if if you're if you're too loose 00:05:17.260 --> 00:05:20.370 align:start position:0% is if if you're if you're too loose about<00:05:17.560> it<00:05:17.800> it<00:05:18.190> it's<00:05:19.150> you're<00:05:19.510> not<00:05:19.660> clear<00:05:20.080> right 00:05:20.370 --> 00:05:20.380 align:start position:0% about it it it's you're not clear right 00:05:20.380 --> 00:05:23.580 align:start position:0% about it it it's you're not clear right a<00:05:20.830> famous<00:05:21.280> lawyer<00:05:21.520> said<00:05:22.030> what<00:05:22.720> you<00:05:22.960> know<00:05:23.080> what 00:05:23.580 --> 00:05:23.590 align:start position:0% a famous lawyer said what you know what 00:05:23.590 --> 00:05:26.210 align:start position:0% a famous lawyer said what you know what is<00:05:23.860> is<00:05:24.220> what<00:05:24.520> is<00:05:24.610> the<00:05:24.700> definition<00:05:25.150> of<00:05:25.330> is 00:05:26.210 --> 00:05:26.220 align:start position:0% is is what is the definition of is 00:05:26.220 --> 00:05:30.180 align:start position:0% is is what is the definition of is sometimes<00:05:27.220> we<00:05:27.430> can<00:05:27.580> be<00:05:27.670> unclear<00:05:28.740> so<00:05:29.740> and<00:05:30.100> it 00:05:30.180 --> 00:05:30.190 align:start position:0% sometimes we can be unclear so and it 00:05:30.190 --> 00:05:33.540 align:start position:0% sometimes we can be unclear so and it can<00:05:30.370> lead<00:05:30.490> to<00:05:30.610> ambiguity<00:05:31.140> and<00:05:32.140> if<00:05:32.980> you<00:05:33.190> over 00:05:33.540 --> 00:05:33.550 align:start position:0% can lead to ambiguity and if you over 00:05:33.550 --> 00:05:36.170 align:start position:0% can lead to ambiguity and if you over structure<00:05:34.180> data<00:05:34.900> of<00:05:35.110> course<00:05:35.320> it's<00:05:35.500> burdensome 00:05:36.170 --> 00:05:36.180 align:start position:0% structure data of course it's burdensome 00:05:36.180 --> 00:05:39.180 align:start position:0% structure data of course it's burdensome and<00:05:37.180> here's<00:05:38.020> some<00:05:38.170> well-known<00:05:38.470> phonetic 00:05:39.180 --> 00:05:39.190 align:start position:0% and here's some well-known phonetic 00:05:39.190 --> 00:05:42.330 align:start position:0% and here's some well-known phonetic characters<00:05:40.740> if<00:05:41.740> you<00:05:41.890> think<00:05:42.100> about<00:05:42.220> the 00:05:42.330 --> 00:05:42.340 align:start position:0% characters if you think about the 00:05:42.340 --> 00:05:44.550 align:start position:0% characters if you think about the personality<00:05:43.000> people<00:05:43.330> who<00:05:43.480> keep<00:05:44.290> correcting 00:05:44.550 --> 00:05:44.560 align:start position:0% personality people who keep correcting 00:05:44.560 --> 00:05:45.930 align:start position:0% personality people who keep correcting you<00:05:44.860> and<00:05:45.010> saying<00:05:45.190> you<00:05:45.250> can't<00:05:45.460> say<00:05:45.640> it<00:05:45.730> that<00:05:45.880> way 00:05:45.930 --> 00:05:45.940 align:start position:0% you and saying you can't say it that way 00:05:45.940 --> 00:05:49.190 align:start position:0% you and saying you can't say it that way you<00:05:46.360> know<00:05:46.480> this<00:05:46.770> you<00:05:47.770> can't<00:05:47.980> do<00:05:48.130> it<00:05:48.250> that<00:05:48.430> way 00:05:49.190 --> 00:05:49.200 align:start position:0% you know this you can't do it that way 00:05:49.200 --> 00:05:51.960 align:start position:0% you know this you can't do it that way too<00:05:50.200> much<00:05:50.380> structure<00:05:50.710> is<00:05:51.070> annoying<00:05:51.670> and 00:05:51.960 --> 00:05:51.970 align:start position:0% too much structure is annoying and 00:05:51.970 --> 00:05:53.670 align:start position:0% too much structure is annoying and developers<00:05:52.720> don't<00:05:52.990> want<00:05:53.140> to<00:05:53.230> deal<00:05:53.350> with<00:05:53.530> it 00:05:53.670 --> 00:05:53.680 align:start position:0% developers don't want to deal with it 00:05:53.680 --> 00:05:57.660 align:start position:0% developers don't want to deal with it right<00:05:53.830> so<00:05:55.770> let's<00:05:56.770> go<00:05:56.980> look<00:05:57.130> at<00:05:57.310> what<00:05:57.520> the 00:05:57.660 --> 00:05:57.670 align:start position:0% right so let's go look at what the 00:05:57.670 --> 00:06:00.500 align:start position:0% right so let's go look at what the Semantic<00:05:58.030> Web<00:05:58.060> is<00:05:58.240> right<00:05:58.900> highly<00:05:59.800> formalized 00:06:00.500 --> 00:06:00.510 align:start position:0% Semantic Web is right highly formalized 00:06:00.510 --> 00:06:05.640 align:start position:0% Semantic Web is right highly formalized metadata<00:06:01.510> so<00:06:02.940> it's<00:06:03.940> it's<00:06:04.630> very<00:06:04.720> strict<00:06:05.320> so 00:06:05.640 --> 00:06:05.650 align:start position:0% metadata so it's it's very strict so 00:06:05.650 --> 00:06:09.930 align:start position:0% metadata so it's it's very strict so whether<00:06:06.250> something<00:06:06.700> conforms<00:06:07.270> to<00:06:07.590> to<00:06:08.940> what 00:06:09.930 --> 00:06:09.940 align:start position:0% whether something conforms to to what 00:06:09.940 --> 00:06:11.910 align:start position:0% whether something conforms to to what what<00:06:10.270> your<00:06:10.390> ontology<00:06:10.780> is<00:06:11.110> or<00:06:11.230> not<00:06:11.320> is<00:06:11.620> really 00:06:11.910 --> 00:06:11.920 align:start position:0% what your ontology is or not is really 00:06:11.920 --> 00:06:14.850 align:start position:0% what your ontology is or not is really clear<00:06:12.690> it's<00:06:13.690> layered<00:06:13.960> on<00:06:14.140> top<00:06:14.170> of<00:06:14.500> the<00:06:14.560> open 00:06:14.850 --> 00:06:14.860 align:start position:0% clear it's layered on top of the open 00:06:14.860 --> 00:06:15.620 align:start position:0% clear it's layered on top of the open web 00:06:15.620 --> 00:06:15.630 align:start position:0% web 00:06:15.630 --> 00:06:19.320 align:start position:0% web lots<00:06:16.630> of<00:06:16.750> standards<00:06:17.170> data<00:06:17.410> and<00:06:17.770> tools<00:06:18.330> and 00:06:19.320 --> 00:06:19.330 align:start position:0% lots of standards data and tools and 00:06:19.330 --> 00:06:21.240 align:start position:0% lots of standards data and tools and here's<00:06:19.870> the<00:06:20.080> things<00:06:20.320> that<00:06:20.560> it<00:06:20.680> provides<00:06:21.010> it's 00:06:21.240 --> 00:06:21.250 align:start position:0% here's the things that it provides it's 00:06:21.250 --> 00:06:24.680 align:start position:0% here's the things that it provides it's really<00:06:21.490> important<00:06:21.910> is<00:06:22.800> there's<00:06:23.800> linkage<00:06:24.340> and 00:06:24.680 --> 00:06:24.690 align:start position:0% really important is there's linkage and 00:06:24.690 --> 00:06:28.020 align:start position:0% really important is there's linkage and there's<00:06:25.690> lots<00:06:25.960> of<00:06:26.080> reference<00:06:26.850> through<00:06:27.850> your 00:06:28.020 --> 00:06:28.030 align:start position:0% there's lots of reference through your 00:06:28.030 --> 00:06:31.950 align:start position:0% there's lots of reference through your eyes<00:06:28.860> the<00:06:29.860> other<00:06:29.890> one<00:06:30.250> is<00:06:30.430> the<00:06:31.300> descriptions 00:06:31.950 --> 00:06:31.960 align:start position:0% eyes the other one is the descriptions 00:06:31.960 --> 00:06:35.010 align:start position:0% eyes the other one is the descriptions like<00:06:32.020> how<00:06:32.260> what<00:06:32.740> things<00:06:33.010> are<00:06:33.340> and<00:06:34.020> like 00:06:35.010 --> 00:06:35.020 align:start position:0% like how what things are and like 00:06:35.020 --> 00:06:36.690 align:start position:0% like how what things are and like somebody's<00:06:35.530> a<00:06:35.560> person 00:06:36.690 --> 00:06:36.700 align:start position:0% somebody's a person 00:06:36.700 --> 00:06:38.400 align:start position:0% somebody's a person what<00:06:37.000> is<00:06:37.120> a<00:06:37.150> person<00:06:37.570> well<00:06:37.750> you<00:06:38.080> might<00:06:38.230> have<00:06:38.260> a 00:06:38.400 --> 00:06:38.410 align:start position:0% what is a person well you might have a 00:06:38.410 --> 00:06:40.440 align:start position:0% what is a person well you might have a resource<00:06:38.860> that<00:06:38.980> describes<00:06:39.610> what<00:06:39.850> a<00:06:39.880> person<00:06:40.300> is 00:06:40.440 --> 00:06:40.450 align:start position:0% resource that describes what a person is 00:06:40.450 --> 00:06:42.810 align:start position:0% resource that describes what a person is sounds<00:06:41.260> ridiculous<00:06:41.800> but<00:06:42.130> if<00:06:42.340> you<00:06:42.460> want<00:06:42.640> to<00:06:42.730> do 00:06:42.810 --> 00:06:42.820 align:start position:0% sounds ridiculous but if you want to do 00:06:42.820 --> 00:06:44.550 align:start position:0% sounds ridiculous but if you want to do something<00:06:43.030> more<00:06:43.240> automated<00:06:43.720> it<00:06:44.050> might<00:06:44.410> be 00:06:44.550 --> 00:06:44.560 align:start position:0% something more automated it might be 00:06:44.560 --> 00:06:46.500 align:start position:0% something more automated it might be good<00:06:44.680> to<00:06:44.800> know<00:06:44.950> this<00:06:45.250> object<00:06:45.490> as<00:06:45.910> a<00:06:45.940> person<00:06:46.360> in 00:06:46.500 --> 00:06:46.510 align:start position:0% good to know this object as a person in 00:06:46.510 --> 00:06:50.280 align:start position:0% good to know this object as a person in this<00:06:46.600> object<00:06:46.840> as<00:06:47.140> an<00:06:47.260> airplane<00:06:47.910> and<00:06:49.290> the 00:06:50.280 --> 00:06:50.290 align:start position:0% this object as an airplane and the 00:06:50.290 --> 00:06:53.370 align:start position:0% this object as an airplane and the deeper<00:06:50.590> side<00:06:50.920> of<00:06:51.040> it<00:06:51.130> is<00:06:51.280> reasoning<00:06:52.320> that<00:06:53.320> you 00:06:53.370 --> 00:06:53.380 align:start position:0% deeper side of it is reasoning that you 00:06:53.380 --> 00:06:54.930 align:start position:0% deeper side of it is reasoning that you structure<00:06:53.860> your<00:06:54.010> data<00:06:54.340> in<00:06:54.610> a<00:06:54.790> way<00:06:54.910> that 00:06:54.930 --> 00:06:54.940 align:start position:0% structure your data in a way that 00:06:54.940 --> 00:06:57.480 align:start position:0% structure your data in a way that something<00:06:55.450> can<00:06:55.600> reason<00:06:55.960> about<00:06:56.020> it 00:06:57.480 --> 00:06:57.490 align:start position:0% something can reason about it 00:06:57.490 --> 00:06:59.520 align:start position:0% something can reason about it and<00:06:57.730> so<00:06:58.180> here's<00:06:58.420> why<00:06:58.630> this<00:06:58.690> is<00:06:59.140> what<00:06:59.320> Tim 00:06:59.520 --> 00:06:59.530 align:start position:0% and so here's why this is what Tim 00:06:59.530 --> 00:07:00.170 align:start position:0% and so here's why this is what Tim berners-lee 00:07:00.170 --> 00:07:00.180 align:start position:0% berners-lee 00:07:00.180 --> 00:07:02.400 align:start position:0% berners-lee wanted<00:07:01.180> and<00:07:01.450> this<00:07:01.570> is<00:07:01.630> what<00:07:01.840> he<00:07:01.930> was<00:07:02.050> proposing 00:07:02.400 --> 00:07:02.410 align:start position:0% wanted and this is what he was proposing 00:07:02.410 --> 00:07:05.640 align:start position:0% wanted and this is what he was proposing this<00:07:02.770> is<00:07:02.920> why<00:07:03.250> we<00:07:03.400> all<00:07:03.520> go<00:07:03.790> through<00:07:03.820> this<00:07:04.650> this 00:07:05.640 --> 00:07:05.650 align:start position:0% this is why we all go through this this 00:07:05.650 --> 00:07:07.890 align:start position:0% this is why we all go through this this work<00:07:06.010> to<00:07:06.250> build<00:07:06.370> a<00:07:06.520> Semantic<00:07:06.910> Web<00:07:06.940> which<00:07:07.660> many 00:07:07.890 --> 00:07:07.900 align:start position:0% work to build a Semantic Web which many 00:07:07.900 --> 00:07:10.980 align:start position:0% work to build a Semantic Web which many people<00:07:07.990> didn't<00:07:08.470> and<00:07:09.370> ideas<00:07:10.150> software<00:07:10.540> agents 00:07:10.980 --> 00:07:10.990 align:start position:0% people didn't and ideas software agents 00:07:10.990 --> 00:07:15.630 align:start position:0% people didn't and ideas software agents that's<00:07:11.320> a<00:07:11.500> big<00:07:11.650> one<00:07:13.470> the<00:07:14.470> the<00:07:15.130> notion<00:07:15.340> was<00:07:15.610> that 00:07:15.630 --> 00:07:15.640 align:start position:0% that's a big one the the notion was that 00:07:15.640 --> 00:07:17.610 align:start position:0% that's a big one the the notion was that when<00:07:16.540> if<00:07:16.690> we<00:07:16.720> all<00:07:16.930> have<00:07:17.080> the<00:07:17.200> structured<00:07:17.590> data 00:07:17.610 --> 00:07:17.620 align:start position:0% when if we all have the structured data 00:07:17.620 --> 00:07:19.560 align:start position:0% when if we all have the structured data out<00:07:17.920> there<00:07:18.100> something<00:07:18.430> could<00:07:18.790> comprehend<00:07:19.450> it 00:07:19.560 --> 00:07:19.570 align:start position:0% out there something could comprehend it 00:07:19.570 --> 00:07:22.860 align:start position:0% out there something could comprehend it and<00:07:19.750> create<00:07:21.090> automated<00:07:22.090> services<00:07:22.540> for<00:07:22.750> us 00:07:22.860 --> 00:07:22.870 align:start position:0% and create automated services for us 00:07:22.870 --> 00:07:27.030 align:start position:0% and create automated services for us arrange<00:07:23.740> airplane<00:07:24.400> flights<00:07:24.730> agents<00:07:26.040> things 00:07:27.030 --> 00:07:27.040 align:start position:0% arrange airplane flights agents things 00:07:27.040 --> 00:07:31.620 align:start position:0% arrange airplane flights agents things like<00:07:27.250> that<00:07:28.050> and<00:07:29.250> I<00:07:30.250> think<00:07:30.640> I<00:07:31.030> think<00:07:31.330> one<00:07:31.450> of<00:07:31.480> the 00:07:31.620 --> 00:07:31.630 align:start position:0% like that and I think I think one of the 00:07:31.630 --> 00:07:33.870 align:start position:0% like that and I think I think one of the more<00:07:31.990> interesting<00:07:32.230> aspects<00:07:32.830> of<00:07:32.980> it<00:07:33.070> was<00:07:33.250> like 00:07:33.870 --> 00:07:33.880 align:start position:0% more interesting aspects of it was like 00:07:33.880 --> 00:07:36.150 align:start position:0% more interesting aspects of it was like an<00:07:34.000> ecosystem<00:07:34.270> a<00:07:34.750> value<00:07:35.110> chain<00:07:35.320> of<00:07:35.350> data<00:07:35.680> if 00:07:36.150 --> 00:07:36.160 align:start position:0% an ecosystem a value chain of data if 00:07:36.160 --> 00:07:38.730 align:start position:0% an ecosystem a value chain of data if all<00:07:36.370> the<00:07:36.490> data<00:07:36.670> is<00:07:36.880> more<00:07:37.600> formally<00:07:38.170> connected 00:07:38.730 --> 00:07:38.740 align:start position:0% all the data is more formally connected 00:07:38.740 --> 00:07:40.860 align:start position:0% all the data is more formally connected you<00:07:39.310> can<00:07:39.340> you<00:07:39.850> can<00:07:39.970> build<00:07:40.120> things<00:07:40.450> on<00:07:40.630> top<00:07:40.810> of 00:07:40.860 --> 00:07:40.870 align:start position:0% you can you can build things on top of 00:07:40.870 --> 00:07:43.650 align:start position:0% you can you can build things on top of it<00:07:41.080> reliably<00:07:41.590> and<00:07:41.920> in<00:07:42.550> a<00:07:42.670> way<00:07:42.820> that's<00:07:43.090> one<00:07:43.540> of 00:07:43.650 --> 00:07:43.660 align:start position:0% it reliably and in a way that's one of 00:07:43.660 --> 00:07:47.430 align:start position:0% it reliably and in a way that's one of the<00:07:43.750> great<00:07:43.960> benefits<00:07:44.080> of<00:07:44.530> smart<00:07:44.860> contracts<00:07:46.440> so 00:07:47.430 --> 00:07:47.440 align:start position:0% the great benefits of smart contracts so 00:07:47.440 --> 00:07:49.530 align:start position:0% the great benefits of smart contracts so I<00:07:47.800> give<00:07:48.430> you<00:07:48.460> that<00:07:48.640> I'm<00:07:48.790> gonna<00:07:49.060> go<00:07:49.330> over<00:07:49.420> a 00:07:49.530 --> 00:07:49.540 align:start position:0% I give you that I'm gonna go over a 00:07:49.540 --> 00:07:53.010 align:start position:0% I give you that I'm gonna go over a interesting<00:07:50.530> example<00:07:51.330> some<00:07:52.330> there's<00:07:52.690> a<00:07:52.750> tool 00:07:53.010 --> 00:07:53.020 align:start position:0% interesting example some there's a tool 00:07:53.020 --> 00:07:55.140 align:start position:0% interesting example some there's a tool called<00:07:53.050> Protege<00:07:53.980> and<00:07:54.250> that's<00:07:54.790> how<00:07:54.880> you<00:07:54.940> create 00:07:55.140 --> 00:07:55.150 align:start position:0% called Protege and that's how you create 00:07:55.150 --> 00:07:58.170 align:start position:0% called Protege and that's how you create ontology<00:07:55.660> and<00:07:56.580> Protege<00:07:57.580> that<00:07:57.820> people<00:07:58.060> did 00:07:58.170 --> 00:07:58.180 align:start position:0% ontology and Protege that people did 00:07:58.180 --> 00:08:00.870 align:start position:0% ontology and Protege that people did projet<00:07:58.510> did<00:07:58.720> really<00:07:58.930> humorous<00:07:59.880> ontology 00:08:00.870 --> 00:08:00.880 align:start position:0% projet did really humorous ontology 00:08:00.880 --> 00:08:03.330 align:start position:0% projet did really humorous ontology called<00:08:01.240> pizza<00:08:01.630> and<00:08:01.840> this<00:08:02.590> this<00:08:03.010> pizza 00:08:03.330 --> 00:08:03.340 align:start position:0% called pizza and this this pizza 00:08:03.340 --> 00:08:06.900 align:start position:0% called pizza and this this pizza ontology<00:08:03.730> will<00:08:04.480> help<00:08:04.630> you<00:08:04.780> bake<00:08:05.020> the<00:08:05.910> perfect 00:08:06.900 --> 00:08:06.910 align:start position:0% ontology will help you bake the perfect 00:08:06.910 --> 00:08:09.390 align:start position:0% ontology will help you bake the perfect pizza<00:08:07.120> data<00:08:07.480> and<00:08:07.840> you<00:08:08.500> can't<00:08:08.710> violate<00:08:09.130> it<00:08:09.280> like 00:08:09.390 --> 00:08:09.400 align:start position:0% pizza data and you can't violate it like 00:08:09.400 --> 00:08:11.040 align:start position:0% pizza data and you can't violate it like you<00:08:09.520> can't<00:08:09.700> put<00:08:09.910> a<00:08:09.940> hamburger<00:08:10.300> bun<00:08:10.570> on<00:08:10.690> top<00:08:10.900> of 00:08:11.040 --> 00:08:11.050 align:start position:0% you can't put a hamburger bun on top of 00:08:11.050 --> 00:08:13.050 align:start position:0% you can't put a hamburger bun on top of that<00:08:11.140> thing<00:08:11.410> and<00:08:11.950> call<00:08:12.190> it<00:08:12.310> a<00:08:12.340> pizza<00:08:12.550> and<00:08:12.970> you 00:08:13.050 --> 00:08:13.060 align:start position:0% that thing and call it a pizza and you 00:08:13.060 --> 00:08:15.690 align:start position:0% that thing and call it a pizza and you can<00:08:13.870> actually<00:08:14.170> validate<00:08:14.560> this<00:08:15.070> verify<00:08:15.640> this 00:08:15.690 --> 00:08:15.700 align:start position:0% can actually validate this verify this 00:08:15.700 --> 00:08:23.940 align:start position:0% can actually validate this verify this thing<00:08:16.770> so<00:08:18.690> think<00:08:19.690> about<00:08:19.750> linkage<00:08:22.650> so<00:08:23.650> here's 00:08:23.940 --> 00:08:23.950 align:start position:0% thing so think about linkage so here's 00:08:23.950 --> 00:08:25.590 align:start position:0% thing so think about linkage so here's some<00:08:24.100> standards<00:08:24.460> that<00:08:24.610> that<00:08:25.030> deal<00:08:25.450> with 00:08:25.590 --> 00:08:25.600 align:start position:0% some standards that that deal with 00:08:25.600 --> 00:08:27.060 align:start position:0% some standards that that deal with linkage<00:08:25.990> and<00:08:26.170> you<00:08:26.230> have<00:08:26.320> your<00:08:26.530> eyes<00:08:26.590> which 00:08:27.060 --> 00:08:27.070 align:start position:0% linkage and you have your eyes which 00:08:27.070 --> 00:08:28.290 align:start position:0% linkage and you have your eyes which we're<00:08:27.220> all<00:08:27.340> familiar<00:08:27.550> with<00:08:27.820> but<00:08:28.090> it's 00:08:28.290 --> 00:08:28.300 align:start position:0% we're all familiar with but it's 00:08:28.300 --> 00:08:30.270 align:start position:0% we're all familiar with but it's actually<00:08:28.630> a<00:08:28.660> really<00:08:28.780> specific<00:08:29.260> way<00:08:29.950> to<00:08:29.980> use 00:08:30.270 --> 00:08:30.280 align:start position:0% actually a really specific way to use 00:08:30.280 --> 00:08:34.320 align:start position:0% actually a really specific way to use your<00:08:30.460> eyes<00:08:30.840> and<00:08:31.840> XML<00:08:32.800> namespaces<00:08:33.370> and<00:08:33.820> you've 00:08:34.320 --> 00:08:34.330 align:start position:0% your eyes and XML namespaces and you've 00:08:34.330 --> 00:08:35.640 align:start position:0% your eyes and XML namespaces and you've probably<00:08:34.540> seen<00:08:34.870> these<00:08:35.050> things<00:08:35.320> in<00:08:35.500> a<00:08:35.530> lot<00:08:35.620> of 00:08:35.640 --> 00:08:35.650 align:start position:0% probably seen these things in a lot of 00:08:35.650 --> 00:08:37.770 align:start position:0% probably seen these things in a lot of HTML<00:08:36.130> you<00:08:36.250> don't<00:08:36.430> know<00:08:36.520> what<00:08:36.669> they<00:08:36.790> are<00:08:36.970> but 00:08:37.770 --> 00:08:37.780 align:start position:0% HTML you don't know what they are but 00:08:37.780 --> 00:08:41.640 align:start position:0% HTML you don't know what they are but essentially<00:08:38.710> these<00:08:39.040> are<00:08:39.150> defining<00:08:40.290> with<00:08:41.290> with 00:08:41.640 --> 00:08:41.650 align:start position:0% essentially these are defining with with 00:08:41.650 --> 00:08:43.880 align:start position:0% essentially these are defining with with these<00:08:41.770> your<00:08:41.979> eyes<00:08:42.160> what<00:08:42.940> these<00:08:43.210> names 00:08:43.880 --> 00:08:43.890 align:start position:0% these your eyes what these names 00:08:43.890 --> 00:08:47.190 align:start position:0% these your eyes what these names namespaces<00:08:44.890> are<00:08:45.040> as<00:08:45.280> they're<00:08:45.610> used<00:08:45.850> later<00:08:46.270> on 00:08:47.190 --> 00:08:47.200 align:start position:0% namespaces are as they're used later on 00:08:47.200 --> 00:08:49.650 align:start position:0% namespaces are as they're used later on this<00:08:47.290> HTML<00:08:47.920> or<00:08:48.340> in<00:08:48.520> this<00:08:48.610> case<00:08:48.820> in<00:08:49.060> this<00:08:49.150> RDF 00:08:49.650 --> 00:08:49.660 align:start position:0% this HTML or in this case in this RDF 00:08:49.660 --> 00:08:53.160 align:start position:0% this HTML or in this case in this RDF and<00:08:50.730> you<00:08:51.730> can<00:08:51.880> see<00:08:52.030> down<00:08:52.210> here<00:08:52.240> how<00:08:52.600> there<00:08:52.780> lies 00:08:53.160 --> 00:08:53.170 align:start position:0% and you can see down here how there lies 00:08:53.170 --> 00:08:56.040 align:start position:0% and you can see down here how there lies how<00:08:53.470> these<00:08:53.620> namespaces<00:08:54.310> are<00:08:54.340> utilized<00:08:55.050> like 00:08:56.040 --> 00:08:56.050 align:start position:0% how these namespaces are utilized like 00:08:56.050 --> 00:08:57.120 align:start position:0% how these namespaces are utilized like right<00:08:56.260> there<00:08:56.440> you<00:08:56.560> have<00:08:56.620> a<00:08:56.680> Creative<00:08:57.100> Commons 00:08:57.120 --> 00:08:57.130 align:start position:0% right there you have a Creative Commons 00:08:57.130 --> 00:08:59.550 align:start position:0% right there you have a Creative Commons license<00:08:57.910> and<00:08:58.150> you<00:08:58.690> see<00:08:58.900> what<00:08:59.020> their<00:08:59.170> terms 00:08:59.550 --> 00:08:59.560 align:start position:0% license and you see what their terms 00:08:59.560 --> 00:09:01.860 align:start position:0% license and you see what their terms license<00:09:00.370> what<00:09:00.610> is<00:09:00.700> a<00:09:00.730> turn<00:09:01.150> what<00:09:01.450> are<00:09:01.570> terms 00:09:01.860 --> 00:09:01.870 align:start position:0% license what is a turn what are terms 00:09:01.870 --> 00:09:04.200 align:start position:0% license what is a turn what are terms what<00:09:02.260> is<00:09:02.350> a<00:09:02.380> license<00:09:02.950> well<00:09:03.640> something 00:09:04.200 --> 00:09:04.210 align:start position:0% what is a license well something 00:09:04.210 --> 00:09:07.650 align:start position:0% what is a license well something automated<00:09:04.780> can<00:09:05.350> go<00:09:05.560> up<00:09:05.770> here<00:09:05.800> and<00:09:06.670> and<00:09:07.060> look<00:09:07.450> at 00:09:07.650 --> 00:09:07.660 align:start position:0% automated can go up here and and look at 00:09:07.660 --> 00:09:11.940 align:start position:0% automated can go up here and and look at and<00:09:08.140> and<00:09:09.130> go<00:09:09.520> to<00:09:09.580> that<00:09:09.820> URL<00:09:10.420> and<00:09:11.320> go<00:09:11.530> find<00:09:11.800> out 00:09:11.940 --> 00:09:11.950 align:start position:0% and and go to that URL and go find out 00:09:11.950 --> 00:09:14.460 align:start position:0% and and go to that URL and go find out what<00:09:12.220> terms<00:09:12.520> are<00:09:12.820> and<00:09:13.090> if<00:09:13.600> you<00:09:13.750> go<00:09:13.930> to<00:09:13.990> that<00:09:14.200> URL 00:09:14.460 --> 00:09:14.470 align:start position:0% what terms are and if you go to that URL 00:09:14.470 --> 00:09:17.520 align:start position:0% what terms are and if you go to that URL about<00:09:14.920> terms<00:09:15.280> you<00:09:15.880> can<00:09:16.060> learn<00:09:16.330> and<00:09:16.660> see<00:09:17.200> data 00:09:17.520 --> 00:09:17.530 align:start position:0% about terms you can learn and see data 00:09:17.530 --> 00:09:20.190 align:start position:0% about terms you can learn and see data about<00:09:18.340> what<00:09:18.580> those<00:09:18.730> terms<00:09:19.000> are<00:09:19.210> if<00:09:19.750> that<00:09:19.840> you 00:09:20.190 --> 00:09:20.200 align:start position:0% about what those terms are if that you 00:09:20.200 --> 00:09:22.860 align:start position:0% about what those terms are if that you will<00:09:20.410> still<00:09:20.770> works<00:09:21.390> that's<00:09:22.390> the<00:09:22.450> problem<00:09:22.720> with 00:09:22.860 --> 00:09:22.870 align:start position:0% will still works that's the problem with 00:09:22.870 --> 00:09:24.630 align:start position:0% will still works that's the problem with the<00:09:22.930> web<00:09:23.110> is<00:09:23.320> the<00:09:23.350> VC<00:09:23.800> rules<00:09:24.010> might<00:09:24.220> not<00:09:24.400> work 00:09:24.630 --> 00:09:24.640 align:start position:0% the web is the VC rules might not work 00:09:24.640 --> 00:09:28.820 align:start position:0% the web is the VC rules might not work any<00:09:24.820> more<00:09:25.170> often<00:09:26.170> on<00:09:26.470> these<00:09:27.340> servers<00:09:27.730> go<00:09:27.910> down 00:09:28.820 --> 00:09:28.830 align:start position:0% any more often on these servers go down 00:09:28.830 --> 00:09:32.850 align:start position:0% any more often on these servers go down so<00:09:29.830> descriptive<00:09:30.160> meaning<00:09:31.290> it's<00:09:32.290> it's 00:09:32.850 --> 00:09:32.860 align:start position:0% so descriptive meaning it's it's 00:09:32.860 --> 00:09:35.100 align:start position:0% so descriptive meaning it's it's essentially<00:09:33.370> symbols<00:09:33.910> like<00:09:34.480> what<00:09:34.690> what<00:09:34.990> is 00:09:35.100 --> 00:09:35.110 align:start position:0% essentially symbols like what what is 00:09:35.110 --> 00:09:36.600 align:start position:0% essentially symbols like what what is describing<00:09:35.650> what<00:09:35.860> what<00:09:36.100> is<00:09:36.190> the<00:09:36.430> name<00:09:36.580> of 00:09:36.600 --> 00:09:36.610 align:start position:0% describing what what is the name of 00:09:36.610 --> 00:09:39.210 align:start position:0% describing what what is the name of something<00:09:37.000> and<00:09:37.510> it<00:09:38.020> seems<00:09:38.560> silly<00:09:38.860> to<00:09:39.070> us 00:09:39.210 --> 00:09:39.220 align:start position:0% something and it seems silly to us 00:09:39.220 --> 00:09:40.860 align:start position:0% something and it seems silly to us because<00:09:39.460> we<00:09:39.670> just<00:09:39.700> talk<00:09:40.060> when<00:09:40.360> we<00:09:40.450> understand 00:09:40.860 --> 00:09:40.870 align:start position:0% because we just talk when we understand 00:09:40.870 --> 00:09:44.820 align:start position:0% because we just talk when we understand this<00:09:40.960> stuff<00:09:41.170> but<00:09:42.060> you<00:09:43.060> know<00:09:43.830> something 00:09:44.820 --> 00:09:44.830 align:start position:0% this stuff but you know something 00:09:44.830 --> 00:09:48.630 align:start position:0% this stuff but you know something automated<00:09:45.280> really<00:09:45.840> it's<00:09:46.840> it<00:09:47.560> has<00:09:47.830> to<00:09:48.010> know<00:09:48.190> so 00:09:48.630 --> 00:09:48.640 align:start position:0% automated really it's it has to know so 00:09:48.640 --> 00:09:50.730 align:start position:0% automated really it's it has to know so an<00:09:49.300> assertion<00:09:49.630> that<00:09:50.050> we<00:09:50.140> might<00:09:50.320> make<00:09:50.350> is<00:09:50.560> Los 00:09:50.730 --> 00:09:50.740 align:start position:0% an assertion that we might make is Los 00:09:50.740 --> 00:09:53.910 align:start position:0% an assertion that we might make is Los Angeles<00:09:51.130> it<00:09:51.280> is<00:09:51.730> a<00:09:51.850> city<00:09:52.380> the<00:09:53.380> assertion<00:09:53.830> on<00:09:53.860> a 00:09:53.910 --> 00:09:53.920 align:start position:0% Angeles it is a city the assertion on a 00:09:53.920 --> 00:09:56.550 align:start position:0% Angeles it is a city the assertion on a Semantic<00:09:54.370> Web<00:09:54.400> would<00:09:55.030> be<00:09:55.410> broken<00:09:56.410> up<00:09:56.530> like 00:09:56.550 --> 00:09:56.560 align:start position:0% Semantic Web would be broken up like 00:09:56.560 --> 00:09:59.880 align:start position:0% Semantic Web would be broken up like this<00:09:57.060> subject<00:09:58.060> predicate<00:09:58.390> object<00:09:59.170> this 00:09:59.880 --> 00:09:59.890 align:start position:0% this subject predicate object this 00:09:59.890 --> 00:10:02.160 align:start position:0% this subject predicate object this object<00:09:59.950> is<00:10:00.460> a<00:10:00.490> URI<00:10:00.820> it's<00:10:01.390> really<00:10:01.630> clear<00:10:01.900> what 00:10:02.160 --> 00:10:02.170 align:start position:0% object is a URI it's really clear what 00:10:02.170 --> 00:10:05.160 align:start position:0% object is a URI it's really clear what Los<00:10:02.830> Angeles<00:10:03.310> is<00:10:03.460> it's<00:10:03.670> a<00:10:03.760> type<00:10:04.000> of<00:10:04.030> and<00:10:04.540> all 00:10:05.160 --> 00:10:05.170 align:start position:0% Los Angeles is it's a type of and all 00:10:05.170 --> 00:10:07.470 align:start position:0% Los Angeles is it's a type of and all this<00:10:05.380> stuff<00:10:05.680> right<00:10:05.890> here<00:10:06.160> this<00:10:06.430> is<00:10:06.670> at<00:10:07.390> the 00:10:07.470 --> 00:10:07.480 align:start position:0% this stuff right here this is at the 00:10:07.480 --> 00:10:10.470 align:start position:0% this stuff right here this is at the basis<00:10:07.990> of<00:10:08.170> a<00:10:08.230> stinner<00:10:08.470> called<00:10:08.740> RDF<00:10:09.330> this<00:10:10.330> is 00:10:10.470 --> 00:10:10.480 align:start position:0% basis of a stinner called RDF this is 00:10:10.480 --> 00:10:12.960 align:start position:0% basis of a stinner called RDF this is all<00:10:10.660> the<00:10:10.780> triple<00:10:11.050> and<00:10:11.400> RDF<00:10:12.400> is<00:10:12.580> all<00:10:12.730> about 00:10:12.960 --> 00:10:12.970 align:start position:0% all the triple and RDF is all about 00:10:12.970 --> 00:10:16.530 align:start position:0% all the triple and RDF is all about declaring<00:10:13.660> many<00:10:14.440> many<00:10:14.830> many<00:10:15.130> triples<00:10:15.610> to 00:10:16.530 --> 00:10:16.540 align:start position:0% declaring many many many triples to 00:10:16.540 --> 00:10:18.300 align:start position:0% declaring many many many triples to create<00:10:17.170> something<00:10:17.470> that's<00:10:17.530> meaningful<00:10:17.770> and 00:10:18.300 --> 00:10:18.310 align:start position:0% create something that's meaningful and 00:10:18.310 --> 00:10:24.440 align:start position:0% create something that's meaningful and and<00:10:19.150> then<00:10:19.690> it<00:10:19.810> even<00:10:19.900> connects<00:10:21.510> so<00:10:23.070> just 00:10:24.440 --> 00:10:24.450 align:start position:0% and then it even connects so just 00:10:24.450 --> 00:10:27.270 align:start position:0% and then it even connects so just descriptive<00:10:25.450> meaning<00:10:25.930> standards<00:10:26.350> how<00:10:26.530> how<00:10:27.130> it 00:10:27.270 --> 00:10:27.280 align:start position:0% descriptive meaning standards how how it 00:10:27.280 --> 00:10:29.070 align:start position:0% descriptive meaning standards how how it would<00:10:27.520> be<00:10:27.670> expressed<00:10:28.180> in<00:10:28.330> the<00:10:28.420> pizza<00:10:28.630> ontology 00:10:29.070 --> 00:10:29.080 align:start position:0% would be expressed in the pizza ontology 00:10:29.080 --> 00:10:31.140 align:start position:0% would be expressed in the pizza ontology so<00:10:29.860> you<00:10:29.920> have<00:10:30.070> toppings<00:10:30.580> right<00:10:30.790> you<00:10:30.910> want<00:10:31.060> to 00:10:31.140 --> 00:10:31.150 align:start position:0% so you have toppings right you want to 00:10:31.150 --> 00:10:32.520 align:start position:0% so you have toppings right you want to talk<00:10:31.300> about<00:10:31.420> what<00:10:31.630> a<00:10:31.660> topping<00:10:32.080> is<00:10:32.260> it's<00:10:32.470> a 00:10:32.520 --> 00:10:32.530 align:start position:0% talk about what a topping is it's a 00:10:32.530 --> 00:10:34.020 align:start position:0% talk about what a topping is it's a functional<00:10:32.980> property<00:10:33.400> an<00:10:33.520> ingredient<00:10:33.940> of 00:10:34.020 --> 00:10:34.030 align:start position:0% functional property an ingredient of 00:10:34.030 --> 00:10:37.770 align:start position:0% functional property an ingredient of pizza<00:10:34.710> and<00:10:35.710> this<00:10:36.100> is<00:10:36.310> how<00:10:36.490> you<00:10:36.550> would<00:10:36.850> declare 00:10:37.770 --> 00:10:37.780 align:start position:0% pizza and this is how you would declare 00:10:37.780 --> 00:10:40.080 align:start position:0% pizza and this is how you would declare that<00:10:37.960> for<00:10:38.230> a<00:10:38.260> machine<00:10:38.650> a<00:10:38.920> machine<00:10:39.910> could 00:10:40.080 --> 00:10:40.090 align:start position:0% that for a machine a machine could 00:10:40.090 --> 00:10:41.820 align:start position:0% that for a machine a machine could possibly<00:10:40.660> understand<00:10:41.140> what<00:10:41.170> a<00:10:41.260> topping<00:10:41.680> is 00:10:41.820 --> 00:10:41.830 align:start position:0% possibly understand what a topping is 00:10:41.830 --> 00:10:43.440 align:start position:0% possibly understand what a topping is not<00:10:42.340> that<00:10:42.460> the<00:10:42.550> Machine<00:10:42.790> understands<00:10:43.240> what<00:10:43.390> a 00:10:43.440 --> 00:10:43.450 align:start position:0% not that the Machine understands what a 00:10:43.450 --> 00:10:45.210 align:start position:0% not that the Machine understands what a topping<00:10:43.840> is<00:10:43.960> but<00:10:44.590> the<00:10:44.680> machine<00:10:44.950> would<00:10:45.040> be<00:10:45.100> able 00:10:45.210 --> 00:10:45.220 align:start position:0% topping is but the machine would be able 00:10:45.220 --> 00:10:47.850 align:start position:0% topping is but the machine would be able to<00:10:45.340> interact<00:10:45.640> with<00:10:45.910> topping<00:10:46.870> data<00:10:47.140> in<00:10:47.410> a<00:10:47.740> way 00:10:47.850 --> 00:10:47.860 align:start position:0% to interact with topping data in a way 00:10:47.860 --> 00:10:53.610 align:start position:0% to interact with topping data in a way that<00:10:48.070> is<00:10:48.570> reasonable<00:10:49.570> right<00:10:51.810> it's<00:10:52.810> as<00:10:53.200> a 00:10:53.610 --> 00:10:53.620 align:start position:0% that is reasonable right it's as a 00:10:53.620 --> 00:10:56.300 align:start position:0% that is reasonable right it's as a developer<00:10:54.250> it<00:10:54.520> seems<00:10:55.300> ridiculous<00:10:55.810> however 00:10:56.300 --> 00:10:56.310 align:start position:0% developer it seems ridiculous however 00:10:56.310 --> 00:11:00.210 align:start position:0% developer it seems ridiculous however that<00:10:57.310> you<00:10:57.460> go<00:10:57.670> through<00:10:57.820> this<00:10:57.970> effort<00:10:58.390> to<00:10:59.170> help 00:11:00.210 --> 00:11:00.220 align:start position:0% that you go through this effort to help 00:11:00.220 --> 00:11:04.559 align:start position:0% that you go through this effort to help something<00:11:00.699> automated<00:11:03.000> so<00:11:04.000> to<00:11:04.120> take<00:11:04.269> it<00:11:04.449> one 00:11:04.559 --> 00:11:04.569 align:start position:0% something automated so to take it one 00:11:04.569 --> 00:11:06.629 align:start position:0% something automated so to take it one step<00:11:04.810> further<00:11:05.019> and<00:11:05.350> it<00:11:05.440> gets<00:11:05.889> further<00:11:06.250> and 00:11:06.629 --> 00:11:06.639 align:start position:0% step further and it gets further and 00:11:06.639 --> 00:11:08.069 align:start position:0% step further and it gets further and further<00:11:06.819> and<00:11:07.120> deeper<00:11:07.420> and<00:11:07.509> deeper<00:11:07.569> the<00:11:07.899> more 00:11:08.069 --> 00:11:08.079 align:start position:0% further and deeper and deeper the more 00:11:08.079 --> 00:11:11.490 align:start position:0% further and deeper and deeper the more you<00:11:08.139> dig<00:11:08.350> in<00:11:08.670> structural<00:11:09.670> meaning<00:11:10.319> to<00:11:11.319> be<00:11:11.440> able 00:11:11.490 --> 00:11:11.500 align:start position:0% you dig in structural meaning to be able 00:11:11.500 --> 00:11:13.079 align:start position:0% you dig in structural meaning to be able to<00:11:11.649> reason<00:11:12.370> about<00:11:12.579> something<00:11:12.910> you<00:11:12.970> have<00:11:13.060> to 00:11:13.079 --> 00:11:13.089 align:start position:0% to reason about something you have to 00:11:13.089 --> 00:11:15.269 align:start position:0% to reason about something you have to know<00:11:13.300> how<00:11:13.509> these<00:11:13.779> things<00:11:13.839> might<00:11:14.259> relate<00:11:14.769> how 00:11:15.269 --> 00:11:15.279 align:start position:0% know how these things might relate how 00:11:15.279 --> 00:11:16.769 align:start position:0% know how these things might relate how these<00:11:15.459> entities<00:11:15.940> that<00:11:16.329> you're<00:11:16.420> talking<00:11:16.600> about 00:11:16.769 --> 00:11:16.779 align:start position:0% these entities that you're talking about 00:11:16.779 --> 00:11:19.740 align:start position:0% these entities that you're talking about pizza<00:11:17.110> toppings<00:11:17.860> mushrooms<00:11:18.519> how<00:11:19.360> they<00:11:19.569> might 00:11:19.740 --> 00:11:19.750 align:start position:0% pizza toppings mushrooms how they might 00:11:19.750 --> 00:11:22.650 align:start position:0% pizza toppings mushrooms how they might relate<00:11:19.930> and<00:11:20.290> what<00:11:20.949> is<00:11:21.069> appropriate<00:11:21.730> like<00:11:22.480> it 00:11:22.650 --> 00:11:22.660 align:start position:0% relate and what is appropriate like it 00:11:22.660 --> 00:11:24.960 align:start position:0% relate and what is appropriate like it might<00:11:22.870> not<00:11:23.019> be<00:11:23.110> appropriate<00:11:23.199> to<00:11:24.069> put<00:11:24.279> a<00:11:24.519> pizza 00:11:24.960 --> 00:11:24.970 align:start position:0% might not be appropriate to put a pizza 00:11:24.970 --> 00:11:26.910 align:start position:0% might not be appropriate to put a pizza as<00:11:25.300> a<00:11:25.360> topping<00:11:25.810> on<00:11:25.899> top<00:11:25.959> of<00:11:26.230> a<00:11:26.319> mushroom<00:11:26.439> and 00:11:26.910 --> 00:11:26.920 align:start position:0% as a topping on top of a mushroom and 00:11:26.920 --> 00:11:30.139 align:start position:0% as a topping on top of a mushroom and still<00:11:27.879> call<00:11:28.060> it<00:11:28.089> a<00:11:28.209> pizza<00:11:28.509> that's<00:11:28.810> not<00:11:28.990> valid 00:11:30.139 --> 00:11:30.149 align:start position:0% still call it a pizza that's not valid 00:11:30.149 --> 00:11:32.490 align:start position:0% still call it a pizza that's not valid to<00:11:31.149> us<00:11:31.240> that's<00:11:31.420> ridiculous<00:11:31.899> but<00:11:32.050> to<00:11:32.199> a<00:11:32.230> machine 00:11:32.490 --> 00:11:32.500 align:start position:0% to us that's ridiculous but to a machine 00:11:32.500 --> 00:11:34.530 align:start position:0% to us that's ridiculous but to a machine that<00:11:32.740> really<00:11:33.069> might<00:11:33.310> count<00:11:33.610> if<00:11:33.759> it's<00:11:33.850> making 00:11:34.530 --> 00:11:34.540 align:start position:0% that really might count if it's making 00:11:34.540 --> 00:11:38.129 align:start position:0% that really might count if it's making pizza<00:11:34.990> so<00:11:36.060> here's<00:11:37.060> how<00:11:37.209> the<00:11:37.269> stander<00:11:37.899> might 00:11:38.129 --> 00:11:38.139 align:start position:0% pizza so here's how the stander might 00:11:38.139 --> 00:11:40.889 align:start position:0% pizza so here's how the stander might come<00:11:38.410> come<00:11:39.069> about<00:11:39.310> there's<00:11:39.899> there's 00:11:40.889 --> 00:11:40.899 align:start position:0% come come about there's there's 00:11:40.899 --> 00:11:44.879 align:start position:0% come come about there's there's something<00:11:41.139> in<00:11:41.670> in<00:11:42.670> the<00:11:43.569> ontology<00:11:43.930> standard 00:11:44.879 --> 00:11:44.889 align:start position:0% something in in the ontology standard 00:11:44.889 --> 00:11:46.199 align:start position:0% something in in the ontology standard w3c<00:11:45.759> owl 00:11:46.199 --> 00:11:46.209 align:start position:0% w3c owl 00:11:46.209 --> 00:11:48.960 align:start position:0% w3c owl it's<00:11:46.449> called<00:11:46.660> transitive<00:11:47.230> property<00:11:47.519> now<00:11:48.519> here 00:11:48.960 --> 00:11:48.970 align:start position:0% it's called transitive property now here 00:11:48.970 --> 00:11:51.720 align:start position:0% it's called transitive property now here this<00:11:49.329> is<00:11:49.389> the<00:11:49.750> almost<00:11:50.560> philosophical<00:11:51.399> notion 00:11:51.720 --> 00:11:51.730 align:start position:0% this is the almost philosophical notion 00:11:51.730 --> 00:11:52.230 align:start position:0% this is the almost philosophical notion about<00:11:51.850> it 00:11:52.230 --> 00:11:52.240 align:start position:0% about it 00:11:52.240 --> 00:11:54.300 align:start position:0% about it what<00:11:52.629> is<00:11:52.779> philosophical<00:11:53.500> ingredients<00:11:54.250> of 00:11:54.300 --> 00:11:54.310 align:start position:0% what is philosophical ingredients of 00:11:54.310 --> 00:11:56.300 align:start position:0% what is philosophical ingredients of ingredients<00:11:54.759> are<00:11:54.819> ingredients<00:11:55.180> of<00:11:55.360> the<00:11:55.449> whole 00:11:56.300 --> 00:11:56.310 align:start position:0% ingredients are ingredients of the whole 00:11:56.310 --> 00:11:59.910 align:start position:0% ingredients are ingredients of the whole and<00:11:57.660> the<00:11:58.660> idea<00:11:58.870> is<00:11:58.930> that<00:11:58.959> you<00:11:59.259> have<00:11:59.829> an 00:11:59.910 --> 00:11:59.920 align:start position:0% and the idea is that you have an 00:11:59.920 --> 00:12:01.619 align:start position:0% and the idea is that you have an ingredient<00:12:00.160> on<00:12:00.430> a<00:12:00.490> pizza<00:12:00.730> then<00:12:01.240> agreement<00:12:01.569> me 00:12:01.619 --> 00:12:01.629 align:start position:0% ingredient on a pizza then agreement me 00:12:01.629 --> 00:12:03.629 align:start position:0% ingredient on a pizza then agreement me have<00:12:01.750> a<00:12:01.779> sub<00:12:02.050> ingredient<00:12:02.589> but<00:12:03.220> that<00:12:03.370> sub 00:12:03.629 --> 00:12:03.639 align:start position:0% have a sub ingredient but that sub 00:12:03.639 --> 00:12:05.189 align:start position:0% have a sub ingredient but that sub ingredient<00:12:04.120> is<00:12:04.240> still<00:12:04.449> an<00:12:04.600> ingredient<00:12:05.019> of<00:12:05.110> the 00:12:05.189 --> 00:12:05.199 align:start position:0% ingredient is still an ingredient of the 00:12:05.199 --> 00:12:07.230 align:start position:0% ingredient is still an ingredient of the pizza<00:12:05.380> and<00:12:05.769> it's<00:12:06.250> amazing<00:12:06.639> but<00:12:06.730> you<00:12:06.850> have<00:12:07.029> to 00:12:07.230 --> 00:12:07.240 align:start position:0% pizza and it's amazing but you have to 00:12:07.240 --> 00:12:09.660 align:start position:0% pizza and it's amazing but you have to tell<00:12:07.420> a<00:12:07.480> machine<00:12:07.870> about<00:12:08.769> that<00:12:09.040> otherwise<00:12:09.490> it's 00:12:09.660 --> 00:12:09.670 align:start position:0% tell a machine about that otherwise it's 00:12:09.670 --> 00:12:11.759 align:start position:0% tell a machine about that otherwise it's going<00:12:09.759> to<00:12:09.819> get<00:12:09.939> very<00:12:10.000> confused<00:12:10.209> and<00:12:10.779> possibly 00:12:11.759 --> 00:12:11.769 align:start position:0% going to get very confused and possibly 00:12:11.769 --> 00:12:13.800 align:start position:0% going to get very confused and possibly make<00:12:11.949> a<00:12:11.980> pizza<00:12:12.310> that<00:12:12.579> isn't<00:12:12.850> isn't<00:12:13.480> gonna<00:12:13.600> work 00:12:13.800 --> 00:12:13.810 align:start position:0% make a pizza that isn't isn't gonna work 00:12:13.810 --> 00:12:16.350 align:start position:0% make a pizza that isn't isn't gonna work out<00:12:13.990> right<00:12:14.339> so<00:12:15.339> here's<00:12:15.610> here's<00:12:16.089> how<00:12:16.300> that 00:12:16.350 --> 00:12:16.360 align:start position:0% out right so here's here's how that 00:12:16.360 --> 00:12:19.860 align:start position:0% out right so here's here's how that looks<00:12:16.889> again<00:12:17.889> as<00:12:18.040> a<00:12:18.069> developer<00:12:18.670> I<00:12:18.910> might<00:12:19.720> be 00:12:19.860 --> 00:12:19.870 align:start position:0% looks again as a developer I might be 00:12:19.870 --> 00:12:22.410 align:start position:0% looks again as a developer I might be terrified<00:12:20.290> of<00:12:20.319> this<00:12:20.670> but<00:12:21.670> I<00:12:21.819> might<00:12:22.000> use<00:12:22.149> a<00:12:22.180> tool 00:12:22.410 --> 00:12:22.420 align:start position:0% terrified of this but I might use a tool 00:12:22.420 --> 00:12:24.900 align:start position:0% terrified of this but I might use a tool that<00:12:22.509> would<00:12:22.630> generate<00:12:22.870> this<00:12:23.550> not<00:12:24.550> enough 00:12:24.900 --> 00:12:24.910 align:start position:0% that would generate this not enough 00:12:24.910 --> 00:12:28.410 align:start position:0% that would generate this not enough tools<00:12:25.839> are<00:12:26.439> out<00:12:26.769> there<00:12:27.069> that<00:12:27.939> are<00:12:28.089> easy<00:12:28.240> to 00:12:28.410 --> 00:12:28.420 align:start position:0% tools are out there that are easy to 00:12:28.420 --> 00:12:29.610 align:start position:0% tools are out there that are easy to deal<00:12:28.600> with<00:12:28.630> not<00:12:28.930> enough<00:12:28.959> tools<00:12:29.319> are<00:12:29.410> out<00:12:29.439> there 00:12:29.610 --> 00:12:29.620 align:start position:0% deal with not enough tools are out there 00:12:29.620 --> 00:12:33.629 align:start position:0% deal with not enough tools are out there generating<00:12:30.160> this<00:12:30.250> kind<00:12:30.490> of<00:12:30.550> thing<00:12:31.889> so<00:12:32.889> here's 00:12:33.629 --> 00:12:33.639 align:start position:0% generating this kind of thing so here's 00:12:33.639 --> 00:12:35.610 align:start position:0% generating this kind of thing so here's here's<00:12:34.209> a<00:12:34.329> here's<00:12:35.079> one<00:12:35.199> of<00:12:35.259> my<00:12:35.319> favorite 00:12:35.610 --> 00:12:35.620 align:start position:0% here's a here's one of my favorite 00:12:35.620 --> 00:12:37.499 align:start position:0% here's a here's one of my favorite topics<00:12:35.829> these<00:12:36.250> crazy<00:12:36.579> pizzas<00:12:37.000> they<00:12:37.149> make<00:12:37.329> in 00:12:37.499 --> 00:12:37.509 align:start position:0% topics these crazy pizzas they make in 00:12:37.509 --> 00:12:39.420 align:start position:0% topics these crazy pizzas they make in places<00:12:37.810> like<00:12:37.930> Taiwan<00:12:38.139> and<00:12:38.410> Japan<00:12:38.470> I'm 00:12:39.420 --> 00:12:39.430 align:start position:0% places like Taiwan and Japan I'm 00:12:39.430 --> 00:12:41.819 align:start position:0% places like Taiwan and Japan I'm probably<00:12:39.639> Hong<00:12:39.850> Kong<00:12:40.089> this<00:12:40.569> pizza<00:12:40.930> has<00:12:41.139> little 00:12:41.819 --> 00:12:41.829 align:start position:0% probably Hong Kong this pizza has little 00:12:41.829 --> 00:12:44.639 align:start position:0% probably Hong Kong this pizza has little baby<00:12:41.980> hot<00:12:42.189> dogs<00:12:42.459> little<00:12:43.180> ketchup<00:12:43.899> so<00:12:44.230> on<00:12:44.350> top 00:12:44.639 --> 00:12:44.649 align:start position:0% baby hot dogs little ketchup so on top 00:12:44.649 --> 00:12:46.439 align:start position:0% baby hot dogs little ketchup so on top of<00:12:44.769> each<00:12:44.860> baby<00:12:45.040> hotdog<00:12:45.459> and<00:12:45.730> then<00:12:46.209> you<00:12:46.329> can 00:12:46.439 --> 00:12:46.449 align:start position:0% of each baby hotdog and then you can 00:12:46.449 --> 00:12:49.199 align:start position:0% of each baby hotdog and then you can kind<00:12:46.630> of<00:12:46.689> see<00:12:46.809> the<00:12:46.930> logic<00:12:47.850> now<00:12:48.850> if<00:12:48.939> you<00:12:49.000> want<00:12:49.149> to 00:12:49.199 --> 00:12:49.209 align:start position:0% kind of see the logic now if you want to 00:12:49.209 --> 00:12:52.049 align:start position:0% kind of see the logic now if you want to make<00:12:49.300> an<00:12:49.420> automatic<00:12:49.509> Pizza<00:12:50.350> make<00:12:50.980> Baker<00:12:51.339> its 00:12:52.049 --> 00:12:52.059 align:start position:0% make an automatic Pizza make Baker its 00:12:52.059 --> 00:12:53.579 align:start position:0% make an automatic Pizza make Baker its it<00:12:52.480> could<00:12:52.630> use<00:12:52.750> the<00:12:52.899> ontology<00:12:53.230> and 00:12:53.579 --> 00:12:53.589 align:start position:0% it could use the ontology and 00:12:53.589 --> 00:12:55.620 align:start position:0% it could use the ontology and potentially<00:12:54.370> make<00:12:54.519> this<00:12:54.639> pizza<00:12:55.059> and<00:12:55.269> still<00:12:55.540> be 00:12:55.620 --> 00:12:55.630 align:start position:0% potentially make this pizza and still be 00:12:55.630 --> 00:12:57.749 align:start position:0% potentially make this pizza and still be a<00:12:55.660> valid<00:12:55.839> pizza<00:12:56.350> according<00:12:56.740> to<00:12:56.949> the<00:12:57.430> ontology 00:12:57.749 --> 00:12:57.759 align:start position:0% a valid pizza according to the ontology 00:12:57.759 --> 00:12:59.939 align:start position:0% a valid pizza according to the ontology but<00:12:58.509> it's<00:12:58.660> kind<00:12:58.839> of<00:12:58.870> ridiculous<00:12:59.259> that's<00:12:59.740> why<00:12:59.889> I 00:12:59.939 --> 00:12:59.949 align:start position:0% but it's kind of ridiculous that's why I 00:12:59.949 --> 00:13:06.329 align:start position:0% but it's kind of ridiculous that's why I chose<00:13:00.220> this<00:13:02.339> really<00:13:03.339> it's<00:13:04.740> it's<00:13:05.740> pedantic 00:13:06.329 --> 00:13:06.339 align:start position:0% chose this really it's it's pedantic 00:13:06.339 --> 00:13:08.309 align:start position:0% chose this really it's it's pedantic like<00:13:06.550> it's<00:13:06.759> it's<00:13:07.089> it's<00:13:07.449> too<00:13:07.720> much<00:13:07.899> work<00:13:08.110> and 00:13:08.309 --> 00:13:08.319 align:start position:0% like it's it's it's too much work and 00:13:08.319 --> 00:13:10.559 align:start position:0% like it's it's it's too much work and that's<00:13:08.529> man<00:13:08.949> who's<00:13:09.100> Barney<00:13:09.399> called<00:13:10.240> it<00:13:10.420> right 00:13:10.559 --> 00:13:10.569 align:start position:0% that's man who's Barney called it right 00:13:10.569 --> 00:13:13.440 align:start position:0% that's man who's Barney called it right there<00:13:10.779> and<00:13:11.170> he<00:13:11.769> actually<00:13:11.949> worked<00:13:12.819> on<00:13:13.000> many 00:13:13.440 --> 00:13:13.450 align:start position:0% there and he actually worked on many 00:13:13.450 --> 00:13:18.720 align:start position:0% there and he actually worked on many at<00:13:14.140> the<00:13:14.610> w3c<00:13:15.750> and<00:13:16.980> and<00:13:17.980> he<00:13:18.070> started<00:13:18.340> digital 00:13:18.720 --> 00:13:18.730 align:start position:0% at the w3c and and he started digital 00:13:18.730 --> 00:13:20.280 align:start position:0% at the w3c and and he started digital bazaar<00:13:19.030> which<00:13:19.240> is<00:13:19.330> a<00:13:19.360> really<00:13:20.200> interesting 00:13:20.280 --> 00:13:20.290 align:start position:0% bazaar which is a really interesting 00:13:20.290 --> 00:13:22.680 align:start position:0% bazaar which is a really interesting company<00:13:21.040> right<00:13:21.160> now<00:13:21.190> and<00:13:21.790> I<00:13:22.030> consider<00:13:22.570> him 00:13:22.680 --> 00:13:22.690 align:start position:0% company right now and I consider him 00:13:22.690 --> 00:13:25.170 align:start position:0% company right now and I consider him sort<00:13:22.990> of<00:13:23.050> an<00:13:23.170> antihero<00:13:23.640> he<00:13:24.640> developed<00:13:25.000> a<00:13:25.060> new 00:13:25.170 --> 00:13:25.180 align:start position:0% sort of an antihero he developed a new 00:13:25.180 --> 00:13:28.950 align:start position:0% sort of an antihero he developed a new standard<00:13:25.450> called<00:13:25.660> json-ld<00:13:26.340> and<00:13:27.660> the<00:13:28.660> idea<00:13:28.900> is 00:13:28.950 --> 00:13:28.960 align:start position:0% standard called json-ld and the idea is 00:13:28.960 --> 00:13:31.020 align:start position:0% standard called json-ld and the idea is that<00:13:29.020> you're<00:13:29.260> going<00:13:29.440> to<00:13:29.620> add<00:13:29.830> context<00:13:30.640> to<00:13:30.670> data 00:13:31.020 --> 00:13:31.030 align:start position:0% that you're going to add context to data 00:13:31.030 --> 00:13:33.450 align:start position:0% that you're going to add context to data with<00:13:31.660> a<00:13:31.690> lot<00:13:32.020> less<00:13:32.260> work<00:13:32.560> as<00:13:32.740> a<00:13:32.770> developer 00:13:33.450 --> 00:13:33.460 align:start position:0% with a lot less work as a developer 00:13:33.460 --> 00:13:36.240 align:start position:0% with a lot less work as a developer now<00:13:33.820> json-ld<00:13:34.270> is<00:13:34.660> becoming<00:13:35.050> a<00:13:35.380> very<00:13:35.830> important 00:13:36.240 --> 00:13:36.250 align:start position:0% now json-ld is becoming a very important 00:13:36.250 --> 00:13:38.700 align:start position:0% now json-ld is becoming a very important standard<00:13:36.580> like<00:13:36.730> for<00:13:36.880> example<00:13:36.970> the<00:13:37.710> Google 00:13:38.700 --> 00:13:38.710 align:start position:0% standard like for example the Google 00:13:38.710 --> 00:13:40.710 align:start position:0% standard like for example the Google accepts<00:13:39.370> it<00:13:39.520> if<00:13:39.700> you're<00:13:40.030> an<00:13:40.120> airline<00:13:40.420> and<00:13:40.450> you 00:13:40.710 --> 00:13:40.720 align:start position:0% accepts it if you're an airline and you 00:13:40.720 --> 00:13:44.010 align:start position:0% accepts it if you're an airline and you want<00:13:40.900> you<00:13:41.320> want<00:13:41.500> the<00:13:41.770> the<00:13:42.550> flight<00:13:43.450> tickets<00:13:43.840> to 00:13:44.010 --> 00:13:44.020 align:start position:0% want you want the the flight tickets to 00:13:44.020 --> 00:13:46.950 align:start position:0% want you want the the flight tickets to show<00:13:44.200> up<00:13:44.380> in<00:13:44.530> your<00:13:44.680> email<00:13:44.950> that<00:13:45.130> way<00:13:45.960> Google 00:13:46.950 --> 00:13:46.960 align:start position:0% show up in your email that way Google 00:13:46.960 --> 00:13:48.990 align:start position:0% show up in your email that way Google will<00:13:47.080> accept<00:13:47.380> json-ld<00:13:47.710> so<00:13:48.250> json-ld<00:13:48.610> has 00:13:48.990 --> 00:13:49.000 align:start position:0% will accept json-ld so json-ld has 00:13:49.000 --> 00:13:51.600 align:start position:0% will accept json-ld so json-ld has become<00:13:49.300> quite<00:13:49.680> quite<00:13:50.680> a<00:13:50.740> large<00:13:50.890> standard<00:13:51.370> and 00:13:51.600 --> 00:13:51.610 align:start position:0% become quite quite a large standard and 00:13:51.610 --> 00:13:53.460 align:start position:0% become quite quite a large standard and here's<00:13:52.000> what<00:13:52.180> it<00:13:52.270> looks<00:13:52.480> like<00:13:52.660> it's<00:13:53.200> a<00:13:53.290> lot 00:13:53.460 --> 00:13:53.470 align:start position:0% here's what it looks like it's a lot 00:13:53.470 --> 00:13:57.420 align:start position:0% here's what it looks like it's a lot less<00:13:54.370> ponderous<00:13:55.030> than<00:13:55.300> the<00:13:56.170> RDF<00:13:56.860> that<00:13:57.160> you<00:13:57.250> saw 00:13:57.420 --> 00:13:57.430 align:start position:0% less ponderous than the RDF that you saw 00:13:57.430 --> 00:14:00.300 align:start position:0% less ponderous than the RDF that you saw earlier<00:13:57.610> it's<00:13:58.360> not<00:13:58.480> XML<00:13:58.870> is<00:13:58.990> JSON<00:13:59.410> very 00:14:00.300 --> 00:14:00.310 align:start position:0% earlier it's not XML is JSON very 00:14:00.310 --> 00:14:02.070 align:start position:0% earlier it's not XML is JSON very developer<00:14:00.730> friendly<00:14:01.030> but<00:14:01.570> it<00:14:01.690> still<00:14:01.900> has<00:14:02.050> a 00:14:02.070 --> 00:14:02.080 align:start position:0% developer friendly but it still has a 00:14:02.080 --> 00:14:06.080 align:start position:0% developer friendly but it still has a lot<00:14:02.410> of<00:14:02.560> elements<00:14:02.890> that<00:14:03.160> are<00:14:03.730> semantic<00:14:04.300> or 00:14:06.080 --> 00:14:06.090 align:start position:0% lot of elements that are semantic or 00:14:06.090 --> 00:14:10.110 align:start position:0% lot of elements that are semantic or provide<00:14:07.090> context<00:14:08.550> so<00:14:09.550> when<00:14:09.850> you<00:14:09.940> think<00:14:10.090> about 00:14:10.110 --> 00:14:10.120 align:start position:0% provide context so when you think about 00:14:10.120 --> 00:14:13.290 align:start position:0% provide context so when you think about semantic<00:14:10.720> etherium<00:14:11.820> like<00:14:12.820> what's<00:14:13.090> the 00:14:13.290 --> 00:14:13.300 align:start position:0% semantic etherium like what's the 00:14:13.300 --> 00:14:15.120 align:start position:0% semantic etherium like what's the appropriate<00:14:13.630> level<00:14:14.200> how<00:14:14.320> far<00:14:14.620> do<00:14:14.770> we<00:14:14.830> want<00:14:15.040> to 00:14:15.120 --> 00:14:15.130 align:start position:0% appropriate level how far do we want to 00:14:15.130 --> 00:14:15.510 align:start position:0% appropriate level how far do we want to go 00:14:15.510 --> 00:14:15.520 align:start position:0% go 00:14:15.520 --> 00:14:18.900 align:start position:0% go I<00:14:15.960> I<00:14:16.960> consider<00:14:17.680> it<00:14:17.890> I'm<00:14:18.100> thinking<00:14:18.520> about<00:14:18.640> it 00:14:18.900 --> 00:14:18.910 align:start position:0% I I consider it I'm thinking about it 00:14:18.910 --> 00:14:21.180 align:start position:0% I I consider it I'm thinking about it and<00:14:18.970> I<00:14:19.120> think<00:14:19.390> it's<00:14:19.870> important<00:14:20.260> to<00:14:20.620> foster 00:14:21.180 --> 00:14:21.190 align:start position:0% and I think it's important to foster 00:14:21.190 --> 00:14:23.730 align:start position:0% and I think it's important to foster creativity<00:14:21.760> but<00:14:22.450> not<00:14:22.660> to<00:14:22.840> overdo<00:14:23.230> it<00:14:23.380> right 00:14:23.730 --> 00:14:23.740 align:start position:0% creativity but not to overdo it right 00:14:23.740 --> 00:14:27.150 align:start position:0% creativity but not to overdo it right just<00:14:24.040> enough<00:14:24.400> for<00:14:25.120> us<00:14:25.570> to<00:14:25.660> have<00:14:26.160> composability 00:14:27.150 --> 00:14:27.160 align:start position:0% just enough for us to have composability 00:14:27.160 --> 00:14:29.790 align:start position:0% just enough for us to have composability and<00:14:27.700> you<00:14:28.600> know<00:14:28.660> this<00:14:28.780> is<00:14:28.930> a<00:14:28.960> good<00:14:29.200> metaphor<00:14:29.470> you 00:14:29.790 --> 00:14:29.800 align:start position:0% and you know this is a good metaphor you 00:14:29.800 --> 00:14:31.380 align:start position:0% and you know this is a good metaphor you create<00:14:30.130> a<00:14:30.190> standard<00:14:30.520> for<00:14:30.640> LEGO<00:14:30.820> brick<00:14:31.120> but<00:14:31.270> you 00:14:31.380 --> 00:14:31.390 align:start position:0% create a standard for LEGO brick but you 00:14:31.390 --> 00:14:32.970 align:start position:0% create a standard for LEGO brick but you let<00:14:31.570> people<00:14:31.900> build<00:14:32.140> whatever<00:14:32.380> they<00:14:32.530> want<00:14:32.860> with 00:14:32.970 --> 00:14:32.980 align:start position:0% let people build whatever they want with 00:14:32.980 --> 00:14:37.100 align:start position:0% let people build whatever they want with it<00:14:33.010> but<00:14:33.790> you<00:14:33.910> need<00:14:34.120> to<00:14:34.270> have<00:14:34.480> some<00:14:35.670> structure 00:14:37.100 --> 00:14:37.110 align:start position:0% it but you need to have some structure 00:14:37.110 --> 00:14:39.810 align:start position:0% it but you need to have some structure and<00:14:38.110> aetherium<00:14:38.890> obviously<00:14:39.310> has<00:14:39.490> a<00:14:39.520> lot<00:14:39.790> of 00:14:39.810 --> 00:14:39.820 align:start position:0% and aetherium obviously has a lot of 00:14:39.820 --> 00:14:44.120 align:start position:0% and aetherium obviously has a lot of metadata<00:14:40.800> involved<00:14:41.800> addresses<00:14:42.340> signatures 00:14:44.120 --> 00:14:44.130 align:start position:0% metadata involved addresses signatures 00:14:44.130 --> 00:14:48.090 align:start position:0% metadata involved addresses signatures token<00:14:45.130> balances<00:14:46.020> you<00:14:47.020> know<00:14:47.170> we're<00:14:47.920> going<00:14:48.010> to 00:14:48.090 --> 00:14:48.100 align:start position:0% token balances you know we're going to 00:14:48.100 --> 00:14:50.190 align:start position:0% token balances you know we're going to have<00:14:48.220> identity<00:14:48.580> claims<00:14:48.970> the<00:14:49.450> your<00:14:49.810> eyes<00:14:49.960> are 00:14:50.190 --> 00:14:50.200 align:start position:0% have identity claims the your eyes are 00:14:50.200 --> 00:14:52.460 align:start position:0% have identity claims the your eyes are associated<00:14:50.710> they're<00:14:50.920> in<00:14:51.130> a<00:14:51.610> descriptive<00:14:52.030> side 00:14:52.460 --> 00:14:52.470 align:start position:0% associated they're in a descriptive side 00:14:52.470 --> 00:14:55.910 align:start position:0% associated they're in a descriptive side you<00:14:53.470> know<00:14:53.620> you<00:14:53.650> have<00:14:54.040> a<00:14:55.000> be<00:14:55.450> eyes 00:14:55.910 --> 00:14:55.920 align:start position:0% you know you have a be eyes 00:14:55.920 --> 00:14:58.470 align:start position:0% you know you have a be eyes documentation<00:14:56.920> of<00:14:57.130> course<00:14:57.400> and<00:14:57.670> structure 00:14:58.470 --> 00:14:58.480 align:start position:0% documentation of course and structure 00:14:58.480 --> 00:15:01.470 align:start position:0% documentation of course and structure enforced<00:14:59.470> in<00:14:59.650> the<00:14:59.680> AVM<00:15:00.190> like<00:15:00.700> you<00:15:00.910> you<00:15:01.300> can 00:15:01.470 --> 00:15:01.480 align:start position:0% enforced in the AVM like you you can 00:15:01.480 --> 00:15:04.560 align:start position:0% enforced in the AVM like you you can have<00:15:01.750> as<00:15:02.680> many<00:15:03.310> objects<00:15:03.730> as<00:15:03.820> you<00:15:03.970> want<00:15:04.180> and<00:15:04.360> you 00:15:04.560 --> 00:15:04.570 align:start position:0% have as many objects as you want and you 00:15:04.570 --> 00:15:06.900 align:start position:0% have as many objects as you want and you know<00:15:04.750> that<00:15:05.020> nobody<00:15:05.380> is<00:15:05.500> going<00:15:06.460> to<00:15:06.580> mess<00:15:06.640> around 00:15:06.900 --> 00:15:06.910 align:start position:0% know that nobody is going to mess around 00:15:06.910 --> 00:15:11.820 align:start position:0% know that nobody is going to mess around with<00:15:07.120> it<00:15:07.330> if<00:15:07.450> it's<00:15:07.600> done<00:15:07.810> right<00:15:08.340> so<00:15:10.680> one<00:15:11.680> of<00:15:11.710> the 00:15:11.820 --> 00:15:11.830 align:start position:0% with it if it's done right so one of the 00:15:11.830 --> 00:15:13.470 align:start position:0% with it if it's done right so one of the reasons<00:15:12.130> why<00:15:12.250> we<00:15:12.490> we<00:15:12.880> should<00:15:13.060> put<00:15:13.240> more 00:15:13.470 --> 00:15:13.480 align:start position:0% reasons why we we should put more 00:15:13.480 --> 00:15:17.400 align:start position:0% reasons why we we should put more metadata<00:15:13.930> if<00:15:14.260> possible<00:15:15.100> into<00:15:15.370> our<00:15:15.550> work<00:15:16.410> is 00:15:17.400 --> 00:15:17.410 align:start position:0% metadata if possible into our work is 00:15:17.410 --> 00:15:20.340 align:start position:0% metadata if possible into our work is the<00:15:17.710> permanency<00:15:18.250> of<00:15:18.280> it<00:15:18.840> we<00:15:19.840> might<00:15:20.050> not<00:15:20.170> be 00:15:20.340 --> 00:15:20.350 align:start position:0% the permanency of it we might not be 00:15:20.350 --> 00:15:23.310 align:start position:0% the permanency of it we might not be around<00:15:20.410> and<00:15:20.920> this<00:15:21.460> this<00:15:22.200> application<00:15:23.200> is 00:15:23.310 --> 00:15:23.320 align:start position:0% around and this this application is 00:15:23.320 --> 00:15:26.010 align:start position:0% around and this this application is still<00:15:23.470> being<00:15:23.650> used 00:15:26.010 --> 00:15:26.020 align:start position:0% 00:15:26.020 --> 00:15:30.290 align:start position:0% in<00:15:26.170> the<00:15:26.560> future<00:15:26.860> and<00:15:27.810> obviously<00:15:28.830> ecosystem 00:15:30.290 --> 00:15:30.300 align:start position:0% in the future and obviously ecosystem 00:15:30.300 --> 00:15:33.150 align:start position:0% in the future and obviously ecosystem thinking<00:15:31.300> about<00:15:31.510> tokens<00:15:31.960> or<00:15:32.080> identity<00:15:32.590> these 00:15:33.150 --> 00:15:33.160 align:start position:0% thinking about tokens or identity these 00:15:33.160 --> 00:15:36.060 align:start position:0% thinking about tokens or identity these these<00:15:33.700> are<00:15:33.940> and<00:15:34.900> identity<00:15:35.650> itself<00:15:35.950> is 00:15:36.060 --> 00:15:36.070 align:start position:0% these are and identity itself is 00:15:36.070 --> 00:15:38.180 align:start position:0% these are and identity itself is potentially<00:15:36.610> creating<00:15:36.910> great<00:15:37.270> ecosystems 00:15:38.180 --> 00:15:38.190 align:start position:0% potentially creating great ecosystems 00:15:38.190 --> 00:15:41.040 align:start position:0% potentially creating great ecosystems you<00:15:39.190> create<00:15:39.700> these<00:15:39.760> footholds<00:15:40.390> when<00:15:40.780> you<00:15:40.900> do 00:15:41.040 --> 00:15:41.050 align:start position:0% you create these footholds when you do 00:15:41.050 --> 00:15:43.880 align:start position:0% you create these footholds when you do metadata<00:15:41.500> and<00:15:41.650> when<00:15:41.740> you<00:15:41.830> do<00:15:41.920> it<00:15:42.040> right<00:15:42.810> and 00:15:43.880 --> 00:15:43.890 align:start position:0% metadata and when you do it right and 00:15:43.890 --> 00:15:46.080 align:start position:0% metadata and when you do it right and swarm<00:15:44.890> itself<00:15:45.310> is<00:15:45.430> actually<00:15:45.550> quite<00:15:45.760> an 00:15:46.080 --> 00:15:46.090 align:start position:0% swarm itself is actually quite an 00:15:46.090 --> 00:15:48.660 align:start position:0% swarm itself is actually quite an opportunity<00:15:46.630> because<00:15:46.980> you<00:15:47.980> can<00:15:48.100> use<00:15:48.220> json-ld 00:15:48.660 --> 00:15:48.670 align:start position:0% opportunity because you can use json-ld 00:15:48.670 --> 00:15:52.740 align:start position:0% opportunity because you can use json-ld in<00:15:49.570> there<00:15:50.020> and<00:15:50.200> you<00:15:50.980> can<00:15:51.130> connect<00:15:51.660> connect<00:15:52.660> all 00:15:52.740 --> 00:15:52.750 align:start position:0% in there and you can connect connect all 00:15:52.750 --> 00:15:54.060 align:start position:0% in there and you can connect connect all these<00:15:52.900> things<00:15:53.170> together<00:15:53.350> like<00:15:53.590> right<00:15:53.890> now 00:15:54.060 --> 00:15:54.070 align:start position:0% these things together like right now 00:15:54.070 --> 00:15:56.510 align:start position:0% these things together like right now we're<00:15:54.220> thinking<00:15:54.340> yolk<00:15:55.000> you'll<00:15:55.480> refer<00:15:56.140> to 00:15:56.510 --> 00:15:56.520 align:start position:0% we're thinking yolk you'll refer to 00:15:56.520 --> 00:15:58.890 align:start position:0% we're thinking yolk you'll refer to json-ld<00:15:57.520> that's<00:15:57.970> hosted<00:15:58.270> on<00:15:58.360> swarm<00:15:58.660> in<00:15:58.810> your 00:15:58.890 --> 00:15:58.900 align:start position:0% json-ld that's hosted on swarm in your 00:15:58.900 --> 00:16:00.390 align:start position:0% json-ld that's hosted on swarm in your contract<00:15:59.350> but<00:15:59.740> you<00:15:59.800> should<00:16:00.070> do<00:16:00.160> it<00:16:00.280> the<00:16:00.310> other 00:16:00.390 --> 00:16:00.400 align:start position:0% contract but you should do it the other 00:16:00.400 --> 00:16:02.850 align:start position:0% contract but you should do it the other way<00:16:00.610> around<00:16:00.970> too<00:16:01.270> so<00:16:01.960> that<00:16:02.200> all<00:16:02.530> your 00:16:02.850 --> 00:16:02.860 align:start position:0% way around too so that all your 00:16:02.860 --> 00:16:05.640 align:start position:0% way around too so that all your documentation<00:16:03.430> all<00:16:04.060> your<00:16:04.390> data<00:16:04.630> all<00:16:05.410> your 00:16:05.640 --> 00:16:05.650 align:start position:0% documentation all your data all your 00:16:05.650 --> 00:16:07.380 align:start position:0% documentation all your data all your contracts<00:16:06.100> everything<00:16:06.460> somebody<00:16:07.060> could 00:16:07.380 --> 00:16:07.390 align:start position:0% contracts everything somebody could 00:16:07.390 --> 00:16:08.760 align:start position:0% contracts everything somebody could figure<00:16:07.570> it<00:16:07.750> all<00:16:07.840> out<00:16:07.900> even<00:16:08.410> if<00:16:08.530> you're<00:16:08.650> not 00:16:08.760 --> 00:16:08.770 align:start position:0% figure it all out even if you're not 00:16:08.770 --> 00:16:10.110 align:start position:0% figure it all out even if you're not there<00:16:08.980> to<00:16:09.130> explain<00:16:09.460> it<00:16:09.640> even<00:16:09.910> if<00:16:10.000> your 00:16:10.110 --> 00:16:10.120 align:start position:0% there to explain it even if your 00:16:10.120 --> 00:16:11.670 align:start position:0% there to explain it even if your documentation<00:16:10.690> is<00:16:10.960> on<00:16:10.990> the<00:16:11.170> web<00:16:11.320> that<00:16:11.500> no 00:16:11.670 --> 00:16:11.680 align:start position:0% documentation is on the web that no 00:16:11.680 --> 00:16:16.860 align:start position:0% documentation is on the web that no longer<00:16:12.010> exists<00:16:13.680> so<00:16:15.270> the<00:16:16.270> lessons<00:16:16.600> are<00:16:16.690> pretty 00:16:16.860 --> 00:16:16.870 align:start position:0% longer exists so the lessons are pretty 00:16:16.870 --> 00:16:21.120 align:start position:0% longer exists so the lessons are pretty clear<00:16:18.570> be<00:16:19.570> light<00:16:19.810> be<00:16:20.110> light<00:16:20.290> about<00:16:20.590> standards 00:16:21.120 --> 00:16:21.130 align:start position:0% clear be light be light about standards 00:16:21.130 --> 00:16:23.910 align:start position:0% clear be light be light about standards if<00:16:22.060> if<00:16:22.720> we<00:16:22.930> have<00:16:23.080> standards<00:16:23.470> it's<00:16:23.620> more<00:16:23.800> like 00:16:23.910 --> 00:16:23.920 align:start position:0% if if we have standards it's more like 00:16:23.920 --> 00:16:25.230 align:start position:0% if if we have standards it's more like documentation<00:16:24.670> and<00:16:24.790> we<00:16:24.850> really<00:16:25.120> encourage 00:16:25.230 --> 00:16:25.240 align:start position:0% documentation and we really encourage 00:16:25.240 --> 00:16:28.950 align:start position:0% documentation and we really encourage people<00:16:25.600> to<00:16:25.750> do<00:16:25.930> it<00:16:26.020> it's<00:16:26.230> fun<00:16:26.730> and<00:16:27.730> the<00:16:28.600> key<00:16:28.810> is 00:16:28.950 --> 00:16:28.960 align:start position:0% people to do it it's fun and the key is 00:16:28.960 --> 00:16:30.720 align:start position:0% people to do it it's fun and the key is steal<00:16:29.530> the<00:16:29.680> good<00:16:29.860> stuff<00:16:30.100> from<00:16:30.250> the<00:16:30.370> w3c 00:16:30.720 --> 00:16:30.730 align:start position:0% steal the good stuff from the w3c 00:16:30.730 --> 00:16:33.090 align:start position:0% steal the good stuff from the w3c because<00:16:31.480> they<00:16:32.230> really<00:16:32.530> do<00:16:32.620> have<00:16:32.800> a<00:16:32.860> lot<00:16:33.010> of 00:16:33.090 --> 00:16:33.100 align:start position:0% because they really do have a lot of 00:16:33.100 --> 00:16:34.800 align:start position:0% because they really do have a lot of good<00:16:33.250> ideas<00:16:33.640> we<00:16:34.000> don't<00:16:34.150> have<00:16:34.300> to<00:16:34.420> do<00:16:34.540> it<00:16:34.660> all 00:16:34.800 --> 00:16:34.810 align:start position:0% good ideas we don't have to do it all 00:16:34.810 --> 00:16:37.410 align:start position:0% good ideas we don't have to do it all but<00:16:35.530> just<00:16:35.800> explore<00:16:36.430> it<00:16:36.580> and<00:16:36.760> you'll<00:16:36.940> find<00:16:37.180> it 00:16:37.410 --> 00:16:37.420 align:start position:0% but just explore it and you'll find it 00:16:37.420 --> 00:16:38.610 align:start position:0% but just explore it and you'll find it there's<00:16:37.630> there's<00:16:38.050> a<00:16:38.110> lot<00:16:38.290> of<00:16:38.410> very 00:16:38.610 --> 00:16:38.620 align:start position:0% there's there's a lot of very 00:16:38.620 --> 00:16:41.540 align:start position:0% there's there's a lot of very interesting<00:16:39.150> stuff<00:16:40.150> in<00:16:40.330> there 00:16:41.540 --> 00:16:41.550 align:start position:0% interesting stuff in there 00:16:41.550 --> 00:16:43.790 align:start position:0% interesting stuff in there just<00:16:42.550> don't<00:16:42.670> explore<00:16:43.030> it<00:16:43.090> too<00:16:43.240> much<00:16:43.360> because 00:16:43.790 --> 00:16:43.800 align:start position:0% just don't explore it too much because 00:16:43.800 --> 00:16:46.260 align:start position:0% just don't explore it too much because it's<00:16:44.800> quite<00:16:45.130> overwhelming<00:16:45.640> it's<00:16:45.820> for<00:16:45.970> it's 00:16:46.260 --> 00:16:46.270 align:start position:0% it's quite overwhelming it's for it's 00:16:46.270 --> 00:16:48.720 align:start position:0% it's quite overwhelming it's for it's ridiculous<00:16:46.810> sometimes<00:16:47.250> but<00:16:48.250> still<00:16:48.550> the 00:16:48.720 --> 00:16:48.730 align:start position:0% ridiculous sometimes but still the 00:16:48.730 --> 00:16:51.120 align:start position:0% ridiculous sometimes but still the vision<00:16:49.150> of<00:16:49.270> it<00:16:49.420> is<00:16:49.720> quite<00:16:50.080> amazing<00:16:50.350> it's<00:16:50.740> it's 00:16:51.120 --> 00:16:51.130 align:start position:0% vision of it is quite amazing it's it's 00:16:51.130 --> 00:16:54.800 align:start position:0% vision of it is quite amazing it's it's very<00:16:51.220> interesting<00:16:51.490> history<00:16:52.090> so<00:16:53.050> that's<00:16:53.770> it 00:16:54.800 --> 00:16:54.810 align:start position:0% very interesting history so that's it 00:16:54.810 --> 00:16:57.510 align:start position:0% very interesting history so that's it hope<00:16:55.810> this<00:16:56.050> helps<00:16:57.040> you<00:16:57.160> make<00:16:57.190> your 00:16:57.510 --> 00:16:57.520 align:start position:0% hope this helps you make your 00:16:57.520 --> 00:17:01.060 align:start position:0% hope this helps you make your applications<00:16:58.950> that's<00:16:59.950> it 00:17:01.060 --> 00:17:01.070 align:start position:0% applications that's it 00:17:01.070 --> 00:17:07.700 align:start position:0% applications that's it [Applause] 00:17:07.700 --> 00:17:07.710 align:start position:0% 00:17:07.710 --> 00:17:15.289 align:start position:0% [Music]