Uni Tour Germany 11.2009

Recommending courses to students in online platforms is studied widely. Almost all studies target closed platforms, that belong to a University or some other educational provider. This makes the course recommenders situation specific. Over the last years, a demand has developed for recommender system that suit open online platforms. Those platforms have some common characteristics, such as the lack of rich user profiles with content metadata. Instead they log user interactions within the platform that can be used for analysis and personalization. In this paper, we investigate how user interactions and activities tracked within open online learning platforms can be used to provide recommendations. We present a study in which we investigate the application of several state-of-the-art recommender algorithms, including a graph-based recommender approach. We use data from the OpenU open online learning platform that is in use by the Open University of the Netherlands. The results show that user-based and memory-based methods perform better than model-based and factorization methods. Particularly, the graph-based recommender system proves to outperform the classical approaches on prediction accuracy of recommendations in terms of recall. We conclude that, if the algorithms are chosen wisely, recommenders can contribute to a better experience of learners in open online courses. Soude Fazeli, Enayat Rajabi, Leonardo Lezcano, Hendrik Drachsler, Peter Sloep

The document provides a summary of a lecture on CSCW in times of change and social media. The lecture discusses how CSCW and social media are transforming organizations into networked structures and how personalization of data is enabling personalized paths for consumers. It also explores applications of these changes in domains like science and health, and outlines future challenges in areas like open science, linked data, and mobile technologies.

The widespread adoption of Learning Analytics (LA) and Educational Data Mining (EDM) has somewhat stagnated recently, and in some prominent cases even been reversed following concerns by governments, stakeholders and civil rights groups about privacy and ethics applied to the handling of personal data. In this ongoing discussion, fears and realities are often indistin-guishably mixed up, leading to an atmosphere of uncertainty among potential beneficiaries of Learning Analytics, as well as hesitations among institutional managers who aim to innovate their institution’s learning support by implementing data and analytics with a view on improving student success. In this presentation, we try to get to the heart of the matter, by analysing the most common views and the propositions made by the LA community to solve them. We conclude the paper with an eight-point checklist named DELICATE that can be applied by researchers, policy makers and institutional managers to facilitate a trusted implementation of Learning Analytics.

Impact of the Financial Crisis on the Energy Sector Dr. Fatih Birol Chief Economist International Energy Agency World Energy Council Rome, 19th March 2009

The DELICATE checklist contains eight action points that should be considered by managers and decision makers planning the implementation of Learning Analytics / Educational Data Mining solutions either for their own institution or with an external provider. The eight points are: 1. Determination: Decide on the purpose of learning analytics for your institution. What aspects of learning or learner services are you trying to improve? 2. Explain: Define the scope of data collection and usage. Who has a need to have access to the data or the results? Who manages the datasets? On what criteria? 3. Legitimate: Explain how you operate within the legal frameworks, refer to the essential legislation. Is the data collection excessive, random, or fit for purpose? 4. Involve: Talk to stakeholders and give assurances about the data distribution and use. Give as much control as possible to data subjects (permission architecture), and provide access to their data for the individuals. 5. Consent: Seek consent through clear consent questions. Provide an opt-out option. 6. Anonymise: De-identify individuals as much as possible, aggregate data into meta-models. 7. Technical aspects: Monitor who has access to data, especially in areas with high staff turn-over. Establish data storage to high security standards. 8. External partners: Make sure externals provide highest data security standards. Ensure data is only used for intended purposes and not passed on to third parties. We hope that the DELICATE checklist will be a helpful instrument for any educational institution to demystify the ethics and privacy discussions around Learning Analytics. As we have tried to show in this article, there are ways to design and provide privacy conform Learning Analytics that can benefit all stakeholders and keep control with the users themselves and within the established trusted relationship between them and the institution.

The document discusses emerging web technologies including: 1. New web standards like HTML5, canvas, and video that provide richer content without plugins. 2. Adaptive content approaches like CSS media queries that allow content to respond to different device capabilities. 3. Using the browser as a platform for applications through widgets and Opera Unite, which leverage web standards and APIs to create cross-device apps without native software.

