in Indonesia, but most of us here and most of us in this field are called, imagine, to build a universal, what are called the right-state yam integration. Is this real? The words are, when, is that, to all the database, because there is a communication on database, and it's very, very useful before it's too late to adjust the common tools, and to map it, organizing a second workshop on this in June. Thanks a lot, Nikola, and thanks also to the organizers for inviting me here, so it's really a pleasure to be here and to tell you a bit about the work that we've been doing on Materials Cloud.  So the first challenge has already been introduced by Joffrey, and thanks for that. It's a high throughput, so how do you organize large numbers of calculations in a consistent way where you all know this problem? The second problem is maybe what comes afterwards. So you have done your calculation, not necessarily a high throughput, but there's a lot of data sitting around, so that's the story of the PhD student, Bob, who knows exactly how he did his calculations, where he put the data, but then he leaves the group and the data is still sitting there, and the next PhD student, Alice, has to pick it up and she gets lost in the data jungle, so how do we improve on that situation? Then there's the related open science problem. So say I've done my calculations, I've written a draft for my paper, how do I open access to all the data that I have in a meaningful way? And not many people do this nowadays because it is an enormous amount of work, and I think the key challenge here is how can we make this process easier? And finally, I've called this knowledge transfer, or what we call it dissemination, so what I'm thinking about is, say I'm collaborating with an experimental group, I've done some calculations for them, and now I would like to share this data set that I have with the group, I would like to communicate this data set to them, and of course I don't have the software I have to view the data, so I've often been in this situation and I felt that making a few plots and putting it into a PDF was really not an optimal way of communicating to them what I wanted them to see. All right, this brings me to the second part, and so this is the architecture diagram for AIDA. AIDA in essence is a collection of Python packages that you install on your local machine, so a workstation or laptop, that allows you to set up, submit, and monitor material science calculations. AIDA takes care of transferring the input files from your machine to the supercomputer, submitting the calculation at the supercomputer, monitoring the queue, and when the calculation is done, retrieving the results back to your local machine. And what sets AIDA apart from other similar approaches is that you have a local database, and so this is a database sitting locally on the computer where you have installed AIDA, and this is essentially a history of everything that happened. So AIDA stores there, for every calculation, which inputs were used, where it was submitted, who submitted it, when it was submitted, which outputs were produced, et cetera. And this data is stored in a directed graph, and it is this graph that helps us with the open science and the data general problems. AIDA is free and open source. It's developed in this GitHub repository. There's a number of plugins for different material science code available, and let me just say, so if you want to start developing AIDA plugin for your code, you just copy our plugin template that we provide and start from there. You can do that completely independently. It's a very modular setup. All we ask is that you please register your plugin on the AIDA plugin registry. There's a little bit of information that is very helpful for you to reserve the name for the plugin, and it's also helpful for the AIDA community to know that you're working on it. And who knows? I mean, somebody might come and help you. Now to the architecture of Materials Cloud. Materials Cloud, in essence, is an AngularJS web app that can communicate with an AIDA database through a REST API. So this is what we call the Explore section. So this is about exploring a database, an AIDA graph, through the web browser. And there are four other sections. So there's this cover, which is about providing user-defined entry points to an AIDA database. There's Work, which is about running and launching calculations in the browser. Learn a number of... You'll find recordings of lectures and tutorials together with slides. And finally, there's the archive, which is a place where you can upload your research data, get a document object identifier for it, and then link to this data in your paper. But this is all very abstract, and so what I really would like to do is to show you a few examples of what this actually means. The first example is the SSSP that was already introduced by Nicola. So this, again, is a collection of pseudo-potential libraries, and for each element in the periodic table, it essentially tells you which pseudo-potential gets the job done with the lowest cutoff. So we go on materialscloud, beta.materialscloud.org, click on Discover, SSSP, and we're presented with a periodic table. Now, the color indicates which pseudo-potential library is suggested for this particular element. The number is the cutoff in Ritback, and what I didn't say, there's two different versions of the SSSP, one intended for precise material modeling and one intended for high throughput screening. So now we're in the efficiency version, and it says for carbon, it suggests, in this case, the potential from the PS library 1.0 with a cutoff of 45 Ritbacks. And that is nice and fine, but how did it come to this conclusion? So I can click on the element, and I get an overview of different properties that were computed for the different pseudo-potentials. I'm not going into that in detail. There's an equation of stage versus an all-electron calculation, again, for the different pseudo-potentials. And a few other plots, like a cohesive energy as a function of wave function cutoff, and what I'm going to look at here is the maximum phonon frequency as a particular Q-point, again, for the different pseudo-potentials. And this is all nice and fine, so if I'm mainly interested in converged phonon properties, this plot can help me decide which pseudo-potential to use, but the problem with these user-defined interfaces is that no matter how many plots you make, you will never be able to expose all the data you have. And this is where AIDA now comes in. So in this plot, actually all of these data points link to an AIDA node. And when you click on the data point, you get to the node in the database. In this case, this is some post-processed data from an AIDA calculation. You can see who did it. And then here, using this provenance browser, you can go up the AIDA graph and see where this data came from. So this is, if you jump over this Python function that did the post-processing, you eventually get to the node that represents the calculation for the phonons. So you can look at the input file that was used, or any of the outputs, for example, if you want to download the dynamometer matrix. And here, again, in the provenance graph, you see all the different inputs and outputs that went into this calculation. And, of course, one of the inputs is, for example, an SCF calculation that was done with the PW code. So you can go further up the provenance tree. By the way, note that this is not done by Gianluca Pandini, so somehow Nicolamuni was able to, Gianluca Pandini did the post-processing of the calculations that were done by Nicolamuni. And, right, so here we are now at the quantum-expressive calculation. And one of the things that you can see here is now the structure. So the structure, for example, is something that you did not get from the plots. It's not included in our interface because we didn't think about including it. But you might want to know that the structure that was used to do these convergence calculations or what you might want to do is say you have a new sort of potential that is not in our list. You want to redo the convergence test using exactly the same parameters as we did to make them comparable. So you download the input files and you redo the calculations. And then if you're not happy with downloading individual files but you want to have everything, sorry, this is not what I wanted, you go to the archive section, you find the entry for the SSSP there. So there's a UI that will be cited, I guess, in the archive paper. And you can download the whole AIDA database, you can download an archive of all the plots and basically import it into your AIDA instance and start your calculations from there. For the second, so there's also an example of there's also a section for the 2D materials work that Nikola showed earlier on. I don't have time to show all of that but you're welcome to have a look on materialscloud.org. So I will jump over that to the phone workflow, which is another example of what Nikola showed but now we're going to look at this in a slightly different way. So this is part of the work section of Materials Cloud. So we go to Materials Cloud, go to work and click on the Jupyter button and what happens now is at CSCF there's a Docker instance started for me and in this Docker instance there's a Jupyter notebook server and what I see now is nothing but the Jupyter notebook that is rendered as a web app. And down here we have the phone on workflow that Nikola talked about and while it is true that it is very easy to use what Nikola didn't tell us is that of course you still have to set up the machine on which this workflow can run. And setting up this machine you need to know a little bit about how to install Aida, how to install Jupyter, etc. This is something that Materials Cloud takes away.  So the reason we use Jupyter notebooks and Python here is not because they give you the most fancy user interface, they do not but because we believe firmly that this is the simplest way of writing these apps and so what we're going to do now is we're going to edit this app live and add another example structure here. So at the moment we have four input structures, let's add silicon. So we click on edit app. All of this is now the source code of this app. Everything is editable, so also the text which is simply marked down and now we simply search in the quell code for the first occurrence of diamond which was the first element in the list. So this is the list that generates the dropdown and so this is essentially what I did when I modified the app because I didn't write this app, it was Giovanni Pizzi and Nicola and I thought let's make an example of how to add a new structure. One thing is the dropdown list, another thing is you need to actually generate the crystal structure to give to Aida. This is just for lines here and why is that is because it's using the crystal function from the atomistic simulation environment which just needs the atomic and it's just the element, the position in the unit cell, the space group and the cell parameters. Of course silicon has the same space group as diamond so we essentially just need to change the lattice parameter and a few variable names and that's it. When we're done we click on save and we go back into app mode and now we should have added silicon to the input structures and we can submit the format calculation with silicon. So this was not sped up that is real time and the message that I would like to give is if you know how to program and if you know a little bit of Aida then you can write such a workflow. Skip over the results because I want to show another example which is from another group, this is from the nanotech services laboratory at EMPA in Switzerland and this laboratory is a mixed theoretical and experimental laboratory and one of their main lines of research is the synthesis of atomically precise graph in nano-rhythm and so the experimentalists every now and then they ask the theory guys could you please investigate this structure because we want to synthesize it and what they did is they programmed both workflows inside Jupiter and interactive ways to browse the results that they obtained the calculations done using Aida. So this is an example of browsing their graph in nano-rhythm database. So this is a very specific user interface for this use case you see a structure of the nano-rhythm and a few properties and now you can interactively explore some of the properties of these nano-rims. For example you can compare the bandgap of these two nano-rims you compare it starts a small work function a small calculation that runs I think in this case directly on the virtual machine which simply plots the two structures side by side together with the Fermi level. Another thing you can do is you can show the projected density of state so this might be interesting if you are designing the edge of the nano-rhythm you will want to know which atoms are particularly important for the density of states near the Fermi level so by default it shows the full density of states for both spin up and spin down and then you can select one atom and if you wait a little bit it shows you the density of states predicted on this particular atom. Again there is also something that experimenters might want to do. Finally you can have a look at the local density of states so this is very important for this group because they do scanning probe microscopy in particular scanning tunneling spectroscopy and so you can select a particular band structure and what it shows you here is now the local density of states and on top of the ribbon at a particular height for this particular k-point. So this is something that you would get if you do for example a constant height scanning tunneling spectroscopy scan over the ribbon and this is something that specialists can directly compare to experiment and below here you have the spin density which is another thing that they are interested in they can download the picture and put it into their presentation so they were in the beginning the experimenters were quite skeptical about getting this work started it sounded like a lot of work and they said okay maybe I'm not sure whether this is going to be useful but they have since changed their mind so this is from the head of the experimental laboratory and he can use this interface for comparing band structures for looking at the properties of these ribbons and well I would say they have been won over let me mention one last thing and that is quantum mobile so what is quantum mobile quantum mobile is simply a virtual machine image that you can load into the virtual box software that runs on any operating system so Windows, Linux, Mac OS and what this takes away from you is the necessity to set up AIDA and Jupyter so inside virtual box you have AIDA and Jupyter pre-installed you have all of the max codes pre-installed plus CP2K as well as there are AIDA plugins so they are ready to be used through AIDA so if you have like a lecture where you would like to use AIDA this is something that you might want to use and the last point I would like to emphasize is that this is a by design this is a very modular setup so we don't just have the virtual machine image but on GitHub we also have the scripts to set up the virtual machine and if you need for your lecture some additional tools that are maybe not so easy to install or you have some other modifications that you need you simply go there you clone the GitHub repository you make a few adjustments and you produce your own quantum mobile so let me conclude so AIDA is our way of dealing with the high throughput problem and in particular the AIDA graph is our map to the data jungle and what I can promise you today is that if you do your calculations with AIDA now they are ready for open science material cloud is a younger project it's now in public beta but the archive is now accepting submissions from our partners so if you affiliate with Mux for example and you're very welcome to check it out and about the Jupyter part so my main message it is simple to write also there the workflows are shared on GitHub and run it wherever you like run it on your own machine run it on quantum mobile or run it in the material cloud I have to acknowledge the many many people who are working tirelessly to make materials cloud AIDA better and better both at EPFL and also elsewhere with this I thank you for your attention


