Okay. Our next talk is sneaking in network security. Our speaker Max is going to tell us how to scale up defense for computer networks and in particular how to integrate that in existing networks. Okay. Max is a pen tester, an ex pen tester and now a member of the blue team. Applause to the public. Thank you. Hello. My name is Max Burkhardt and I'm here to talk about introducing security in networks. Like me, with a small team, I managed to implement a model of segmentation of networks in a sensitive way. I'm a security engineer at Airbnb, so I have practical experience in that network. I think that the techniques that we're going to learn today can be applied to a lot of networks. So I'm going to talk a little bit about the technical theory and what happened when we implemented it.  So let's talk about network security. So let's talk about network security in 2018. Segmentation is still a very good idea because we know that everything, we know that commitments will happen on the networks whenever someone can forget and pass on a server. And security on the networks can prevent that vulnerability to the security areas higher. However, I think I've never been involved in network pentesting in the whole segment. We know why. We grow quickly. We know that when networks grow quickly, small teams, especially in a startup like Airbnb, have to prioritize their work where they have the most impact. And that's usually the perimeter. So when a network grows quickly, in the end, you have a network with a hard shell, with a hard exterior and a soft interior. So if the attacker finds a way to penetrate, it has relatively much freedom of moving inside the network. So we know that as network experts, we know that there is a problem. So to give you an idea of the scale that this project dealt with, last year we implemented this. The Airbnb network had more or less 2,300 services, more or less 20,000 security nodes from the network. And maybe an instance in EC2 or in a Kubernetes pod. And we did more than 1,100 installations per day. And we know that it's difficult to build, to modify this large architecture. And because of that architecture, it's difficult to work and find the areas where there are difficulties. Finally, it's a very important issue to talk about the productivity of the real estate development. If you are writing code every day, if you lose 5% or 10%, that's a very expensive thing. The question was, how do we make the center of the network have appropriate security? We can't start from scratch and stop all the development. We heard a lot, especially in the pen testing, often in the community, about how to do the same thing in defense of security. We can put in the defenses and have nobody know we were there. Theoretically, we have to stop thinking about security as if it were something that was around the development process. This was the way it started 30 years ago, so first you have to do your application, test it and then put security. But it doesn't work anymore. So what we are talking about is a new way to do things. The one that mixes security with development, like agile security, etc. This is not something that we invented, because a lot of people are working on it. But I think that most of the time people think like this, in terms of application, and it's time to put it together with the network security. I think the most important thing is to build a security solution that goes for web development, which is something that also serves for people to develop the waves, because it's something that can be easily scaled. It's not impossible to work so that the attackers do nothing, so we have to find a solution. And as we are managers of good projects, we are going to prepare all of this here. Everything we build can't be on the path of engineers. Maybe it can be something that they don't have, but they shouldn't think about it. They should implement security by default. It's something that we wanted to do for a long time, but in that case our goal is to make it difficult to make an insecure configuration of a network. And finally, we want to build something that is flexible, a flexible network to implement different protocols that we are going to be using. You don't know what we are going to be using within six months, everything we are working on. It might be a Linux, it might be another project, maybe Haskell and Azure, we don't know. I don't know what it will be in the future. So it should be agnostic of those decisions, the implementation. So this sheet is basically the solution in two orations. We are going to use the SMUTU in a system of services discovery for authentication and security, and with zero configuration, without configuration. We are going to dive into each of these parts, and I'll show you in different parts, and I'll show you how you can see everything to make an invisible security. So, to start off, I have sort of isolated three pillars of this. The first is TLS in the development of the service. TLS is one of the most important protocols in the security industry, and it gives us properties that we can use in all parts. So this is the first pillar. Prepare everything in a way that we can use TLS, and make sure that they work in all parts. The second pillar is to combine the identity, not with the identity. In the additional network segmentation, everyone addresses the IP address, but we want to talk with one of the different from our network, because we are using TLS identifiers. I'll talk about this later. Finally, we are going to generate an authorization map, determining automatically what services you have to talk with. We can try to update things automatically to make sure that the connections can't be lost. So this is a diagram, and we are going to see different parts. It's a very simple diagram of a network with three nodes, and they can use this authentication to know who they are, and they can use authorization logins that is sort of centralized map, and it shows what nodes the network is. It shows that it decides that it has to do with the others. Let's jump into the first pillar here, which is the implementation of TLS. So specifically here, we're looking at the... Before I start, though, it's important to jump to basic concepts here. We're using mutual TLS here, which is... You've certainly heard of traditional TLS, where you have a client that is verifying the identity of a server, and you get the cert to make sure that the... It matches the domain name, and so on. But TLS is also very wide, and it can also verify two senses. So you can have a client that also has a certificate so that the server can check who is using an equally strong certificate. This is pretty hard to deploy on the public web because it's not used, and it has to do it in your own network. This works really well. So this is really great because this means you can have a strong authentication and we know how to deal with these sort of systems. And so not only can we make sure that a client doesn't know that they're talking to the client, but the server is looking who's talking to them, and they know that the way it seems appropriate. This is a term that I hadn't heard about a long time ago. This is a term that I hadn't heard about a long time ago. This is a term that I haven't heard much about in companies before being in Airbnb, where we use a lot of cloud services, but basically the meaning is that you have a node on the network and you have to find other nodes on the network with which to communicate. And basically it's implemented with DNS, and for example you want to, for those of you who don't know, you want to do a Google search and you go to google.es and DNS is looking for a server that can provide you with Google. And as we know, a network has to be very flexible and things move a lot. So service discovery, the service discovery has to be very flexible. It can be problematic because it basically tries to be a network map, it tries to help and say, oh, look, I find the service here, I find the other service here. But it can also have an effect on security. Airbnb uses a framework that's called SmartSec, and that's what was there when we started this project. That's what we were using then, and that's what we mounted our architecture. What we're going to use is applied to what we did, but I'm sure you can also use it in other places. This is something that Airbnb created in open source a few years ago. Basically it uses ZooKeeper and HAProxy to make the services can communicate with each other. If you look at the example above me, you have service A, service B, and it's going to try to communicate with a ZooKeeper cluster. One wants to communicate with the service B, so it's going to look for the location of the service B through HAProxy. The service A, if you want to call the service B, sends a question to the local host, and HAProxy is going to find a node that can answer your question. The important thing is that this system is not designed for security. You just ask for a list of nodes and you get a list of nodes and you're going to try it. But I'm going to show you how to implement security in this system. So, before the security modifications we did, when service A wants to talk to service B, it sends a question to HAProxy and it's going to send it to another node and it's going to send the internet to service B. There's not much security here. What we added is a secure shim. So, another proxy, the reverse, which is in the node that receives the messages, it's in service B and we reconfigured it to communicate only with TLS Mutual. So, now all the packages through the internet are in a TLS tunnel. But the important thing is that service A and service B haven't been modified for anything. So, we modified the security model radically without touching anything from the engineer's code. And here's where we're talking about invisibility. There are several benefits. The way we have two services with proxies that are using TLS and there are things that can do authentication and verification through the tunnel. Security was able to build these controls and build these controllers at once and distribute them through the internet. The same proxies can work as well as languages or what protocols they're using. So, instead of using authentication, authorization code and having to verify the authorization of the code, we just did it once. The other thing is that having these proxies on both sides is actually really helpful for no reasons. So, for things like this, it's a very better thing. Better ability to load testing. You know, load testing. And that's what we got through the internet on the support of other infrastructure teams at the company. They don't have to try to do it on their own, but it helps. So, basically, they're doing the opposite of what the NSA wanted to do. Here's the presentation where they're showing what's in Google's cloud. So, there are a lot of things that need to be TLS. There's one important point about this particular approach that's kind of the basic way of doing it is the exclusivity of the proxies. So, we leave all the... So, this is very important that the only way to talk to a proxie is by going around and you don't have to use the proxie. So, you can evaluate the authentication. So, we have to make sure that this is going to be impossible. Now, we're going to talk about how to solve this problem, but we have to think about if you're trying to implement something like this. So, by implementing a new proxie into an existing service without changing the code of the services. The first point is what we want to do is a segmentation. We have to make sure that the only things that are allowed can be communicated. So, we have to build a sense of identity that allows us to do this verification. So, we're going to talk about how to do these certificates there and we're going to talk about and how we decide how we're going to function. So, segmentation. We're trying to make sure that we're able to make sure that a node can only be able to talk to the items that it can talk to. If a node needs to talk to a service, it's going to do that. So, maybe for the reasons of business, it needs to talk to it. But it needs to make sure that only the nodes that have to do it can do it. So, we want this to happen at a level that can talk to each other and then maybe they can get on a certain predefined channels. But in a micro-service network or a network that has a lot of dynamic communication, maybe we have to think about this more at a service level and not at a node level. For example, we say that we want the service of payment configuration to communicate with the back-end of the service. So, we can start to represent these decisions instead of this static node level. That is to say that we have a lot of services and each service that wants to communicate what allows to save locations. So, we have these proxies that understand TLS and TLS is great to understand identities. So, we can start to create this network so we can be in this state in which we only know certain identities and can only communicate with those specific identities. And this is something that can change a little depending on the network's topography. So, you have to find a concept identity that meets certain attributes. So, this identity that you decided to use has to be different for each case because you cannot distinguish between the services. It is an identity that the node cannot change for itself because the attacker can modify the identity of the node and move to other parts of the network in which it should be automatic so that there is no to configure it manually so that there is no need to be an Excel table and find a certificate for a specific node. And finally, we decided to use the TLS certificates and we also wanted something that could be introduced in the certificate so if you have a configuration system or a cloud permission system you always talk with a function that gives you the identification of the instances. And this worked really well because the different services can change and you have to manage the services yourself and represent the certificates like strings. So what we are going to do now is we need to give an identity and we need to give certificates that allow nodes to prove their identity in this TLS communication so we can then build a map of what identities can access what services. And we are going to distribute that map so we are going to say for the payment let's say that you can talk with these identities, but with other nodes. So only some nodes can access some things. So how do we do this map? This is the third pillar which is the final segment of this part. So we have to think what I can do and distribute it. The question is it's a matter of trust. How do you realize what you have to talk with? With the least amount of human action possible. So we wanted to lower the cost of human if you have to have people who spend the whole day making firewall configurations it's going to be very expensive and difficult to keep safe. And we wanted to be far from a configuration list where you have a lot of security engineers who think what to do with who. So we are going to go to the existing code. You can see how the network works and how the configurations are and how to use it to try how the communication works. This is getting to an interesting point because the decisions you make now depend on how you think about your organization. We decided that if you can use code and that you can make changes. This is something that may be based on your organization's set up. We are going to talk about that in a moment but for us we realized that we have a Chef repository that can distribute information to all of the nodes running in our network. And the solution is in a parsable way was saying what the very service work. And then there is the dependency of the services. So service one has the dependency in our monitoring and etc. And there is a repository that is difficult to control. You have to be an engineer that has peer review to be able to upload code here. We realized that service one is a part authorized for the production. To do that we built this service called Arachne, Arachne like the Greek goddess and Arachne So basically it's continuously pulling our Chef repository to find out what connections have been defined by people that can be trusted to build this reverse map that defines what services can communicate with what services. And that can be sent to the three reasons that we are going to talk about later. And this comes to the services of this kind of authentication. And the way you generate this map depends on how you think of internal dangers in the company and in our case we made the decision in pure conscience to trust our engineers but it depends on how you see this problem and understand a little bit of control. And this system is quite flexible and it can have something that already discovers almost everything it can and it can publish a new authorization map. So if you want more controls than this for example if there is something that you have to give a new connection and confirm it while still taking away a lot of that boilerplate work we can actually go further instead of just telling us discovery proxies to allow these identities and banning these others because we are just using this without additional we can trust in the support of these protocols the proxy reverse that we use has a functionality to inject information about the client in the Http streams so this applies almost all of our services use an Http so that already with almost everything we need whenever you enter a message with TLS you can read this header to discover information that makes trivial configure permission levels within the network this would have been something very complicated to implement before having this system because we would have to configure all kinds of passwords, codes and secrets and this makes us reduce all the cryptography complicated to the TLS protocol to be able to focus on other things so these are the three pillars of our solution we implement TLS for everything to have the security that we need then we give the identity to everything so they can communicate one with another and reinforce segmentation with lists of allowable connections and then we generate this map reading the chief configurations but I'm not here to sell this solution because I like it but there are disadvantages and I'll be honest before you consider implementing a solution like this these are the things that we think and we decide to accept first we will need synchronize this map constantly lists of permissions instead of having centralized instead of having centralized configuration of permissions like through a firewall or something like that you are distributing it through various nodes so you have a lot of communication through the network to synchronize this configuration you can use a little bit of caching to make things easier but still you can add attention to the configuration second if Telesa has a problem like for example Hartplit you have a lot more problems than what you are used to because you are trusting in the security in the center of your system but the reason for this is that it happens again if there is a security problem between Telesa security will be working many nights so if we are installing several systems to configure to repair this security problem even so we will repair the rest of the solutions adding more reverse proxies in the traffic is quite complicated introduced a lot of interesting behavior in the services and it is interesting to know that the addition of Telesa almost did not break but the additional communication in the network had surprising effects you have to be able to run software in all the places where they communicate because you need a place where you can download the permission lists normally with servers this is very easy but with services but with devices and OTs or services of other offers it is difficult to use this finally you have to have a way to deactivate certificates because if one of these services is attacked and compromised you have to be able to deactivate all the permissions it has that is a bit difficult there are ways to solve the problem but you have to consider it so install it and implement it I hope you have described it in a practical way this is not purely theoretical this is something we have implemented and I hope you can explain what I have learned during this process so to start with the technical details we build this mainly with open source and open source so for proxy we use Envoy it is an open project that is growing a lot in open source and with a good reason it is very good it is modern, it is fast it has extensive functionality with TLS and generally it helps us a lot but a problem we had with Envoy is that it is very specific with HTTP 1.1 and that leads to some other applications that did not have much care with the use of this protocol as I as I said before we gave each entity an identity because it was natural for us it showed the way we think about security and the permissions to control what services we have a Ruby script that works all the time is Acne the authorization maps are files that can be achieved in S3 where you take out the things it was about four minutes to web of services and the network of services meaning that it is about a four minute delay in between a change that is a service at least four minutes that you have to wait until the changes are solved and then you have to deploy such a change to production and then you have to install those changes where a new dependency gets added that that has to be done we have specific availability considerations of accessibility that are very specific we wanted to make sure to make sure that if Arachne falls and we can't generate those maps that the traffic could continue working we didn't want to stop all the traffic that was happening and if we decentralize all the authentication we want to be able to base it on the benefits of decentralization and then we have to make sure that if Arachne had a technical problem that the changes would stop being refreshed that means this still works even if it falls like last year things still work the nodes can't go down the topology but the cars still works this was a choice that we made early on when there are new interesting things that happen with Arachne and security can be realized before other people realize it and the plan was to activate these six points to do a map of authorization and verify it and make it work before we touch some services and then we verify and then we have to give a certificate of identification which is a very small change that can be applied easily to put a certificate in the nodes which is easy to verify that this works before starting the next point to check that it works and it's all good we install the blockchain proxy we install proxies in all parts and then we start checking how the traffic works the traffic still doesn't work because of the traffic the roads the paths and this helps us configure this step and we also configure and we try this step before continuing next we start creating the traffic and we configure the configuration so we can turn it on or turn it on depending on the service and then we have a part of the service that seemed representative of different types a great variety of things that seemed to us that they could make our system and we look if this worked and the next step was the radical step which was that we started we put everything to work in a moment and so it's the way that sometimes you want to do things but we chose for a good reason we have two people working on this program in this project and we have other thousands of engineers doing other services as quickly as possible so we wanted if we knew that if we went little by little we would never be taking the step or the others all at the same time and then we moved to the next point and the next was to put together all the localhosts so we could have security and this was the hardest from a security point of view because you have to wait until you are at point 6 to see the benefits but so we could take a step back if something didn't work we realized if a service did something that we didn't have to do, we took a step and we could fix it to visualize this we started with the nodes we built the authorization map we moved on to adding we put the certificates we installed the reverse processes with the logic of authorization we turned on the TLS for some things to be sure that it worked and then on the day of application we turned on TLS for everything else we did this in April of this year and there were several things that worked we went from 15% of internal TLS to 70% in just one night which was very good and it wouldn't have worked in any other way we made sure there were several benefits that had to do with security or not and this gave us more support from the organization for other changes and so these changes helped these changes to other engineers who were afraid of losing their time so we had to make sure that there were benefits for them and then we put a more easy configuration because that way we identified everything else and I didn't have to think about creating a connection with TLS and that brought benefits performance numbers are good I'm going to talk about it later and there were several metrics that showed that something worked and that improved the other thing that we did was making sure that we had the right configuration we did routine TLS in several services so we realized that a service had a problem we didn't have to roll the whole thing back in all parts but we could work only in a few services and as I'm here to tell you the truth there are several things that didn't work as I said before using proxy in everything it sounds good on paper but it has problems in practice in 20,000 to 25,000 services almost all work but some of them started to work some things change even small things like changing the case of headers it can give some weird comfort in some applications and it can also bring problems like web sockets and there were things that didn't work with that but then there was a quick part to show how the servers had to work but then it worked pretty well but we didn't realize that there was weird behavior in some services but these behaviors would have problems not because they had to do with security and our process of testing was good to realize what would happen if everything started to work with the TLS we tried that well what we tried was what happens if all the services that depend on your box start to want to use TLS and then we had some problems especially the Open Proxy had a previous version it couldn't work well with TLS so it would load the same certificates in all the connections which worked a little weird and that's something we could have tried better before and the last thing I wanted to mention is connecting the services with the localhost it was something that took more than we thought we had created templates that showed the services connected with the localhost but it took a couple of weeks more than we expected because it was more difficult than we expected I wish we could have allocated a little more time it's something that I would have liked to have planned more time for it I already talked about performance because someone always asks when you talk about a TLS and people ask why it's so slow luckily I can confirm that things even sometimes go faster things I didn't expect when they say it wouldn't work it would happen but it did a number of our services improved even 80% what happened is that we had a bunch of these services that had been implemented for example TLS services and we wanted them to be very secure but the TLS had been involved in the application but that takes a while when you have to restart it so it was useful to remove the TLS the handshake in all the connections when a box comes up with a system that connection can exist weeks or months so those cash are very hot in such a way that the caching is very close to 100% so it only pays the cost of the encryption that is in the hardware in the network it was a huge advantage it didn't slow down the TLS and to implement this in your own infrastructure I imagine some of you don't have the networks that are as segmented as you would like and this is a nice way to implement segmentation in a big and easy way and I have a few points that can help decide if it's a good idea for you to do this first, how can you distribute these proxies in your infrastructure we have an advantage that we have a management system that could install software that could configure it and we had software that could also be configured in the same way this was quite natural for us to have in mind next how can you assign identities to nodes this is important because identities are very specific and if you already have a specification system then it's quite easy to configure it to be certified otherwise it's much more work will you need to configure manually these access control lists or can you generate them automatically if you can generate them automatically that's when you're going to have these efficiency gains so if you have if you're in a situation then that's what you want to push or promote if you don't have it there are some solutions in the market that can handle it but Istio and Consul are two systems that are promoted as solutions for these types of problems and already implement this security system so to explain it this is not something that we implement Istio and Consul implement it for you in a way that you can easily package this is something they don't do it on the side of the configuration but they do it quite well so of course you can implement it with the security discovery system as we did if you don't use these systems so to summarize I'm here to tell you that you can change an authenticated network and the reason that is because you can make invisible changes and you can make the system fast for the system of authentication maps the engineers that are developing a microservice before the system implementation and after the system implementation basically does the same as before basically does their changes, tells who wants to communicate with the system with the other service but now if an attacker manages to attack one of those systems suddenly there is a network where before it could communicate with any service now it can't go through the system and this is something that I think is possible very good I think where before you tried to implement security now it's possible thank you very much for listening if you want to stay in touch ask me questions outside of the session questions and answers you can write me on twitter or email or if you just want to see something under rbnb.io thank you very much applause from the audience thank you max thank you max if you do have a question please line up on the microphones try to limit your question to a single sentence if you'd like to leave at this point please do that as quietly as possible signal angel your first question from the internet please hello why do you use opensl and not implementation so I guess I think I said this as an example any but do you use the stack that works best for you but switching to something like something like libresel is probably a good idea number two your question hi great talk what are you talking about what are you doing to mitigate the risk of ssrf in the host well that's something that I'm worried about as someone who works on the app in a company that only works with hp it's something very delicate we are seeing how that code is very careful to avoid any problems that come to the internet but my work is trying to make that better number one very interesting idea interesting idea basically it includes a vocation it's an intelligent idea but now we don't have the work together so there's no proxies that works with this but if it works well because if you work if you manage this work it's something that would work because you can't make it an identity at least we but if you have a network that has it, it could work did they audit the proxy code before placing it before putting it in front of all the services yes number two what are the cost implications for implementation what are the cost implications for your operations the costs are pretty low because the proxy reverse is very efficient we didn't have to do anything else just see the configuration it's pretty cheap the generation of the map is very cheap because it's only written by Ruby the most expensive is the transfer of the authorization I think it's something we can reduce seeing how often we see and if we don't make a lot of topology we can lower the frequency in which we exchange but in general the costs are pretty low in terms of certification are you limiting the certification life or what kind of control do you have there we want to get to a point where the certification is more quickly there are communities that are doing a very good job in terms of making it last a couple of weeks or a couple of days but we can still say our point of view is that we ask things like putting them on a list in which they are denied it's something that prevents things in about four minutes so we can use the active promises but we are improving our infrastructure so that we can use it more quickly thanks your question since you do all of this on a flat level 3 do you use payment information how does your authentication affect if these systems are connected to other systems on the network and not separated by firewalls and similar things our network is interesting the payments are separated and the rest of the network affects us that doesn't affect us but this is an effective way it's specific a web page so we don't have to do this specifically it's something that has been done favorably you can elaborate how how to react to the changes you made in your talk how thanks for doing this it's something that I like to talk about I think that the security is going to sell well your solutions when you're thinking of something like that it's crucial to make sure that there's something important for the security school and so a lot of those things for us are more on developer ease and productivity for example reducing the difficulty for them for example improving the performance as I talked about before these are things that other teams other teams like that they were open to our proposal and so it was a good plan to have a good plan to do the homework to do tests and think as in the structure more about security security is the last end but we have to make sure that we're burning our credibility in the rest of the organization in a way that I thought a lot about forgetting about the benefits of security and how I'm going to sell Thank you microphone one your question do all nodes Do all nodes and what technology do you have to use to render emfoy? Everything that's my website is jason almost which downside is the data form it puts the list of identities in the configuration of the on-boy, and this uses it as a configuration of its automatic life, and they go down in two seconds. Have you considered using PAPSAPUSH as just the relevant metadata of the clients to give them the information of the entire map of the network? Yes, you can easily segment what information you are providing. It's a matter of time development. But we have two other methods of discovery, but it would be much easier. In particular, if it's like any other IAM role, you can do IAM specific web data. So that wouldn't be very difficult to implement. Thank you for all the answers. The chat is over, applause for the audience.