The document discusses the future of web technologies, focusing on three main areas: 1. New web standards like HTML5 that provide more capabilities without plugins through elements, forms, canvas and video. CSS3 media queries also allow adaptive content for different devices. 2. Adaptive content through media queries and responsive design can make sites work across devices that vary in screen size, input, and capabilities. 3. The browser is emerging as a platform through widgets, JavaScript APIs and the browser runtime, allowing development across devices without writing for each platform natively. Standards will make the browser a ubiquitous platform.

Bruce Lawson of Opera toured Indonesian Universities discussing web standards, HTML5, CSS Media Queries and cross-device development.

This document compares native applications, web applications, and widgets for mobile devices. Native applications have direct access to device features but must be developed for each platform. Web applications can be written once and deployed anywhere but run inside the browser without direct device access. Widgets combine the cross-platform capabilities of web applications with the ability to access device features and run standalone like native applications.

This document provides an overview of Silverlight, including what it is, why it was created, its features, how to build Silverlight applications using Expression Blend and Visual Studio, and resources for learning more. Silverlight is a web development framework that allows building and running rich interactive applications across browsers and operating systems using HTML, CSS, and JavaScript.

The document is a presentation about HTML5 given by Frédéric Harper of Microsoft Canada. It introduces HTML5 and its key features such as video, audio, canvas, drag and drop. It discusses the different stages in the HTML5 specification process. It also covers strategies for using HTML5 across different browsers, including the lowest common denominator approach, polyfills, and alternate experiences. The presentation encourages learning more about HTML5 and having fun building projects with it.

A talk I was asked to give on the various options for building mobile applications / getting content onto mobile devices. I chose to organize it as gradient surveying the spectrum from web to native, all the stuff in between. Unfortunately for native I've only had experience with iOS so I couldn't really speak towards the other platforms. I do think that non native solutions can take care of 95% of the use cases, and this gap will only narrow as time goes on - I'm thinking back to early 2010 when cross platform SDKs like Appcelerator Titanium came onto the scene and how much has changed.

The document discusses whether a "one web" approach can accommodate diverse mobile users, including those with disabilities. It argues that while the same information may not be available across all devices, the web should provide reasonable access. Key points include: - Web standards like HTML, CSS and JavaScript can help create an accessible experience across devices when combined with guidelines like WCAG and MWBP. - Emerging technologies like CSS media queries, HTML5 and WAI-ARIA have the potential to further improve accessibility on mobile. - Developers should use progressive enhancement and set an accessible baseline first before advanced features to ensure an inclusive web.

Silverlight is a technology from Microsoft for building rich interactive applications for the web. It allows developers to use XAML and .NET languages to create animations, media playback, and other rich features within a browser. Silverlight applications provide a consistent experience across browsers and platforms using a small browser plugin. It is well suited for creating immersive media experiences, rich internet applications, and delivering content across devices from desktop to mobile.

The document discusses the evolution of using the web as a real application platform. It outlines key technologies like HTML5, JavaScript, and WebGL that have advanced the capabilities of web applications. The document also notes shortcomings in earlier versions of the web around user interaction, performance, and compatibility issues. However, new technologies and browser improvements have helped address many of these issues. The document concludes that the web is becoming a viable platform for developing full-featured applications that combine the benefits of installed software and web-based applications.

My Slides for my Talk about being Always On is a lie and how developers could add improvements to their web site to deliver a great experience even when the network is flaky!

The document provides tips for optimizing websites for mobile and cross-device use. It discusses the varied mobile landscape and capabilities that websites need to account for. Key recommendations include using responsive design with CSS media queries to render pages appropriately based on screen size and features. The document also advocates the "One Web" principle of providing consistent content across all devices when reasonable.

This document discusses approaches for cross-device web development and accessibility. It covers developing websites that can be accessed and used across different devices like mobile phones, laptops, tablets, TVs, and more. It recommends using responsive design with CSS media queries to optimize websites for different screen sizes and capabilities. It also discusses using standards like SVG and following best practices for mobile and accessible development.

The document discusses different approaches for building cross-platform web apps: 1. Progressive Web Apps (PWAs) which work across devices and can be installed like native apps using web technologies. 2. Electron which allows building desktop apps with web technologies but results in larger apps. 3. Hybrid apps which combine a web view layer with native platform integration via plugins but have web-based UIs. 4. JavaScript-driven native apps like React Native and NativeScript which use JavaScript to build truly native mobile apps.