All right, so yeah, I'm Tyreyn Abelay. I am managing director of an agency called DRAWL. We call ourselves the Enterprise Experience Agency, but what that really means is we do an awful lot of Headless. We also own headless.com and I'll tell you more about that a bit later. The general idea is we want to start building a platform to engender improved development resources, guides and so on for Headless WordPress and other Headless CMS y gallwn y cyddiw, ond dwi'n creu'r clywir, ac yna'r fanhawn. Cysylltiad, mae'n clywed. Felly, y dyma'r siwr, yna'r sefydliad mewn ei ddweud, gallwn hwnnw i ddweud y teimlad BT, gan y gallwn ni'n sig g mencion SOE. Mae'n ddweud ond dwi'n golygu'n cyfnod gyda'r bydd Nîr. Mae'n ddweud y cyddiw i'ch ddweud yma'n gof Plusau Cymryd. Headless. I think that direction it's going is more about composability than just Headless as a technology. Finally, how you can benefit from it in normal WordPress builds, and then going into a full WordPress, a Headless WordPress builds rather. Just to start off, you're all aware already, but Headless has been done before out in the wild. there has been TechCrunch which was kind of earlier on, when are you? There we go. Well done on TechCrunch. There is the time, not sure what happened to the S. They have a bit of a headless setup, if you want to talk to Ian about that. They have some interesting stuff going on maybe arguably more composable than headless. We have built Andrew Authority and SoundGuides and more recently we have rebuilt wpng's website ond heddler's wordpress and done some really interesting stuff I'll show you a bit of that later on So to start off let's talk about kind of what it's been understood as. I think heddler's is often talked about as just the coupled back end of front end, which obviously that's exactly what it is But I think that kind of where we're going with it now is more just this idea of composability overall I think that as we go forward, actually Tim mentioned this in the talk, that there is a bunch of benefits of having things distributed, so security could be one of those but I think that it also allows you this flexibility as you kind of build out functionality to keep things siloed, keep things separate and allow you more sort of room to grow features without building in high complexity into one place So is it just the buzzword? Kind of it is But I think it's more because of the way people tend to see heddler's and not so much because it's useless, I think it really has some value That's kind of proven by the fact that enterprise rely on it quite heavily They rely on it obviously because they do things at a massive scale they've got often a bunch of functionality a bunch of integrations the bigger the company that list can grow into the hundreds and so inherently things are heddlers, things are composable because you've got to integrate so many random different things One thing that I will pull out now is that we sort of see it as a philosophy and it kind of goes across three different things so on the design side I think that there's an opportunity to build composable from the ground up so that means the classic design library type stuff so icons and then up from there into full components so you've got that atomic system of atoms molecules, organisms, all the way up into larger components so you all know what a design library is and then sort of the same thing on the tech stack side so we'll get into microservices and the MAC alliance in a second but it's that MAC alliance thing of everything should integrate together and we should be able to use the best tool for the job in every situation and then finally on the development side so heddlers obviously you end up building things in React or Angular but I think a lot of people are doing React but in React it sort of encourages you to modularise things and encourages you to break things out into components and separate functionality into different sections and you get that same composability thing mirrored at a sort of code level inside a lot of front-end JavaScript projects so I think composability really should be seen as always try and silo out bits of functionality design or features into separate sections it also allows you more flexibility as you develop instead of developing into one massive code base you can develop into a smaller one that's more purposeful and more focused on a specific feature so some quotes so I think that the general idea is that I think that business owners are seeing heddlers and composability as a way to mitigate risk one of the other things that we don't really talk about with this stuff is that if you build something monolithic you're investing all of your time money, effort and intelligence or expertise or know-how into one massive thing it's not a bad thing and in some situations well, in a lot of situations that makes a ton of sense, it simplifies things but I think that the way that people are using heddlers most successfully or using the idea of composability most successfully is when they're using it to accelerate their business and they're using it to sort of get a head start by going to a specific sort of vendor let's say framework in the case of React to get a head start in a way that makes a big difference for their business so instead of trying to spend years getting a single page application like experience on WordPress just build the React front end and sort of use the best bits of that particular framework so the Mac Alliance has kind of done this all before and so kind of a lot of what I'm saying is a straight rip of what the Mac Alliance stands for so microservices break everything out into individual bits of functionality API first that should be able to be integrated into anything, anything you build should be able to integrate into anything else you might want to build or use cloud native I like this one because scalable and flexible and resilient servers in WordPress are tricky to get right in the React and sort of it's a lot easier and more common and then finally headless I don't think I need to explain that one so once again separate chunks of functionality as there is reusable and distinct components in microservices basically harping on that point of go to the best tool for the job whenever you can so let's show an example real quick so this is what we do on the design system level it's nothing special hopefully all you guys are pretty familiar with Figma boards that look like this but I think the important thing to think of here is that this is yes this is the design side but realistically we mirror this all the way up to the top so and that can that can get into complex things maybe you've got a sort of meta navigation feature that is spanning across loads of sites ideally you break that up into something that is very easy to implement and transferable to any other sites you're working on and that sort of thing and I think that so this particular quote I think is a bit like clearly MAC Alliance is pushing for a specific goal here they are pushing for that MAC Alliance ideal of integrate everywhere and so on and they are pushing for more people to come on board but I think it still proves a point we've obviously seen a lot of success with MAC Alliance and I think it's generally where the industry is going you're getting more and more I can't remember where I saw it on LinkedIn probably but I think the number of things that marketers have to integrate and it's the same situation in publishing, same situation in e-commerce the things that people are having to integrate is becoming a wider and wider array and I think it's more and more important as developers and agencies that we, you know, sort of open ourselves up to that world because it seems to be the thing that's coming down the road lots of people have a lot of success and I think that there's a lot of concern in the WordPress community because it's something quite new I think the reality is those that you can build headless quite successfully and you don't necessarily need to use out on all the nice benefits of WordPress so what that looks like is essentially instead of having everything in WordPress you start to look at a system like this so if we're looking at marketing tools for site tracking obviously you've got things like analytics or mix cloud or that sort of thing you've got product information management systems you've got campaign systems you've got promotions and discounts and loyalties and you can go for loyalty line for your loyalty program in an e-commerce situation for a UI framework you might go for React or maybe you prefer Angular or Vue for application it's next or next or something along those lines for API you can choose from rest API you've got loads of options and this is the cool thing is that in amongst all of these this is maybe just a small selection for any one of these things you can choose something that's big up a 10 and it threw me so it's like what am I supposed to do with a 10 anyway so you've got options throughout all of these things and that's a nice thing is that when you come to building your specific platform let's say and you've got a client who needs a really specific thing instead of saying can we find a way to build this very specific functionality in WordPress maybe you just go to a vendor or a SaaS platform or something that provides that thing in exactly the way that particular client or use case needs and that's a nice thing about that flexibility I'll also say that I think this is this is kind of the lifestyle of it but there are those other things once again that security like for example security is a really important one like spreading the complexity across a range of services really does do wonders for security you have to imagine that if you tried building all of these things into WordPress you're going to get a lot of code complexity and feature complexity and it's a lot of stuff in one thing obviously yes you can split things into plugins and you don't have to build it all into core or a theme or anything like that it's nice going to someone who's going to do one of those things very well i.e. loyalty line probably will do a better job of a loyalty system than you can build into WordPress or WooCommerce for example quick one if anyone does get into headless just install vanilla extract is really good it basically allows you to build a tailwind type CSS framework but built at compile time this is kind of the nerdiest thing i've got in this set of presentation slides but it's really worth it and it completely changes the way you build the frontend alright so one's headless a bad idea and i think this is an important one because i can come off as a little bit too confident about headless when the reality is it doesn't work all the time in fact a lot of the time it doesn't work so one lacking the team expertise that's not a jab at you guys for not being able to do it that's just the way it works obviously headless relies heavily on javascript and knowing that side of the world if you don't have experience with building single page applications it might be tricky getting into it it's also sometimes going to cost you significantly more if you don't have the team or you've got to hire sort of externally to do it it will cost you significantly more i don't think that's a forever thing building it and you've got the team in house you can definitely manage it but it can cost more and then finally adding unnecessary complexity there's been a push in the last year or two i think or i'm hearing a lot of SMBs shooting for headless i don't know if headless makes sense in the SMB space all the time i think there's use cases for sure but i think generally speaking what you want to look at is am i going to give myself an unnecessary level of complexity to deal with even once the team's gotten up to speed if you think that you're just adding complexity that's going to extend timelines 20% forever just don't do it if you're not getting any benefits that sort of outweigh that additional time cost but i still want to have a piece of the pie so firstly you probably all heard of hybrid but essentially there are things that you can do to get some of those benefits if you want fancy animations and fancy UI you can embed react and all of the javascript frameworks into a site specialised roles i think is an important one one of the things that headless forces you to do is separate your back end and front end team and so that ends up meaning that you've got experienced, bless you by the way you've got experienced front end devs working on front end stuff and you've got experienced back end devs that classic thing of people do stuff better when they enjoy what they're doing i don't know how many devs we've got in the room but you probably have a tendency towards back end or front end so it's nicer to work on what you like then finally Gutenberg blocks is composability in a sort of UI system i think that everyone's probably very aware of Gutenberg blocks these days but i still do hear tales of people not building sites with them so get on it and then the good bits this is once again the stuff that you know already it's omni channel, it gives you more sort of styling and front end capabilities it gives you access to things that are far more sort of specialised for front ends i didn't pause that time but now i've just made everyone aware of the fact that you just did it again and native like UI UX i think this is an important one people have been talking for the last five years about native like UI and UX on web applications leading to higher conversion rates and just general stickiness with people, i think people feel a lot more comfortable in a native like UI and then finally localisation, personalisation, A-B testing you can do all of that stuff without any performance issues you can bundle it into your original request to the back end and you won't see any performance slow down on the front end so that's cool content editor experience is the next thing people tend to ask about their like but wordpress is supposed to be easy and plug and play and the good news is you can actually do it you don't really lose anything it does take a bit of work but you can get a pretty like for like situation where you get full editing capabilities in Gutenberg blocks on the back end and then obviously you've got your front end so the sort of upcoming look at headless, i think that here it starts to get a bit like okay am I do I have a dog in this raise or something but the honest truth is this is just sort of where it's going i think that there has obviously been a lot of hype around headless but that is reflected by the fact that companies seem to be moving in that direction I don't know how quickly it will get to the point where everything is that way or for all ever get to such a world but it's definitely where it's going and of course so onto headless.com so a lot of the things that I've talked about has just sort of been scratching the surface but we think that there's probably a better way to do it which is build a platform that allows us to share information and that's headless.com so it will be a sort of platform agnostic and community agnostic or rather agency agnostic thing where we can essentially share resources, guides documentation and so on and I'm going to have to rush otherwise he's going to hold up another sign right click is gone the roadmap very quickly is firstly just sort of get a base level there next we want to start sort of building resources into a fuller capacity and get complete coverage over core integrations like Yoast and ACF and so on and then eventually we'll get round to doing a starting framework and what you can contribute you get to be a thought leader give back to community and collaborate with other experts it's a classic word press community stuff that we all know and love and we're hoping that it can become a really good sort of knowledge resource for headless and essentially reduce the level of effort for developers to get into it and marketers to get into it and publishers and so on finally a quick summary you specialize technologies use the best tool for the job why not don't limit yourselves modularize modularize and reuse functionality I think that's something you can apply to any situation I mean to be fair the first one you can apply to any situation as well and finally enable your devs to work with frameworks that are really targeted for the specific thing they're building once again you know javascript works really well on the front end it runs great in browsers so in whatever way you do it whether it's hybrid or headless get the most out of it and once again obviously word press is a great backend I think that about covers it yeah that's pretty much it so yeah questions yes 10 to 15 minutes can go on any question how do we make sure word press is seen as a good sort of headless cms because more challenges clients have see stuff now how does word press like fail because the cms target themselves it's like a headless cms word press doesn't do that but personally I think it's really good yeah I think so as well so the weird thing about word press and just headless cms is in general is that if you use a headless cms there's not really a high level of effort it's just the way it works so if you go to like Magnolia or Sanity or Contentful or any of them you have to build an API it doesn't just do it all for you it's kind of the same situation and so really then the comparison becomes the content editor experience which arguably I think we would all agree is better in word press and so in terms of convincing the client I think it's in my mind I think it's more about giving them a general over-understand overall understanding of what the situation is with headless and then word press and its content editor experience sort of speaks for itself questions so when we did the WP Engine site what we really wanted to do was mirror our sort of like front-end code on the back-end but it was something that we ended up not doing because it did sort of reach a level of complexity that we weren't really happy with that said there are it is at the end of the day similar styling so you can share that code on initial build and then as you make sort of feature updates to a block let's say it's a much smaller ask for a back-end developer to add those sort of slight design changes or something like that the reality is as you probably saw from that slide I won't go back to it but the back-end side is not one for one the front-end but it gives a really close 99% representation so it's still a nice sort of editing experience I would say it's kind of something I didn't want to get into you need to really go into the setup to make it easier put it like this it's more a case of what you're used to I think so all honest truth basically we started more as a headless agency than we did a wordpress agency we're fairly young and we started more with headless than we did wordpress and I've got to say at a sort of dev process level I think we prefer working on headless than we do just sort of monolithic I think setup-wise any most like next apps or most front-end apps have a fairly simple sort of dev and local development process where you can have a live preview and then running the back-end on local is the same process that you're used to whether you're using local or docker or some sort of custom setup to run it locally so I don't think it adds a high level complexity but once again if you are able to separate out teams and have a front-end dev working on the front-end and a back-end dev working on the back-end then hopefully you shouldn't have to set it all up on your own does that answer? I don't know sorry go ahead go on how do you feel that if you go to a really composable headless approach how do you feel this should maybe adapt or evolve our attitude towards looking at the wider WordPress ecosystem in particular context I'm thinking here is something that typically we're looking at e-commerce in a WordPress world we're going, oh what will we use with but once you start thinking now it's headless I've got much more options for API's compatibility what is the ecosystem we need to take account of if we think of WordPress as something in a headless world well I think that's the cool part actually is it gets WordPress into that game it gets WordPress into oh it's actually one of the potential vendors for CMSs alongside all of the other things that integrate into each other so obviously you mentioned big commerce and big commerce of the Mac Alliance and part of that world of tech stack that integrates to everything and so that is the fun thing you're not talking about what's a WordPress plugin anymore you're talking about what has a REST API and a lot of bloody stuff has a REST API basically so you can kind of open up your horizons in terms of what possible was that the statement you were kind of turning into it's like the challenge of it we're really comfortable being in this WordPress world so I think so I think that that challenge of it is I think that the breakpoint this is such a touchy feely thing to say but I think the breakpoint for when you should go headless is you'll feel it like it will reach a level of complexity what you're trying to do that you're like oh at this point I should just do it headless or I should do it compose a war API I think there's a bunch of stuff like probably the first 90% of stuff or 90% of websites that any of us are going to interact with really don't need that level of complexity but there'll be something that you have to do that will be so tricky or so like the functionality you're looking for will be a level of complexity where you'll just be like you know what this could be headless because before that point you can get away with a plugin or you can get away with a of the shelf solution but yeah there's a level of custom I suppose that you get into it's very hard to define that in a general way but I think it's going up into sort of the enterprise or you've just got a very large feature set or just like a feature complexity yeah go ahead how micro should you get I know within the sorry say that again how micro should you get within your technical architecture and with some purest of the micro service space you know go right down everything is an actionable message and then you build it up from there as a basis it's like you know we talked about different degrees I suppose about where you sit with a matter of micro skill what is it still very practical or are you looking for something I think that's these sorts of questions I think they're the things where and I think with headless everyone wants to ask the question like including us of like when's the right time to do this do that but that's a question that's really going to depend on the client and the budget because one client might have an appetite for spending a bit more in order to get a more focused end result focused is in focused on specifically the goals that they've got whereas a smaller client you know maybe isn't willing to go to that level of complexity or sort of in depth planning and it's just not going to make sense but I think basically you should go you know if you think of it as like one of those sort of tree diagrams or you've got one big thing at the top and then it sort of branches out I think you keep branching until you're getting to a point of you know it's too much for your team to manage too many you know services involved to keep track of or just diminishing returns for the complexity that you're adding in by adding those services any more questions oh my god does that mean I can get off stage now no is that everything awesome


