WEBVTT 00:00:02.669 --> 00:00:05.530 Forbidden terms, we're going to talk about forbidden 00:00:05.530 --> 00:00:08.150 terms. I'm not sure everybody's familiar with 00:00:08.150 --> 00:00:10.890 the concept, so let's explore that a little bit. 00:00:11.490 --> 00:00:14.669 So where's this coming from? Recently, we've 00:00:14.669 --> 00:00:18.469 seen that President Trump has decided that there's 00:00:18.469 --> 00:00:21.289 a particular term that we use a lot that should 00:00:21.289 --> 00:00:26.800 not be used. So it became a forbidden term. When 00:00:26.800 --> 00:00:29.899 we are creating our language assets, our glossaries, 00:00:29.960 --> 00:00:32.039 let's focus on glossaries for example, one of 00:00:32.039 --> 00:00:35.820 the things that happens is that we have to somehow 00:00:35.820 --> 00:00:40.960 give a status to all the elements, all of the 00:00:40.960 --> 00:00:43.600 entries of the glossary, right? And one of the 00:00:43.600 --> 00:00:46.679 things we need to do is obviously to inform. 00:00:46.920 --> 00:00:48.979 ourselves and everybody else is going to use 00:00:48.979 --> 00:00:52.899 this glossary let's go with that what kind of 00:00:52.899 --> 00:00:55.880 situation is going on with that particular term 00:00:55.880 --> 00:00:59.179 therefore when you propose a term and it's not 00:00:59.179 --> 00:01:01.420 been seen by anybody else it can be for example 00:01:01.420 --> 00:01:05.040 it can have status proposed let's say right or 00:01:05.040 --> 00:01:07.939 term candidates something like that then hopefully 00:01:07.939 --> 00:01:11.760 depending on your workflow it can become an approved 00:01:11.760 --> 00:01:16.700 term it can become a preferred term, it can be 00:01:16.700 --> 00:01:21.299 eventually deprecated and it can be forbidden, 00:01:21.579 --> 00:01:25.599 right? So these are some of the more mainstream 00:01:25.599 --> 00:01:29.859 ways that you have to give your terms status 00:01:29.859 --> 00:01:33.510 in a glossary, for example. So what are they? 00:01:33.849 --> 00:01:35.870 The proposed term is obvious, right? So if nobody 00:01:35.870 --> 00:01:37.849 else has looked at it and it's already there, 00:01:37.890 --> 00:01:40.030 someone proposed it, it's only at that stage, 00:01:40.069 --> 00:01:43.689 it's a proposal, maybe let's not use it yet to 00:01:43.689 --> 00:01:47.170 see if it can be approved or not by someone. 00:01:47.269 --> 00:01:50.909 But because there was a reason to somehow propose 00:01:50.909 --> 00:01:55.109 this term for this particular glossary or client 00:01:55.109 --> 00:01:58.569 or nomenclature or whatever it is, what we can 00:01:58.569 --> 00:02:02.969 do is to wait for it to be approved or checked 00:02:02.969 --> 00:02:05.230 to see what happens. But one of the things that 00:02:05.230 --> 00:02:10.610 can happen is that even before it's used or after 00:02:10.610 --> 00:02:14.370 a period of being used a term can become forbidden. 00:02:14.789 --> 00:02:19.009 This means usually in the regular life of language 00:02:19.009 --> 00:02:23.430 services usually means that within the client's 00:02:23.430 --> 00:02:27.169 brand or type or style of communication you should 00:02:27.169 --> 00:02:31.650 not use this particular term, which usually is 00:02:31.650 --> 00:02:34.870 correct in other circumstances. But for this 00:02:34.870 --> 00:02:37.389 particular brand, it should not be used. And 00:02:37.389 --> 00:02:40.150 this is obviously an example for all the UI, 00:02:41.310 --> 00:02:44.150 all that terminology, all the buttons and all 00:02:44.150 --> 00:02:47.729 of that names of functions, names of features 00:02:47.729 --> 00:02:51.430 that you have between Microsoft and then Apple. 00:02:51.669 --> 00:02:55.449 So if it's a PC, you'll use a certain type of 00:02:55.449 --> 00:02:59.150 terms. If it's a Mac or iOS system, you will 00:02:59.150 --> 00:03:01.949 use another set of terms, but they all refer 00:03:01.949 --> 00:03:04.409 to the same button, for example, or to the same 00:03:04.409 --> 00:03:08.229 function, right? So obviously, in Apple's terminology, 00:03:08.710 --> 00:03:12.870 it's probably, I'm hoping, forbidden. Maybe it's 00:03:12.870 --> 00:03:14.889 not marked like that, but it's the idea, right? 00:03:15.110 --> 00:03:17.990 It's forbidden to use that specific term, which 00:03:17.990 --> 00:03:21.590 obviously is connected to Microsoft, for example, 00:03:21.729 --> 00:03:24.330 which is just the most basic example. So in this 00:03:24.330 --> 00:03:27.830 case, President Trump, right, had a term that 00:03:27.830 --> 00:03:31.319 we all use. So artificial intelligence, and he 00:03:31.319 --> 00:03:34.039 decided it was forbidden. So it's against the 00:03:34.039 --> 00:03:36.159 law. It might have consequences. You might go 00:03:36.159 --> 00:03:39.879 to jail if you are within that circle of President 00:03:39.879 --> 00:03:44.060 Trump, his mental glossary, right? And you use 00:03:44.060 --> 00:03:47.460 the term artificial intelligence. So this became 00:03:47.460 --> 00:03:50.960 a forbidden term, right? It's a conceptual idea 00:03:50.960 --> 00:03:53.800 to be forbidden. But in real life, this is exactly 00:03:53.800 --> 00:03:56.819 what happens. If a term is not within your brand, 00:03:57.180 --> 00:03:59.039 what you think should be your communication, 00:03:59.300 --> 00:04:03.219 it should become forbidden because for the rest 00:04:03.219 --> 00:04:06.439 of the community is a term. that is correct. 00:04:06.680 --> 00:04:09.860 It's very dangerous to keep it around or not 00:04:09.860 --> 00:04:13.020 mark it as forbidden because you run the risk 00:04:13.020 --> 00:04:16.180 that it will be used. So President Trump this 00:04:16.180 --> 00:04:19.160 week has been inspiring me a lot because of talking 00:04:19.160 --> 00:04:21.639 about forbidden terms, right? Because it's something 00:04:21.639 --> 00:04:23.879 that is very dear to me. And I think it's very 00:04:23.879 --> 00:04:26.439 necessary. It's something that most people don't 00:04:26.439 --> 00:04:29.680 think about in their terminology workflow because 00:04:29.680 --> 00:04:31.660 it's not really talked about. But I think it's 00:04:31.660 --> 00:04:34.259 one of the most useful status that you have. 00:04:34.439 --> 00:04:39.019 especially when it comes to a more visible part 00:04:39.019 --> 00:04:42.779 of your content or terminology. So this is what 00:04:42.779 --> 00:04:46.339 a forbidden term is. It's a term that should 00:04:46.339 --> 00:04:51.540 not be used in your communication under any circumstances, 00:04:51.879 --> 00:04:53.879 right? So this is what it is, a forbidden term, 00:04:53.899 --> 00:04:57.800 and it should be marked as that status forbidden, 00:04:58.480 --> 00:04:58.680 right?