So hi, my name is Chris and I work at Digital New Zealand. We harvest metadata from nearly 150 institutions. We map it to a common schema that anyone can access through an API and we do this to make New Zealand's digital materials easier to find, share and use. Today I'm going to talk to you about some research and development work that we've been doing and then test an idea on you. This is... not my Mac. There we go. So link data. Link data is an amazing yet elusive idea. It extends the conventional web by providing a means to identify and refer to specific entities or concepts and it supplies a way to describe how those things are related. Together the entities, concepts and relationships constitute a set of assertions about how we think the world is. A set of assertions that can be queried, analysed, extended, shared and visualised. So, for example, our collections might have a person entity, Colin McCann, a place entity, Timaru, and a subject concept of say modern painter. Link data enables you to encode these little triplish statements like Colin McCann was born in Timaru or Colin McCann was a modern painter that can then slot into a much larger data network of assertions that spans institutions around the world. A network where you can ask questions like, show me all of the 20th century painters who were born near Timaru or who were McCann's contemporaries and the chronology of their paintings. So, folk have been talking about variants of link data and it's close cousin, the semantic web, for a couple of decades now. And it turns out to be a wee bit tricky to build. Our respective institutions structure data in different ways. This diversity complicates the act of forging links between entities and items. The National Library of New Zealand, the Alexander Turnbull Library, Te Papa, Auckland Art Gallery, Christchurch Art Gallery, Victoria University, Otago University and a host of other institutions all hold various works, photographs and writings relating to the artist Colin McCann. Although each institution is generally internally consistent in how they describe people, the metadata standards we follow and the data structures that we employ differ from one another. And so, although it's easy for a human to recognise that Colin McCann is the same as McCann, Colin is the same as McCann, John, Colin, 19-1987 those subtle distinctions are tricky to teach a computer. Perhaps this is the heart of the problem. So some time ago, Courtney Johnston made a Digital New Zealand set where she organised Colin McCann's work into chronological order. Her sets pulled paintings and sketches from all over the show, collections up and down the country, and she presents them together as a rough progression. I imagine it took her hours. She's created a handful of similar sets for other artists such as Ann Noble and Fiona Partington. The end result is that wonderful combination of something that is at once beautiful and useful. However, it is unsustainable and it doesn't scale. Right now, in this moment, I would like to see the evolution of Gordon Walters' paintings. I would also like to see, I don't know, Robin Morrison or John Pascoe or Marty Friedlander's photographs and how they developed over time. We collectively have that data in order to do this, but it's just, well, it seems really tricky. New Zealand may be small, but we've collected and digitised a fair amount of stuff. Truckload after metaphorical truckload of photographs, artworks, manuscripts, maps, articles, documents, audio recordings, films, ephemera and more. It is astonishing when you pause to think about it. And those things, those millions of works and commentaries and records, they refer to tens of thousands of places, hundreds of thousands of people and countless events both large and small in our nation's history. The good news is that generations of thoughtful, dedicated catalogers, curators and researchers have spent years describing this stuff. The tricky bit is that we employ a diverse range of practices, follow different standards and make use of a multitude of metatata schemes. Linking our data and our metadata together requires us to overcome these differences and that's what I've been exploring. So before the final part of the talk, or I'm just going to kind of just totally geek out on you, I'm going to note four underlying principles that inform this work and shaped my thinking. And I raised them explicitly in order to test them. So please let me know if any of these premises are either incorrect or irrelevant. The first, our collective interests overlap. So we, the nation's memory institutions and exhibition spaces, we share much in common with one another. There are differences, and trust me I'll get to those in a moment, but there is tremendous overlap in our concerns and in our interests. Each of our institutions hold only a partial account of Aotearoa's histories, contemporary states and possible futures. The works and writings and records relating to specific people and places and events are really conveniently housed in neat institutional buckets. The reality of the situation is that we are the collective stewards for a towering, glorious, densely connected tangle. And yet, the second principle is that our institutions, collections and practices are incredibly diverse. Just a few of the ways that we differ include our descriptive practices, the technical systems we use to manage our data, our metadata formats, where our staff's expertise lie, our institutional histories, our responsibilities and governance structures, the audiences that we serve and the budgets that we operate within. This heterogeneity is inevitable and probably also desirable, but it poses significant challenges to linking data because it takes a lot of work for dissimilar collections to be able to talk to one another, which leads to the third principle. We do stuff differently. Sometimes we've been doing stuff differently for a very long time indeed. We've built up particular sets of workflows, standards, expertise and technologies, investing considerable time, money along the way. I've been involved in a few workshops, both here and abroad lately, where folk discussed what it might mean to align their practices. And I've got to tell you, it sounds really hard and like it will cost a lot of money. I do think that these, how do we do it? This is the way that we do it. How is that different from the way that you do it? I think that those conversations are useful and enlightening and important. But from what I see, the metadata singularity is a long way off. This final premise is a volunteer quote that my colleague Michael Iscarides introduced me to. It's almost certain that there will be incorrect data and flawed methodology in what I'll round off by showing you. However, I think that we need to start somewhere. And I also think that we need to do it ourselves and not leave it in the hands of say, me and VF and Orchid and just trust it to other people to do it. So what I'm going to show you is I'm sharing something I guess as both a straw man and as scaffolding. A straw man because I think that we need a first attempt to examine, to consider and to debate in order to work out what this should and shouldn't be. And scaffolding because I believe that in order to actually realise what that linked data dream, we may need a temporary structure that provides an initial frame to build things off that we can safely dispose of when it no longer serves a useful purpose. So here's the experiment. I approached staff from four quite different institutions and asked them if I could have a crack at linking their person authority metadata together. I got 146,000 names from the Alexander Turnbull Library. So both people and corporate entities and others. Over 5,000 people, all the rest of people, 5,000 people from Te Papa, 2,700 artists from the Auckland Art Gallery and 2,100 person entities from Tiara. So let's just trace some of the data through the workflow that I set up. So the first thing that I did was I just pulled it all in. I just pulled in all of those thousands of names. And here you can see the different ways in which the institution structure them. So you've got your Colin McCann, your McCann, Colin John, McCann, Colin John, 1919-1987. I took those names and I tried to put them into a standard format. There are edge cases here. I realised that this is a very western take-on names and people and I would love to talk about that around the coffee table. But again, I'm just trying to get something to remove the dates and handle those elsewhere. You'll see those later. I then broke all of the parts of the words up into different parts into different little bits. So we've got Colin McCann, Colin John McCann. And then, and this is quite a simplification. I just chucked them all together into a big, big document store and started trying to match them. And the way that I matched them was I first matched on first names and tried to find all of the first names that were either identical or roughly similar. So stuff that was sort of close enough doing some fuzzy string matching. I then tried to find all of the final parts of a name that, again, were also either identical or very, very close indeed. I threw away all of the stuff where it didn't match and then looked for the stuff where both the first name and the final name matched to narrow it down and ended up with what I called my weak matches. I then found strong matches by comparing birth dates and death dates. And so a strong match is all that we're going to look at from here on. I think that there's potential to work with the weak matches, particularly with crowd sourcing. So further refinement by birth and death date. So a coincidence matrix of the matches across institutions. So we'll conduct gallery to Te Ara. Te Ara, there were 69 matches. Strong matches. 875 to Papa and so on. I find that the coincidence matrix is a little hard to read. So I turned it into a chord diagram and a chord diagram it's a bit unusual and I wonder if Mike Dickerson will like this. I've been watching his Twitter stream today. I might be in trouble. But a chord diagram, what it does is it divides the perimeter of a circle up into parts. We have and then it connects across to show linkages between the entities. So you can see actually the largest commonality is between Te Ara and the Alexander Turnbull Library where there were 1,601 strong matches and only a few very small number. I think 69 and 179 between Te Ara and the Auckland Art Gallery and Te Ara and to Papa respectively. Lots of crossover between the others though. So I did all of this matching and then I thought what would it look like for Digital New Zealand to have an authority API. So again this is all just R&D. This is not something that we're launching on Tuesday or anything like this. And I'm sorry I don't have a demo. My laptop did what Sonya's did before so I'm not as brave as her. So what I've done is I set up a simple API with HTML and JSON views and I think we should probably do XMLRDF of each person and you can imagine extending it to places and events.  I used the schema.org vocabulary with a few extensions because you always have to extend these vocabularies. But then I was also thinking about you folk. And I was thinking about wouldn't it be useful to actually not just have one place where you have your URL but that you can also use your own institutional languages to look these things up. So when Te Papa supplied them all to me the Colin McCann entity is party number 1502. When Auckland Art Gallery supplied it to me their institutional ID is the Intigid 867. Turnbull for example myRN number 18245. And the idea is that an institution can look up using their own language and get back how all of the other institutions talk about this thing. And this is what I was hoping to demo. I can show it to anyone. I'll be here for the next two days who'd like to see it. But I built a web application with all of this stuff. So this is an index of the matches. And I then linked it across to the Digital New Zealand API. So what we have here is a page of Colin McCann and you can see that there are the four matches at the top, the four different authority matches. And then I've gone into the Digital New Zealand API and used the language of each institution to look up the creator and then assembling it in chronological order. So this is a chronology of McCann's paintings. It's just automatically generated by the system. We can do this. It's really quite neat. And then you can just pick another artist. So Peter Perry's photography, for example, from the 70s on. It's splicing together on the fly to Papua and Auckland Art Gallery in chronological order. So you can even see the double ups, for example, with it held in both institutions. So what I see this as being, if we were to do this, would be almost not acting as some sort of master or ultimate authority on this stuff, but much more like a telephone exchange where we're saying when you talk about this, they're talking about that and sort of just connecting people from one authority set to another. There's a lot of open questions here, and this is really just the start of a discussion. But the question I really have for you is is this worthwhile and is this something that we should look at doing? To date, this has just been what sometimes called at work one of a train project. We're basically doing it to and from work on the train. That's my train office. It's really great. Except when they change the trains and I don't like the new trains. I like the old ones. But to date, that's as far as we've got from really just doing it in bits of spare time and bits of kind of when things aren't burning down, I might spend half an hour on this thing. So if you think this is worthwhile or interesting, or if you think this is pointless and no good, then please approach us and talk to us about it. I'll put up a blog post next week and I'm going to try and circulate a white paper on this soon. So thank you very much.