You need trouble. Sorry. First, today I want to show you how to... First, I'm a blogger from Japan. I have been living in Taiwan for three years. First, half a year I've been in Taipei, and after then I moved to Thailand and I still live in Taiwan. And my job is to write blogger. And five years ago, I wanted to ask a question. Do you write in a blog using WordPress or Node? Do you want to do the monetization in your WordPress blog? No. I have never known the Taiwanese blogger how to do the monetization in Taiwan. Thank you. This is my information. I live in Taiwan. This is my background. First, I stay in Japan. And second, I moved to the Philippines to study English. After that, I do the Australian working for them. And then in 2015, I do the working for them in Taiwan and I still live in Taiwan. Many people think, why Japanese live in Taiwan to do writing blog? Before the back in 2015, five years ago, I was a study student. I was an English school student in Philippines to study English. And my life has changed because I met a beautiful Taiwanese girl. Yes, I fall in love with her. And as a Taiwanese friend said, if you have US$1,000, you can live in Taiwan. It's a great idea. I want to live in Taiwan. I decided. But important things, money is very important. That's why I decided. At that time, I had a blog and I decided to do the monetization for living in Taiwan. Yes, this is the start. After that, I studied how to do the monetization, the WordPress in Japan. Japan's blog. Today, I want to show you some of the global systems, some of the local Japanese companies provided advertisements. First, Google AdSense. Do you know Google AdSense? You know, yes. That's why, if you check my blog and click my Google AdSense, I can get one Taiwanese Zara. Yes. This system needs to have more pageview. Second, I deleted.  You know, Taiwanese know the Rakuten e-commerce. Like booking.com. I add advertisements on my own blog. Booking.com gives us a cashback. This is my... Maybe next month, I can get 2,200 euro. This is the system. Maybe Taiwanese or other people can get the same system. This is the ASP. It's called Japanese People for ASP, Affiliate Service Provider. This is a... For example, this is Japan's ASP site. This is one of the famous travel agency. They want to sell their travel package tour. Two, nine, three days to go to Taiwan. Include a ticket and include a hotel. But it's hard to connect directly. It's a travel agency and me. It's system is very complex. It's hard to check the analytics or check... It's hard to... I need to tell them the bank account or something. It's very complex. It's like an internet advertisement agency. Instead of them. I don't... This is... This system is a company and a blogger contracted to each other. Directly. I think this system is much more famous and popular in Taiwan. I also do this. I write a PR article for Taiwan local government. And Taiwan travel agency and Japan's travel agency. This one, the Japan's travel agency provides and we contracted. One month, two hundred, two thousand, twenty-five... Twenty-five thousand Japanese dollars. We have many way. And I search many this way for living in Taiwan. No one of the people read my blog. I cannot get money. That's why I have to close my blog. Today I want to introduce. Making this blog is the first need to the marketing very important. Second, making content. The final part is monetization. And also five years ago. Four years ago I stayed in Australia using working for the visa. And I wrote my blog. But few people read my blog. Maybe page view is around thirty-thousand page view. Thirty-thousand or... Thirty-thousand or... Fifty-thousand. I think it's small. I can get only maybe three hundred or four hundred US dollars. It's impossible to live in Taiwan. I think why my blog is huge. I think why many Japanese cannot read my blog. Couldn't... Why Japanese read my blog? After that I checked the Australian government's site. This is working for the people within Australia. 2015. I really surprised. Japan people twelve thousand people come to Australia to use working for the visa. It's really small. Let's not Taiwan. You can imagine. I was so surprised. The final I realized.  It's impossible to monetize. After that I changed to focus to Taiwan. Probably. I checked my Japan's government's site. How many people visiting? One. One hundred. I understand. Market is really important. It's one three page view. Recently twenty. I focused on travel. Why? Because spent. And it's really... One thing people don't need to... One thing people understand. People don't need to buy the hostels and airplane tickets many times. But people who want to travel. Need to buy the many things. Tickets, hostels. Or Japan company provides insurance. And credit card. One credit card is... Very... I think from this maybe five thousand... Maybe one thousand Taiwan dollar. One contract. Company provides us. If you make a context. What will you do? After you decide to travel? Taiwan? I think we will search many things. Hostels. Which travel... Which famous sightseeing spot. Or how we go to main station from the airport. We use Google. When I write the article. I focus on the key word. I will guest park recommend Taiwan exchange. Maybe Taiwan woman. Good choice. Good choice. This is in Chitawa. My blog is number one. We use the... We use this system too. The local... If we search the Taiwan exchange. We can get many key words. I see the... I need to write the Taiwan exchange ATM or... Exchange... T shop. We can exchange. Do the exchange. This is one of the idea when I write the article. This is my article tweets. This is... If I write the Taiwan... It's not good for the... I write many articles. When I state. One... One two... This is my article. When I state the type of poster. I took many pictures. I think the many articles. Many information. Also the... This one. Place the laundry. How much is it? Kitchen. The Japanese people doesn't know the... Other information. For the bus terminal. Or restaurant. This is not included. Booking.com. This information is not included. Booking.com or Agoda Expedia. That's why I need to... Add these information. Or exchange the... Place. And most important. How do we go to the poster? Which is... We are doing the main direction. This is also Japan's... Ocaro. And kids' search keyword system. We every day get the information. My keyword. Keywords. Sightseeing. Recommend. It's a role. Ranking is not good. We need to change the article. This is very important information I cannot show you. This is very important. Many Japanese people who are like this do this. Check the keyword and writing the article. Many times. And get the final part. Monetization. Which part is... This part is like this. That's how to say. I stayed at many bakpaka. One, two, three, four. And the total. Taipei recommended guest house. A bakpaka, 2018. Which part is good? Area is good in Taipei. This is near to Japan. Sightseeing, sports. This is... Much more local. This is a very useful. Introduce to the bakpaka when I stay. And I stay. I add the link. Link. Click to my blog. One, two, three, four, five, six. Six. Seven. Last part. I recommend which part is best. This part is Taipei bakpaka store. Currently my blog, Taipei bakpaka store is number one. Total, total, total. Robots working to help out travel. Traveling to travel helps to do many things. Good things. And my presentation is finished. Right? Yes. Let's see. That's the DRC. Can we use it? Yes. Yes. What about today? DRC. DRC. DRC. No, we need to pay them. 20,000 Japanese. 300 US dollars. Almost. Some money. 300 US dollars. They sell them. Those are my moments. Because sometimes in the... Stan and... Please introduce to the beautiful Taiwanese person. That's why I crossed my phone. I opened an email about you. You were writing about travel. I was really writing about travel. How fast that is? Fasten it. Fasten it. Fasten it. Fasten it. It's about... Maybe... It's how to explain. Fasten it. Because I didn't know the... First time I... First time I stayed in Japan. I didn't know the Australian and Taiwan. After that... After half a year... Half a year I moved to Australia. I started writing about Australia. Efficient rate income. Maybe... British card is better. 3-1,000 Taiwan dollars. Or if we negotiate... Company give a much more higher... Commission. Around 2,000. Many Japanese people want to do... Sell the credit card.