Sascha Corti With Internet Explorer 9, Microsoft has entered the league of HTML 5 browsers and with its active participation in the W3C working groups, the company proves its engagements towards the new and emerging standards. Developers however are often left wondering where the boundaries are drawn between HTML5 web site, plug-in based rich internet application and smart client or “app”. This session intends to answer this question and uses many examples to show you some of the most important enhancements introduced by HTML5, CSS3, SVG, DOM, WOFF and ECMA script. You will learn now the standards are still evolving and how Microsoft is contributing. http://soft-shake.ch/2011/conference/sessions/microsoft/2011/09/06/introduction-to-html5.html

The document discusses HTML5 and provides an overview of its key elements and features. It begins with a definition of HTML5 as a draft specification from the W3C that adds new elements like canvas, video and audio. It then provides summaries of important HTML5 elements and features like video, audio, canvas, SVG, CSS3, DOM scripting, geolocation and more. The document concludes by discussing resources for learning more about HTML5 and considerations around using HTML5 versus apps or other technologies on mobile.

The document discusses the history and evolution of web browsers and standards. It notes that early browsers in the 1990s included Mosaic and Netscape Navigator. In the late 1990s, Internet Explorer and Netscape competed using both open and closed standards. HTML5 was developed in the 2000s to better support web applications and add new elements like video. The document also discusses approaches to making websites mobile-friendly, including responsive design using viewport meta tags and media queries.

This document provides an overview and introduction to programming with Windows Presentation Foundation (WPF) using XAML. It discusses key WPF concepts like the logical and visual trees, dependency properties, templates, styles, resources, and layouts. It also covers programming with 2D and 3D graphics, data binding, animation, multimedia, and documents. The document recommends resources for getting started with WPF and provides an agenda for the presentation.

1. HTML5 is a major revision to the HTML standard that is still under development and aims to be the future of the web. 2. It includes new elements like <video>, <audio>, and <canvas> that allow embedding multimedia without plugins, as well as features like geolocation. 3. The HTML5 specification is very large, covering HTML, SVG, CSS, and APIs. It aims to provide a common standard for web applications. 4. HTML5 is not just a marketing term - it represents an ongoing effort to develop a unified standard for the next generation of the web.

HTML5 is a draft specification from the W3C that adds new elements like canvas, video and audio to HTML. It is not finished yet and continues to evolve. HTML5 introduces elements like article, section and aside to structure content. It also supports new media capabilities like playing video and audio natively in the browser without plugins. HTML5 is supported in Internet Explorer 9 and later, and also in other modern browsers like Chrome and Firefox.

WCAG is supposed to give us a reasonably objective way of saying whether or not the sites we are building/auditing are "accessible" (to a particular baseline). However, they are only as useful as our understanding and interpretation of the guidelines' normative text. And, of course, it is not perfect - with some omissions, handwaving, and straight-up loopholes. So where does this leave developers and auditors? In this talk - a reprise of a previous talk, now updated to cover new SCs from WCAG 2.2 - Patrick may not have all the answers, but he'll have a good rant around the subject anyway...

Update about Pointer Events Level 3 work for the upcoming W3C Technical Plenary and Advisory Committee (TPAC) 2023 in Seville https://www.youtube.com/watch?v=r0spZl1qaa0 https://w3c.github.io/pointerevents/ https://www.w3.org/TR/pointerevents/ https://www.w3.org/2023/09/TPAC/ https://patrickhlauke.github.io/touch/w3c_tpac2023_pewg/ Cross-posted from https://www.w3.org/2023/09/TPAC/group-updates.html#pointer-events

WCAG is supposed to give us a reasonably objective way of saying whether or not the sites we are building/auditing are "accessible" (to a particular baseline). However, they are only as useful as our understanding and interpretation of the actual guidelines' normative text. And of course they're not perfect - with some omissions, handwaving, and straight up loopholes. So where does this leave developers and auditors? In this talk, Patrick may not have all the answers, but he'll have a good rant around the subject anyway...

WCAG is supposed to give us a reasonably objective way of saying whether or not the sites we are building/auditing are "accessible" (to a particular baseline). However, they are only as useful as our understanding and interpretation of the actual guidelines' normative text. And of course they're not perfect - with some omissions, handwaving, and straight up loopholes. So where does this leave developers and auditors? In this talk, Patrick may not have all the answers, but he'll have a good rant around the subject anyway...