The National Broadcasting Company and its affiliated stations present the Pacific story. In the mounting fury of world conflict, events in the Pacific are taking on ever greater importance. Here is the story of the Pacific and the millions of people who live around this greatest sea. The drama of the people whose destiny is at stake in the Pacific War. Here, as another public servant, is the tale of the war in the Pacific, and it's meaning to us and to the generations to come. Japan's Highway of Steel. 23rd and 25th in the waters of the Philippines. The Japanese Navy suffered its most disastrous defeat in the history of the Empire. 24 Japanese warships were sunk. 24 out of the 60 Japanese ships in the battle. 34 were damaged. 34 knocked out of service for months. Only two Japanese warships escaped without harm. By this victory, the U.S. Navy won control of thousands of square miles of the western Pacific. Also, there were other figures to report. We are sinking Japanese shipping at the rate of 2 million tons a year, and Japan can build only 1 million tons a year. These were the cold facts. Japan is a maritime nation. To supply her far-flung troops, she must have ships. And to bring back raw materials from the land she has conquered, she must have ships. But the Japanese have long been preparing for the eventuality of being throttled at sea. Today, as the U.S. forces draw the news tighter around her sea communications, Japan's inland strategy becomes clear. Japan is developing a railroad system to stretch from Korea to Singapore. The development of this railroad system is linked with the basic thinking of the Japanese. Wars are won by land fighting. Ships are for the transportation of troops. Observers who watched Japan's development of the railroad system on the mainland of Asia in the last third of a century inquired into the Japanese thinking. Do you mean that you do not think of ships as a fighting force? Ships are for transport and for protecting communications. But what of Admiral Togo's crushing victory over the Russians at Tsushima? The Russian fleet was 18,000 miles from home. Every advantage was ours. That implies that you Japanese avoid taking risks with your vessel. You might say that we prefer taking risks in another way. Your country and Britain think of your Navy as defensive weapons. You use your Navy to keep the enemy away from your homeland. We use our Navy to take our troops to the lands where the decisive battles will be fought on land. I see. Then your Navy is a servicing unit for your land forces. It is the land forces that win wars. With this thinking, the Japanese long ago took steps to assure her land forces of transportation on the mainland of Asia. After Admiral Togo had destroyed the Russian fleet, the Japanese took over Russia's leases of Port Arthur and Dyeron in Manchuria. With this, they also took over the railroad connecting Port Arthur and Dyeron in the interior of Manchuria. This became the first unit of the Japanese rail system on the mainland. And soon they were busy with the second unit. Mr. Asikawa, my government requests an explanation why this bridge is being built across the Yellow River without the consent of the Chinese government. Has not the Chinese government given Japan rights to maintain the railroad between Mukten and Anton here on the border of Korea? The rights you speak of were forced from us, but the Chinese government gave no rights to Japan to build a railway bridge across the Yellow River. The bridge is necessary in order to make direct rail connections between Busan and Korea and Mukten in central Manchuria. But the Chinese government did not intend that Japan should develop such a railroad system. We are building this bridge at our own expense. I must tell you that the Chinese government does not approve of the building of this bridge and that building operations must be stopped at once. But the Japanese went on building the bridge. And when it was completed, they had a railroad extending from Korea, over which they then held a protectorate, up to Mukten, and from there up into the northernmost reaches of Manchuria. This railway became the spearhead of Japanese aggression on the mainland of Asia. The South Manchuria Railroad, which the Japanese now control, is a desperate threat to us here in China. I say that we must develop a railroad of our own and a seaport to supply it. You have recommendations to make? Yes. Look at this map of Manchuria. Yes. We will develop a port here at Hula Tower. That is very close to the Japanese control of Beijing Mukten Railroad. Less than ten miles.  British and American bankers offered to finance the development of the port at Hula Tower and the railway to Siberia. But the Japanese were not caught napping. Is it not true that China has a treaty with Japan concerning such a development? The secret treaty you refer to was rung from China by force. If China should proceed with this project without referring it to Japan, it would be difficult to estimate the seriousness of the trouble that might result. The Japanese forced the Chinese to drop their project. Then the Japanese planned their own railroads in Manchuria and off China and had China build them and help pay for them. We will, of course, advance the money for the building of the railroad. The Japanese advanced the money, but their purpose was clear. In effect, Japan's got a mortgage on those railroads. And that isn't all. The Japanese sought to it that the railroads were built where they will do the most good in time to come for the Japanese. The Japanese were looking ahead to the time when they would need and use those railroads. And meantime, they lost no opportunities. In World War I, Japan came into the war on the side of the Allies and seized Qingdao. She also seized the Kiao Chao Xin An Railway. And then one day in 1915, to the astonishment of the world, she made her notorious 21 demands on China. Japan demands that the Chinese government consent to the building of a railroad from Qifu or Lunghao to join the Kiao Chao Xin An Railway. Japan demands that the Chinese government agree that whenever permission is granted to a third power to build a railroad, or to make a loan for the purpose of building a railroad in South Manchuria and eastern Inner Mongolia, that the consent of the Japanese government will first be obtained. Japan demands that control and management of the Kirin Chang John Railway be handed over to the Japanese government for a period of 99 years. Japan demands the right to build a railroad connecting Wuchang with Kiyukan and Manchang. Another railroad between Manchang and Hang Chao. And the third railroad between Manchang and Chao Chao. Japan demands that China must consult with Japan whenever the need arises. China resisted but was forced to accept five of the 21 demands. Step-by-step Japan was developing the railroad which one day she would use the good advantage in her bid for world power. On July 7th, 1927, a conference of Japanese military, political and industrial leaders was held in Manchuria. What they discussed made world history. Rettos! Rettos are not to deceive ourselves. Transportation is the key to operations on the mainland. Or not only that, it is the key to our national defense. Or do not think in terms of defense. We must think in terms of expansion. If we wish to develop the natural resources of the mainland and strengthen our military position, we must build a railroad, especially in northern Manchuria. If we build a railroad in northern Manchuria, our purpose will become obvious to the entire world. Or if we control the great systems of transportation on the mainland, there will be no need to hide our designs. No, we will need transportation to conquer Manchuria and Mongolia and China. And when we have accomplished this, the rest of Asia, including the South Sea islands, will be ours whenever we wish to take it. These were the principles laid down in the Tanaka Memorial. And soon they were translated into action. September 18th, 1931. The Japanese today attacked the Chinese at Mukden and are now planning out to occupy all of Manchuria. It was no accident that the Japanese struck at Mukden. Mukden is a strategic railway point. By the time they struck the railroad, they'd so long been planning and having the Chinese build. They were ready for military operation. The Japanese took all of Manchuria. Now they have their railroad system from Korea up into Mukden, and from there to the important points of Manchuria. Watch Beiping next. Observers on the scene saw this coming. The blow fell where they expected it. July 7th, 1937. The Japanese today attacked the Chinese and the Marco Polo Bridge outside Beiping. They are now moving to occupy northern China. From Beiping, they drove on Shanghai. Mile by mile, they took over the railroads as they advanced. From Shanghai, they struck westward and southward. They drove on the Tiantang Bridge, crossing the Tiantang River at Hang Chao. And in the van of their onslaught, there was frenzied activity at the bridge. Get that cart moving across the bridge. One of the wheels is broken. It's lost down under the load. Well, whip up your horse and drag the cart out of the way. You're holding up the traffic on the bridge. My horse will be 106. He cannot drag the wagon with the broken wheel. Everything we have is on the cart. Drag that cart out of the way. You'll have it jumped over the side of the bridge down into the river. Now move. My horse cannot pull it. Here you. Help this man tie a plank under the broken hub of this cart here. And the rest of you, man, help them drag it across. Now, sir, do you think the Japanese will be here? I don't know, but we're moving everything possible over the bridge before they get here. Keep moving over there. Keep moving. Oh, I've never seen such traffic. We're moving everything, military supplies, government supplies, food, railroad stocks. What are you going to do with the bridge? That's up to the military. Keep moving over there. Oh, that bridge was completed a lot more than two or three weeks ago, wasn't it? Yes, and it took years to build it. The lucky thing we have it, for at least we can get some of our supplies across the Hang Chao and then back into the rear. We have the plank tied under the broken wheel now. All right, good. Take your men and give them a hand getting his cart across the bridge. All right. Get up there. Get up there. Look at that broken wagon dragging across the bridge with that load. Keep it moving up there. What is from the colonel? You ought to stop all traffic across the bridge at once and to withdraw to safety. Yes, sir. Stop all traffic. Lockade the bridge. All right. What about all this traffic lined up to get across? They cannot get across. The Japanese are coming. The traffic that was stopped swelled out like a sea on the miles approaching the bridge. Motor mobiles, horses and wagons, trucks, locomotives and railroad rolling stock. The destruction of the chim-pang bridge haunted the Japanese drive, but not for long. The Japanese swarmed across the river and took Hang Chao. And within a year, they had taken Cam Ton, China's principal force for war materials. With the taking of Cam Ton, they controlled the operation of the Cam Ton-Hang Chao Railroad. Unit by unit, the Japanese were seizing controls of China's railroad. Cam Ton had fallen into Japanese hands and Hang Chao and Nan Chang and with them went their railroad. We have now been at war more than a year. And it is now clear that the strategy of the Japanese has been to paralyze us by seizing or controlling our railroads. They hoped they would force us to surrender. In order to continue resistance, we must fight to hold every possible mile of railroad and to build new lines, whatever we can manage it. We have lost Cam Ton and we have lost Hang Chao. But we still control much of the railroad lines between them. Yes. It is my belief that we should tear up the sections that are in danger and move them to sectors where they will be of more use to us. The rails and the rolling stock and all. Everything that can be moved. Well, where would you move it? To the Hang Yang Guiling District. If we do not move it, we shall lose it all to the enemy and they will use it against us. It was decided. The task of moving a railroad from one sector to another was undertaken. Tens and hundreds of thousands of Chinese bent their backs to the job and by fall 1938 traffic was moving over the new line. Report. In the first ten months of operation, 480 military trains were moved over the new Hang Yang Guiling section of railroad. Report. One million persons or a million tons of supplies were moved over the new Hang Yang Guiling section of railroad in the first ten months of operation. Where the Chinese could not save their railroads, they were moving them. But the Japanese continued their relentless drives and troubles mounted for the Chinese. Since the fall of Canton we have been bringing war materials in through Indochina. But today we have been informed that the French are not in sympathy with trans-shipping through Indochina. Have they stopped our shipment? Not yet. While there is still time we must build a railroad of our own down to Indochina. The plans were worked out but the Japanese continued to swallow up China's remaining railroads. By the middle of 1939 Japan controlled most of the railroads from the north of Manchuria down through north China down to the southern port of Canton. By the middle of 1939 the Japanese had seized 80% of the 11,000 miles of railroad that China had at the opening of the war. By the middle of 1940 the situation was still worse. Strong units of Japanese troops landed at Haifeng, French Indochina. They're landing a lot of Japanese. What are they going to do? Take over Haifeng? The Japanese have come in to prevent Haifeng from falling into the hands of the enemy. Whose enemy? France has been out of the war since June. But Indochina is not at war with China or in the life of Japan. We are not in a position to prevent the Japanese from landing here and at Hunaya. Oh, it's Kanai too, huh? What about the airfields at Tong King? The Japanese are also in control of them. Looks to me as a bystander that the Japanese have taken control of all northern Indochina. These are protective measures. What do you suppose this will do to the Yunnan Railway into China? The Chinese are already tearing up the section of the Yunnan Railway near the Indochina frontier. Wow. Well, these troops coming ashore here have cut off just the box China's last outlet to the outside. There is still the Bemerode. But the Bemerode was not a railroad. And soon it too was closed.  The coming war in the Pacific was shaping up. Now it was 1941 and halfway around the world, Hitler sprang at the throat of Soviet Russia. The far east shook with the reverberations. The Japanese already firmly established in northern Indochina now drove southward and occupied all of Indochina. And from Vichy France came an important announcement. On their floor, the Vichy government has today signed a protocol with the Empire of Japan. These Japanese troops have come down here to Saigon to protect this French naval base against the enemy. That's what Vichy says. Could they just buy a coincidence? Also be interested in the railroad that leads from here in Saigon up to High Falls? What do you think? Well, to try to put this occupation of Indochina means to the disadvantage of China. It also should mean something to Britain. Because of Singapore? Yes. Japan now has not only a handy little springboard for an attack on Malaya, but also on Singapore which by the way is only 650 miles away. At first the Japanese had gone into Indochina to blockade China. They were converting Indochina into a military base for further aggression. Two days after Pearl Harbor the Japanese engineered the so-called surrender of Thailand. And two months later they had taken Singapore. Their task now was to close the gaps between their railroads, link them together in one great interconnecting system. But while the Japanese were forging their overland railroad collider on the mainland they were losing at sea. Forward torpedo room. Number two out tube. Cube's ready forward, sir. Zero one four. Zero one four. Zero two zero. Zero two zero. Zero one zero. Fire one. Set up on number two. Number two ready, sir. Fire two. Total number of Japanese ships sunk by Americans. Eight thousand. Seven thousand. Six thousand. Five thousand. Four thousand. Three thousand. Two thousand. One thousand. Now let's get back to the carrier. Throughout 1942 and 1943 U.S. land and sea forces attacked Japanese shipping and inflicted staggering losses. Look at this. I saw that. And she knows planes have sunk a Japanese cruiser in a flock of smaller supply ships. We must have sunk a couple of million tons of Japanese shipping. Well, we have. Maybe two and a half million tons. I can't see how Japan is going to make up those losses. The chances are she can't. She can't build much more than a million tons a year.  That'll not stop the Japanese operations on the mainland. And that is our big problem. As the U.S. Navy carried the war deeper and deeper into the western Pacific into the waters of the enemy, Japanese sea losses mounted still higher. But meantime in China it was becoming increasingly apparent that Japan's inland strategy was paying off. By the spring of 1944 the objective of Japan was clear to cut China in two. And to this task Japan committed her best train to her most efficient troops. Weeks of savage fighting and Yang had the last fall into the Japanese. This gives the Japanese possession of the entire railroad between Beijing and Hangzhou. Japanese have advanced with a powerhouse drive taking city after city. Their immediate objective now appears to be the closing of a 60 mile gap around Guilin. The Japanese were bringing up supplies for the assault on Guilin. They only closed the gap between the railroads. But it would mean the wiping out of the strong U.S. air bases at Guilin. Help me. Help me move this stove. All right. Let me get hold of it here. No. There. Now I must rest. We cannot rest until we have the street torn up for the pillbox. I work all night. I'm old yesterday. Yes. And all the night before that fire. Everyone is working. Look at the hills. How they are being fortified. And the barbed wire stretched out everywhere the Japanese could come. Every street and every empty place is dug up for trenches and pillboxes. But I am so tired. I can't work no more. Rest a little. Then perhaps you can help some more. It is said that we will fight for every foot of Guilin. The Japanese will only pass when they have killed us. Come. Come. Pick up your shovel. We must get the pillboxes in here. Do not stop working. Come, Shannon. Try a little more. Yes, yes. I will try. Bye. As the tens of thousands of Chinese struggled to complete the fortifications before the Japanese came, all available American supplies were brought in. All right.   Get those trucks unloaded over there. Get going. We're going to need every ounce of this stuff. Presently the Japanese started their drive on Guilin. They averaged 10 miles a day in the early stages and intelligence revealed their strength. The Japanese are converging on Guilin with seven strike divisions. They're well-equipped and well-trained. The railroads are bringing up enormous amounts of supplies to support them. From the U.S. air bases, there was an almost continuous traffic of warplanes taking off and returning permission. Hello, Shannon. We strapped them up and down the ranks after the farmers laid their eggs on them, but it doesn't seem to make any difference. They keep right on coming. They must be advancing at night. They are. All right. Get those ships serviced. Take a breather, Lieutenant. You'll be going right up again. But in the face of the resistance, the Japanese drove on. At last it became obvious that the Guilin air bases could not be held. It took us more than a year to accumulate those supplies. Every ounce was flowing in over the hump. And there it goes up and smoked. Still liquid, the Chinese resisted to the last. Behind the Japanese, as they advanced, the railroads brought up more and more reserves, more and more supplies to feed into the battle. Airforces in China have been pushed back hundreds of miles from the south China coast. The Japanese now have an overland railroad carados in the 743 miles from Tokyo down through China and French Indochina to Singapore. The Japanese are now engaged. One bright spot is that the Japanese still have to build about 500 miles of railroad to complete their overland caradaw. And since the great part of the caradaw is in Chinese territory, the Japanese will be vulnerable to Chinese attacks all along the line during the building. Well, of course, that's a possibility. Also, railroad traffic is no match for shipping. But it is an excellent alternate. And there's still another advantage the Japanese have in this railroad system. In the operations in the islands, the Japanese were not able to reinforce their troops, not able to keep them supplied once we land it. But on the mainland, it'll be a different story. How strong would you say the Japanese land forces are in China? All would be difficult to say accurately. But there's reason to assume that she has at least 4 million combat troops in China and probably as many or more in reserves. Well, if she can keep them supplied, she has a definite advantage. With her railroad, she'll be able to transport troops quickly and keep them supplied. So even if we should destroy her navy and throttle their shipping, Japan would still be able to offer enormous resistance for their highway of steel. You have been listening to the Pacific story presented by the National Broadcasting Company and its affiliated independent stations as a public service to clarify events in the Pacific and to make understandable azug Send ten cents, insist the coin to to university of California President Berkley California. The Pacific story is written and directed by Arnold Marquess. The first score was composed and conducted by Thomas Paluso, your narrator, Gain Whitman. This program came to you from Hollywood. This is the National Broadcasting Company.