ۅ accompablery dh 끝 aap ۅcompablery ۅcompablery ۅcompablery ۅcompablery ۅcompablery ۅcompablery ۅcompablery ۅ growth ۑ ۚ ۗ ۴ ۑ ۔ ۓ ۗ ۶ attempts ۈ ے � Katherine


It's now time for Member Statements, the Member from Wellington, Halton Hills. Mr. Speaker, the promise of the future in Ontario calls us to pursue excellence in post-secondary education, leading to good career track job opportunities for graduates, and a stronger innovation-based economy for the province. This goal requires partnership and vision. That's why we were so excited to hear the government's commitment to build a new university campus in Halton. I was glad to be in attendance when the announcement was made last Wednesday in Milton. Wilford Laurier University's President, Max Blau, says a university campus will strengthen and complement the town of Milton's vision of a diversified workforce to drive economic prosperity and meet the evolving needs of Ontario's economy. Region of Halton Chair Gary Carr, who spoke at the announcement, has provided strong, effective leadership on regional council in support of this proposal. Mayors Gord Krantz and Rick Burnett have also been vocal advocates, and we thank them as well. As members will recall, in recent months I've been publicly urging the government to approve Laurier's proposal for a new Milton campus to give our students another post-secondary education option close to home. While the Minister announced a call for proposals for this coming January, she did not indicate any timeframe for when the new campus will be completed and open for students. We all know this is a long-term project and it won't be built overnight, but surely Milton residents and Laurier's supporters deserve to know the government's timetable for completion of the new campus. I urge the Minister to announce this publicly and soon. Let's work together to build the promise of the future in Ontario. Thank you very much, Mr. Speaker. Thank you for their members, students, members from Niagara Falls. Mr. Speaker, I rise today to let everyone in this house know about an 18-year-old girl from our riding who is a hero and inspiration. She just loves to run. Her hero's name is Julianne Miske. Julianne was born with a very rare genetic disorder which caused her to suffer through multiple surgeries and infections. Joe and Bernadette are her incredible parents. Just a few years ago, she realized she had a passion, a passion for running and run she has. With the help of her coach, her Niagara Falls City Councilor and teacher at St. Mike's, Victor Pierangelo, who runs these races beside Julianne, she has gone on to be a four-time Ontario Federation of School Athletic Association pair cross-country champion and also a three-time offset track and field champion. Her latest victory came at Sasa last Thursday. Mr. Speaker, just six weeks ago, Julianne discovered she had a rare form of bone cancer in her jaw. She is going through chemo and will have to have a bone from her calf transplant into her jaw. It's tough when someone has to battle cancer, letting someone so young and with so much talent. On Thursday, the students at St. Mike's Catholic High School were there with Julianne cross the finish line, wearing her number 320. The students all came to support her. They were there chanting Julianne's name and holding signs that said, you can do it or mind over matter or simply be strong. We are all so proud to say that not only did Julianne run at Sasa last Thursday, but this Saturday should be running again at OFSSAA in Port Colburn. Well Julianne, we all know that you will do it again because you are so strong and we are all so proud to have you here with us today. We wish you all the best, have fun on Saturday and we'll be running with you in spirit. Thank you. Member statements. Member from St. Catherine's. Thank you Mr. Speaker. Before I commence the statement I would like to join with the member for Niagara Falls and all members and wishing her the very very best. This is a real story of courage and I thank you for your indulgence along me as one of the members to join with the member for Niagara Falls and those wonderful tributes. Okay. I am pleased to rise in legislature today to recognize our collective efforts to protect water, farmland and nature in Ontario. I applaud the government for committing to grow the green belt by adding 21 urban river valleys and seven coastal wetlands. This commitment builds on the work of previous governments and protecting the old ridges, moraine and Niagara's carpets. Ensuring the sources of our water and food are protected is truly something on which we can all agree no matter what party we represent. Today I stand here in support of the 26,000 Ontarians and 120 organizations who are calling on all parties to protect our water supplies by growing the green belt. We have letters to support from Niagara to Northumberland, Simcoe to Wellington and from every community in the greater Golden Horseshoe. We have support from ratepayers, associations, agricultural groups, youth groups, environmental organizations and others. They're asking for a science-based expansion, the green belt to include a blue belt of vulnerable water supplies and features. The blue belt would protect drinking water supplies for millions of residents and support our economic powerhouse, Ontario's farmers and grape growers. It would also make our region more resilient to extreme weather and climate change. The green belt is already overwhelmingly popular. More than 90% of Ontarians agree with it. This popular groundswell shows that now is the right time to grow the green belt. Thank you, Mr. Speaker. Thank you. Further members, same as the member from Halliburton Fourth Lakes Project. Thank you, Mr. Speaker. I rise today to recognize the amazing work of members of 53 police services across Canada, most of them in Ontario, who recently conducted Operation Northern Spotlight.  As noted in the official report, during coordinating investigations over a six-day period, police charged 47 people with over 78 offences. Police were also able to ensure the safety of 20 people who had been working in the sex trade as a minor or against their will, including some as young as 14 years old and most of them under 19. The evil of human sex trafficking is in our neighbourhoods, it's in every corner of Ontario, which has been recognized as a major hub of human sex trafficking in Canada. As I travel across our province, I find myself speaking with former victims who felt like they had no hope of escaping this invisible chain of modern-day slavery. We must continue to do everything in our power to support our police officers and victim service organisations as they deal with this scourge. Once again, I want to express my gratitude for the dedication of our police services involved in Operation Northern Spotlight. They brought much-needed attention to the issue of human sex trafficking. More importantly, they saved 20 young people from the clutches of brutal thugs who will hopefully face the full force of justice in our courts. Well, thank you, Mr Speaker, and let me set this up for you. So imagine the Elliott Lakes gentlemen's knitting challenge that's the setting. So we have a new business that's opened up by Maya Puno in Elliott Lakes. She's opened up the knitting room, promoting a lot of yarn, fibre, and the opportunity to learn new skills. And to help her out, I challenged the editor of The Standard, which was Kevin McChefrey. I challenged Elnos, representative William Elliott, and I challenged the Mayor, Dan Marchazzella, and I also challenged the Elliott Lake Fire Chief, John Thomas. And you know what? They answered my call, Mr Speaker. They came in and William Elliott came in with the extra auntie.  Well, we all got together, Mr Speaker, and let me tell you, you had a bunch of burly boys tied up in yarn, making a scarf, and having a lot of fun doing it. We didn't have a problem doing it. As a matter of fact, I just delivered my final product to our leader, Andrea Vorowath, yesterday, and she is wearing it quite proudly. You know who the winner is at the end of the day, Mr Speaker? The Elliott Lake Food Bank. The Elliott Lake Food Bank received the funds that were raised throughout the day. Over $700 was raised during the day. And for the individuals that came to the event, they all contributed a non-perishable food item. It's a fantastic event. Step out of your comfort zone, knit a scarf, help your food banks. It's a lot of fun. Thank you for the members' statements, the members of Mrs. Sagar Brandt himself. Mr Speaker, this past Sunday I was pleased to attend the 18th Phoenix Ball, which is hosted each year by the Miss Sagar Board of Chinese Professionals and Businesses, known as the CPB. This year's charity ball has attracted over 450 patrons from throughout the GTA, including many from my own diverse riding of Miss Sagar Brandt himself. Since 1999, in fact, this organization and its foundation have raised over $2 million for worthy causes. This year, proceeds will go to the E-Hong Centre for Geriatric Care in my riding. I would like to thank for its years of charitable work, as well as its presentation of an important business community in the region. I also thank the CPB board members, past and present, for their public spirit, vision and compassion for others. Mr Speaker, they are, as individuals and in our organization, wonderful examples of active business leadership in the community. Thank you, CPB, for your great work, keep up the good work. I'm very proud of you. Thank you, Mr. Speaker. Thank you. Further members' statements? The member from Kitchener, Conestoga. Yes, as we join with our veterans, our heroes, to recognize the passage of the Remembrance Week Act here at Queen's Park. I wanted to take the opportunity to also recognize all of those who work so hard all year long to honor our military men and women in ceremonies, dinners and get-togethers throughout Waterloo Region. And while Remembrance Week gives us an annual opportunity to thank our past and present members of our armed forces, most importantly, those who have made the ultimate sacrifice, it's the work of those unrecognized volunteers from our area halls, churches, temples and legions that ensure those opportunities are shared across the area in our community. Speaker, there are so many who work tirelessly to provide the stages on which residents from across Waterloo Region are able to say thank you, that I want to say a big thank you to them. Thank you to those working to pull together events on Saturday when Remembrance Services will take place at New Dundee Public School, followed by the New Hamburg 19th Annual Veterans Appreciation Dinner, later in the evening over at the Royal Canadian Legion Branch 532, put on by the Ladies Auxury. Also, thanks to the volunteers working on Sunday's Linnwood Remembrance Service and the Elmira Remembrance Day parade put on by the Elmira Legion Branch 469. Thank you to all those participating in our local Sikh Remembrance Day ceremony to remember Canadian war heroes and Canadian sacrifices while celebrating the Sikh tradition of military service. And thank you to the many volunteers throughout our region who will be busy preparing November 11th ceremonies in New Hamburg, Elmira, Kitchener and Waterloo. Thank you for your service that allows us to thank all of our veterans for theirs. And thank you too. Thank you for your understanding as a member from Nickel Belt. Thank you, Speaker.  You see, Speaker, for the last eight years, they both live at the Shalom Gardens, a retirement home in Grinsby, and they believe that they would move to the Shalom Manor on site if they ever needed long-term care. How wrong can two good people be? In August, Clarence fell and his need changes. He got admitted into Shalom Manor close to his wife. His wife could not cope anymore in the retirement home and the family chose to put her in the nursing home with her husband. The problem is the CCAC said you have to put at least four choices on your application. Well, sure enough, Jesse was sent to a nursing home in St. Catherine away from her husband. Since August, the family have pleaded with everybody who would listen to them to bring her mom and dad back together at Shalom Manor. Spousal reunification comes after crisis. The long-term care system in their community is in crisis all the time. The chances of Jesse and Clarence to be reunited is zero because they will always be crisis ahead of them. This is wrong. The system has to be changed. The minister must intervene and make sure that those two people are allowed to live their lives together like they did 70 years ago when they said yes to marriage. They're not the first one to go through this. It has to change. It has to change now. Thank you. Thank you very much, Mr. Speaker. And I want to express my thanks to the member from Simple Gray who asked the member from Parkdale High Park and myself to join him on an act to proclaim Remembrance Week. I feel very honored to have joined him on this bill. And in this house, we're at our best when we give expression. We come together to give expression to those things that are important to all of us, to all the people that we serve and certainly remembering those who have served and continually serve us is one of those things. Now, when we remember, we remember family and families.  So Robert Ainsley Kavanaugh, the brother of Yvonne Hooper, then Yvonne Kavanaugh, enlisted underage for the Second World War. He served as a Navy commando, naval seaman in and was killed at the end. And my mother-in-law Yvonne, who's 96, I'm going to get in trouble for saying that now because she hears this, remembers his he is alive in her heart and she's done a lot to keep that there for 96 years. We recognize that in our family by our granddaughter Sloane having the second name Ainsley. And what I want to say is that many families are touched. We're all touched by these acts of sacrifice and continuing acts of sacrifice that people are making. And that I hope that next week, in Remembrance Week, we all have an opportunity to reflect on the importance of that. Thank you very much. I thank all members for their statements. I beg to inform the House following a report was tabled, the 2015-16 annual report of the ombudsman-