HTML offers many features and attributes that can make your sites more accessible...but only if they're used wisely. Can there really be "too much accessibility"? Audio recording: https://archive.org/details/Psf8August2007.PatrickH.Lauke-TooMuchAccessibilityGoodIntentions

Patrick H. Lauke: Styling Your Web Pages with Cascading Style Sheets / EDU course / University of Salford / 13 February 2006

Patrick H. Lauke: Evaluating web sites for accessibility with Firefox / Manchester Digital Accessibility Working Group (MDAWG) / 1 March 2006

Patrick H. Lauke: Managing and educating content editors - experiences and ideas from the trenches / Public Sector Forums / 10 May 2007

Patrick H. Lauke - Implementing Web Standards across the institution: trials and tribulations of a redesign / Institutional Web Management Workshop IWMW / Birmingham / 28 July 2004

Patrick H. Lauke: Geolinking content - experiments in connecting virtual and physical places / Institutional Web Management Workshop IWMW / York / 16 July 2007

WCAG 2.0 is the new set of web accessibility guidelines that was released in 2008 as a recommendation by the W3C. It addresses some issues with the previous WCAG 1.0 guidelines by being technology-agnostic, having clearly testable success criteria focused on user outcomes rather than techniques, and removing outdated requirements. WCAG 2.0 provides more freedom for authors while still ensuring accessibility. It includes 4 principles, 12 guidelines and 61 success criteria to evaluate websites. The transition from WCAG 1.0 involves evaluating sites based on the new success criteria and testing areas that may be different.

This document provides an introduction to web accessibility. It begins by addressing some common misconceptions about accessibility, noting that it aims to accommodate people with a wide range of disabilities, not just visual impairments. The document emphasizes that accessibility is important for both ethical and legal reasons, and that inclusive design benefits all users. It then outlines key web accessibility guidelines from the W3C, providing examples of how to make content more accessible through proper semantic markup and alternative text. The conclusion stresses that accessibility is an essential consideration for web development.

Patrick H. Lauke: Doing it in style - creating beautiful sites, the web standards way / WebDD / Reading / 3 February 2007

The document discusses common misconceptions and pitfalls around using web standards. It argues that web standards are about more than just validation - they are about semantics, separation of concerns, and pragmatism. Some key points include: using the most appropriate HTML elements to convey meaning rather than appearance; applying styles through CSS instead of presentational markup; avoiding non-semantic class names; and recognizing that not all uses of tables or images are invalid. The document advocates for balancing standards with practical concerns like multiple authors and one-off content needs.

Ian Lloyd/Patrick H. Lauke: Accessified - practical accessibility fixes any web developer can use / South By Southwest SXSW / Austin, Texas, 11 March 2007

One from the archives...presentation about the development of the University of Salford website in 2007

Patrick H. Lauke: Keyboard accessibility - just because I don't use a mouse doesn't mean I'm second class / Skillswap Bristol / 11 Nobember 2008

Vanilla HTML is limiting and boring. Our clients demand highly engaging and interactive web experiences. And wouldn’t you know, with just a bit of HTML and JavaScript we can craft amazing custom controls, widgets and effects that go far beyond the confines of traditional static markup. But how can we ensure that these custom experiences are both understandable and usable for people with disabilities, and in particular those using assistive technologies such as screen readers? In this talk, we will look at the basics of making some common custom-built components accessible - covering how browsers and assistive technologies interact, the limitations of HTML, and how ARIA can help make interactive experiences more accessible. In addition, we will explore some of the recent additions in ARIA 1.1, as well as some particular challenges when it comes to traditional ARIA patterns and assistive technologies on mobile/tablet/touch devices. Evergreen slidedeck at https://patrickhlauke.github.io/aria/presentation/ / https://github.com/patrickhlauke/aria/

