Hello and welcome to the International Daily Roundup by People's Dispatch where we bring you major news developments from around the world. Our headlines. Further arrests made the assassination of General Moise amidst the crisis in Haiti, several arrested police cracked down on homeless encampments in Canada, reporters without borders, demands halt on Pegasus spyware exports, and in our video section we take a look at the summer Olympics in Japan where there are growing calls for cancellation. In our first story, we go to Haiti where investigations into the killing of de facto President General Moise are ongoing. Authorities have stated that 26 suspects have been detained so far, including 18 former Colombian soldiers, three Haitian police officers have also been detained alongside at least two Haitian Americans. Among them is Pastor and Dr. Christian Emmanuel Sinon who has been named as by officials as the alleged mastermind. Police Chief Leon Charles stated on July 14 that Moise's assassination had been planned by the Dominican Republic. He showed a photo of Sinon with the director of the US-based company CETU Security and the head of the Council of Worldwide Capital Lending Group. These two firms have been accused of financing and planning Moise's assassination. Meanwhile, a wanted notice has also been issued against Senators and Moise Critics, John Joel Joseph. With several key details of the assassination still unclear, people in Haiti have raised several questions. These are related to the role of the police in leading the investigation. Moreover, as reported by AP, no one from the President's security detail was injured. Haiti is also witnessing a political crisis in the absence of a parliament. With regular constitutional norms not in place, Moise appointed Ariel Henry took over as Prime Minister on July 19. He has replaced Claude Joseph who is taken over as the head of state after Moise's assassination. Meanwhile, the people of Haiti continue to face violence and insecurity. The country has been witnessing a surge in kidnappings and attacks by armed groups. Local media reported that 10 people were abducted from a bus headed to Port-au-Prince on July 15. The attack was carried out by a group of armed individuals and the driver stated that the passage's belongings were robbed. 7 of the abducted people were later released. Fighting between armed groups in Port-au-Prince is estimated to have displaced over 10,000 people in June. A radio channel has also reported several fewer shortages in the country with long lines at gas stations. Several civil society groups are now coming together to find possible solutions to the ongoing crisis. In our next story, several people were injured after police violently evicted a homeless encampment in Canada. Located in the city of Toronto, several unhoused people had been living in the Lamport Stadium Park for weeks. Local organizers reported that hundreds of people had gathered to protect the camp on July 21. However, on orders of the city government, police broke through the fences and barricades. The standoff between the protesters and the police reportedly lasted around 8 hours. According to the encampment support network Toronto, 26 people were arrested by the day's end. They are facing charges including obstruction in assaulting police officers and trespassing. In an official press release, city officials stated that 30 structures had been removed from Lamport Stadium. It further stated that two people had accepted referrals to a shelter in the hotel and five were already in the shelter system. The release also stated that three people left and one person refused permanent housing. Wednesday's events at Lamport Stadium followed similar violent eviction of 26 people from Alexandra Park. As per an official statement, 68 structures were removed from the area on July 20. Toronto city officials have issued four trespassing notices to encampments citing COVID-19 risks. While officials have stated that indoor housing has been offered, unhoused people have been exiting shelters over the past few months. This is due to several factors such as increased and random check-ins and strict restrictions on movement and amount of belongings. Moreover, the insecurity of the accommodation also leads to people ending up back on the streets. Activists have now increased calls for more sustainable and affordable forms of housing. We are now next going to talk about the Pegasus scandal where reporters without borders have remanded that Israel stopped the export of the spyware. This follows revelations made this week by 17 media organizations as part of Pegasus Project. Findings are shown that the spyware developed by the Israeli NSO group was used to target journalists, activists and lawyers. A list of 50,000 phone numbers has been found in a massive database, so 1,000 people across more than 50 countries have been identified so far. The presence of spyware has been confirmed in 37 instruments. Nearly 200 journalists and editors working in news agencies including Reuters, The New York Times and the YR were targeted. Moreover, 14 heads of state including 3 presidents, 10 prime ministers and a king also featured in the list. These include French president Emmanuel Macron, Iraq's Barham Saleh and South Africa's Cyril Ramfosa. The prime ministers of Pakistan, Egypt and Morocco were also targeted and may have been targeted for spying. The numbers of at least 50 people linked to Mexican president Andrell Manuel Lopez Obrador were also found on the list. The NSO group has stated that Pegasus is so exclusively to government agencies to fight terrorism and crime. As reported by the Guardian, the company is closely regulated by the Israeli Defense Minister. Reporters without borders has argued that Israel is using NSO exports as a supplement to its foreign policy. The organization has demanded a halt on the sale of spyware until the regulatory framework is established. That's all we have time for today, we will be back tomorrow with more news from around the world. Until then, keep watching People's Patch.


We're introducing how to pin task templates in lists. Get everyone on the same page by pinning up to 20 task templates to a list so everyone who accesses the list can quickly create tasks in a consistent format. You could even set a default template for each list so your team knows exactly which template to use in every scenario.


U.S. urges Zelensky to focus on fighting corruption, U.S. Secretary-General Janet Yellen has called on Ukrainian President Volodymyr Zelensky to focus on fighting corruption and strengthening public administration. Yellen stressed that the U.S. will continue to provide economic support to Kyiv and welcomed the Ukrainian authorities' focus on fighting corruption and strengthening accountability and good governance. Continuing to address these difficult issues will be key to delivering the future that Ukrainians deserve, Yellen said. She stated that Ukraine's economic team has developed the right policies and achieved significant results in a difficult situation, referring to Kyiv's implementation of the IMF's $15.6 billion loan program. She added that the IMF program has been key to ensuring macroeconomic stability and advancing reforms, stressing that continued work on these reforms would be essential for the country's recovery. Earlier, CNN reported that the United States had urged Ukraine in recent weeks to make more efforts to fight government corruption, linking them to further non-military support, including through a note diplomatique. Prior to that, the U.S. sent a list of priority reforms to Kyiv and international donors for consideration, which it proposes to use as a guide in decisions on assistance to Ukraine.