The COVID-19 vaccine and flu vaccine are different, and it's safe to get both vaccines at the same time. So don't hesitate. Vaccinate. The Pike County Health Department reminds you that the strongest defense is vaccination against flu and COVID. The Central Appalachia Climber Coalition will be hosting their annual Spring Breaks at Breaks Interstate Park, April 8th through 10th. The Coalition is working alongside the Access Fund to fix infrastructure and clean the park. We are going to try to work with the Access Fund trail crew a couple different times to bring them sort of extra hands and extra volunteers. And we have a campground reserved at the park and we're trying to bring in all the climbers we can and or you don't have to be a climber, but anybody who's interested in helping to build out this infrastructure and trails and maybe learn how to climb. The event will begin Friday afternoon with climbing and break into groups Saturday and Sunday morning to target specific areas that need maintenance. So within four years we went from about 30 routes to 350 routes and so the amount of climbing spread out throughout the park in a pretty diverse way and in order to access all of that you need trails that are sustainable and so now that there's a guidebook there's quite a few more people coming out and as of now there are certain trails to some of the areas that were only developed for a small number of climbers or a light use, light traffic on the trails. As the trails experience heavier traffic many wash out and leave climbers to create their own trails damaging the environment. Hopefully we'll do you know one big trail weekend and the trails we build will last 10, 12 years and be low maintenance trails from then on. So it's ultimately important for safety, sustainability and environmental conservation because it keeps people on the right trails. For more information on the event visit Central Appalachia Climber Coalition or the Breaks Interstate Park on Facebook. For Mountain Top News, I'm Brianna Robinson.