Hello. Hello, hello. Hello, Chris. Hey, Taylor. Oh, hey, Taylor. We'll get started about five past. I put the slides in the chat. We'll get started about five past. We'll get started in two minutes. I see Camille is here. Is Brian Grant here? Don't know if he's dialed in today. Hey, Chris. Good morning. Hey, Ken. How's it going? It's going well. We'll get started in a minute. Busy, busy morning already. Oh, no worries. I apologize. Yeah, lots of people are either stuck in board meetings or have travel conflicts. So we're a little bit light on TOC members today. But obviously appreciate your presence. Alrighty. Is Jonathan or Solomon? I don't know the call. I don't see them. All right, cool. I'll get started. So yeah, we have a lot of TOC members that are currently, you know, traveling or have conflicts that have come up. So we're a little bit light today, but no reason for us not to hold the meeting. Since Alexis is not here, I will drive the meeting this time around. In terms of the agenda, I'm going to go through a little bit of an update in terms of the election schedule, a little discussion on a working group process. We have a community presentation from the cross-cloud folks, and then we'll kind of just open up the questions from the community. So slide six. So we are now in the phase of the election where the TOC is voting on the TOC's selected seats. The vote will be closing at the end of day, April 5th. Pacific time. We have 10 fantastic, qualified candidates. So I look forward to the TOC, seven TOC members getting their votes in for those two TOC selected seats. Does anyone have questions in the community based on that process or timing? Cool. Look forward to making that announcement. Slide seven.  Brian Grant has voted, so I'm waiting for other TOC members to send their votes in so we could come to a conclusion on that one. And then Fluent D and Prometheus are in queue to be voted upon to graduate. There's just a couple of small things they need to do before we formally call the graduation on that and to fulfill their graduation requirements. Does anyone have any questions here? Awesome. Moving on. Slide eight. Just a quick update. You know, we have a couple projects that are requesting to be presented to the TOC for essentially, you know, getting accepted into the sandbox. There's telepresence and open messaging. You know, I'd like to call upon our TOC contributors and community members to take a look at these issues before they present and feel free to make any comments there or ask questions to the teams before they formally present to the TOC and wider community. Moving on to slide nine. There's been a few folks that have approached the TOC and in particular me of setting up some new working groups. We essentially had a informal process of doing these and I'm just trying to codify a more formal process on how to propose these similar to kind of how we handle projects where people just send a pull request with their proposal and we get community discussion on GitHub and have a presentation from them. So I'd ask the TOC and the community to take a look at that pull request and hopefully by the next TOC meeting we could get that solidified and kind of move forward so folks from the community could propose some new working groups that they're interested in exploring. Does anyone have questions on that from the TOC or the community? We can hear you, Chris. We just don't have questions. No worries. I like a very non-controversial TOC meeting. This is good news to me. Thanks. All right. Yeah, so look forward to that. Please take a look at it. I mean, this is exactly what we're doing anyway for working groups. I just need a mechanism for people that are interested in proposing new ones to provide an avenue for community discussion. So there's some really cool stuff coming in the pipeline. People are really excited. All right. Next up, I'd like to give a little bit of an update from the CNCFCI working group and the cross cloud community. So let's see. I don't know if Denver or Lucina is going to be driving, but I think you're on the call. So we'd love to kind of hear from you. Hello. Hello. Hey, Lucina. I don't hear you. Okay. I hear someone now. Hi. Hey, Taylor. How's it going? Good. All right. It's now off to you. Slide 10. So go for it. Sounds good. I'm going to go ahead and share my screen. Awesome. Go for it. Look good, do y'all? Yep. Okay. So it's been a good while since we presented to the TOC. Some of y'all may have seen some updates earlier, but we'll do kind of an overview of everything and see where we're at now. So this is a cross cloud CI project. Here's the cross cloud CI team. Some of the folks, Denver and Lucina are on the call and I think Watson as well. So a little quick overview of why we're here. So everyone knows the CNCF is growing like wild. Lots of new projects, new clouds, partners, everything else. And we'd like to see the projects working well together and validating that they're looking great on all the cloud providers supporting their cloud native features. So this project is trying to, its goal is to test the projects on the cloud providers and the interoperability between all the projects themselves. The backend testing system is composed of a build cross cloud provisioning stage and a cross project stage. There's also a status repository server with an API and a dashboard to show those results. We want to target all of the CNCF projects. Right now we have 40 NS, Hermitius, Flinty, Linkardy, as well as of course Kubernetes. We're also trying to target non CNCF projects. We've added the Linux foundation project onapp specifically the service orchestrator. On the clouds we're targeting all the public private bare metal. For bare metal we're using packet and for private clouds we've added open stack recently. I'm going to go ahead and start a live demo so we can see how some of this works. This is the production dashboard. It's updated daily at 3 a.m. Eastern. It shows the different stages of the build system, the deployment, the ED testing, Kubernetes provisioning, and the status of those. It's testing the stable as well as the head release of the projects. In later phases on some other screens we may be showing some of the other stable releases. Right now this is an overview screen and we have Kubernetes, Hermitius, Core DNS, Flinty, Linkardy, and Onapp. On the cloud providers you can see AWS, Azure, Google Clouds, IBM Cloud, bare metal, and open stack. If we click through you can go to the commits out on GitHub for the various projects on the build side. We can go through to see the backend build system for Onapp. This actually ties in with their CI system. They're using Jenkins and Nexus for container repository. I'm going to go ahead and start off a deploy to see this running. We went ahead and did the builds and the Kubernetes provisioning earlier because that can take anywhere from half an hour to an hour to run through everything including end-to-end tests. We don't want to wait that long.  This is calling out to the API and triggering that. What this is going to do is start the... We can see it here. It's starting the pipelines that will deploy each of the apps to Kubernetes across every cloud. There's quite a bit that are going to run through. Right now it's getting some of the software, Helm, and the container that actually does the deploy is ready. Then it'll move on to the app deploy face here. We can see it's starting to run across each of these for Prometheus. This will keep going through as it gets deployed with Helm on to Kubernetes. After that, it will deploy and run the end-to-end test, which we try to source from upstream and work with the projects. Here's a quick overview of what we were just looking at, all the different parts of the dashboard. I want to go through a quick timeline where we've been. In February 2017, the project started and then June, we had our first demo to the CI working group. That was showing primarily the CI system and how the different pipelines work to build, provision, and deploy. In August, we demoed to the TOC, showed some of the designs for the dashboard, as well as the API status, status repository. Then we had the green light on the design in September. In December, we had some sneak peeks at KubeCon and had the release of the dashboard in January 2018 with the status repository, as well as a reworking of the back end to use the different components independently, like provisioning can be used independently, or the app deployment and E to E phase. In March, we've had quite a few new releases, including adding some new projects, new clouds like IBM Cloud. We added OpenSack, as well as the Onap project, which was our first external integration with the CI system outside of GitLab. That was pretty great. What's next? We're going to be adding new projects, new clouds on the project slides, Envoy Yeager coming next and notary some others here. We're going to target Oracle, is the most likely target for April. We're hoping to have this out and then getting to Huawei, Alibaba. Eventually, we're going to be adding ARM support, starting with Kubernetes on ARM and going forward. Inside the project itself, some of the updates that we're going to be doing would be automating the updates of the releases from projects upstream and testing those and then pushing them out to the dashboard. Right now, the process is a couple of steps to get them out. We're also planning on having the history in the API for all of the tests and the artifacts and everything else to be available in the status repository so that it can be queried externally. You can look up stuff like a version of Kubernetes with what version of Prometheus worked on that and use those externally to the dashboard. This will also help us to do rollback to previous releases. If we had a failure on 196 on a deploy or maybe Onap wasn't running, then we could point that out in the dashboard with full chips or whatever else. That'll tie in with some of the next screens that we're doing. Probably on a Kubernetes project screen for that filter, we may be showing 1.8 and other stable releases. For the collaboration side, working with other groups, we're working with the OpenCI community that came about from a face-to-face before ONS this past week and working on a collaborative white paper together for how that should look. We've also been working on an RFC for pipeline messaging protocol. Have the link here. Anyone wants to check that out? We're going to be working with VMware and IBM Cloud talking about their provisioning. We're looking at Spinnaker as an option for doing some of the stuff to do with GitLab. Now that the cross-cloud system has a layer between the backend platform that has workers and runners as well as some of the projects themselves for their end-to-end tests. Hermitius is working on a lot of their end-to-end tests including performance and stuff. We're running to tie in and try to see where we can complement directly and reuse those for DNS as well. We're also looking forward to talking about the GitOps and how we use it and where we could improve and tie that into the project. The next CI working group is April 10th. We're planning on being at KubeCon, CloudNativeCon, and Copenhagen. We're going to have an intro as well as a deep dive for the project and how folks can get started, whether you're a project or if there's any cloud providers that want to talk to us. OpenStack was really great on Chris Hodge, who wanted to call out for helping, as well as Melvin, trying to work with us to add OpenStack support. We'll be there to try to show how folks can do that and contribute directly. Here's where you can join the CI working group mailing list. If you have any more questions, feel free to jump on there. If you check out the GitHub cross-cloud CI, we've been updating the READMEs. It has an overview in the main and the different components like cross-cloud or cross-project. We're trying to update those READMEs so that you can use the components directly independent of the cross-cloud CI project. That's our update, pretty big from the last time. Any questions? Hi, I have a question for Malibor. Can you hear me? Yes, I can. Would it be suitable for testing Kubernetes certified distributions? I'm thinking of Cubespawn, for example. I couldn't understand that last part. Would it be okay to use that for testing Kubernetes certified distributions? I'm thinking of Cubespawn, which is a tool to test Kubernetes on a developer's laptop. We are trying to use Kubernetes conformance test for our conformance on all the cloud providers. There is a conformance sig and we're trying to follow some of the things that are happening there, like feature flags, that'll be able to test various features on cloud providers. It could be used. Dan, are you here on the car? Hi, I am. CNCF is both funding the cross-cloud work and running the certified Kubernetes. The quick context I'll give you is that on certified Kubernetes, the sort of clever part of that program is that although each provider needs to run their own conformance tests and upload the logs in order to certify, the program also has a crowdsourcing element that any future user or customer of that distribution or platform can run those same tests and evaluate it and report back if some API is no longer conformant. I'm not sure if there's a CI rule for that and we wouldn't necessarily be wanting to run a ton of proprietary software and having to deal with just inevitable bugs and stuff. We're up to 52 certified Kubernetes out there, so that would be a ton of effort. The part that I am potentially interested in expanding into is there's this nascent effort to try and separate out the different cloud aspects of Kubernetes into their own out-of-tree repos and then there's some question of, well, how do you ensure that that code is maintained over time and that it keeps running? I would love to see the CI, the cross-cloud work used to demonstrate the official out-of-tree version for each of the new clouds that's being developed and to show that the head of Kubernetes is not breaking things on it, but that really is a super new effort and it's a proposal. The code's open source, it's available to the cloud providers and it's something I mentioned on the SIG architecture call, but we'll see if that actually goes forward or not. Alvin, do you want to maybe specify your question a little bit more or does that address it? Yes, that's what I'd like to make a show. Thanks. Certainly. I would love to just hear other feedback on the cross-cloud stuff. Are there people on the call who this is new to and who think this is either kind of cool or they might be interested in looking at the Terraform recipes that we're using? Again, everything's under Apache 2.0 or do folks see this as duplicative with other projects out there? It's been a pretty significant investment from CNCF and it continues to be and so we're very interested in feedback on whether we're on the right direction or not. I have another question. Which Linux distribution does it use to test Kubernetes, for example? Does it use something like Fedora or Ubuntu or something completely different? Hey, this is Timber from the cross-cloud team. At the moment it uses CoreOS for the underlying OAS, but all the structure of getting everything on the OAS is done via CloudNet. Theoretically, we can replace the OAS with Debian or Santos or any CloudNet capable OAS. So let's say someone wanted to write this Bob-wise. By the way, it's really looking great. This has been a great effort. Bob actually should claim credit as the godfather of this because he's the one who asked for a dashboard 18 months ago. Bob, I think it took a little longer than we were expecting, but... Yeah, I know. This is really cool. Can you comment maybe a little on... Some of these questions I think are... Hey, we'd like to see something happen, like add some additional thing here and I think you understandably are concerned about explosion of combinatorial explosions, but let's say someone did want to, I don't know, add tests for a different distro as the other caller was mentioning. Is there a way for someone to volunteer effort or effort or resources to make that happen? Would you be open to that? Yeah, definitely. Changes should be pretty easy to integrate and it's just expands the matrix, the only... So it would just be a pull request into the code that deals with the provisioning. The only thing that might be a little bit of effort where we haven't quite got to yet is showing matrices on the dashboard. So it deployed on AWS with this or with this and that matrix would get really big, especially when you have maybe networking, like Weaver's, Calico, the matrix just gets bigger and bigger and bigger. You need to figure out a way to deal with it at some point because it'd be cool to show that. Right. I think there are likely some combinatorial issues even just within the projects. For example, Kubernetes with container D and Kubernetes with Docker just to pick an obvious example off the top of my head. Yeah, definitely. And Bob, yeah. I mean, if there's demand for it, we can add it to the main dashboard, but of course anybody can also fork this and run their own versions with their own combinations. I do see the value though in having the official version support more things. So Bob, we are planning on having some of those Docker and different choices and we'll be showing, I think some of those may go on to a sub page or a filtered view to show some of those others versus what is the main view. And then as Dan said, anyone could run the dashboard and the status repository, but any of the components can be split off. And the dashboard is actually all configuration driven so that if you spin up the code, then you can point to whatever your configuration is and say, I only want these projects to show whatever that may be, then that could be used. So someone may want to use it just for their project, which would be fine. Right. I mean, I understand the possible utility of using this to do some other kind of testing, but I think, I don't know, I guess for the sake of the community, I'd rather see more people contribute to this set of tests than split it off and run it separately. Feels like it would have more value in the long run as long as we can support that. Absolutely. I think when we release the status API with the history, it'll be, it'll help with having the different scenarios, because then we could have different tests that are running that may not be shown on the main overview screen, that people could access them either directly via the API or possibly another view, which may not be the dashboard, but we may have views or some type of big list for the matrix of different scenarios and all the different testing. As far as contributing tests, having any project work on end to end tests that work outside of their build system, so user end test versus a CI internal only really helps. So Core DNS is a great example. They're trying to make sure all of their tests will run independently for an end user, and then it doesn't depend on a specialized CI environment, and that's how we've tried to do the test examples, and we're trying to help. So any project that can do that, or if someone wanted to contribute to say Fluent Day and help provide those end user integration tests, then that would be great. A good way to help. And there's a lot of new projects we'll be adding, so if they're contributing to any of those other CNCF projects, then by the time we get there, if the tests are done, that would be wonderful. I know the point of this isn't scale testing, but just as a matter of curiosity at this point, what's the sort of server scale that these tests are being run against? At the moment, it's the three multi master nodes, and we're only using one worker at the moment because of the way we had to shrink, because of the way Onap's being deployed at the moment. Onap isn't able to use the single volume. It's got to be all in one host, so it was either set up NFS across all the nodes, or just use one worker. So we're just on one scheduler at the moment until the Beijing release comes out for that. Do all the tests even work with only one worker node? Thought there were some that required multiple nodes. There should be some that require multiple nodes. I think the only one that would give us grief at the moment would be Kubernetes, but we're just running a subset of the tests, so we don't hit that. But if we wanted to do some density tests, then we'll probably get struck by that. I'm not 100% sure on this, but I'm 80% sure that Kubernetes conformance tests will pass running on a single node. Okay, I'll try to get that fixed. I agree that demon sets would be like an obvious example where that seems... Well, networking seems like an obvious example. Yeah, and we define what that should look like, Brian. It doesn't know what we should do as a TOC, kind of define what that minimum set of compliance... The SIG architecture owns that in Kubernetes. Okay, I'll define that as far as you know. At the moment, there are a lot of areas where the tests are... We started with the tests that we had, so we're looking at places where the tests need to be expanded. This is definitely one of the areas it looks like. So I had a question, which is, have the folks working on this... I'm poking around the GitHub repo, looking at the Terraform. Have you talked to the Kubernetes cluster lifecycle special interest group about what you're doing? Because I think reinventing how to deploy Kubernetes is probably duplicates work that the cluster lifecycle SIG is doing. I don't believe we've had a call with cluster lifecycle yet. We did have a few calls with Aaron from SIG, the infrastructure SIG. That would be the testing SIG, I would guess. Yeah. Brian, Aaron and also Tim Hawken have both looked at this and Jago and a number of others, but we're not wedded to the Terraform approach that we're taking. Yeah, I just think it's going to be hard to... We would love to have that. I guess I... What's the specific project or code out of SIG lifecycle that you would compare this to? In terms of actually deploying for the first time, spinning up, spinning down kind of thing? Well, the Terraform bits, that part we call provisioning, and then actually bringing up Kubernetes on it, we call that bootstrapping. There are a number of projects. I think the two main ones would be the cluster API effort and the cops. Right. And so we looked at cops and thought the Terraform was going to be a more general purpose, but essentially we're willing to transition off of all this Terraform onto whatever the official way of doing it is if there's a recommendation on this. So I think starting with maybe a presentation to cluster lifecycle would be a good next step. Yeah, I think that would be a good next step. Yeah, we're discussing how to... What our reference implementation be for running our own Intuit tests as we replace the existing deprecated QBOP mechanism. So, yeah, I just think if you're maintaining your own on several different cloud providers, that's going to be hard to do as the system continues to evolve. Great, we'll take that as an action. Okay. Hi, this is Aaron Boyd. I had a quick question. With the Kubernetes testing on the different clouds, is that also testing persistent storage? I know I talked with a couple of you guys in the past about that component. I don't know the criticality of it, but I was curious if that was integrated. At the moment, we're just running the conformance subset and what that gets. So I believe conformance tests some storage, but it's not extensive. But we'd like to get to a point where we can profile and be like, we're on this cluster, AWS do a subset of the AWS integrations and include storage. Right, okay, thanks. Whoever's speaking is chopping up for me. Yeah, it's comprehensible. Maybe you can just type it into the chat window instead and we'll read it. Yep, yeah, you're still chopping up, so please type it in the chat. I don't know who it is, so that's the other problem. Well, I guess the question is from Albin. Is this building only daily tests or would it be plugged to a pull request on GitHub? That's the question. At the moment, this is a nightly run, so it goes slowly. Yeah, so not on every pull request. Okay, thanks. Any other questions for the cross-cloud folks? All righty, cool. Thank you, Denver, Taylor, and everyone involved at the project. It's great to see it progress. You're welcome. Thanks for all the great feedback. Appreciate it. Cool. All right, so moving on. So slide 27.  I know you're planning your first kind of official meeting soon, so be good to kind of get people up to speed and how to get them involved with the efforts. No problem, Chris. So we are organizing a meeting for next week for the reference architecture work. And there's a site in GitHub. There's a location you can sign up for that group. And just to please let me know, I'm looking forward to meeting next Tuesday with everyone. Can you also send out a note to the mailing list, Ken, on that one? I can. Just to my folks. Thanks. Yeah, absolutely. Any questions for Ken on reference architecture? 2.0. Alrighty. So moving on next up, slide 28. So as you're aware, CNCF helps put on events for our community and projects. We have a big event coming up in Copenhagen in early May, May 2nd to 24th. I will just remind people that please book your hotels early. We are going to sell out that event and hotel space is going to be a bit of a challenge. So the earlier, the better. We also have two other events that we're hosting the year, our first event in China and an event in North American Seattle in December. So sponsorships are available for Shanghai and Seattle. And we'd love to have a huge presence in China, given that it's our first event. So please submit talks and consider sponsoring the event. Dan, you have any other thoughts on call for action here? Well, just that the call for papers is going to open at KubeCon. So you can begin thinking about it. We're going to have an option to submit your talks to Shanghai, Seattle or both. Awesome. Alrighty. Moving on slide 29. Just a reminder, our next meeting will be April 27th. We'll have two community presentations. One from the telepresence project and one for a proposed working group around security called SAFE. We will also at that time have two new TOC members. So look forward to that announcement. Other than that, any other questions? Slide 30 is basically open Q&A. We have about 15 or so minutes left. So if anyone has time to ask questions to the TOC or the wider community or CNCF staff, we'd love to hear it. Chris, I have a question. Sure. Dan Shaw, I'm actually from the SAFE group. And I was just wondering, saw the working group process kicking off. Do you have any expectations about how long that process is going to take to land? You know, I see the discussion is getting off there. Yeah, it's hard to say. My assumption is just follow the proposed template. I actually have a meeting with some other folks from the SAFE group today and I'll guide them through the process. So in general, you have the slot to present to the TOC next week, or sorry, in two weeks. And we'll kind of follow the template as dictated in kind of that PR. I don't think we're going to var very far from what's there. Makes sense. Cool. Thanks, Dan. Any other questions out there? I see Brian and Bob arguing about cigar architecture and what it owns. Clarifying. Clarifying. Any other questions from the community to staff or the TOC? Well, if there's no other questions, I'll give everyone 15 minutes back with just a friendly reminder for the TOC members that are on the call to vote on the Linker D to Sandbox to Incubation Proposal. I think Brian Grant is the only one that has put forth a vote. So to Camille, can please consider throwing down a vote for the end of this week and hope to see many of you in a couple of weeks where the telepresence project and the SAFE WG will be presenting and then hopefully we'll see many of you in Copenhagen in May. So enjoy the rest of your day and here's 15 minutes back. Cool. Take care, everyone. You too. Thanks. Thanks. Bye-bye. Bye.