Helen is the UQ Project Manager of Scholarly Communication and Repository Service. Today Helen will talk about data publishing at UQ. Helen, over to you. Hi, good afternoon everyone. I was really pleased when Natasha got me to talk about data publishing because here at UQ Library we've been trying to build a bit of a solution around that and particularly for the long tail of research data here at UQ. So I have said it specifically about data publishing at UQ Library because I'm very aware there are some groups around UQ doing some fabulous work in this space but I will focus very much on what we're doing here in the repository. And so thinking about data publishing really raises questions of why we're going to do it, how we're going to do it, how our research is going to gain credit for the data that they've produced and particularly how they're going to gain credit separate from and in addition to the analysis of this data in publications. So what we're really trying to look at is really how we can build those meaningful connections between publishing the data and publishing the scholarly work. It's actually my favorite part of the data lifecycle, data publishing because it can be both the beginning and the end. So it might be that you're tidying up your data at the end of a project and looking to archive it. But if you go one step beyond that, I do archiving your work and you really start looking at depositing your data or publishing it and you really are giving sort of the start of another project.  So there's been talk for a while now about making data a first-class scientific output. Here in this paper from 2012, they discussed achieving that through formalizing the methods for citation and publication and thereby incentivizing data sharing. I think that's really important when we go around talking to researchers here at UQ is to really make sure that they're understanding that the incentives behind sharing data, if we talk about the data with them about being a primary research output, that really starts to click with them and they start to understand more often where we're coming from. Crucially, a point of difference which we talk about with researchers is around archiving data versus publishing data. So if when you archive your research data, that can be obviously very beneficial in terms of preserving the data. But when you publish it, it allows for things like validation and peer review of the data which really enhances science as a whole. So we're going to researchers talking to them about not only the academic credit that they'll get but also about that the results of their work will be verified by others that they'll be able to expose their data to decide a peer review which to some of them can be quite scary especially when we're talking again because that's that long tail of research data who perhaps aren't as familiar with this idea as data sharing is on this. But we're really trying to provide a mechanism to ensure the quality of data sets available. So at UQ, what do researchers want when we go out and talk to them? What is it that we're saying that they want? They would like, I think, research data archiving somewhere to preserve their research data a way of sharing it, a way to publish their research data in a way that treats it as a primary research output and that's crucial I think as to why we've implemented the data publishing infrastructure here in our institutional repository. We very much wanted researchers to feel that they were going through that process of publication in a simple way as they would with their other scholarly work. And we do talk to them about peer review and verifiable results making sure their results are validated and reproducible and the idea of getting academic credit. But I'm just putting all these words in their mouth. I'm not sure do researchers really know that they want that? So when we go out and talk to people, we've done a lot of work in this area and we're very lucky here in the library to have a team of librarians who work in research output services as well as that client service liaison librarians. So we're able to go out and talk to researchers about what they actually do want. So we did a couple of things. We've continually evaluated our data management service since 2014 as well as collected user stories from people. So they tell us that the largest ever data sets they work with perhaps aren't that big. You know we are really trying to provide this facility here for people who don't have other options who aren't working in these big areas which perhaps provide these nice fancy work clothes for them. So they're telling us they're not working with huge data sets but that they have many different types of data. That their storage locations for archive data are a little concerning that they will store it on their external hard drive or on their computer. So we know they want to preserve their data and they want to save it into the future but perhaps they're not sure about how to do that. We know that 53% of them wanted to keep their data permanently. So the idea of data archiving isn't something that they're adverse to. They're happy to keep their data permanently but it's taking that next step and actually publishing their data, sharing their data that perhaps they're trying to facilitate. So these are some of the real user stories, real researchers said these aren't things I've made up and that they want to store their research data in such a way that others can cite it. That seems to be really important that they get credit for their work but they need access to institutional repository storage solutions for their data as required by the journals they intend to publish in. So we did a bit of an environmental scan recently where we looked at for the past five years everything that UQ has published we analyzed those publications by journal and by funder and then one of our data librarians went and dug out for the top 25 journals by productivity so by sheer number of publications at UQ and also by an overall time cited so you can say by an overall total number of sites for papers in certain journals. So we got two lists of top 25 journals, one for productivity and one for overall time cited. What we found were those policies for those journals and only 7 out of 25 in terms of sheer weight of numbers required data sharing, still a lot 7 out of 25 but in the highly cited or you know journal list of the 25, 18 out of the 25 had a data sharing policy in place. So we know that UQ researchers are publishing in journals a huge number of which 18 out of 25 which are requiring them to share their data. So this researcher here isn't unusual and the most frequent phone call we're getting at the moment in the team is people who are trying to publish their research data in a journal that's requiring them to deposit their data somewhere and they're looking for a solution to that problem. They also would like stats on who downloads their data so that's a little bit more difficult to work through for them but they are interested in who's looking at their data. This researcher said they needed to be able to securely store their sensitive data but also share it with other researchers and collaborators. So we knew that we had to build infrastructure that made sense to people who had data that perhaps needed to be mediated access. This person would need to be able to permanently store their research data in a way that was open and accessible in order to meet the requirements of a funding agency. So as well as analyzing UQ's research output by journal requirements we did the same for funding agency requirements. We looked at all the funding agencies named on UQ research outputs in the last five years and we found that there are multiple funding agencies that are putting this pressure on to researchers to make sure that their data is open and accessible. That's both Australian ones as well as international ones named on UQ research publications. We knew that they wanted to store and accommodate all the research data along with everything that goes with it. So they need facilities to apply data dictionaries, metadata, lab notebooks so that it can be used by researchers in the future. So these are all really great user stories to come from our researchers. These are really good use cases that we're able to accommodate using our institutional repository. And I do think that over the years that we've been here and talking to researchers very much the conversation is starting to change and we really are changing that terminology now. So people are beginning to start to talk to us about data publication instead of data sharing. The conversation is really I think the start of a culture change here at UQ which is I think very good to see. And the idea that researchers should share data to advance knowledge and promote the common good is quite an old idea but in recent years we're really seeing a lot of enthusiasm from them. I think because people are starting to look at how they can get that academic credit and how it can lead to very much a conversation around research integrity and an audit trail from raw to published data but then also from the published data to the publication. And I think that's where you get very strong trustability. And this is what we're working towards is really the idea that data is deposited alongside at the same time as publication of any scholarly output. So at a time that UQ researcher is publishing a paper that we give them an easy workflow and a trusted system for them to deposit the data that goes along with that publication and link the two things together. And really by integrating the data publishing with the other publishing we're giving them real credibility, trustability. So it says here in this paper, the relationship is best accomplished in systems and repositories where the custodian has trusted status within their relevant communities. And again I think that's why it fits really well in the repository and really well with the library. But it also requires robust infrastructure that's quick and simple to use and we first implemented the form which I will show you very shortly in our repository a couple of years ago and it has come through a number of iterations where we've tried to make it very user centric and very straightforward for researchers to use we do want them to do it, we want them to deposit the data, we want them to describe it. And so we're trying to make it so that they can use it and be confident that it's a straightforward workflow. So if it's going to become part of normal scientific practice it really does have to be easy to achieve. So when researchers come and talk to us about publishing their research data we will quite often talk to them about if there's a discipline specific repository because I do feel that those are very relevant to certain researchers and we talked to them about instead of archiving their data on their external hard drive perhaps go and use a specific repository like that or we tell them also about UQE space. So the fact that they can actually describe their research data in UQE space we talked to them about the idea that data that underpin a journal article should be made concurrently available and we talked to them about the fact that we can link that data metadata record with their publication metadata record. They can be shown to be related objects and I think that really just they start to really understand the value behind what we're trying to achieve here. We make it discoverable so we obviously send all our research data metadata up through to Research Data Australia and then we also send that through to the data citation index so we're able to track citations of their data sets through that which has been really a key thing I think for people to really comprehend the impact that this can have, which is really good. So I'll show you a little bit more about how, but we have this need some extra help, email data at library so we have a generic email address there which comes through to the team here in the library. We're very lucky to have some very skilled and specialist data librarians working here. We have I suppose it's a relatively small team but a very dedicated team that work very hard to process these records as they come through and to really have those conversations with researchers articulating clearly the relevant funder and journal requirements that they can use the institutional repository that it's known, that it's trusted that it can integrate with that other publication workflows and link to that other related publications or data sets. We try and really keep it very research-centric and build them a profile of their data sets. We can give them DOIs for the data sets. We show them how to license the data set. We show them how to cite it and how they should be showing other people how to cite their data correctly. We still find a lot of people just either acknowledge a data set or mention it somewhere in the paper so we're really trying to push them out to proper citation. And then we can do things like if their data is actually stored in a trusted subject specifically repository, we can link out to that or they can upload their data if it's a fairly small data set. They can choose mediated access to their data or they can choose open access so they can actually link to it or upload it or they can just have a contact person so that people that wear the data set exist but they would like to mediate the access to that. And we can also add an embargo period if required. So if somebody comes to us and says they need six months, twelve months and buy a period on the data set, we can facilitate that as well. So this is what UQE space looks like, the home page. And when you log in, you go into my UQE space. You'll notice here you can see my UPO options. That's something that Elliot and admin can see. So a researcher starts with the tabs, my research, possibly my research, admissing publication. Then they have two more options, my research data and admissing research data. And I really think by having the data sets up there in that prominent along with the publications gives the right message. It gives the status of research data as a primary research output. So they know they're getting the list of my research publications. They know they can claim publications that might possibly be theirs and the system will present those to them. But they can add publications if they think we're missing them but that they can also get a list of their research data, which it looks like this. The data sets below are currently attributed to you and people really like this page. But then they can also go to admissing research data set and this is what they get. It's a fairly simple form and like I said, we've gone through a couple of different iterations and we are actually looking to redesign all the forms in each space at which point it will get a bit of a facelift but I think we're pretty happy with the fields that we've got in there at the moment. So the citizen goes in. They add a simple amount of metadata, not too much. All the mandatory fields are up top so they can fill those in and get a lot of that done very quickly. They go through and they can add access conditions. So this is where they'll tell us if they'd like to be open access or mediate access. And this is where they'll pick a license in terms of access for the data set, which we talked to them about in great detail because obviously if you're making your data available online, you need to make sure that you're releasing it under conditions that you feel comfortable with and they'll also allow for reuse. So we talked to them about what the different restrictions on the different licenses mean. We talked to them about copyright and whether or not copyright exists in their data. If copyright doesn't exist in their data, which quite happens the case in Australia, we talked to them about UQ terms and conditions, which is a very simple thing that says, you're very welcome to use my data. Do anything you want with it but I'd like you to attribute me. So we talked about various options around licensing in terms of access just to make sure that they're feeling comfortable. I think for some people it's quite a new idea that they're just going to put their data out there online or publish their data online. Then we go through various things. They can upload their work. They can add links to the location of data if it's for in Pangea or Dryaddon with their repository, for example. And then they tick a little deposit agreement that says they're the creator or the co-creator, that they're authorized to deposit it. They've got permission to include any third party content that it's original, doesn't infringe any legal rights. And that by depositing it, they're granting UQE space a license to reproduce it and make it available. And that the data creators' moral rights to be associated will be respected by UQE space. And then before the record's published, it's checked by one of our specialist research output librarians. So every record that comes through, every time a researcher says Admission Data Collection, they fill through the metadata. It doesn't go automatically published online. It comes through to our team. We check very carefully through the record and we quite often will contact the researcher and speak to them about the metadata that they provided and make sure that it's a rich resource because I do feel if you're publishing data, the metadata you provide around it is very important. And to make sure that that data and metadata are consistently high standard would be certainly a thing that we have here at UQE Library. So then you end up with a final record. This is a record from the E-FISH Genomic Database repository. They're a great group here at UQE. They analyze all these amazing fish and sharks and they get all the genomic information of which they say they use roughly about 3% of the information that they collect and then they're very happy to make the full amount of information available online. And you can see here we've got the file actually attached there so people can just download it. And we also have a link through to the full text publication. So we're making sure that you've got that trail from the dataset to the publication and also to any other related publications or datasets. I do think that's the main thing here by popping all this information directly into their institutional repository. It's really giving us that advantage and that integration with other aspects of publishing which is where you're going to get the credibility I think with researchers. This is the second half of the record. You can see they pick their creative commons attribution but non-commercial license. It tells you about type of data. All very standard metadata but enough for you to go off if you're going to try and discover the dataset. So in the future here at UQE Library some of the plans that we have is to centre around creating more of this research-centric data management infrastructure. So we have a couple of different projects on the go at the moment funded by the enhancing systems and services and suites of projects. I guess you would call them here at UQE. They are trying very much to provide this umbrella and university-wide infrastructure that's really going to help researchers sort out their workflows and that includes management and use of the data from the DMP all the way through to storage, preservation and reuse. So we expect this will tie in very closely with the existing information that we have in eSpace. We know from our user research that research has required that easy-to-use infrastructure that's available to them at no cost and that allows for best practice work with but with minimum administrative intervention. So we're not trying to give them an administrative task to do but we're trying almost like John said to be collecting that metadata earlier in the process so that by the time it comes to the end of publishing they're not having to remember everything that they've already got quite a well-established set of metadata by that point. So currently at the UQE library we do have a DMP online tool. There's no flaw in a metadata from that into the repository and there's no links to storage provisioning. There's no links to published record metadata. However, we are well positioned to capture that information in eSpace because we know we've got the infrastructure I've shown you now. We've got that complementary projects around data sharing. We know we can do the licensing, DOI. We can send it through to RDA. We can send it through to DCI. So we know we're in a good position to do this. We've done an awful lot of brainstorming and I like the little bit there on the wall that says can do. We know we can do this. There's also one that says it's my data. I'm not publishing it but I don't believe that one. So we really are going to work towards thinking about having an idea of project level minimum viable metadata which can be fleshed out into a DMP which can have other information added to it. We really are at UQE trying to look across a huge number of different disciplines and they all require something slightly different and a few of them have different ideas as to what data publishing even is. So by keeping this idea of minimum viable metadata at the project level we're keeping it very simple. That allows, I think, as wide as we can possibly get at UQE coverage. We're not trying to go for everyone. I said at the beginning there are people at UQE doing this really well without us so we're not trying to over arching trying to get onto all of those people but for the people that don't have working systems the new system will allow research project level metadata captured in a DMP to cascade the data lifecycle automatically provision data storage and then we can use that information to publish one or more data dataset metadata records linking back to the original data and also linking forward to a set of publications that came from that project level and data collection. So I think that's a really good situation to be getting into and certainly that's the vision although I think it would be not coming probably I'm going to say 12 months but it's certainly the direction that we're heading in and I've got a quote here from Vincent Smith who says the power of published data is amplified by ingenuity through applications and uses unimagined by the original and distant from the original field without connecting these disparate datasets the true potential of data reuse and repurposing is lost and that's from his paper on data publication towards a database of everything in which he has the idea that perhaps we can I want to say co-iculate everything into one large huge database that can be queried and solve all kinds of interesting problems so I really do think that publishing data is something worth investing a lot of infrastructure a lot of thought, a lot of infrastructure into and something we're very excited to be part of here at the library today. Thanks Helen we look forward to hearing more from you in one year's time but for now Susanna let's move to the question time any questions? Yes there is one there is it possible that UQ can share the list of journals that require data publishing I'm about to start working this out for the journals that I see you publishing and it would be great to have a central repository for this information Yes I'm very happy to share that information, we did look very specifically at UQ's publications of many and then slice the data just everywhere we've been publishing but I'd imagine it would be very similar across the university so I'm very happy to share that information That sounds fantastic So what software are you using is the question? We use it's an in-house it's just what's used to build our institute for repository so I do believe it's all open source and online but yeah it's all the in-house development stuff Apart from the DMP online which is an implementation of the DCCs DMP online from the UK Obviously you're welcome with your brilliance there Alan That's all the questions we have for the moment Perfect, thanks everyone Thanks for your time Thank you