In this presentation, we will calculate the allowance for doubtful accounts and the bad debt expense using the percentage of revenue method. So first let's consider what we're doing here, why we're doing it, and the two methods that we can use to do so. We're looking at the accounts receivable account and the revenue account, and we can consider the problem with accounts receivable or sales on account, sales on credit in two different ways. We can think of it in terms of the balance sheet problem where we focus in on the accounts receivable or we can focus in on the income statement problem where we focus in on revenue. Now as we focus in on either side, we're going to fix the other side to some degree because when we make a journal entry, it's going to be the same journal entry, meaning or the same accounts, although the dollar amount may differ between the two methods and the estimates used, the two accounts will be a debit to bad debt expense and a credit to the allowance for doubtful accounts. It's just the method we're going to use that will make the difference here. So are we going to focus more on the problem on the income statement or the problem on the balance sheet? What are these two problems? Well, if we look at the balance sheet, then we could say, well, this accounts receivable account showing $1,146,3 is necessary for us to have on the books when we give this information to creditors because they want to know that number. However, it's going to be overstated to the degree that there are some accounts we're not going to get paid with. So we need to figure out how much we're not going to get paid for and make some type of estimate for that. Now to make the estimate, we can't just reduce this accounts receivable account because we don't know who's going to pay us. It's just an estimate. So we know that based on past history, some people aren't going to pay us, but we don't know who. Therefore, we can't go to the subsidiary ledger over here and choose which of these individual, that's down here, which of these individual customers will not pay us. And so that means we can't really reduce the receivable itself. And we wouldn't really want to either because we want to give our reader more information than that. We want to say, hey, this is how much is owed to us. And this is just an estimate. And the difference between these two then is the net receivable we believe we're going to get paid. That's going to be the balance sheet side that we need to do something about that we need to solve for. The income statement side has a problem as well, however. And that's the fact that this revenue account, any revenue account that we made sales on account for credit going through accounts receivable, then our revenue accounts that again, we might not get collection on, meaning we made the sale here on account. If we never get cash, then it's kind of like that sale never happens, not a real sale if we're never going to get paid on the sale. So we should reduce the sales in a perfect world by the amount we're not going to get. We never reduce revenue typically. So we're going to make an expense called bad debt expense. And rather than us waiting to determine that something is uncollectible on the receivable side and then recording the bad debt expense on the income statement at the point in time, it is uncollectible. The direct write-off method, non-journal accepted accounting method typically. We want to estimate, because that wouldn't be good matching, that would be writing off bad debt for sales that happened prior to this. It wouldn't be matching up these sales this month, this year with the bad debt expense. So what we're trying to do here is figure out how much of these sales are going to be uncollectible. If we use the method before we talked about figuring out the allowance for doubtful account, then this side will kind of fall out and it'll be okay, but it's not really focusing on this account. If we focus on this side then, rather than using the accounts receivable focusing on the balance sheet to make the adjustment, we will focus here on revenue. And we'll say, okay, how much of that revenue that we made on account will be uncollectible based on past experience or industry standards. And by focusing on revenue here, we'll still make the same journal entry and do something to the allowance account, but our main focus will be on revenue and it should be, you would think, more accurate than on the revenue side. We should be getting this revenue side more accurate. The two methods in a perfect world would come up to the same number, but they pretty much never will on the two, as they're both going to be estimates focusing on the different side of this journal entry. So under this method, we're focusing more on the revenue side. And what we're going to do is we're just going to say that 3% of the revenue is uncollectible. Now, we could have much more complex methods than that. We could try to determine how much of the receivables were on account clearly. We don't really want to count cash sales and maybe even how much is still out there. But for most book problems in this, from a pretty simplified method and typically the method being more simplified in any case than the receivable method where we typically have an aging process, we're just going to take the percentage of sales. For that reason, for one, the reason that I think most people typically focus on the balance sheet and let the income statement kind of be fixed by the fixing of the balance sheet. And two, because it's a bit more complicated for book problems and therefore they concentrate it on more, you're probably going to see that the accounts receivable method, percentage of receivable method used more often to calculate allowance and that debt. But note that the sales method is usable and it's there. And it's good to know because it emphasizes this other factor, the fact that we have this other matching problem on the income statement. It's not just the balance sheet problem we have. Okay, so if we do this, we're going to take that 378 times 3%. So we'll do that with our formula right here. I'm going to be in D11, D21. And just say this equals 378,000 times 3%, 0.03. And that's it. So I'm just going to take, or if we did that, of course, in the calculator. It's just the 378, that times 3% or 0.03, given us that 11,340. That's going to be the debit to bad debt expense. So I'm going to copy bad debt expense. We're going to put that in C21, right click and paste, 123. We're going to credit something for that same amount. I'm going to do that with our credit plug formula, negative of that number. So I'm just going to put the brackets around it. And that will be going to allowance for doubtful accounts. So we'll copy the allowance for doubtful accounts, right click and copy. We're going to put that here in C22, right click and paste 123. There's our journal entry. Note how much simpler it is here because what we're not doing as we do in the allowance method is concerning ourself with what's already in the allowance account. It doesn't matter because we're focusing on getting this side right, and this side doesn't have what's in the allowance account already in there. Note that the allowance account, what's already in there, represents an error in some ways from prior estimates. So what we're not doing is letting the prior estimates mess up our current estimate for this time period. We're making our current estimate for the matching principle based on just the revenue number, not based on trying to kind of fix the past error from this receivable or allowance, which wasn't exactly right. And it's never going to be exactly right because it's just an estimate. So we don't have to do any kind of subtraction. It is what it is. We'll just base it on revenue. And then whatever happens to the allowance account happens. So we're going to record that. So here's the bad debt expense. It's going to be the second to last account on the trial balance. And therefore, the second to last account on the general ledger. So let's find it. We got the assets, the liabilities, which we have in the equity and the revenue. Here's the bad debt expense. So we're in AA9, AA9, we're going to say equals. We will scroll back over. And we'll scroll back down. And obviously, you can use the bars here, any other method to roll back over. But we want to pick up D21 and enter. So there we have it increasing that to $11,340. That $11,340 then appearing on the trial balance. We're out of balance by the $11,340 until we record the allowance for doubtful accounts, which is what, the third account on the trial balance. And therefore, third account on the general ledger. Here it is, the allowance for doubtful accounts. We want to be on the credit side. I'm in cell T13, T13. This equals, we're going to scroll back over, scroll back down, and pick up that $11,340 and enter. So it's going to go up from that $15,003 by the $11,340. Remember, it's a contra asset account going up in the credit direction, a little bit unusual for an asset account. And that's the $26,640, which we also see on the trial balance. Therefore, the difference between the $1,146,3 and the $26,640 is $1,19,660. We are decreasing, note, the amount of the net receivable here on the balance sheet side, although the focus is down here on the income statement side, where we decreased net income. We had revenue here. We're subtracting out that revenue, matching this actual bad debt to that revenue, even though we don't know who's not going to pay us. We're using an estimate to try to match that up to the same time period in accordance with the accrual matching principle to bring that income down. This is still income revenue, which is credited over the expense of $366,660.