From the Cosmopolitan Hotel in Las Vegas, Nevada, it's theCUBE, covering Coupa Inspire 2019. Brought to you by Coupa. Welcome to theCUBE from Coupa Inspire 19 at the Cosmopolitan in Las Vegas. It's a pretty, pretty swanky place here. Very excited to welcome to theCUBE for the first time from Accenture. Jesse Hanger, director of Capability Network, sourcing and procurement. Jesse, welcome. Thank you, glad to be here. Oh, our pleasure to have you. So here we are, day two of the main stuff going on here, all talking about business spend management, BSM, this new category that Coupa is defining, had the chance yesterday to speak with Rob Bernstein, their CEO, Robbie Chalker was there. And it's one of the cool things that Coupa is doing is it's now, it's procurement, it's invoicing, it's expenses, it's payments, but it's also helping to redefine procurement and finance. And it is. I mean, it's a huge shift when we think about in industry the same shift that Salesforce had years ago when it comes to CRM. When Coupa started talking about this, maybe two years ago, you know, I had a little bit of a head scratcher. I saw some of their slides and I thought to myself, that's a bit much to say you're gonna change this. But the funny thing was, no one else had come up with a real definition of this. We finally had procurement technology that was at a level that you could capture this type of data and information and it could go broader than just my MRP system and bills of materials and to everything into your travel and expenses, into how you're sourcing things, into your basic inventory. And so, it took me a while to come around but it's been, it was a slow journey for me but clearly business spend management is the future of what we look at with procurement. Because for a CPO, it can't just be about saving money or reducing costs. You have to start driving business and you can't drive business if all you do is save money. Exactly, and that's been something that I've learned a lot from in the last week or so alone is how influential a CPO can be. This person can be not just the money saver, it's shareholder value. Bottom line growth of the business. Yes, and one of the things that I really appreciate is Coop has done a great job the last two days of sharing the voice of the customer.  Yeah, and so when you do think about it from their customer's perspective, from our client's perspective at Accenture, this is not easy, right? Some of this, changing the way you do things and changing your overall procurement operating model, it's not easy stuff. There's a reason why there are so many big companies like Accenture that do this kind of work because it's hard and it's needed, right? We come in with a different perspective. Having a platform like Koopa to really initiate that transformation, to be the lever that moves the company from where they were, to where they want to be and where they need to be to be competitive in the market, it makes our job so much easier across the broader supply chain practice to really not just make the change, but we use a big consulting word to instantiate it so that it stays, right? We don't make it better this year. We make it better moving forward. It's an evolution. It is. But that requires the right mindsets to go from a tactical role of managing budgets and things to being strategic, being able to identify fraud detection, for example. Right. Well, and again, I think that's, when they talk about their sweet synergy and the fact that all of these components of the platform, right, they're not separate modules. They hate when we say modules, so it's the T and E module. All of these components, because they are all natively integrated and the data structure is the same on the backend, things like the fraud detection become easy for Koopa, not in other platforms. So having, again, the more things you are doing with Koopa, the more data you have and the more you can get the benefit from the broader ecosystem from the, over $1 trillion in spend that's gone through that's fully classified, coded, detailed. Now all of that spend helps that fraud engine do a better job. The community that you mentioned that they were saying, I think Rob Bernstein, CEO of Koopa said yesterday that since 2016, around the time they went public, it's been a 5x increase in the amount of spend being managed through the Koopa platform. Accenture has over 50 deployments of Koopa in 72 countries. You guys are also managing over 100 billion of that. But this community that they described yesterday so eloquently is very collaborative, allowing not just customers to leverage from other, from peers best practices, but suppliers as well. Talk to us about some of the thing, like the way that they're writing now in terms of this community intelligence and how is it going to help Accenture really be able to help more companies get that visibility and that control of all their spend? Right, so as an example, at Accenture, when you look at the analyst reports, we do very well when it comes to our procurement practice and the spend that we're helping companies manage outside of a platform. So we've got, I think the latest number I saw was like $1.8 trillion that we have helped companies source in the last handful of years. So that is something that gives us a huge competitive advantage. The same thing is true of Koopa and you said how they're writing this wave, honestly, I don't think they're writing the wave yet. I think the wave is still building and they're about to start writing it. I think that what we're going to see over the next one to four years is going to be a fairly significant shift in how that data is going to drive very discreet and concrete value to all the members of the community. Wow, that is exciting. One of the things that we talk about in terms of changes to the CPO's role in CFO are these ways of disruption. One of them is consumerization. And I think Raja talked about that this morning, it was talked about a number of times yesterday. We spoke about it on the program. We're consumers all the time. Whether we're getting up in the morning at a conference and going to buy a coffee at Starbucks or something that we want to order from a vendor like an Amazon, we have this expectation that we can get it or if we want to buy a car, we have all of this data that we've never had before so empowered, but then we go to our work lives. And if we're in whatever role we're in, maybe I'm in marketing and I need to do a trip so I've got to go and do a travel expense. We want the same ease of consumerization. Your thoughts on Coupapay, the expansion of Coupa with Openvine, the AWS marketplace on bringing that consumerization in, do you think like, yes, that's exactly what we need? So the first place of bringing in the consumerization was really how Coupa was engineered years ago. When we go back to before they had release numbers and it was fall of 2007, they had numbers like that. Coupa really did give you an experience that was like Amazon. It was, we used to say, we're gonna bring your shopping experience from Sunday afternoon to your desk Monday morning. And as that happened, now you start to see a different piece and that is a greater uptake in terms of the usage of procurement platforms. So instead of people, it's easier to pick up the phone and call Bill over at my supplier and say, I need a case of whatever. It's actually easier to do it in the platform and I can still give Bill a call and go have a beer with him if I wanna maintain the relationship. But I don't have to make everyone in my transaction start with a phone call that necessitates three additional phone calls later on to check on the status. Instead, I can do it in the platform very quickly. When you expand that out to what now Coupa Pay is gonna offer, especially when we look at our clients that have challenges with multiple financial systems, multiple banks that are processing their payments as you shift it away from that multiple outlet situation and you can move it large, if not all of that, into Coupa Pay, you're streamlining things for dozens, if not scores of people in your company and making it better for them. Some of the stats I saw in the press release about the amount of payment processes that are still manual and still 40% of it by paper check. I got one client that writes 40,000 paper checks a year. How receptive are they to digital transformation? I mean, they almost think it's too good to be true, right? When you talk to clients like that, Fortune 500 companies and when we talk to clients like that and you tell them what you heard from Coupa is true. They're not just selling, you're trying to sell you something. They're telling you how it really works for clients and we've seen it. I look at the last dozen or so clients I've worked with last year and a half, I was doing some analysis, $51 billion, $50.8 billion in revenues is the average for those clients. So big companies, really big companies. And as we look at those, you'd be surprised at how many of them have challenges with a lot of manual processes still. They're the top of their field but they still have those challenges. So bringing this to them and as they are deploying Coupa and seeing what they can realize in terms of efficiencies, it actually makes my job really fun because everybody's going to be happy when we're done. That is win-win. One of the things Rob said yesterday, I said, I know a little bit about Rob and some of his proudest moments are hearing clients articulate success and he goes, one of my favorite things is going into whether it's a $50 billion a year company or not where there's someone, maybe in the state suite that just is skeptical. And he goes and then just takes one champion who sees this vision to convert that person to, oh my gosh, we can have this crystal ball of visibility of everything and really leverage that to drive digital transformation so that the business is faster to identify new products, new revenues, convert customers faster, increase customer lifetime value and the impact there is exponential. Well, and that's one of the reasons why I think our partnership with Coupa is so rich is because Accenture is more a technology company. We're not just focused on accounting. We're not just focused on finance. We have a lot of technology resources. We usually have a lot of connection into the CIO and the IT suite of leadership. They're the ones that are typically the most skeptical. They've been through dozens of rollouts of different things and they've seen them go anywhere from 0% to 50% effective. So because we've got the relationships there and we can have these conversations with CIO and say, this is different. This is going to be a very different kind of program for you and we're coming in and telling you that we can work this together as your partner and be successful and again, you get six months into it and the light's fully on at that point and they're on board. And so in fact, next year we're looking forward to bringing one or two CIOs on stage with us at Inspire 20 to talk about it from an IT perspective. Awesome, well I look forward to hearing that. Jesse, thank you so much for joining me on theCUBE this afternoon. Exciting stuff, control visibility, who doesn't want that? Exactly. It's good times. Excellent, thanks Jesse. Appreciate it. Appreciate being here. For Jesse Hanger, I'm Lisa Martin. You're watching theCUBE from Coupa Inspire 19. Thanks for watching.