Florida, it's theCUBE, covering Sapphire Now. Headlines sponsored by SAP HANA Cloud, the leader in platform as a service. With support from Consolink, the cloud internet company. Now here's your host, Peter Burris. Welcome back to SAP Sapphire. My name is Peter Burris. We're part of theCUBE and we're bringing you the signal from the noise here at Sapphire and I've got a great guest, an absolutely fantastic guest. Akash Agarwal who runs the mobility at SAP, but specifically you own that crucial Apple relationship that everybody's talking about here in the show floor. So we're going to get a chance to talk about the Apple relationship. Why don't you tell us a little bit about what you do first? Yeah, so I've been at SAP for a few years. I came in from a mobile startup. Focus here at SAP is to take our great products into our customer base and new customers and help them with the mobile journey. And mobility as you know is front and center of any digital transformation message that's out there. And SAP is helping take our customers and the solutions that we have and make them more digestible, consumable on mobile. Digestible, consumable on mobile. Sounds like Apple. So one of the most important things we've heard this week is we heard new relationships with Microsoft and some others, but a lot of the buzz has been about this Apple relationship. Tell us a little bit about it. Yeah, so the Apple announcement was in my humble opinion, one of the biggest announcements that happened in the history of SAP. And it's an iconic company. It was two icons that got together. And I think the partnership was about 20 months in the making behind the scenes. 20 months. Yes, I mean it takes a long time to get two large companies to work together. But the output and the end result, I think was fantastic. As you saw, it was a very big announcement. And Bill McDermott quoted on Monday that we got something in the order of four billion press hits between when the announcement was done and the Friday. So the announcement was done on a Thursday, Thursday and Friday of last week. We were just swamped by the media covering this announcement. And I think the most powerful thing about this announcement is it's two great technologies, two great solutions coming together. SAP bringing their leadership in the enterprise space and Apple bringing their beautiful iOS platform. And basically the output of that should benefit our customers, our partners, and the whole world. Make it run better, run simple, and run beautiful. Well, I was actually going to say, taking all those things, but you kind of mentioned it. Also taking Apple's customers and SAP's customers, which are sometimes very difficult to separate when you think about how many employees are under management of SAP software, 300,000 corporations on a global basis. What should we expect to be some of the first milestone outcomes of this partnership? So the first few things that you're going to start to see, they have a big presence here at Sapphire as well. But some of the big things that you're going to see out of this partnership is a new way, a next generation of applications. Apple is bringing their design expertise, they're bringing their expertise of beautiful UI, coupling it with our design concepts from Fury, and helping us build beautiful and magical output that will manifest itself in native iOS applications. And these applications are going to be centered around four major industries in the next six to 12 months. They're in the retail industry, they're in the asset maintenance industry, in the service industry with an application around project management, and last but not least, in the healthcare industry. You heard big announcements today from Steve Singh on the Connected Health platform, and we want to create next generation applications that help you interact with your doctor, help you interact with your own health, so you can capture all the post medical output that you've gotten, and then interact with that using beautiful iOS applications. So those are some of the components that you'll see, and we're also building an SDK, which is the best of our HANA Cloud platform, the best of iOS, coupled that together into an SDK that you can take out into the ecosystem from which they can develop net new applications. So that's really important, so it's not just a partnership that allows SAP to evolve its platform for mobile, it's also an SDK that allows SAP's ecosystem to evolve its platform in the context of how Apple has shown us mobile works. Absolutely, I mean 90% of this show floor is SAP ecosystem. So every single partner can benefit from this partnership. People who build solutions on SAP, people who extend solutions, and people who help integrate and implement solutions, they can all benefit from this partnership. That's one, number two, we have 2.5 million developers right now in our HANA Cloud platform, immediately all those developers will have access to this SDK from which they can build out beautiful iOS experiences. So that's one set of the ecosystem, then the other set of the ecosystem is there are 11 million Apple developers out there that have been primarily focused on building consumer applications, and now they will have an opportunity to build applications in and around the SAP ecosystem. SAP has been traditionally a difficult platform to build around, and now with this partnership, with this SDK, those developers can build native rich experiences in the industry, in verticals, in horizontals that are leveraging mobility. So it opens up a huge gamut of possibilities for both us and for the developers that Apple has fostered over the years. So I think it's good for the industry because one of the things that we haven't seen and one of the reasons this partnership came about was we haven't seen the total consumerization of at the enterprise. You today are using these applications to interact with social media, with other applications for your own daily lives, but business and enterprise still has a long way to go. And hopefully this partnership will help bridge that gap in simplicity, in efficiency and in design of making those applications seamless. So when you leave the office and you get home, or when you leave the home and you come to the office, there's really no difference in the way you interact with an application on a mobile phone. So the SAP ecosystem that's currently familiar with SAP and the development tooling and is now learning the HANA cloud platform stack, got a pretty good idea how you're going to get to them and bring them along. How are you going to get those 11 million Apple developers excited about now entering into and set of new enterprise relationships by utilizing what SAP can bring to them from a business opportunity and from, as you said, change the world kind of perspective. Yeah, look, I think developers are inherently, difficult to kind of change. They're set in their ways. However, there are two ways we're going to be doing that. One, I think is we're building a joint iOS SAP Academy. And that will take the best learnings from what we do jointly with Apple and how we build these applications. Apple's going to co-author this Academy, which will provide best practices on using this SDK, on building enterprise applications that incorporate the best design philosophies that we have from the enterprise and best design capabilities that Apple has. So I think this Academy will be kind of chartered to make the message simple, digestible, and consumable by all developers. Let me stop right there. So when you say Academy, you're really talking about a connected and coherent body of knowledge. You're not talking about just a place. So this will be online? You're going to teach taught in schools? Absolutely. So there's going to be, Apple has innovation and design centers. SAP has design centers and design thinking capabilities. We will bring this into physical locations. We will bring this into virtual locations. And we will market this at large in developer forums, in developer communities. There'll be people that, you know, for example, our SIs, they have armies of people that know SAP today, that we want to create an army of people that know both SAP mobility and they also know on a cloud platform and they know iOS. Bring them all together so they can kind of build the applications. And I think, look, there's a lot of money to be made. If you build great applications that drive transformation, that drive value, I think the developers will find a great way to monetize.  But the chance of building an enterprise app that creates value for, you know, a dozen customers in a certain industry could be very, very valuable. And so I think there are two attractions, as I mentioned before. One is obviously being able to make the technology easy, make the technology consumable by developers so they can kind of start using it, take the friction out of the process. And number two, they've got to then see an economic incentive to do that. And I think the economic incentive is pretty clear. Apple is very, very serious about the enterprise. They've got a 25 billion. I was going to ask you about that. Yeah, they have a $25 billion business right now and it's something that they've taken very seriously. They realize that iPads and iOS devices today have sort of creeped in from the BYOD movement, but they want to see, you know, IT buy these devices, give them to their employees for running their business, for making decisions. And I think application vendors like SAP can help, you know, be a catalyst towards that kind of mission. And you know, it's very hard to bet against Apple. It's a company that sort of came from nowhere and became the leading mobile brand in the world. I think the same opportunity awaits them in the enterprise. And I think they're taking a very deliberate approach in the enterprise of not trying to go out there alone. Enterprise is a complex market and there are certain vendors like SAP that have been in the market for 40 years, understand the customer problems, understand how business is running and using software, but the transformation is upon us. And you know, we go to market across 25 verticals. Each vertical is getting transformed in a major way by technology, by mobility, by the advent of the cloud, by mobility. And I think this application, the application that we developed together and this partnership will help catalyze that transformation. Yeah, especially since Apple, as you said, there are going to be a couple of different SDKs that will be able to become together for developers. But Apple's also shown historically that or revealed new ways to create great software and what the software should look like and how it should behave and the new gestures that are possible. And you're going to be able to bring all that into the ecosystem. Yeah, the partnership is a very, very deep one and it is to share joint roadmaps with what they're doing in iOS, how we're looking at the world. So let me give you an example. So Apple has many APIs that they exposed today to various developers, health kit, car kit. They have the 3D touch system for basically being able to put your thumb on to the, you know, the on and on device on the home screen on the Apple device, iOS devices and that takes you in into the application and authenticates you. Think about that authentication, not only just authenticating you right on the device but authenticating you inside the enterprise, knowing that when Akash comes in, he has authority for signing an expense report up to $10,000 or $20,000. So it's not just him getting into the device but it then picks up his role and then gives him the opportunity to look at all the purchase orders, all the expenses that he can do. So that's just an example of an integration that can go much deeper than just the device. So Apple has a number of technologies, I think, that will become very relevant as we integrate with them in our applications for the enterprise.  The signals that are coming in on a real-time basis into the application. So let's talk about how your customers may be able to behave. Not your IT customers narrowly but your over your aggregate businesses. And let me test this on you. So historically, IT has wanted a very stable SAP platform. Adding, you've done a phenomenal job of adding new functionality to it, capability, success factors and others. Meanwhile, your employee, the customers of those IT organizations, the employees and increasingly external folks want to be able to translate their expertise and the knowledge that they have of a problem into software as fast as they possibly can because they want to be able to solve the problems that are proximate to the actual specifics of an event. Follow me? Yeah, yeah. All right, so is this, am I going to be in a position where I can get an SAP compliant application in the app store that someone with the main knowledge of a problem can go down and say, this will solve the problem and it's going to keep my IT organization happy because it's SAP compliant? Is that what we're talking about? You know, I think that will depend on company by company. I can't make a generic statement on behalf of all the CIOs out there. But certainly, we're taking the friction away from the process. And one of the major elements of the friction has been the ability to get data out of SAP. So with this SDK, I think the cloud is helping the fact that we're putting our HANA services in the cloud with HANA Cloud Platform, our objective is to make it easier to get at that data. And Apple's objective is to interact with that data on a mobile device, on a disconnected device that's running on a 3G or a 4G or an internet connected device. And the ability to be able to do that will definitely create a lot more interactions. It will create the ability for either IT to develop those applications much faster or for some third parties to do that. So the end result is if the customer wants to have access to some data this way or that way, they'll be able to ask for it and they'll be able to get it much faster. So what it does, it creates, from an SAP perspective, it creates a tremendous more amount of value for our customers and also increases the engagement. Because data, just being data is no good. Data needs to be consumed. Data is the new oil. You've heard that term. So the applications and interactions that are available with that data on iOS, either it's just going to be a catalyst for enabling that. Well, one of the needs of digitization is to be able to take expertise and knowledge and practice and translate it into software as fast as possible. And this relationship, we can see how this can accelerate that whole process and great software gets created. So one last question. What's the buzz other than the Apple SAP relationship? What's the buzz that you're getting from the show forth? I think the buzz every year is that SAP is transforming itself. Every year people feel it's a company that they really want to do business with even more than they did last year. That's kind of what I take away. I've been here about three and a half years and every year I'm seeing SAP becoming a nimbler SAP appreciating that the world around them is changing, helping the customers get on that change management story very quickly with the solutions, with the partnerships and with the agility. And I think that it's not your old grandmother's SAP anymore. It's a company that's becoming nimble. It's a company that's becoming flexible. It's a company that's demonstrating that people want value, people want ROI fast and people want to see empathy across the board. And I think that is something that, I feel that it's not something you get to straight away and there's definitely an incremental change. I think that's sort of the major takeaway here and I think there's a lot of solutions here that can really help any kind of business. I mean, we're sitting amongst the SME sort of stand here. A lot of people don't associate SAP with small business, but there's a lot of good initiatives going on in that area and you can find customers that are fortune 10 companies here and you can also find the fortune 5,000 and then startups as well. I think it's a cross-section of companies. Super, Akash Agarwal, thank you very, very much. This is the gentleman who owns the Apple relationship at SAP, phenomenal advance in technology and in the technology industry that's going to point to a lot of good change on the horizon. Thank you very much for joining us here at theCUBE. My name is Peter Burris. theCUBE here at SAP Sapphire. We're going to be back for even more of Sapphire and theCUBE in a few moments. There'll be millions of people in the near future that want to be involved in their own personal wellbeing and wellness. Nobody wants to age in a way that we're bound to a chair or a bed.