Okay, recording is happening great. Okay, well, let's begin then arena That's okay, we have 30 minutes for both of you and we're not quite there Can you see the screen? Yeah, okay, good. So this presentation as I said already is about location integration project or location index and the number of government organizations like ABS, Department of Environment and Energy, Agriculture, Science Australia and CSIRO. This project is also part of a big deeper project which that integration partnership for Australia. So it's quite a big project. It's two years in duration and we are now half way through the second. Yeah. So to start with, it's just Oops, can we get to the video? Can we get the sound? Arena, we're not actually here in the audio so it's not We will? Can we? Okay, calm down. I'll try to pause it. So let's try now and let me know if you can hear it because for me it's We're not really getting the audio coming through now. Okay, no, okay. So we skip then the video itself. That's okay. And it will be included into the presentations or the links so people can look at it later. Okay, thank you. Yeah, no, that's okay. Yeah, so basically the purpose of location index is to integrate different types of geography and try to bring together spatial and non-spatial data and connect data on society, economy and environmental layers. And what we're trying to do is to create a system which will support decision based on fit for purpose data with non-operative source and using best technology and available on demand from the device of choice because the whole infrastructure is available on the web. So our challenge is how to join multiple geographies and observations together. They are not structured in the same way and we're probably all familiar with those so we have our raster data, we have our vector data and these are just examples of different data types and we have a lot of different tabular data as well and sometimes it has no coordinates itself so geography is represented by description, Tambora, New South Wales, it could be area, it could be represented in latitude-longitude or it could be collected and integrated this way. So the question is how to bring them together and that's what we are trying to do. So we have a number of challenges. So challenge number one is data integration and what we want to do is to have the data to be accessible and also fair principles not just delivered and downloaded so people can access it in SUTI and integrate with their own data set on the web. So we want it to be findable so it needs to be registered or indexed in a searchable source and each of the data objects needs to be uniquely identified and assigned with business identifiers. This also needs to be self-describable from metadata. It needs to be accessible so it needs to follow standardized protocols which are all both free and universally used. We also need to be aware of authentication and authorization procedures. The data needs to be interoperable so it needs to follow some agreed format open preferably and use the same language and agreed set of vocabularies and also reusable. So it needs to be machine-readable and also with no license security constraints and provenance and follow agreed community standards and this is the link to the fair principles for people who want to learn more. So what are we trying to do? We are trying to achieve with our goal semantic integration or clean data, data available on semantic web. So what is the power of the link data? So we can discover it through the web. It's enabled machine-to-machine communications so any data integration or searchability can be achieved quite quickly and at quite large scale. It's also extendable system by the default using semantic web capabilities and because of that we can extend usage of this data beyond our traditional client base and use cases. And also it enables the consistent data mining of multiple spatial and non-spatial data through GIS, without GIS software for opening the data. The other challenge for us is innovative technologies and the technologies we selected to use as link data and also discrete global grid system technologies. So because it's actually unique to globally unique project, no one tried to integrate data at that scale between multiple agencies. So there were a lot of testing of the capabilities themselves. We need to build those capabilities based of our testing, implement new tools for semantic integration of data. We also try to reuse our existing tools and infrastructures where possible. For example, Research Vocabulary Australia was selected as a central place where we can all share our vocabularies. The system is implemented in the cloud and also private repositories. So how to communicate between those is a big question. And CPU access and integration is a huge requirement, particularly from ABS and information about personal circumstances. So we really need to be careful. So what we're trying to do, we're trying to build that extendable system, which is ready for reuse by other people. So the system which is highly scalable, it is secure, and we use cloud tools available to us. The system is flexible. So it can be deployed by different users and custodians in the same repeatable code. We use GitHub code management system and using infrastructure as a code approach for this. And also easy to administer system. So the code deployed as a workflow through the Bitbucket pipelines. Basically the whole system can be picked up and deployed by our users. So I just wanted to say a couple of thoughts about the digest technology because it's not necessarily well known to people. So this technology allows us to integrate data and in spite of its projection and data formats. And the technology is math based rather than GIS based. So what it does, it creates an indexing system of equal area translations around the globe. And therefore every set of larger scale can be divided multiple times. So it's quite easy to apply mathematical algorithms and statistical algorithms rather than our traditional GIS queries. And I'll talk about it a bit later in an example. So our challenge number three is social architecture. So what are we trying to do? We're trying to improve user experience and efficiency for human related processes and also institutional culture. Social architecture is quite a big issue because every organization is doing things in a different way. There is no centralized methods for coordinating activities between multiple parties. So what we're trying to achieve is to build a system which is user centric and also to improve overall governance for data. So we need to be aware of security privacy and understand the ethics and our constraint, potentially constraint factors. We would like to improve data integration workflows between our partner organizations. We would like to build a system which help us to ensure that the currency rather than downloads and then we don't know whether it's new data or not. We would like to enable multiple and quite complex user requirements and use cases. And yes, as I said, a support user centric approach. And basically what we're trying to build here, going through this spaghetti way of managing data when everyone is downloaded, everyone's data and we don't know how it's used, to a more streamlined approach where you basically bring data to location index and index it and capture relationships. And then multiple analysts can access the same index and then apply it to different methods of usage. So how we bring it all together? So at the moment we're building a set of ontologists. They're one centralized ontology for the location index itself and individual ontologists for each of the data sets. We're also building individual registers and planning pages so people can look at how their particular objects look like and see minimum metadata about it. But it's also the system which allows multiple alternative use which is suitable for machine readability of the data. We are pre-calculating indexes of linked datasets. So we know what object is connected to the other object and in what way. And then that allows us to query because multiple datasets. And this example allows us to bring together information for place names, from digital elevation model, and from the GIS index as well. So this is an example of how we plot for digital earth Australia. It's a quite large compilation of satellite imagery and also some pre-built products. However the satellite imagery just give you a range of values and it needs to be calibrated and assigned with different attributes which are suitable for machine or human understanding and further mining and analysis. And it was previously very difficult for them to bring together attribution like in this example's service water attribution and information from the satellite imagery. It would take months and months and was impossible in some cases for the national scale. So we were able to bring together the observations of or measurements from the surface water dataset together with DEA and the two days not months. It's literally took a couple of days to bring it together. It also allows us to integrate raster and vector data and we didn't need to create complex schemas and download them into the GIS was done very quickly. But because it's a repeatable process, it allows us consistent to bring consistent answers for a range of questions. It's repeatable and it allows us very easily to connect big data with little data. And in this particular case it's been done through a common DGIS index. These two columns here. Okay so basically what we did we we assigned DGIS attributes to satellite imagery cells and also to objects from the surface water and were able to connect them together. This is another example where we use the same methodology. So it's matching again digital with Australia satellite data and land parcel. So in this case we are connecting DEA and cadastral information and the question was which land parcel are in which irrigated area. So it was again quite quick exercise for us. So now DEA teams are quite interested in continuing this collaboration and that's the moment we are calculating the whole Australia sort of integration of this data. These examples were done just preliminary just to test the capability itself. So as I said location index is a two-year project. So the first year it was mostly about learning capabilities and technologies. So we created and tested new infrastructure. We created link data index and built capability for both link data and DGIS implemented a number of APIs. And this year we are trying to progress operational synchronization for link data infrastructures which is quite challenging. So we already released the governance framework and the social architecture documents. We are continue we continue developing APIs and our tools at the moment and building a demonstrator at the moment. We are also developing user guides, spatial analysis of data using both semantic web and DGIS capability. So it's going to be available shortly. And we are extending link data index and DGIS to R. So the initial set of data which we were testing included statistical boundaries, GNF or addressing dataset. We also looked at the place names and geofabric but we're extending and being on testing our surface water data for that purpose. And so far it's willing to be quite successful. So what are the benefits? So we are unlocking data potential. So we're enabling machine to machine data integration, analysis and mining. And we're also removing needs for cross agency data transfer. At the moment a lot of time is taken by this. So it's huge improvement in efficiency and also getting more current information to consumers. We also accelerated innovation. So all the developed protocols tools, APIs, etc. they will be available not just to the partners but to all interested parties and their data assets will be available through Internet of Things. So people who we don't know of may basically access our data very easily through the endpoints and services. So we're trying to bring data to seamless data integration across multiple datasets and systems without opening them across. And also maximize collaboration. So one of the big achievements from last year was and all partners indicated this was collaboration. So improving relationship because multiple sectors understanding each other, understanding each other capabilities, building new common use cases. And governance and workflows, common workflows and governance are quite important aspects of this as well. So that is the first presentation. Any questions so far or we'll move to Zavalan? I've got a quick question, I mean, or if we want to use this system, is there any training approach? Not yet. But it's on the red map? Probably we'll be met financially. Because for the moment we're still trying to develop new tools in the procedures, guidelines, etc. So guidelines will be shown as the list. So that would be used as a part of training, but we would like to test those on our part mobilizations first. So any other questions from anyone? Just jump in here. Saru is doing some of the development work on the data aspects. If there's any interest in previewing some of those functionality and providing feedback we'd be interested in engaging anyone who would like to do that. Thanks. Thanks, Jonathan. And is there anybody else internationally who's doing anything similar? No. No, no. That's fantastic. It's such a real fear. Sorry now. Yes. Hi, it's Robin Tottenham from the Department of Agriculture. I mean, I just wanted to ask if you can elaborate a little bit more on there was a point there where you said that there wasn't a need cross-agency data transfer. So I was just wondering how does that actually work? Okay. So what you do is you build this common index which allows you to record relationship between data in one agency and data in a different agency. And through APIs and data services, only this subset of data is getting connected and re-jumped. So the data is open at the agency in the best instance? Yes. So there's a number of prerequisites for the data. So each object from the dataset needs to be assigned with unique identifier. The dataset needs to be open and to be available on the web. So it could be some authentication and authorization processes supplied as well. So it depends on the data and the system. And then basically this index is used as sort of orchestration mechanism for bringing data together. Okay. Thanks, Irina. I also just had another quick question. Do you think Loki will actually change the way we collect information in the long term? So part of this is about the ability to integrate different data types. And I'm just wondering, is this an infrastructure to support a whole different way that we collect different types of information? Or do you think this will actually change the way we collect information? I think it changed the way we use information. That's for sure. It's also how we manage information. Probably not necessarily the collection side of it. So for collection probably my second presentation would be more suitable. But definitely how we use it. Make it more fair. But I think it will actually change some of that collection because you won't have to be as constrained from the start of going, we must collect this data in these units. You actually might collect it one area and you'll be able to transfer it across and so we get to watch this space. Thank you. We can ask Jonathan, do you want to add anything to this? No, I think it was a good overview of Loki's project. We're starting to push some products out in the next few months. So I expect that more will be available for people to hear and interact with in the near term. Yes, so the Department of Agriculture is involved with Location Index and we're working with them. And Jonathan's group in particular on the particular use case. Hi, it's Kiran here. You mentioned that one of the key challenges there was social architecture. So you just elaborate a little bit more on that. Okay, so the social architecture and as I said, it's a number of areas we're trying to look at. And one of particular, well, I would say several focuses, but this central governance is a big question, discussion question for us. So how we can govern this data considering it's a common architecture and there are many partners and many parts coming from different organizations. We need to ensure that all these connection parts are working together. So we have common understanding how we update data, how we bring data together, how it's getting access, etc. So then multiple questions for the governance group and it needs to be a little between multiple partners. So at the moment we basically have a big gap in this space. So this discussion is just starting. So we need to probably talk to multiple partners starting from Australian National Data Commissioner and with between all the partners, but basically it's a bit of a question mark at the moment. The other bits and pieces of social architecture. So when we had the review of the project, most partners said that location index helped them to improve quality of their data because there are certain requirements for data connection, how we present data on the web, the quality of the data was assessed and improved. So it's bringing two changes in the organizational culture itself about how they think about data, how they manage the data itself. Yeah, so those things. And I think something that will be part of that conversation is when data is aggregated, how do you then cite the derived product? It's multiple questions and we're very touched on this, but everyone is aware that it's extremely important factor, equal to data itself and technologies. Thanks. The second one. Presentation number two. So at the moment I am the chair of NSNIC or ICSM metadata group. So metadata itself has multiple challenges. So what we face at the moment is a change in technology. And we all know about cloud computing and hybrid clouds. We know that there are certain requirements for machine availability of the data through advances of things like machine learning and artificial intelligence. There are different expectations from people. We actually in just as Australia is introduction from questions from people, individual questions, they want to find useful for them information online very quickly without calling or connecting someone and make decision about whether they want or not to use this information. The standards themselves, this environment of standards is very complex. So we have ISO, we have OGC, we have WPC, we have community based standards. So to understand their connections and the standards themselves requires a lot of skills. And we don't really have a lot of people who are skilled in this area and sometimes resources are not available in organizations to actually maintain those skills. And we also have our common things like budget time and rules. And in many cases metadata can help with resolving some of those. So what is the metadata for organization, business and the users? So what we want to see is content reached family data. And then it can be used as a promotion and communication tool within organizations, but also as risk mitigation and resource management. So help to promote your organization because users can easily discover the outputs. It can improve efficiency. So as I said, it could be a metadata supporting self-serve service. So they will understand what they're dealing with and make their own choice about it without taking resources from the organization itself. It's reducing cost because you can find information and then we just need to use and to use and share. It's improving machine to machine discoverability and integration. And it's also minimizing the business risk and liability. When you have information about things like legal or security constraints and lineage, you're basically protecting yourself declaring what people can or cannot do with the information upfront. And it's reducing cost for improved resource management overall. So what is the metadata working group and who we are? So the Enzliko was sorry, the Enzliko endorsed establishment of this group and the ICSM is actually established in November 2017. The first meeting was held in June 2018. So we basically went again a bit into progressing. And the idea was that we will coordinate implementation of global metadata standards across Australia and New Zealand. So at the moment, it consists of government agencies, federal and jurisdictional levels, research and academia organizations. They have initial number of organizations involved for 15, now it's going to be 37. And at the moment we have about 100 people on the mailing list. We also run the technical metadata working group, which is subcommittee of the metadata working group, and currently we have four night meetings. And it's quite enthusiastic and persistent group of people progressing a lot of different outcomes. So it was established as a forum for communication and engagement with special communities and interest groups. And we have Australian representatives at ISO, OGC and W3C as members, which help us to integrate our development with those books or get feedback from them. We advise on best practices for metadata and associated tools. And develop and publish metadata best practices relevant for tabularies, crosswalks, communications materials, et cetera. So this is a website where you can access information about the metadata working group. It also has information related to previous meetings and presentations which were done during this meetings, but also the outputs of the group and the documents. So you can contact me if you would like to join the group. And I just put several examples from our projects. So we developed a roadmap which helps us to align our activities with overall decisions from the working group. We are developing crosswalks between different organizational catalogs and different metadata standards. So at the moment we have about five organizations crosswalked between their catalog entries and these organizations using ISO 105-1. We also have mappings to RFCS, which is ARDC standard, and also to DCAT and CCAM. And that's basically the example of what we're trying to do. We also developed the best practices user guide. So at the last meeting which we held in at the end of October, we endorsed the user guide. So it's going to be available on the website shortly. And at the moment we are working on a number of our user guides investigating requirements for things like metadata for imagery and metadata for digital data preservation. But the current focus is metadata for services, how to describe services, what are the important elements. Vacabularies. What we're trying to do is also to publish vacabularies and we using Research Vacabulary Australia for that purpose. And then those vacabularies are available in multiple formats from XML to RDF. So they can be used by multiple use cases and mechanisms. But also the usefulness of those vacabularies, we're always looking for some vacabularies. How to classify these like roads for example, or how to classify the water streams. So these will give people at least centralized access to those vacabularies and they're open for usage. It could help with collaboration in terms of bringing maybe common vocabulary system and yeah, maybe form basis for some private vocabulary system. And also provide advice on metadata for different types of compliance. For example, digital continuity 2020 or GDA 2020 as well. So we're trying to explain to people what elements of metadata should be used to be compliant with those regulations. Irina. Yes. Oh sorry, just wondering how much left in the presentation. That's it. That's it. That's the last slide. So it's very time. So everyone be in touch with Irina and then we can distribute questions and ask some answers along the way. So we'll roll over to looking at the time. Melanie while we're getting the presentation up and running, we might actually differ item number four. Next time we'll take it offline. Just so they run over time. This will be a little bit shorter. So we've called it Elvis has left the building because it's actually went to the cloud. And we're here today, rather than being a GA because our whole infrastructure has gone down. So that's a good good example of why we don't build things in house anymore. We actually go to the cloud. So probably three, three and a half years ago, we used to have a system, the elevation data called native portal. It was terrible. He'd had buttons that never actually did anything. It was written on a server, Microsoft server. And every time Microsoft updated it would cost us $15,000 to get someone to change the code. So just before Christmas three and a bit years ago, we said, it finally fell over. And we said, no, we're not fixing it. So Shane and Crossman and myself were in a meeting. We just, we're not going to do that. We're going to reinvent the wheel and see if we can do this better. So we actually had to set, how do we want to do that better? One, we actually wanted it to work, which at the time was actually quite critical because we had something that didn't work. It had to be technology agnostic. So we didn't want to be stuck like in a Microsoft server anymore. We wanted to actually be out. So we went to the cloud. The cloud for us is that, yes, it works in AWS, but if tomorrow AWS put up their costs, we could pick it up and we could move it to Azure or any other cloud provider. We didn't want to be tied into an infrastructure or a software solution to a problem. We had, it was big data. So we're talking terabytes of data. Had to be fast and had to deliver it really quick. And I had to do it over the web. I had two staff at that point in time just handling queries and putting stuff on a hard drive. We couldn't do that anymore. And it would have been really nice if it stopped the complaints that we were getting, because we're getting a lot. So that was one of our main focuses. And it had to ship and click. We didn't want to do what we'd currently done, which was give someone a terabytes worth of data if they only wanted two gigs worth of actual data from that data set. And probably the biggest change that we did is we actually had to make it simple for the user. My experience of working in government is we love making things simple for ourselves. So we have to do less work. But we tried to not do that, because about how do we actually get data to the user may mean more work for us, but we actually want to focus on that. Had to cost less. We had to keep a linkage to our users. Because in the past, we'd actually made things sissy buy and available, but if you can't tell who's using it, it's hard to validate why you're actually doing it. And the last one was we gave ourselves a month and a half to do it with Christmas in the middle. So we built this infrastructure, we're trying to be quick. We really wanted to just go against a long business model. There's a shop, there's a warehouse, there's a factory, and you deliver it. Don't really care about the shop that much. A lot of people say I'm on another portal. If they're worrying about a portal, that's the wrong thing to be worried about. So my analogy is that you can buy your tin tams from Coles. You can buy them for Woolies.  Not really. You care which warehouse and which factory they came out of. So that was sort of our goal is that if we have an area where we can keep the data such as the warehouse, it doesn't matter how many portals access it, because everyone's accessing the right data. So we used that. We used the factory which is FME to actually clip the data and send it to the warehouse and deliver it to people. So we cut things down from about three days at its quickest to now you're looking at probably two to three minutes to get the same amount of data that you want. So currently two and a half, three years later, we're sitting at nearly 7,000 orders a month, but I haven't changed these sats. We've got over 40 terabytes of data sitting there, oh 40 terabytes delivered each month. We've got 60 plus million dollars worth of data sitting on a server somewhere in AWS and it doesn't cost us a lot. It costs us about $70,000 a year for storage and delivery. Before, we actually had to pay $200,000 a year basically for the disk that was actually running it before. So it's going to take a long time until we actually get to the cost that was costing us mail system. It didn't work. I've got a lot of discrete users because we actually deliver everything through an email, but also now represented with probably got 70 terabytes worth of data sitting in one location. So how should we use that? What should we do? And that's the question we're starting to use. But also we thought we knew who our users were, but we don't actually, when we've actually looked into it. So this is more getting into the users of Elvis. I will be doing a demo quickly of how to use it first. So we've actually surveyed them about a year and a bit ago. Who's using it? So I've got a lot of stats, but I've only got two in this presentation. So people are using it weekly and monthly, significantly. So it's part of how people work now. But this is probably the biggest change is we identified where those orders were coming from. And our biggest user engineering. And that's significant because an engineer wants the data to make a design or decision on, but they want the data that they made that day. So they want to download it. They don't want the service because it doesn't actually allow them to go to court and argue that this is the data they made the decision on. So we actually haven't had a great deal of people saying, oh, it would be great if we had a service of the elevation data because that's not serving the need that they want. And then we've actually worked this into the order process where you actually put what industry do you think you come from. So this is last month's. You can see engineers again. The fourth one, which is construction, is something that a year and a half ago, we hardly had any, but now it's starting to actually take off in that construction. So we're getting some business analysts analytics about this and how useful it is. So that's really quick because I wanted to quickly. So this is the data we've got. It doesn't look like a lot, but there is data covering the whole of the country. New South Wales has been very specific about covering and making available all of this. So it's quite significant. Victoria, not so much, but hopefully that's changing. Western Australia still runs in a model of charging for data. So they haven't got a lot of data on there, but we're starting to build that pressure and that change of what it can mean of making data available is much more beneficial for your jurisdiction or your state to do that. So I'll quickly just give you an idea. So this is going off, checking what data is available for that area that I just selected, try and zoom in. And I purposely chose the border. So we've got some New South Wales planning and industry data. So this is actually top-over symmetry. So if I scroll over it, you can see where that coverage of that data is. New South Wales spatial services. I've got one meter and two meter products. You can see all the tiny little, they do it in two kilometer square grids, point clouds, Geoscience Australia data. I must have missed the border. So it basically goes and it finds this. So all the data that is in the system that is available and gives you the option of how you can actually access it. So if I choose one, so it's quick. I'm actually interested in that one. I want to download it. Put your email in. You tell it you're not a robot because we're the only site that actually has been hit with an attack just by someone actually reporting repeat tiny little orders. The good thing is it didn't actually break it. It just slowed it down. So that's it. Anyway, we'll do that. Put your email in and it'll send you an email to download it off from Amazon. Thanks so much, Ben. So if anyone has any questions, probably best if you know you've been and if people might be interested in the system architecture in use case, I think they can understand how it might overlap with what they're doing or control to do and also be interested to hear how because this was pre-locked, how did you have all of this across various providers, consistency, etc. So yeah, it's never been a technical problem. It's always been a relationship problem. So it's about going out and actually talking to the states and territories about how they can be involved. If you don't charge them for the data there, that's their value proposition. And it's to the point where they are saving millions of dollars because they don't have to build an infrastructure themselves to do it. Yeah, it's over the time. So Melanie just very, very quickly to reply about location in that. So if we have a presentation about place names, that's probably connection to location metrics as well. So that's really good. Yeah. Great. Let's do that. Super. Okay. Apologies to people who didn't want to go over time. We are over time. Thanks so much to everyone for participation. We will defer extending our teams until the next meeting. Would anyone like to say anything before we disappear? So Melanie, the next meeting, date? Nothing's set in stone. So let's have a little chat about that and come up with one that might be and yeah. That'd be good. Currently in the presentation list, we've got things down for the 21st, which is next week, probably a bit too soon. It was the FSDF and the 2026 agenda. But we'll have to confirm that by email. Yeah, let's do that. And please, everyone, we'd really like to hear from you. And we have some documents in place, the upcoming presentation ideas, ideas or resources that you'd like to see come out of this. So yeah, please be in touch. Then I'm seeing what will be in touch about the occasion and on my presence, et cetera. Thank you. Great. Thanks so much. Thank you. Thanks. And please contact us if you've got any requests, information, requirements. Bye. Great. Thank you, everyone. Bye.