Let's wrap up our discussion of mathematics and data science and the data principles and talk about some of the next steps, things that you can do afterwards. Probably the most important thing is you may learn about math a long time ago, but now it's a good time to dig out some of those books and to go over some of the principles that you've used before. The idea here is that a little math can go a long way in data science.  All of those are important in data science, and it's helpful to have at least a working understanding of each. You don't have to know everything, but you do need to understand the principles of your procedures that you select when you're doing your projects. There are two reasons for that very generally speaking. First, you need to know if a procedure will actually answer your question. Does it give you the outcome that you need? Will it give you the insight that you need? Really critical. You need to know what to do when things go wrong. Things don't always work out. Numbers don't add up. You get impossible results or things just aren't responding. You need to know enough about the procedure and enough about the mathematics behind it that you can diagnose the problem and respond appropriately. And to repeat myself once again, no matter what you're working on in data science, no matter what tool you're using, what procedure you're doing, focus on your goal. And in case you can't remember that, your goal is meaning. Your goal is always meaning.


Everybody forced here ripping 20 22 tops diamond icons baseball hobby 1 box number 15 random hit style There's 10 hits in the break sometimes 11 if there is 11 will count will combine two of the lesser hits But 10 spots 10 hits will do the random at the very end after we type in the hits as we go along here Good luck everybody and thank you for joining. Yeah, it's not a good idea Mike First up. We've got a quad diamond show.  Hey, oh, it's honey one of five Love the diamonds and icons man. These boxes are so fire show. Hey, baby big show. We've got a Ronald Acunha junior auto Sweet Acunha icons of the diamond. That's five of five Five of five on that Acunha. I Could not tell that was lower. They're gonna be lower number than the others Maybe he only signed five. Maybe that's what it is Sweet Acunha to five. Good luck on that one too. Good stuff starts this box Yeah, these are really nice SB Acunha mag as well Next up is a Randy Johnson auto 18 of 25 the big unit. Yeah, maybe Mike. I'm not sure again I'm not sure how other platforms work as well, you know, Randy Johnson 18 and 25 Got a relic of some sort here is a patch auto Xander Bogart's 13 or 3 of 25 Excuse me Xander Bogart's patch auto 3 of 25 Red Sox, let's keep them. Let's keep them Next up.  Got a red parallel Ozzy Smith silver ink auto five of five the wizard sweet Ozzy Was it for a reason? Guessing how you do an Ozzy Smith back flip. I for sure couldn't red ink auto Carlton Fisk nine at 25 You don't have to answer I'll answer for you guys Carlton Fisk auto red nine at 25 Team color match of that ink Got a Reggie Jackson auto eight of ten. Mr. October It's almost October actually nice Reggie next up is a Red ink auto Paul Molliter two of ten nice Molliter and on the back low numbered here. Who's it gonna be? It's a Yankee. I see a Yankee helmet Two of five that looks like an a right. Yeah. Yeah, it's a Aaron Aaron judge red ink auto two of five Sick hit there. Oh, that's awesome a Aaron two of five I potential al MVP Out of doing a mag as well Left, let's do the random It's 11 it's always 11 now man, so let's see the the Reigns and The show is big The Randy and the Reigns I think then right? Yeah, Randy Johnson Tim Reigns getting combined It's 11 again man Randy Johnson Tim Reigns going together So we have ten spots or the 11 hits guys We combined the Randy Johnson auto to 25 and the Tim Reigns auto to 25 because the relic was the quad diamond Shohei Otani And that's a big card It seems fair to me All right, you all know the drill We're going to roll the dice random the names and then the hits the same amount of times and put it side by side To see who's got what? 12 times six and six Orange Oreos. I love orange Oreos. It is October now then They're the better Oreos you guys like red from Christmas or orange from a from Halloween. I like orange Good luck 12 times one Two three four five six seven eight nine ten eleven twelve John a down to Bernie s 12 times on the hits now. Good luck everybody one two three four five six seven eight nine ten eleven twelve The Reggie Jackson down to the Ronald Acunia There you go John a with the Reggie Jackson auto Michael K the Shohei Otani quad diamond Christopher H to Ken Griffey Jr. Auto to 25 that one was sick John a the Randy Johnson and Tim Rains Autos there Bernie s the Xander Bogart's patch auto the Aaron judge auto the Carlton Fisk and the Ozzie Smith Joel Joel and with the Paul Molliter and Bernie s the Ronald Acunia. That's gonna do it everybody get the results posted We'll keep moving on here