Well, home is where you feel welcome here. I feel welcome. So this is also home for me If I go abroad and if I am well accepted, then that's also my home Yes, I have I have been been all around the world and and It was not always easy and you feel that some time or another I am a migrant here, but you can be a migrant in my country as well and we treat you well in my country So you should treat as well to make the other side understand that you are not a threat and No matter where you come from Asia Africa Europe America Wherever you can be part of the society you can be integrated within the society if the other side will allow you to will permit you to and That's the most important thing And perhaps that's the most difficult thing to overcome to to gain their confidence and their And be treated in the same levels. I am a migrant so migrante com muito orgulho


Hello, I'm Professor Vaneel Urando and I'm going to talk to you today about distinguishing and using facts in legal analysis and legal application. So when you are working with a problem of any kind, especially if you're getting a story told to you by someone or as an attorney, are you working on a law school exam or bar exam? There will be a lot of facts and the key to you being able to decipher out the problem and solve is being able to categorize the facts appropriately. This method of categorization that we're giving to you is only for your internal use. It is not terminology that you would ever use on an exam or with a partner. This is just a way for you to be able to understand the facts and categorize them appropriately, but you should never talk about background facts or key facts or colorable facts or preclusion facts or red airing facts. That terminology is only a terminology that we're using with you to help you understand the facts. Okay, so to move into that we're going to provide a definition for each of the type of facts and give you an example of those facts. So to start off with, let's start with a problem. I have to smile because this problem uses the name of my youngest son and my niece and it's an old problem. It's a problem that both of them are in their 40s now and to tell you how old this problem was, I made this problem when they were teenagers. So time passes, but the law and how you approach the law isn't really different after 20, 30 years.  Issa then remounts his bicycle and pedals away. The blow knocks her out and she's hospitalized for three weeks. Cuyah is completely unaware of who had hit her and later she learns it was Issa. Can she successfully sue Issa for battery? So this is a basic fact pattern and to start off with, with any basic fact, the call of the question will dictate how you look at the fact. If I had said can she sue for assault, it will change which facts are what kind of facts. Can she sue for intentional infliction of emotional distress? Can she sue for false imprisonment? The role that facts play is completely dependent upon the call of the question, which means you should always read the call of the question before you read a problem. Because if you don't, you can be thrown off just through your reading because you will make judgments about the importance of facts that are, will be wrong when you get to the call of the question. So when you're faced with a problem, start with the call of the question. When you're faced with a question, start with the call. And that's whether it's a hypothetical, whether it's an essay question, or whether it's a multiple choice question. Start before you read the body. STEM are major part of the question. Read the call of the question and see what it's asking for. And then you read the rest of it in light of that STEM. Can she successful sue ESA for batter? So essential facts are those facts which create a dispute. Remember now, we define an issue as those things over which two attorneys will argue about. If two attorneys won't argue about it, then they are not key facts. They are not, they don't create a dispute. They are essential facts. And again, facts can play more than one role even under the call of the question. So essential facts are facts that if change, this dispute would no longer exist. So battery is an intentional tort. Okay. If you said she accidentally, instead of intentionally, you no longer have a dispute over an intentional tort. You may have a dispute over whether there was negligence. You may have a dispute over whether there was strict liability, but you won't have a dispute over intentional tort. If there is, if you change the fact that he intentionally hit her. Again, he hit Cuyah. That's for a battery. That's a key fact because if you said he threw a rock at her and missed her, then there's no touching. There's no contact. A kit battery requires a contact. And again, this goes, one of the reasons we didn't get into the facts earlier is because there is a level of law that is, that you need to know to be able to determine whether or not something is a key fact or essential fact. You are, so here you have, we say under a battery, there has to be hit. If we were trying to show for an assault, we would need to show that she actually saw the blow coming in order to show apprehension. The blow knocks her out and she was hospitalized for three weeks. Those are two different facts and they're both key facts because they both go to show a harmful contact. The hospitalization for three weeks can be, goes to show a harmful contact. If without that, we could still argue battery, but we have to argue possibly that it was an offensive contact if there was, if we cannot show harm. So those are key facts to the battery. It's not always easy to agree on what is a key fact, and so you will make mistakes, I will make mistakes, and we will, and in fact the dispute itself may be over whether or not it's a key fact. If you have a factual argument, go back to one of the earlier videos, you could have a factual argument over whether or not it's a fact, whether or not it's a key fact, but a key or essential fact is a source of the dispute. The dispute can be over the problem, the dispute can be over an issue in the problem, but there is a dispute. A lot of what you get in exams and especially when you get people off the street are background facts. Background facts helps round out the story, but when you change, but they're not a source of the dispute, because if you change the fact, they don't affect the dispute in any way. Now if they affect the dispute, that is if they cause the dispute to go away, if they introduce a doubt about an element being solved, then they're not a background fact, they're an essential fact. So for the problem that we just talked about, where she got hit is not a really significant importance. She was hit in the back of the head and the question becomes, so what? She could have been hit in the harm, she could have been hit on the leg. The key here is that there was harm and we show there was harm, but it doesn't matter if she was hit in the back of the head. That is a background fact. His riding, his bicycle are her walking down Shoria Street. The name of the street is unimportant. The time is unimportant. What difference is it 11.30 or 11 o'clock or 11.45 or midnight or 2 a.m. or 1 p.m. Is getting off of his bike doesn't affect the battery? The question is, how does any one of these affect the dispute in terms of whether she can sue for a battery? In my estimation, it doesn't affect it at all. Now you may want to argue that it does and you could make a credible argument and I'd be willing to listen to how this particular fact affects whether or not there's a battery. But as far as I can see right now, it doesn't affect. You want to make sure that you don't get into arguing background facts. Even putting background facts into your discussion takes away time and effort. One of the things you want to remember is if it's a background fact, you probably don't need in your analysis in your application because it's not going to change anything. You're just telling a story at that point and when you have a limited amount of time in a limited amount of space, you don't need to tell the story. You need to do analysis and application of the facts that are essential and important. So emotionally charged facts should not make a difference in the case. That's why I call them colorable. It's not the kind of facts that you will want to bring up on a law school exam in terms of affecting whether or not there's a battery. In fact, I doubt that your law school exam will even include things like race and gender, but you might want to, but there definitely be something you should take into consideration in the practice of law that these kind of facts should not affect the outcome of a case, but they will. Preclusion facts are facts which on their face satisfy an element or make it incapable of a element being satisfied. That is, you can hardly argue that he didn't intend to hit Cuyah when the fact says he intended to hit Cuyah. You can't argue that the contact wasn't harmful when the facts say he knocked her out. You can't argue that it wasn't harmful when the fact says she was hospitalized. Okay. And sometimes people, because they want to do IRAC, issue rule analysis, conclusion, they will make arguments that are completely unnecessary. It doesn't, when you have preclusion facts, facts that preclude you being able to make a two-sided argument, you still need to deal with it and we will show you a way of dealing with it, but you need to know that there is no dispute here. You must apply the facts to show that the element is or is not met, but you do not want to argue that they are not met. You're precluded from making that argument. Red herrings are facts that look and act like a key fact, but they aren't. They can be emotionally charged and sexy, but they have no impact on the outcome of the issue. And what they do is divert your attention.  Now, if intent wasn't satisfied and the only fact was being jealous, then that might be an invitation for you to say motive is irrelevant. And it still might be an invitation to say motive is irrelevant. It in motive is irrelevant. Eesa mounts his bicycle and pedals away, again, an emotionally charged fact because it looks like he's fleeing the area, but it doesn't change the battery, because whether he stays around and tries to help her or runs away, neither one of those situations affects the battery, the existence of a battery. So part of the problem is then how do you deal with a red herring? Another red herring is that she was completely unaware of who hit her, a red herring for a battery, but an essential fact for an assault. But the call of the question said battery. So whether her being completely unaware of who hit her is irrelevant to the battery. So the question becomes how to handle these red herring or none issue fat? Ask your professor, he or she will want you to either ignore them and to not even mention them or explain why it's not an issue. I believe it's a better, it's adds to your analysis to explain why it's an issue as long as you do it quickly and succinctly. And this is true for bar exams to explain why it's not an issue, but it's again, you do not Iraq and it's important to do it quickly and succinctly. And we will, as we progress through the course, we will give you a method for doing that. Right now, we just want you to begin to recognize that when the facts are red herring. So when in doubt, tell your press professor why the fact is ill, that the fact is irrelevant and why. Again, do so in a brief manner. Here's an example. Although Kui was completely unaware of who hit her till later, she can still hold ease the liable for battery since weariness is not required in battery. Boom. One sentence taken care of, but do not Iraq, do not crack. The issue is whether there's a contact. The rule is awareness is not necessary for contact. In this case was unaware, Kui was unaware, however, awareness is not necessarily consequently there is a contact. You don't want to do all that. See the difference between the one sentence that I did and the Iraq, which was for sentences. Instead, you want to make the statement as a part of your analysis of an appropriate issue that's not you don't want to make this a separate issue. So reading a law school exam for facts. First, whether it's a large exam with a lot of facts and a lot of problems or a short answer question. Read the call of the question first. Read the whole question thoroughly and isolate key facts from non key facts. The figure out a way that you will identify key fact and start practicing that method now. So circle a key fact or underline of these key fact or annotate the key fact in the margin of the exam by identify writing the problem or the issue it raises. So if a key fact will raise an issue or solve an issue put in the margin which issue it raised or which issue it solves. Read Pete step number two looking for additional key facts that you may have missed. That's how you read a law school exam for facts or read a short answer exam for question or a multiple choice question. Read the call of the question first before you read the body. Read the body sort of looking for key facts quickly because the key facts will help you solve the problem. So trust the process. You trust the process by working on these different parts. You've got to practice like someone who practices just notes or scales or one type of shot. You're going to have to practice just spotting key facts. It will give you some practice on in this course. But if that's all you do you won't have practice enough. What we do in this course is really to introduce you to the things that you need to do more of because you need to be studying three to five hours a week per credit hour that you're in a course. Half of that time needs to be in exam preparation and the kinds of things that we've outlined for you are the kinds of things you need to be doing in exam preparation. If you have any questions or comments post them on Moodle.