This truck has power windows, air, cruise, and a 5.0 Uconnect screen with Bluetooth. It also has 8 speed automatic transmission with heavy duty shock absorbers in the front and the back. Therefore, you will get a very smooth ride. There is plenty of room in this quad cab. We have crew cabs available for sale too. The heavy duty cloth seats are extremely durable with master shield. It's easy to keep clean. The outdoorsman comes with heavy duty rubber mats in the back and front. So come on down to Mountain View Dodge and check out our massive inventory of 2017 Ram trucks at 25% off.


Hello from the ST State and Embedded World 2015 in Nuremberg, where we're talking about security and the increasing demand for it in both computers and consumer devices. Thierry Bousquet has been kind enough to join me. Let's talk about the ST secure element and how it's helping to protect data privacy and the internet of things world. Yes, exactly. So I will demonstrate in this demonstration how you can build a secure solution using STM32 plus a secure element which is called KERKI. What is KERKI? KERKI is a secure element. It is embedded in this board which is inside this IoT. Okay, but let's play and let's start with a demo and let's start with a game. Okay, so in this game I will measure my health using this MEMS and you will see on screen my health. But after I will corrupt the data and will show you how the secure element can help you to protect your data privacy. Okay, so let's start by measurement of my health. As you can see on screen, shaking the MEMS, I measure my health and well done, it seems... Congratulations. Okay, but this is a good story. Okay, in the bad story you can imagine that someone acts your system and because you have no secure elements, your measurement will be bad forever and someone will publish data on the internet and not good data. Okay, so let's imagine and we enable a fake server device. Okay, I know I will restart and I will play with my game. If I measure my health, well done, there is something bad. As you can see, 25% of my health, my system was corrupted by a server. Okay, in fact the server is what? The server is a man in the middle attack. Someone in the internet, change the data between the IoT and the server. Okay, now I will prefer to show you the good things. The good thing is the fact that there is a secure element and the secure element protects your data. Kierke secure elements, ST chip protects your data. So now I will enable the secure elements. Okay, now we are in mode secure. As you can see, there was data exchange between the IoT and the server. The first data that was sent by the fake server, in fact the server detected that the device IoT connected was not authenticated. So there was something that detects that the system was fully active. Okay, go, go, go. So after there is many other cases. In fact, in terms of cryptography, there is different attack that can be done. You could have attack for device authentication that could have attack for data integrity. Someone can change your data. Okay, but also you can have problem of firmware upgrade. Firmware upgrade is what is somewhat change the software that is upgraded to your IoT. Let's see that. So just to finish, last example. Okay, let's imagine I publish a bad firmware inside my IoT. Okay, as you can see there, the firmware is upgrading, but thanks to the secure elements, there will have something that detects that the firmware sent to the secure element was bad. And as you can see, the firmware verification failed and the firmware was corrupted. So everything is fine with the secure elements. I'm reassured. Thank you. Thanks for your time.