Hello, beautiful, and welcome back to my channel. Today, what we're gonna be doing is just the usual, just watching people burn their hair. And also, looking at myself on camera right now, I feel like I could not look any different than when I first started this job. Can we get a side-by-side comparison, Marcel? Can you just like edit in a little side-by-side? What happened to me? Am I angsty again? I don't know if I ever lost my teenage angst. I literally look like a little rebel child right now. And I don't mind it. I do like looking emo again. I feel like I'm digressing, I'm getting older, but I'm also trying to be my little teenage self still. Is that how aging works? I guess I'm okay with it. Let me know what you guys think of my look today. And do you like Old Brad or New Brad? Cause Old Brad was a lot. New Brad is even more, but I prefer New Brad. All right, enough about me, cause nobody cares. So today, perms. Some people love them, some people hate them. A lot of people are horrified of them because of bad experiences they had in the 80s. And I feel that a lot of perms were very messy in the 80s and it got really out of control. And a lot of people just got their hair ruined by their hairstylist because you know what? Believe it or not, perms are very, very, very hard to do. Sometimes harder than hair color is to do. So when I see people do it at home, I'm like, dude, okay, one thing doing hair color at home, it's another thing doing perms at home. Perms are literally science, man. And it takes a lot of experience to a really good perm. Experience that I don't even have, okay? It was like a year and a half of education and I still don't know how to do a perfect perm. It seems like an easy process, but I will explain the entire thing as you watch these videos and tell you exactly why it's not as easy as it looks. Okay? But you guys, let me just bore you for one millisecond. You guys have also been asking me to do a giveaway involving Glitterati by X-Mondo, my haircare brand. If you already know what it is, then that is what it is. I have a haircare brand and I'm very excited about it. If you guys like to enter the giveaway, I'm giving away three bottles of Glitterati to anybody worldwide. And all you have to do is follow me on my Instagram, bramondomyc, and follow X-Mondo on Instagram at X-Mondo Hair. Here is the handles, that's what they're called. And then like my most recent picture that has to do with the giveaway, you'll see it. It's the most recent post on my Instagram page. Just give it a like, do whatever you want, comment. And on April 11th, I will be picking three of you to be the winners of Glitterati. So if you guys would like to receive Glitterati for free, possibly, then go enter. It's super easy and fun. Oh my God, giveaways. Yeah, all right, you guys. Let's start watching perm fails. Let's do this. And our first video is by hair manar, hair mananar, at TV. And it is called, I tried to perm my own hair, fail. All right, girl, let's see what happens. At least she put a little bit of thought into this. At least she contacted a few cosmetologists and asked for their advice. I'm a little concerned, however, why those cosmetologists said it was okay. Oh my God, by the way, I totally forgot. Yo, I have a different hair color. I know, I'm sorry. I know a lot of you guys like this bright colored hair. I had a heart attack after doing it. It was cool for like literally an hour and then I hated my life. I didn't really get stared at every second of my life as if I'm getting less stares with this hair color.   Okay, now that I've got that out of the way. Just what I thought. I'm ready for this. Wait, I'm excited. Okay, yo, already, already, she is doing very bad job. So there's no end papers involved with this. End papers, if you don't know, this is what they look like. They're used to keep the ends wrapped while you're perming the hair. And if you don't, you can have a lot of issues with having hooks at the end of your hair or your hair could not properly curl at the bottom. Also, when she's twisting it up the hair rod, you need to make sure all the hair is evenly distributed on the hair rod around some spots. If there's more hair in one spot, the waiting solution is not gonna fully penetrate the entire hair strand. Wow, that's a lot for me. Really bringing back memories. Okay, so definitely, if you're gonna ever try this at home, please don't, but also please don't. So I'm not even gonna say what I was gonna say because I don't even want you to do it at home. I don't, I don't want you to do it at home. I just want you to not. And also, I don't think she's putting a lot of thought to the placement of where she's putting these rods in her hair. We'll just keep watching, I wanna explain later. Acidic, I was told, is the less damaged hair, yeah. Okay, I'm sorry to keep stopping, but another big thing. First of all, I don't really know what kind of perm she's using, but you're supposed to do it on wet hair. I don't know why her hair is dry. I'm 99.9% sure you don't ever do a perm on dry hair. I never have, I never seen anybody do it on wet, on dry hair. That's just not how it works. What is going on, girl? I thought you consulted. What happened to the consultation with the cosmetologist? I'm sorry, so much information in this video. If you don't like information, just don't watch this video. Goodbye. But, if you do want information about this, then keep watching, because I'm gonna keep stopping it every five seconds, and I'm gonna talk a lot. This frizziness, whatever it looks like on the rod, like if it looks nice and pretty and smooth and clean, that's usually how it's gonna come out, pretty nice, smooth and clean. If it's not smooth and clean and perfect, you're gonna get some frizzy, frizzy, frizzy curls. Like it's gonna be really bad. Like you're gonna end up perming frizz into your hair. So that's really just a bad idea, okay. All right, stopping it again. We're talking about types of perms, okay. This is gonna be a very informational video. So this is where it gets really complicated. It's been a minute. Really gonna try my best to give you the most accurate, perfect information possible. I did research before this video to make sure most of the things that I know are correct. We have acidic perming solutions. We have alkaline perming solutions. And we have exothermic perming solutions. Bam, we got those three, all right. We're gonna go through them real quick. Acidic perming solutions are generally the most gentle perming solutions at a pH value of six to seven. Normal hair strand pH is a five. So if you're pushing it beyond that, it's gonna be a little more harsh. So if you're pushing it to seven, pushing it a little bit. But it definitely goes up higher than that with alkaline perms. So acidic perming solutions are made with glycerol monothioglaculate. My cosmetology teacher would be so proud of me right now. Basically, an acid perm is not gonna break as many bonds as the other perms would. Which is gonna be good for people who have previously colored their hair or have dry hair or have a little bit of damage in their hair. But I would really not recommend you do any kind of perm if your hair is severely dry. It's not gonna look good. If your hair's healthy too, moderately dry, you've colored it once or twice. It's not bleach blonde or anything. You could probably do it, but otherwise I would not recommend it. Like I could not do it on my hair. My hair would be so damaged. Okay, almost an alkaline perm has an approximate pH value of 9.5. So it is definitely bringing up that pH very high. This should not be used on people who have dry hair or have previously colored hair. This is for people who have virgin hair, very healthy, healthy hair, who need more bonds broken in the process in order to achieve the wave. In this perm solution, we use ammonium thioglaculate, which is more harsh, of course, than an acid perm. Then again, like I said, this is best for normal, healthy, or resistant hair. So if your hair's super thick, super healthy, this will be the perm for you. And lastly, we have exothermic perming solutions, which are self-heated perming solutions, which can be either acidic or alkaline. And I'm not even gonna get into that because it's a whole other thing, but it's complicated. A lot of information. So she is using an acid perm, which I would recommend for her. So I don't know why she's saying that's wrong because she has previously colored hair. Her hair looks a little dry. Usually blonde hair is. So acid perm would be good for her. And an exothermic one would be best, but I don't know what she's using. She didn't really say what she's using. It's telling me now to dump every single item out. Yo, she literally braided the top of her hair. I have never tried to do a perm with braids. That seems a little risky and inconsistent. Look at that. Okay, I don't want to be straight up with you. But it's still bad. You guys, I'm telling you, there are so many steps and it is so hard to do. Even for somebody who's trained to do it that like doing it at home is just like crazy to me. It's a lot of time, a lot of effort. If you don't rinse the hair for the recommended amount of time after you use the perm solution, after you use a neutralizer, it's not going to work. Like you really cannot do that at home. Like it doesn't work like that. Oh, and this poor baby, oh God, her hair. It looks boy feel for you. Babe, just do a chop, just do a chops. That would not happen. Okay, this is another misconception with perms. Ooh, it is an education day on the Brad Amando YouTube channel. Perms, you're never ever gonna get a wave like this. These beach waves, this is not what a perm's gonna do. Perm is gonna give you a natural looking wave. You're still gonna have to style it.  Nope, you can do a beach wave perm.  It is not a thing. It's not gonna happen for you. It is just, that's not how it works. So, cut it. Cut it, I cut it short. Oh my God, I'm so excited. She's gonna feel like it's so much thicker and it's gonna feel amazing. Oh, listen, it looked good long too. It looks cute though. Like she needed the chop. It looks very cute. I'm so happy for you. I love it. At least you got a haircut. I think you needed it. The perm, don't ever do it at home again, girl. Don't even touch the box. Put it away, throw it away. Don't ever look at it again. Don't ever do a perm again. And if you are thinking about doing a perm, don't ever touch that thing. But at least after today, you'll have a little bit more knowledge about how to do a proper one. So, one more video today. We're gonna watch it and we're gonna do it. And this is by Clevver Style. Joe, thanks for coming back on the show. Oh, we're doing a guide. Wait, there's literally a box that's called home perm. That is probably worse than the boxes that say at home ombre. At home perm, there is literally no way of doing it well, unless you've had experience. Yeah, please don't do it at home. My God, they're literally using a bow. No clarifying shampoo, nothing. They're just going right in. What is this?    Somebody tell me. I have no comment. You know what that was? Okay, so they're doing a very tight curl, which is gonna be amazing for him. I'm very excited. This is offensive. Yes! It is so hard, man.  Like, perming solution of getting your eyes, you can go blind. They're just like, let's make them blind. Okay, here's another thing. More education today. So, also, you can leave it up to 45 minutes, I said, but you should be checking the hair strand every 10 minutes or so. Just be super anal about it. You can check it, unraveling it very gently and checking the wave pattern to see if it's there, and then putting the rod back in and adding more perm solution to it.  But you should be checking it every 10 minutes. And that is the way you know if it's done or not. You probably need like 15 minutes on his hair or 20 because his hair is already lightened, like he said before, and she doesn't need all that time. Definitely don't do 40 minutes. Please tell me they didn't do 45 minutes. Just have to check the first curl. Oh, just have to check it. See, they're not gonna know what a good curl looks like. You need to get the solution out, not, no. It's all wrong. It's all wrong. We can stop. Poor guy. Oh, oh God. Oh, please don't rub it. Please don't ever. But now once we're done, we're done. Oh no. The hair is still setting in place. You can't rub your hair after doing a perm. No, you have to be so gentle with it because your hair is still setting into place. Let me do a quick explanation. When the waving solution is applied, it swells the cuticle and the perm solution enters the cortex of the hair and then basically a bunch of chemical stuff happens inside the hair strand and it forms to whatever the hair is placed on. So if it's on a round surface, it's gonna form a curl.  You feel me on that one? And then the bonds are rejoined together in their new position to form the curl. And that is an explanation of how a perm works for idiots. Okay, great. Oh, stop roughing it up. Damn. Literally ramen noodles. I'm so scared.  Moral of the story today, guys.    So just do your research. That's with everything now. Like just do your research. Don't forget to, you know, enter my giveaway because it'll be fun to enter and it'll be fun to win one. Thank you guys so much for watching today.  And I will see you all next time. Peace.