Weerfaa, jy'er on a Sonse face, Great chieftin o' the puddin race, A bindamaa, jy'y taak jy'r place, Painch, trijp, o'r fherm, Willar, jy'y worde o'a grace, As langs m'a erm.  Now horn for horn, they stretch and strive, To lather wheel fill kites belive, And all good man may slike to rive, Ah, be thank it hums. Is there that hour is French regu, Or olio that would staw a sue, Or frikasee that would macke a spew, We perfect scunner, Who looks dun we sneeren, scorn for view, On syke dinner.  Now you powers, why macke mankind, Your care, and dish them out, Their bill of fare, All Scotland once nays skinken, Where that joup's in luggies, But if you wish, her grateful prayer, Gee her a haggis. Ander.


Operation Opsen has three main strategic objectives. The first one is to raise the awareness on this rising threat, be it with the consumers or the low-enforcement agencies, which are not totally, sometimes fully aware of the scale of the problem. The second one is to enhance the cooperation between all the stakeholders, that is to say low-enforcement agencies, police customs, but also the foods and sanitary agencies, which are not necessarily used to working together. The third one is the cooperation with the private sector, because they have the expertise, they know the products, they have a lot of intelligence to be transmitted to us in order to help us fight against the criminals. Opsen 2 is definitely on a bigger scale than Opsen 1, because when we started this initiative, we had only 10 participating countries. Today, in Opsen 2, we are 28 countries, 21 European countries, and the rest are the third countries. So obviously, we managed to raise the attention of the other countries, who have understood the importance of this fight. Europe is particularly pleased with the results of this operation, which shows that we need to keep on strengthening the cooperation among the European countries. The results were amazingly good. All the countries were really involved in the operation. They have deployed a lot of human resources and efforts in these checks and investigations. So, Europe is really, really pleased about the results.