Vanilla HTML is limiting and boring. Our clients demand highly engaging and interactive web experiences. And wouldn’t you know, with just a bit of HTML and JavaScript we can craft amazing custom controls, widgets and effects that go far beyond the confines of traditional static markup. But how can we ensure that these custom experiences are both understandable and usable for people with disabilities, and in particular those using assistive technologies such as screen readers? In this talk, we will look at the basics of making some common custom-built components accessible - covering how browsers and assistive technologies interact, the limitations of HTML, and how ARIA can help make interactive experiences more accessible. In addition, we will explore some of the recent additions in ARIA 1.1, as well as some particular challenges when it comes to traditional ARIA patterns and assistive technologies on mobile/tablet/touch devices. Evergreen slidedeck at https://patrickhlauke.github.io/aria/presentation/ / https://github.com/patrickhlauke/aria/

This document provides an introduction to Accessible Rich Internet Applications (WAI-ARIA). It discusses the need for ARIA to make complex web applications accessible, common ARIA roles and attributes, and best practices for using ARIA. Key points include: ARIA defines roles, states and properties to convey semantics to assistive technologies; common roles include buttons, toggles, and landmarks; and the five rules of ARIA use emphasize using native HTML when possible and ensuring interactive elements are keyboard accessible.

Profile portofolio

Slide of the tutorial entitled "Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Emerging Trends" held at UMAP'24: 32nd ACM Conference on User Modeling, Adaptation and Personalization (July 1, 2024 | Cagliari, Italy)

Everything that I found interesting about engineering leadership last month

In the modern digital era, social media platforms have become integral to our daily lives. These platforms, including Facebook, Instagram, WhatsApp, and Snapchat, offer countless ways to connect, share, and communicate.

Are you interested in dipping your toes in the cloud native observability waters, but as an engineer you are not sure where to get started with tracing problems through your microservices and application landscapes on Kubernetes? Then this is the session for you, where we take you on your first steps in an active open-source project that offers a buffet of languages, challenges, and opportunities for getting started with telemetry data. The project is called openTelemetry, but before diving into the specifics, we’ll start with de-mystifying key concepts and terms such as observability, telemetry, instrumentation, cardinality, percentile to lay a foundation. After understanding the nuts and bolts of observability and distributed traces, we’ll explore the openTelemetry community; its Special Interest Groups (SIGs), repositories, and how to become not only an end-user, but possibly a contributor.We will wrap up with an overview of the components in this project, such as the Collector, the OpenTelemetry protocol (OTLP), its APIs, and its SDKs. Attendees will leave with an understanding of key observability concepts, become grounded in distributed tracing terminology, be aware of the components of openTelemetry, and know how to take their first steps to an open-source contribution! Key Takeaways: Open source, vendor neutral instrumentation is an exciting new reality as the industry standardizes on openTelemetry for observability. OpenTelemetry is on a mission to enable effective observability by making high-quality, portable telemetry ubiquitous. The world of observability and monitoring today has a steep learning curve and in order to achieve ubiquity, the project would benefit from growing our contributor community.

Java Servlet programs

Solar Storms (Geo Magnetic Storms) are the motion of accelerated charged particles in the solar environment with high velocities due to the coronal mass ejection (CME).

Kief Morris rethinks the infrastructure code delivery lifecycle, advocating for a shift towards composable infrastructure systems. We should shift to designing around deployable components rather than code modules, use more useful levels of abstraction, and drive design and deployment from applications rather than bottom-up, monolithic architecture and delivery.

This is a slide deck that showcases the updates in Microsoft Copilot for May 2024

This presentation, delivered at the Postgres Bangalore (PGBLR) Meetup-2 on June 29th, 2024, dives deep into connection pooling for PostgreSQL databases. Aakash M, a PostgreSQL Tech Lead at Mydbops, explores the challenges of managing numerous connections and explains how connection pooling optimizes performance and resource utilization. Key Takeaways: * Understand why connection pooling is essential for high-traffic applications * Explore various connection poolers available for PostgreSQL, including pgbouncer * Learn the configuration options and functionalities of pgbouncer * Discover best practices for monitoring and troubleshooting connection pooling setups * Gain insights into real-world use cases and considerations for production environments This presentation is ideal for: * Database administrators (DBAs) * Developers working with PostgreSQL * DevOps engineers * Anyone interested in optimizing PostgreSQL performance Contact info@mydbops.com for PostgreSQL Managed, Consulting and Remote DBA Services

This is a powerpoint that features Microsoft Teams Devices and everything that is new including updates to its software and devices for May 2024

Password Rotation in 2024 is still Relevant