With non-communicable diseases accounting for 74% of all deaths worldwide, the National Agency for Food and Drug Administration and Control, NAVDAC, has scaled up efforts towards the elimination of trans-fatty acid TFA's from food supplies in Nigeria. NAVDAC Director-General Prof. Mojisola Adeye lamented that more than 36 million people could die annually from NCDs adding that cardiovascular diseases are the number one cause of death accounting for 17.5 million deaths annually. The report There have been several campaigns with the use of unhealthy oil due to its harmful effect on people. Most of these products are reported containing high level of cholesterol which increases the risk of cardiovascular diseases leading to many deaths. To this end, the National Agency for Food and Drug Administration and Control, NAVDAC, has expressed optimism that Nigerians will enjoy better food quality and health following the recent gazette of the reviewed fat oil and food containing fat and oil regulation 2022 and the prepackaged food labelling regulation 2022. NAVDAC Director-General Prof. Mojisola Adeye disclosed this at a press briefing jointly organized by the agency and the Corporate Accountability and Public Participation Africa, KAPA. Prof. Adeye noted that deaths attributable to trans-fatty acid in Nigerian foods leading to heart disease, stroke, cancer, diabetes and chronic lung disease among others will now reduce drastically. We have reviewed the fat and oil regulation and we have a newly gazetted regulation known as fat, oil and food containing fat and oil regulation 2022. This regulation has addressed the second pathway for the elimination of industrially made trans-fatty acids with the limit of not more than 2% in all foods. In addition, the prepackaged food labelling regulation 2005 has also been reviewed to take place of the labelling requirements for trans-fat acids as we now have a reviewed and gazetted prepackaged food labelling regulation. She also revealed that NAVDAC is already working with the industry and partners to find alternative source to the existing partially hydrogenated oils that are the source of industrially produced trans-fatty acids. In a speech, Akibode Uluwafemi, executive director of Corporate Accountability and Public Participation Africa said the media must continue to play a key role in educating the public on the content. It's going from not mandatory little information to more information. You can now see what is the content of saturated fats, what is the content of non-saturated fats because of what?   If you eat too much saturated fats, it can start blocking the lining of blood vessels and once that lining starts decreasing, getting narrowed, the space rather, start getting narrowed, then blood pressure and with that sometimes with diabetes and so on cardiovascular diseases we start showing up. And so what NAVDAC is doing is making sure we are safeguarding the health of the nation by now having a labeling that an informed consumer can really understand and check and see. From the part of the ministry, there may be an overarching policy that is following that will come up with it. We are also reviewing the national safety, food safety and quality policy which have incorporated this regulation to be part of it and it will soon be launched as well so that the health of Nigerians will be perfectly taken into consideration. These are shown us that civil society can strongly partner with government to achieve a lot in this country. And when I mean a lot, I also speak to what concerns your ministry which is the areas of food policy. You mentioned sugar, you mentioned salt and every other things that we consume that we are ready as an organization to continue to partner with KAPA on all these areas and ensure that necessary policies and emergency regulations that will save Nigerians, I mean save Nigerians public health are all in place. I think these regulations are well implemented and we stop having the wrong oils for the populace to use. The populace will be protected without them even knowing that they are even changing their lifestyles. So that's a wonderful thing that has happened with the coming to place of this regulation. The fats, oil and food containing fats and oil regulation 2022 includes provisions on the scope of application, source of edible fats and oils, vitamin A fortification, additives and impurities. It also covers labeling of fats and oils products, labeling limits and claims for trans fats and cholesterol and penalties among others.