We are still looking at what we call the employment rules and regulations in the UAE according to the primary sectors. What are the regulations, what are my rights, what are your rights in the UAE under the government laws and what you should know. In today's video, we are going to look at another article that is number four. We are going to look at another article and that article is what we call article number 20 of the labor law. What does article number 20 of the labor law for article number 20 of the labor law specifically specifies that any anyone sponsor or anyone company is not allowed to employ people of the same sexes that are under what we call the age of 15 years of one age that if those two people are over the same sexes and they are under what we call 15 years of age as you the mother or you the caretaker under same you are not allowed to employ these people at all because this is under what we call the government directive this is the government directive so you are not allowed to what to go to ex or not allowed to definitely employ such kind of people because they will be considered under age uh uh uh under age and violating what we call the rights over in the the rights of their rights in one way which will definitely people will see that is child labor one way. So when you look at article 20 for all it should be just be to remind that article 20 talks about of not employing anyone until it reaches what we call the accepted or what we call the consent the consent days or expected actual expected days that is supposed to get married home and they will be supposed to get off whatever it is then probably can try to go off to this time thank you so much for coming back this yano thank you so much see you again in the next video this mix from the mix creation


In a previous livestream, we simulated a successful phishing attack where we sent an email that looked exactly like one you could get from Office 365. In this video, we will show you the red flags you should look out for to prevent you from giving your password to malicious sources. Red flag number one, look closely at the sending address. I never received an email from this address before, and it seems a bit strange that I wasn't notified ahead of time by my IT administrators. Since this email directly references my IT administrators, I should confirm with them first before clicking on any links in this email. Red flag number two, if you are familiar with the sender's address, take a close look at any misspellings of the domain or extra characters, such as support at protected.trusts.com instead of support at protectedtrusts.com. Red flag number three, attackers love using language that prompts users to take action right away. In this case, we see it used three times. Any email verbiage that creates a sense of urgency should be treated suspiciously. It is the attacker's intent that your initial panic will cause you to try to resolve the issue quickly and without thinking. Red flag number four, when I hover my mouse over the click here link, I see the actual URL has nothing to do with Office 365. Never click the link if you are unsure. You can always manually type in the URL you know to be true in your web browser instead of taking the click here shortcut. In this case, we would go to portal.office.com to check. Red flag number five, if you are a more technical user, checking the message headers of this email indicates that the IP address the message originated from is not one used by Office 365 or our company. If you do get fooled into clicking the link, there are still several red flags to look out for before giving out your login credentials. Red flag number six, the URL for this landing page has nothing to do with Office 365. Be careful though, in a real phishing attempt, the agent will use a URL that looks close to the real thing. Red flag number seven, this login page for Office 365 is out of date. As of 2018, the current login page looks like this. Similar to our tip on red flag number four, manually type in the URL you know to be true if you think the page is suspicious. Red flag number eight, your web browser is smart. Look for the secure label and lock icon by the URL. These will usually appear in green when the website is legitimate. Here is the fake website again. Notice there is no secure label and the lock icon has a red line through it. Also, when I go to enter in my login credentials, my browser gives me a final warning telling me the connection is not secure and there is a strong possibility my login information could be compromised. Finally, red flag number nine, let's say you fall for both the email and the landing page and you end up entering in your email address and password. Even though you already entered in your password, the page redirects to another sign in page. Sometimes the page will stay the same, but the URL has changed. With no indication of my password or username being incorrect, you should know by this point that something is fishy. If you get to this point, it is likely you have just given your login credentials to the phishing agent. It may not be too late though. If you notice this right away, you can still change your password before the phishing agent has a chance to log in with the credentials you just provided. It is still a good idea to contact your IT department to confirm that your account or your machine have not been compromised.