Hi, I'm Zor. Welcome to Unisor Education. We will switch to the next topic on my list of momentum and impulses, which is called conservation of momentum. Now, the conservation of momentum obviously is the consequence of the definition of what is momentum and what is impulse, etc. And I'm going to demonstrate it right now. Now, this lecture is part of the Physics 14 course presented on Unisor.com. I suggest you to go to the website Unisor.com to watch this lecture because the lecture has very detailed notes, exams. It has certain educational functionality for people who would like to study under supervision or self-study. And it's free and there are no advertisements. So, conservation of momentum. Well, let me remind you that momentum is defined in a differential form as the increment of momentum is equal to the force applied to my object of mass m and speed v during the time dt. Infinite decimal interval of time. Or in the form of derivatives it would be derivative of m v of t by dt is equal to f. Alright, now, what does it mean? It means that if there are no forces at all, my momentum is constant. That's very important. The momentum is constant if there are no forces applied to this particular object. Well, obviously because it's mass constant, the speed is also constant since there is no force, there is no acceleration. So, the speed is constant. So, momentum is constant. Okay, this is kind of a simple thing. What's a little bit more important, interesting, but maybe complicated is, let's just switch from one object to a system of objects. So, let's consider you have, well, two objects or three or n, doesn't really matter. Now, what happens if there are no external forces acting on these objects? Well, then the only action which can really change something is their action against each other. For instance, they collide or something like this happens. Now, what's the result of it? Well, whenever, let's just consider collision as the most kind of simple interaction between two objects. Well, it produces certain force, right? When they collide, they act on each other with certain force during certain period of time. So, there is a force which this object is acting upon this object, let's call it f, during some time delta t. This is the interval of collision. But at the same time, this object acts on this one with exactly the same force by magnitude but directed in opposite direction. So, there is a minus f during the same, basically, contact, the same collision time. Which means that their impulses are added together, are equal to zero. So, the total impulse of the system is not really changing. Which means that the total momentum, sum of this momentum plus this momentum also should not change. So, we do have certain change in how these two objects after collision behave. I mean, they might change the speed, change the erection, whatever happens with their momentum. Well, yes, these changes do happen, but the sum of these momentum as vector, vector sum, obviously, should not change at all. Because the total of impulses is exactly zero. Now, force is obviously a vector. So, that's why we have change of momentum of this cause this. Change of momentum of this is caused by this. And if we will add them together, these two will nullify each other. Which means my momentum of the first one plus momentum of the second one as function of t, obviously, is constant. So, that's the most important part of this. And that is the conservation of momentum. So, if there is a system of objects, and that's really important for the system of objects, now we are kind of complicated the picture. There is a system of objects, and there are no external forces. Let's say you are on a spaceship, which is moving somewhere in open space, far from any planet, any gravitation field, etc. It just moves on inertia by itself. So, no external forces are applied to this. Now, inside the spaceship there are maybe people or objects moving left and right, etc. But the total momentum of the whole thing should not change. Which means no matter how they move inside, the spaceship will continue moving in exactly the same direction. Because every action which is happening inside that ship has a reaction opposite in direction and equal in magnitude. And that's why the total impulse is always zero. So, that's a very important law. It's called the law of conservation of momentum. It follows basically from the definition of the momentum. We have fine momentum to be equal to impulse, and the impulses are nullifying each other. And that's why we have this conservation of momentum. Or if you wish conservation of impulses, it's basically the same thing in this case. And that's basically it as far as the theory is concerned. Now, let's talk about practice. So, I would like to solve a couple of problems using this particular law of conservation of the momentum. Here is my first. Let's consider you are playing in a billiard. This is your ball. And this is another ball. So, you hit this one. Now, this ball hits this one. And this ball goes this way. So, it's not exactly a head-on collision. It's under some kind of an angle. So, they are actually going into their own directions. Now, let's consider this is alpha. This is a positive angle alpha. And this is, let's say, it's minus beta. Beta is a positive angle, but this is minus because we are going clockwise. Counterclockwise is a positive direction and clockwise is negative. Now, what do we know? Well, we know this speed. Speed we have hit this particular ball. So, now we have two balls. Let's put this is black and this is white. So, this is initial position in black and this is final position. So, knowing this particular speed and knowing these two angles, I would like to find out magnitudes of these two balls after the collision. So, before the collision, I have this is V and this is zero. After the collision, whatever was zero becomes V1, whatever was V becomes V2. So, I would like to determine what are the speeds of these two balls after the collision. This is actually a very typical problem on conservation of momentum because the conservation of momentum is all you need to solve this particular problem. Now, how can I express my conservation of momentum? Well, I will take the momentum of these two before collision and after the collision, I will equate them to each other and see what happens, right? That's basically the logic of this. So, now what was my momentum before? Well, let's consider the mass of this is m.  That's very important obviously, right? So, this is also m. Now, m is not actually given, but it will basically cancel out at the end. So, it doesn't depend. As long as they're equal to each other, the speeds will depend only on the initial speed of this ball, all right? All right. So, now my initial momentum is P, let's call it zero. It's equal to mv plus m0, so it's mv. Which means my final momentum should also be equal to the same thing, right? Okay. So, if this ball has the speed v1 and angle alpha, now obviously my momentum are vectors. Now, this is a horizontal component and I will put the little letter x. Now, the vertical component is equal to zero, right? This is an x, this is a y. So, since my initial momentum is along the x-axis, now this initial momentum has only the x-coordinate and y-coordinate is zero. Well, let's now consider what will be my final. Now, P1x. Now, what is P1x? So, P1 is a vector of momentum of the system after collision. Well, now what is the x-component of this guy? Well, the x-component would be v1 times cosine of alpha. So, it's m times cosine of alpha. That's the piece of this guy. Now, this also guy contributes certain impulse in the x-direction. So, which one? m times cosine of minus beta, right? Well, we know that cosine is an even function, so plus or minus doesn't really matter. So, let's just put beta. Now, what's my final y-component? Okay, now this is the y-axis. Now, from this v1, I will get this component is v1 times sine of alpha. So, it's m sine of alpha. Now, this is opposite direction, right? So, that's m sine minus beta. And obviously, sine is an odd function, so instead of minus here, I will have minus here. Well, that's okay. And what do I know? Well, I know that this is equal to mv and this is equal to zero, right? Because if two vectors are equal to each other, their x-component must be the same and their y-component must be the same. So, this vector has coordinates m cosine m sine of alpha. This vector has components m cosine beta and minus m sine beta. So, if I'm saying that the sum of these two vectors is equal to this vector, it means that my x-coordinate and my y-coordinate separately should be equal. So, basically I have a system of two equations which allow me to find basically my v1 and v2. Okay, except I made a little mistake here. I forgot to put v1 here and v2 here. These are unknown, obviously. So, this is my system of two equations with two unknown. v1 and v2 are unknown. I didn't see them before, that's why I kind of was surprised myself. Okay, now how can we solve this system? Well, come on, that's just a plain system of two equations, linear equations with two unknown. And first of all, I obviously cancel the m, m, m, m, m and zero also, right? So, my new system of two equations with two unknowns will look like v1 cosine alpha plus v2 cosine beta equals v. Now, v1 sine alpha minus v2, yeah, v2 sine beta is equal to zero. Okay, so as you see, it doesn't depend on the masses.  So, from here, well, I think the simplest thing is let's just multiply this thing by what? Let's say multiply this by sine beta and this one by cosine beta and add them together. What will happen then? This multiplied by sine will be v2 cosine beta and sine beta and this will be minus sine beta and cosine beta. So, if I will add them together, v2 will cancel completely. v1 would be cosine sine beta cosine alpha plus cosine beta sine alpha equals 2 v times sine beta and this is zero, right? So, I multiply left and right by this multiplier and add together and that's what I've got. Now, this is, by the way, sine of alpha plus beta, if you remember trigonometry, right? So, from here, we get v1 is equal to v sine beta divided by sine alpha plus beta. That's the answer. So, that's the component which went that way. This is the magnitude of this particular ball. Now, what's the magnitude of another one? Well, we can do a very similar trick. We will multiply this by sine beta and cosine beta. It will be cosine alpha sine, no, I mean alpha. So, this one will be and then subtract. So, if I multiply this and this by this and then subtract, you will have only this piece, right? Or, alternatively, I can use this and have v2 is equal to v1 times sine alpha divided by sine beta, right? From this equation. So, v2 sine beta should be on the right and then I divide by sine beta. So, whatever happens, it will lead to the same result, obviously. And from this, this is actually easier. So, it's v1 which is this one. I divide by sine beta which can cancel this but multiply by sine alpha. So, it will be this. So, that's the solution. So, using the momentum and the conservation of the momentum, I had the momentum before collision and momentum after the collision. Both are vectors. They have x-coordinate and y-coordinate. And that's how I have arrived to two equations with two unknown variables. And solution is obviously trivial. Okay. I have another problem. Okay, another problem is also two-dimensional thing. I have two objects, object A and object B. Object A goes this way, object B goes this way. So, they are going on the perpendicular trajectories. Now, at moment, now here they have met at zero, at origin of co-ordinates, okay? They met and they stick to each other. Now, as a result, my combined object, which I call AB, would go somewhere here. This would be my AB. Let's consider that they are made of Play-Doh. So, they are moving to each other, stick to each other and continue, obviously, to some direction. Now, what I know is, I know that this object is more massive. So, MB is equal to MA by how many times? Four times. I know that. But this object is faster. So, VB is equal to my, okay, it's three times. So, VA is faster than VB by three times. But the mass of VA is four times less than massive B. So, I know just this. What else I know? I know the magnitude of this speed of the object after the collision. Now, collision is non-elastic, which means they are not bouncing of each other. They are speaking to each other. It's non-elastic collision. So, I know the VB. It's a magnitude. I don't know the angle or anything like that. I just know the magnitude. But I have to know speeds of these guys. VA and VB are unknown. So, I'm going to do exactly the same thing as before. Namely, let's assume that I will consider this object first and I will check its impulse. So, its impulse is PA and it has two coordinates, right? Coordinate X and coordinate Y. Now, coordinate X is MA times VA because it's moving this direction. Now, coordinate Y is equal to zero, right? There are no movement of this object in the Y direction, only in the X direction. How about this object? Well, this object has zero X component. It moves only along the Y axis. And along the Y axis, it has MB times VB. Now, VA and VB are unknown. We don't know them. Masses, we don't know them. But what I can say right now, now this is the vector and this is a vector. I know that the sum of these two vectors has a magnitude given to us. Now, what is the sum of these vectors? Well, obviously, it has X component and Y component. So, the PAB X component is equal to sum of X components, which is MAVA and PAB Y component is sum of Y components, zero plus MBVB. So, this is my sum of these two momentums. And it's supposed to be equal to momentum of this, right? Because they are together right now. So, they have the same speed and the mass is a combined mass. So, let me just make a little easier here. Instead of MB, I can put 4MA, right? And instead of, let's say VA, I will put 3VB. This reduces basically the number of variables that I have, right? So, what is the mass of combined object? The mass of combined object is the sum of these masses. And in terms of the MA, this is MA, this is 4MA. So, when we combine together, the mass is equal to 5MA, right? So, I know basically in terms of MA, I know the mass of this, mass of this which is 4 times greater and mass of this which is 5 times greater because it's a combination of MA and 4MA. So, this is known thing. Okay, that's good. And the speed, we also have absolute value. That's given, that's the only thing which is given. Which means I can combine the knowledge which I have about components of sum of these. And since I know that the sum of these are supposed to be equal to this, I will make an equation. I don't need this anymore. My magnitude of this particular vector is equal to square root of x-component square plus y-component square, right? That's the magnitude of the vector. That's Pythagorean theorem. I know x-component, I know y-component, so this is diagonal. Obviously, it's Pythagorean theorem. So, it's 9MA squared VB squared plus 16MA squared VB squared root. And that's the magnitude of this vector, right? And it's supposed to be equal to magnitude of this vector of the momentum of the combined object Mb, which is its mass, which is 5MA, and speed. And that's the only thing which is given. What do we have from here? Well, obviously, 9 plus 16 is 25, so it's 5MAVB, right? So, it's 5MAVB from which we cancel this and we have the answer VB is equal to VAB. Well, maybe a little unusual that the magnitude of this is exactly the same as magnitude of that. But, well, direction is different. That's number one. Number two, I obviously chose certain numbers to have an easier calculations with square roots, etc., right? So, this is the answer. And since I know the VB, I know that the A is 3 times faster, which is 3VAB. And that's my answer. So, knowing the magnitude of this speed and knowing the proportion between the masses and the speeds, absolute speeds of these two objects, I can actually find their corresponding velocities. Okay, again, what's here? What to take from this particular problem? All you have to do is carefully calculate the momentum of the system, combined all the momentum of each particular object together before whatever happens. In this case, it's non-elastic collision and after. So, before we had two objects in this case, but after we had one object. So, we calculated basically the sum of these two momentum, this one and this one, and equated it to the momentum of the system after the collision. And that's the result of it. So, that's the only thing which you have to really understand how to use the law of conservation of momentum. Before and after whatever happens, you calculate separately, you equate to each other, and from here you basically derive whatever is necessary to derive. All right, that's it. Thank you very much. I do suggest you to go to theunisor.com and read whatever the notes for this lecture is, just to repeat yourself. And if you want, you can probably try to just forget whatever I just said, solve these problems yourself and see if you will get the same results. Also a very helpful exercise. All right, that's it. Thanks very much and good luck.