What's up everybody? Jason here for jazby's case brace comm 2021 tops diamond icons baseball just sold out with this random number block picker to number 26 This includes the angels Baltimore Orioles Chicago Cubs Cleveland Indians New York Mets Oakland A's Pittsburgh Pirates and Texas Rangers and again guys these teams will not be part of the hit list promo But of course good luck to you guys getting a hit here for the fraction of the price So again first we'll randomize customer names and the numbers and we go by left side of the serial number left side first number And there's your example right there in case It'll be a refresher there. Of course any redemptions will go to spot zero You know, so one-on-one just don't go to spot zero then any non numbered cards are randomized to the group So here you go. Here's the dice roller. Here's the customer names PJ Daniel zero through nine roll Three and one four times one two three Daniel last one mode at the top down at Diane four times one two three four four times four times one down to six So Daniel spot one any one-on-ones also spot nine PJ was spot eight Diana was spot seven Daniel any redemptions for these teams will be yours PJ with five and four Chris with two Daniel with three Diane with six so again guys This was just the first RMB randomized. I need to do one more and then we'll start the break in a separate video. Appreciate you guys


I started on this journey and my son is almost 10 and it started off with a lot of medical intervention. Uh, we went through a lot of therapies that were not neurodiversity affirming and I think back to that experience and, you know, even something like occupational therapy, which is a wonderful resource, but thinking back to what he experienced as a toddler with like exposure therapy and we now know that that is not a safe practice. It doesn't get them used to it, it just makes them mask their pain. There was a lot of learning and I think that that's what's hard for with a newly diagnosed autistic child.