What's up everybody? Jason here from jaskiescasebrakes.com. We are doing two thousand and three thousand and four upper-deck SP authentic hobby box break random pack number one and Again guys, we are chasing LeBron rookies and it says 200,000 plus so it says of course 24 spot breaks and start 24 packs Everybody gets a random pack from the sealed box We will first randomize all the customer names and the numbers one through 24 Then whatever number you match up with is what pack we will rip for you 24 packs five cards per pack Again featuring two autographs per box on average including the autographed rookies of LeBron James Carmelo Anthony D Wade and many more look for autographed and Jersey cars from your favorite stars including Michael Jordan Kobe Bryant Tracy McGrady and many more So let's hope let's get a really nice boxer here guys So here you go. Here's a diet roller. Here's a customer name So Michael all the way down to Jeremy and of course you got one down in 24 So let's roll it We got ourselves a one and a four five times. Good luck one two three four and five Larry down to Chris.  I mean just we've had these in our vault for a little bit and Every once in a while we feel like it's cool to bring out a box and see what we've had hiding in there for X amount of days months weeks Alrighty so just the way it came out guys Larry you got packed 24 Michael a pack 16 wrong with 15 Harrison with 17 Christopher with four Matthew with six Christopher with 23 Matt with eight John with 21 Gail with 10 Sean with 20 Gretchen with 22 Chris with two Sean with 18 Matthew with 12 Jeremy with 19 Christopher with 11 Wesley with one Harrison with 14 Sean with nine Christopher with 13 Matt with three Christopher with seven and Chris K with five so really quickly guys. I should kind of do this before the break by just one by the The item description, but We quickly first open up this box now. I'm gonna number the packs So that way we know which pack numbers you guys are gonna be getting And here's SP authentic 0304 Which Tom Brady break? You talking about man. I love a They give us the checklist like in person Alrighty so the way I usually do it guys, I'll just go one all the way down and continue on like that Oh, I think okay. Yeah, I think that's just like a one-time thing, but yeah, I think I Think I think Sean might have talked about it because yeah, I think his his dad had a one and So and sold it to us, but usually I mean usually we get these just randomly 11 13 14 15 This is 0304 upper deck SP authentic 24 All right, you guys so there you go, there's all the numberings for the packs we'll grab them as we Rip through them and again, I'm gonna alphabetize that customer name. That's how we're gonna go Just to make it easier So the customers that got two or more packs or so So actually I'm gonna print out this list really quick and just to make this easier Turn out the labels. How about the shipping team a little bit as well? All righty Chris, we're gonna start off with you man to oh, sorry Two and five Two and five two I mean good luck. You should at least get two autographs in here guys Mike we have some for group rates. I'm not sure I'm personal many other check jaspis.com. Are we got?  Thank you All right Christopher is coming up next and we got pack four pack seven pack eleven thirteen and twenty three So let's go with four We got seven And we have eleven You have thirteen And twenty three Which is going on our four four seven eleven thirteen and twenty three Julio Are you gonna pack four? All right, this one this pack was a little stuck so i'm gonna try my best to Take all the cards out Steve Nash The Globe Jerry Sackhouse And Dirk Seven Spottomar Eddie Jones Dwayne Wagner And Jason Richardson Pack eleven Dirk That's a good question I would say scotty Late 90s early 2000 maybe Robinson Reggie Miller Wesley Tony Kukos Scotty All right pack 13. Yeah, Antonio Davis Chris Weber Bonsie Wells Allen Iverson and Jason Kidd And there you go 98 All right, I'm pack number 23 Sarif You got Matt Harping We got Zavekas Emanian Genobley And Karan Butler Chris we're nothing too crazy here man But it is a nice Dirk though All right It is Gale with pack 10 Here's pack 10 Good luck And our first authentic riggy autographs to level two James Jones Out of 1250 There you go Nice Larry Hughes Clifford Robinson And Quinn Richardson There you go. You got an auto Alrighty Gretchen To 22 All right, we got Amar Sotomar Corey Maggetti Tim Duncan Desmond Mason And Ben Wallace All right, thank you Gretchen All right Next up Harrison you have two pack 14 and 17 17 right here And 14 14, 17 We got a numbered card Stefan Marbury To 3999 AK-47 Matt Harpring Chauncey Billups And Baron Davis 17 Rashard Lewis Latrice Redwell Yeah, Alan Houston Sean Marion And Vladimir Radmanovich Alrighty Continue on Jeremy Lasbon Mojo pack 19 Quinn Richardson And we got SV Pictaculars Paul Pierce Malmashburn Eric Snow Jason Richardson All right, so one more auto hiding guys What pack is it gonna be in guys? Hopefully a good one as well All right, John, you're up next pack 21 Pack 21 Monica Nobley You got Gary Payton Eddie Jones Jerry Stackhouse And Dirk Larry, you're up next pack 24 It's the last pack of the box that we numbered there Antonia McDyves Larry Hughes Clifford Robinson Alton Brand And Richard Hamilton Alrighty Matt, you're up next with three and eight So three and eight There's three Steve Francis Earl Boykin Vince Harder That's Ray Allen Terry And pack eight Oh, we got an autograph We got the auto Behind Eddie Jones Wow, it's a dual autograph Not LeBron James But Larry Bird and Alonzo Morning That is awesome That's pretty sweet, I mean They wrote this almost like what, 20 years ago now Alrighty, well there you go Now this is still gonna be numbered rookies You never know Pack eight, too Alrighty, Matthew You have packs six and twelve Tim Duncan Richard Lewis Carlos Arroyo And another 20 Parker Jaylin Rose Andre Miller Brad Miller Ron Artest Lamar Odom Pack 16 I mean, some of these names I'm just like blown away I don't really know too much Jefferson Nick Van Axel Tyson Chandler And of course some of these guys are just so much Different now Ron with 15 Sam Cassell T-Mac, Tracy McGrady Carl Malone Michael Redd And Zach Rando Alright Sean You got three of them Nine, 18 and 20 So nine 18 And 20 And then pack one We'll be Wesley back here Kenyon Martin Nene Mike Miller Sharif And Antonia McDyne Damon Stoddermire Rafe LaFrance Steve Nash Kobe and Theo Ratliff Last one pack 20 David West Tony Cuccos Ugauskas Carlos Arroyo And Tony Parker Alrighty And last but not least Wesley Last pack Pack one Pagesdoyakovich Paugasal Drew Gooden Vladimir Rodovanovich And Sean Marion Alrighty everybody, there you go You get two autos One of them was a dual autograph Larry Bird Alonzo Mourning which is pretty sweet Or D-Wade Mellow Anything like that But still always fun to rip and see these boxes being opened, you know It's really rare to find these boxes in general And so when you do hit those big LeBron rookies as you can see Why they're priced at 200k plus You know, so Appreciate it everybody, jaspyskatesbreaks.com


Hi, I'm Melys and today with us is Oscar. Hi. Hello. We're here in Geneva at ITU's office for the Future Caster's Summit of 2020 with Firmin. How should digital technologies be used to improve education for all? Well, first of all, technologies are very important for our education. We are brought up into them and I think they should be well used more often in schools like school should teach us how to use an iPad or phone and use them correctly and not abuse of them because well, sometimes it can lead up to very bad decision-making and I think it's very important that we know step-by-step about how to protect ourselves in internet and how to use them properly. What encouraged you about the way digital technologies are heading? In general, they're heading a good way well to my point of view. I use them every day. They're in my life every day and they're very useful. I don't see any negative points about apart from well everything about hacking and more usage, but in a certain way, it's very useful like I said in our education. And finally the most important question. What do you think will be some of your top takeaways from this week's Future Caster's Summit? Well, I think this week I'm gonna learn a lot like a lot. First of all, I'm gonna meet a lot of people and this is gonna be very good. It's a great opportunity and I'm gonna have a lot of experience. It's very interesting. Last year I also did Firmune and I learned a lot and I think this year I'm gonna learn even more and I'm just so glad to be here and excited.