Rubykaigi2008: REST 信者から見た Ruby と Rails
8 likes4,892 views
This document discusses REST and how it relates to Ruby and Rails. Some key points: - REST is an architectural style for building web applications. It focuses on addressability of resources and stateless connections between systems. - Ruby and Rails are well-suited for building RESTful applications due to features like routing and the ability to easily expose resources and links through URIs. - While Rails makes routing and linking resources simple, the code structure can be dependent on the routing. True REST principles emphasize designing applications around resources and links rather than implementation details.
1 of 58
Downloaded 22 times
Ad
Recommended
Working With Rails
Working With RailsDali Wang This document provides an overview of Ruby on Rails including:
- A brief introduction to Ruby and the Rails framework
- A description of the Rails framework components and directory structure
- How Rails works and getting started with a Rails application
- Examples of real world Rails usage and companies using Rails
- A presentation agenda with a demo of Rails
Web技術勉強会 第19回
Web技術勉強会 第19回龍一 田中 The document discusses different methods for connecting Ruby on Rails applications to Apache. It recommends method 3, using Apache with mongrel_cluster and mod_proxy. This allows Apache to recognize and proxy requests to the Rails application running on mongrel, without needing other proxying software. It avoids issues the other methods had with permissions and access.
Ruby on Rails Tutorial Part I
Ruby on Rails Tutorial Part IWei Jen Lu This document provides an overview and agenda for a Ruby on Rails tutorial part 1. It discusses installing Ruby and Rails on Windows, creating a simple DailyLog application to demonstrate the Rails framework, and using the MVC architecture and RESTful design. It also covers generating scaffolds, models, controllers and views, routing and helpers. The document concludes with a section on unit testing in Rails.
Rest and Rails
Rest and RailsChamnap Chhorn This document discusses REST theory and how to apply REST principles in Rails applications. It covers REST concepts like resources, statelessness, HTTP verbs and status codes. It also explains how Rails supports REST with resource routing, link helpers, content negotiation and authentication. The document includes an example case study and discusses refactoring the example to be more RESTful.
Rest And Rails
Rest And RailsKaushik Jha This document discusses REST (Representational State Transfer) and how to make Rails applications RESTful. It covers what REST is, designing RESTful resources in Rails, creating representations of resources, exposing resources through controllers, and consuming RESTful APIs using tools like ActiveResource and jQuery. It also provides tips for making RESTful controllers dry, turning verbs into nouns in URIs, and registering custom MIME types.
Representational State Transfer (REST)
Representational State Transfer (REST)David Krmpotic REST (REpresentational State Transfer) is an architectural style for building web APIs that relies on HTTP verbs like GET, POST, PUT, and DELETE to manipulate resources identified by URIs. Resources can have multiple representations like JSON or XML, and the appropriate representation is selected via content negotiation. REST aims to provide a simple, lightweight interface and takes advantage of existing web protocols to transfer representations of resources between clients and servers. Key REST constraints include using nouns for resources and HTTP methods for actions, making the interface lightweight, client-server, cacheable, and layered.
Reviewing RESTful Web Apps
Reviewing RESTful Web AppsTakuto Wada This document summarizes Takuto Wada's presentation on reviewing RESTful web apps. It discusses best practices for designing RESTful resources and representations, including using nouns instead of verbs in URLs, making URLs reflect the meaning of resources, and ensuring resources are connected through hypermedia links and forms. It also covers appropriate use of HTTP methods, status codes, and content negotiation to build RESTful APIs in accordance with best practices.
Cwinters Intro To Rest And JerREST and Jersey Introductionsey
Cwinters Intro To Rest And JerREST and Jersey Introductionseyelliando dias This document provides an introduction to REST and Jersey. It summarizes a presentation given by Chris Winters to the Pittsburgh Java User Group on April 21, 2009. The presentation introduces REST concepts, discusses why HTTP is successful, and provides an overview of the Jersey framework for building RESTful web services in Java. It also demonstrates a simple note taking application built with REST and Jersey.
The Rest Architectural Style
The Rest Architectural StyleRobert Wilson The document provides an overview of the REST (Representational State Transfer) architectural style. It defines REST, describes its constraints including client-server architecture, stateless, cacheable, uniform interface, and layered system. It also gives examples of how to design a RESTful web API, including defining resources and their representations, using HTTP methods and status codes, and considerations for caching, encodings and security.
Web Clients for Ruby and What they should be in the future
Web Clients for Ruby and What they should be in the futureToru Kawamura Toru Kawamura discusses the need for web clients in Ruby to be adaptable to change by being decoupled and easy to reuse through versatility. He outlines some of the issues with existing tightly coupled clients and gems dedicated to specific APIs. Kawamura proposes a "Web Client" concept modeled after Rack middleware and Faraday middleware, which can be combined and reused across clients and APIs. He demonstrates implementations of this concept through the faraday-hypermedia and faraday-link-extractor gems. The presentation argues that a decoupled, modular approach to web clients following standards can help address current issues around rigid coupling and lack of reusability.
Restful web services rule financial
Restful web services rule financialRule_Financial This document provides an introduction and overview of RESTful web services. It discusses REST principles such as resources, addressability, statelessness, uniform interface, and representations. It also covers designing RESTful APIs, including examples from Amazon S3. The document outlines an agenda to discuss introduction, principles, design, implementations, and implementation of RESTful APIs and web services.
rest-api-basics.pptx
rest-api-basics.pptxAgungSutikno1 The document provides an overview of REST API basics and compares traditional web applications to RESTful APIs. Some key points:
- Traditional web apps use HTML and HTTP, replacing entire pages on each request, while RESTful APIs focus on resources and use HTTP methods to perform CRUD operations.
- REST (Representational State Transfer) is an architectural style using URIs to identify resources and HTTP methods to operate on them. It advocates a stateless, cacheable, layered system of web services.
- Examples show how HTTP methods like GET, POST, PUT, PATCH, and DELETE map to CRUD operations on resources, with content types specifying response formats. Status codes indicate success or failure.
Rails Presentation (Anton Dmitriyev)
Rails Presentation (Anton Dmitriyev)True-Vision Ruby on Rails is an open-source web framework that is optimized for programmer happiness and productivity. It allows developers to write code more easily by favoring conventions over rigid configuration. Ruby on Rails uses conventions to make assumptions about how apps should be structured, reducing the amount of configuration code needed.
REST and Resource Oriented Architecture - okcDG March 2008
REST and Resource Oriented Architecture - okcDG March 2008Ryan Hoegg This document discusses REST (Representational State Transfer), a architectural style for distributed hypermedia systems, and Resource Oriented Architecture (ROA), which provides concrete rules for building RESTful web services. It explains key REST concepts like addressable resources, uniform interface, statelessness, and hypermedia. It also provides an example of designing a RESTful pizza delivery web service using ROA principles like naming resources with URIs and designing representations for resources.
Restful Best Practices
Restful Best PracticesBelighted These are the slides of our talk at Fosdem 2008 (http://fosdem.org).
We explain what REST is, how it is used in Rails, and finally we give some tips on how to architecture your application so that it follows the REST philosophy.
[2015/2016] The REST architectural style![[2015/2016] The REST architectural style](https://cdn.slidesharecdn.com/ss_thumbnails/06crest-160429194845-thumbnail.jpg?width=560&fit=bounds)
[2015/2016] The REST architectural styleIvano Malavolta This presentation has been developed in the context of the Mobile Applications Development course, DISIM, University of L'Aquila (Italy), Spring 2016.
http://www.ivanomalavolta.com
Creating Restful Web Services with restish
Creating Restful Web Services with restishGrig Gheorghiu This document discusses creating RESTful web services using the restish framework. It provides an overview of REST principles like resources, representations, and the uniform interface. It also demonstrates building a simple TODO list management application with restish and discusses testing and deploying restish applications.
Rest APIs Training
Rest APIs TrainingShekhar Kumar This document provides an overview of RESTful APIs and related concepts:
- It describes HTTP methods like GET, POST, PUT, DELETE and PATCH that are used to interact with resources over HTTP.
- It explains HTTP status codes for success (2xx), client errors (4xx) and server errors (5xx).
- It discusses REST architectural constraints like client-server, statelessness, caching, uniform interface, content negotiation and hypermedia.
- It covers concepts like resources, URIs, relationships between resources, content negotiation, versioning APIs, and HATEOAS to make APIs self-descriptive.
What is rest. Why is it part of the Rails way?. Railsconf 2014. Javier Ramirez
What is rest. Why is it part of the Rails way?. Railsconf 2014. Javier Ramirezjavier ramirez When David Heinemeier Hansson started talking about REST in 2006, little could we suspect it'd become such a central part of Rails (and of web development in general). Back then a web service meant something you coded using XML and SOAP. Those were dark times. REST changed it all.
In this talk, I'll explain REST for beginners, I'll talk about why it is such an important architecture, and I'll show all the nice things Rails offers you for building a RESTful application or a RESTful API.
REST Basics
REST BasicsIvano Malavolta Mobile applications Development - Lecture 14
REST Basics
This presentation has been developed in the context of the Mobile Applications Development course at the Computer Science Department of the University of L’Aquila (Italy).
http://www.di.univaq.it/malavolta
Finding Restfulness - Madrid.rb April 2014
Finding Restfulness - Madrid.rb April 2014samlown The document discusses the development of Restfulness, a Ruby library for building REST APIs. It begins by outlining some irritations the author had with existing Rails controllers and API frameworks like Grape. This inspired the author to create Restfulness with a focus on simplicity, treating resources as the focus of requests, and closely following REST and HTTP principles. The summary describes the key components of Restfulness, including simple routing based on resources, separating path, query, and body parameters, and callbacks that control the flow of requests. It also mentions how Restfulness implements error handling and can be run both standalone or as part of Rails applications.
Rest Vs Soap Yawn2289
Rest Vs Soap Yawn2289Kalyan Vijay Kumar Pasumarthi ReST is an architectural style defined by a set of constraints including being client-server, stateless, cacheable, and having a uniform interface. It favors directly addressing resources over remote procedure calls and aims to make systems more scalable and loosely coupled. While sometimes seen as weak due to performance and customization issues, ReST architectures also provide benefits like low barriers to entry and being easier to develop and maintain.
REST e Resource Oriented Architectures
REST e Resource Oriented ArchitecturesGrUSP REST è lo stile architetturale a cui aderisce quello che oggi noi chiamiamo Web. Uno dei problemi storici della programmazione di applicazioni web è l’impendance mismatch fra vari modelli computazionali e di dati (REST, Object Oriented, Relational Model, ecc…). Questa sessione ha lo scopo di evidenziare la problematica con relativi esempi, soluzioni e risultati ottenuti con l’utilizzo di PHP.
Resource Oriented Architectures
Resource Oriented ArchitecturesGabriele Lana This document discusses REST (Representational State Transfer) and resource-oriented architectures. It provides examples of designing RESTful APIs and services using common REST constraints like URIs to identify resources, HTTP methods to manipulate resources, and resource representations. The key aspects covered are modeling the domain as resources, designing URIs, exposing a uniform interface, designing representations, and common interaction flows and error conditions.
REST and RESTful Services
REST and RESTful ServicesDamian T. Gordon Representational State Transfer (REST) is an architectural style where resources are accessed via standard HTTP methods like GET, POST, PUT, and DELETE. Resources can represent both concrete state like a database record or abstract state like a service element. REST services expose resources through a uniform interface and are stateless, cacheable, and layered.
Rest
RestArnon Rotem-Gal-Oz REST (Representational State Transfer) is an architectural style for building distributed systems. It uses stateless operations to manipulate representations of resources through a standardized interface and uniform identification of resources. Common REST implementations use HTTP methods like GET, PUT, POST and DELETE to operate on resources identified in requests by URIs. REST aims to provide a simple and lightweight interface between components to improve scalability for distributed systems.
WebAPIのこれまでとこれから
WebAPIのこれまでとこれからYohei Yamamoto 2014-07-11 API Meetup #1
http://api-meetup.doorkeeper.jp/events/12768
More Related Content
Similar to Rubykaigi2008: REST 信者から見た Ruby と Rails (20)
Reviewing RESTful Web Apps
Reviewing RESTful Web AppsTakuto Wada This document summarizes Takuto Wada's presentation on reviewing RESTful web apps. It discusses best practices for designing RESTful resources and representations, including using nouns instead of verbs in URLs, making URLs reflect the meaning of resources, and ensuring resources are connected through hypermedia links and forms. It also covers appropriate use of HTTP methods, status codes, and content negotiation to build RESTful APIs in accordance with best practices.
Cwinters Intro To Rest And JerREST and Jersey Introductionsey
Cwinters Intro To Rest And JerREST and Jersey Introductionseyelliando dias This document provides an introduction to REST and Jersey. It summarizes a presentation given by Chris Winters to the Pittsburgh Java User Group on April 21, 2009. The presentation introduces REST concepts, discusses why HTTP is successful, and provides an overview of the Jersey framework for building RESTful web services in Java. It also demonstrates a simple note taking application built with REST and Jersey.
The Rest Architectural Style
The Rest Architectural StyleRobert Wilson The document provides an overview of the REST (Representational State Transfer) architectural style. It defines REST, describes its constraints including client-server architecture, stateless, cacheable, uniform interface, and layered system. It also gives examples of how to design a RESTful web API, including defining resources and their representations, using HTTP methods and status codes, and considerations for caching, encodings and security.
Web Clients for Ruby and What they should be in the future
Web Clients for Ruby and What they should be in the futureToru Kawamura Toru Kawamura discusses the need for web clients in Ruby to be adaptable to change by being decoupled and easy to reuse through versatility. He outlines some of the issues with existing tightly coupled clients and gems dedicated to specific APIs. Kawamura proposes a "Web Client" concept modeled after Rack middleware and Faraday middleware, which can be combined and reused across clients and APIs. He demonstrates implementations of this concept through the faraday-hypermedia and faraday-link-extractor gems. The presentation argues that a decoupled, modular approach to web clients following standards can help address current issues around rigid coupling and lack of reusability.
Restful web services rule financial
Restful web services rule financialRule_Financial This document provides an introduction and overview of RESTful web services. It discusses REST principles such as resources, addressability, statelessness, uniform interface, and representations. It also covers designing RESTful APIs, including examples from Amazon S3. The document outlines an agenda to discuss introduction, principles, design, implementations, and implementation of RESTful APIs and web services.
rest-api-basics.pptx
rest-api-basics.pptxAgungSutikno1 The document provides an overview of REST API basics and compares traditional web applications to RESTful APIs. Some key points:
- Traditional web apps use HTML and HTTP, replacing entire pages on each request, while RESTful APIs focus on resources and use HTTP methods to perform CRUD operations.
- REST (Representational State Transfer) is an architectural style using URIs to identify resources and HTTP methods to operate on them. It advocates a stateless, cacheable, layered system of web services.
- Examples show how HTTP methods like GET, POST, PUT, PATCH, and DELETE map to CRUD operations on resources, with content types specifying response formats. Status codes indicate success or failure.
Rails Presentation (Anton Dmitriyev)
Rails Presentation (Anton Dmitriyev)True-Vision Ruby on Rails is an open-source web framework that is optimized for programmer happiness and productivity. It allows developers to write code more easily by favoring conventions over rigid configuration. Ruby on Rails uses conventions to make assumptions about how apps should be structured, reducing the amount of configuration code needed.
REST and Resource Oriented Architecture - okcDG March 2008
REST and Resource Oriented Architecture - okcDG March 2008Ryan Hoegg This document discusses REST (Representational State Transfer), a architectural style for distributed hypermedia systems, and Resource Oriented Architecture (ROA), which provides concrete rules for building RESTful web services. It explains key REST concepts like addressable resources, uniform interface, statelessness, and hypermedia. It also provides an example of designing a RESTful pizza delivery web service using ROA principles like naming resources with URIs and designing representations for resources.
Restful Best Practices
Restful Best PracticesBelighted These are the slides of our talk at Fosdem 2008 (http://fosdem.org).
We explain what REST is, how it is used in Rails, and finally we give some tips on how to architecture your application so that it follows the REST philosophy.
[2015/2016] The REST architectural style
[2015/2016] The REST architectural styleIvano Malavolta This presentation has been developed in the context of the Mobile Applications Development course, DISIM, University of L'Aquila (Italy), Spring 2016.
http://www.ivanomalavolta.com
Creating Restful Web Services with restish
Creating Restful Web Services with restishGrig Gheorghiu This document discusses creating RESTful web services using the restish framework. It provides an overview of REST principles like resources, representations, and the uniform interface. It also demonstrates building a simple TODO list management application with restish and discusses testing and deploying restish applications.
Rest APIs Training
Rest APIs TrainingShekhar Kumar This document provides an overview of RESTful APIs and related concepts:
- It describes HTTP methods like GET, POST, PUT, DELETE and PATCH that are used to interact with resources over HTTP.
- It explains HTTP status codes for success (2xx), client errors (4xx) and server errors (5xx).
- It discusses REST architectural constraints like client-server, statelessness, caching, uniform interface, content negotiation and hypermedia.
- It covers concepts like resources, URIs, relationships between resources, content negotiation, versioning APIs, and HATEOAS to make APIs self-descriptive.
What is rest. Why is it part of the Rails way?. Railsconf 2014. Javier Ramirez
What is rest. Why is it part of the Rails way?. Railsconf 2014. Javier Ramirezjavier ramirez When David Heinemeier Hansson started talking about REST in 2006, little could we suspect it'd become such a central part of Rails (and of web development in general). Back then a web service meant something you coded using XML and SOAP. Those were dark times. REST changed it all.
In this talk, I'll explain REST for beginners, I'll talk about why it is such an important architecture, and I'll show all the nice things Rails offers you for building a RESTful application or a RESTful API.
REST Basics
REST BasicsIvano Malavolta Mobile applications Development - Lecture 14
REST Basics
This presentation has been developed in the context of the Mobile Applications Development course at the Computer Science Department of the University of L’Aquila (Italy).
http://www.di.univaq.it/malavolta
Finding Restfulness - Madrid.rb April 2014
Finding Restfulness - Madrid.rb April 2014samlown The document discusses the development of Restfulness, a Ruby library for building REST APIs. It begins by outlining some irritations the author had with existing Rails controllers and API frameworks like Grape. This inspired the author to create Restfulness with a focus on simplicity, treating resources as the focus of requests, and closely following REST and HTTP principles. The summary describes the key components of Restfulness, including simple routing based on resources, separating path, query, and body parameters, and callbacks that control the flow of requests. It also mentions how Restfulness implements error handling and can be run both standalone or as part of Rails applications.
Rest Vs Soap Yawn2289
Rest Vs Soap Yawn2289Kalyan Vijay Kumar Pasumarthi ReST is an architectural style defined by a set of constraints including being client-server, stateless, cacheable, and having a uniform interface. It favors directly addressing resources over remote procedure calls and aims to make systems more scalable and loosely coupled. While sometimes seen as weak due to performance and customization issues, ReST architectures also provide benefits like low barriers to entry and being easier to develop and maintain.
REST e Resource Oriented Architectures
REST e Resource Oriented ArchitecturesGrUSP REST è lo stile architetturale a cui aderisce quello che oggi noi chiamiamo Web. Uno dei problemi storici della programmazione di applicazioni web è l’impendance mismatch fra vari modelli computazionali e di dati (REST, Object Oriented, Relational Model, ecc…). Questa sessione ha lo scopo di evidenziare la problematica con relativi esempi, soluzioni e risultati ottenuti con l’utilizzo di PHP.
Resource Oriented Architectures
Resource Oriented ArchitecturesGabriele Lana This document discusses REST (Representational State Transfer) and resource-oriented architectures. It provides examples of designing RESTful APIs and services using common REST constraints like URIs to identify resources, HTTP methods to manipulate resources, and resource representations. The key aspects covered are modeling the domain as resources, designing URIs, exposing a uniform interface, designing representations, and common interaction flows and error conditions.
REST and RESTful Services
REST and RESTful ServicesDamian T. Gordon Representational State Transfer (REST) is an architectural style where resources are accessed via standard HTTP methods like GET, POST, PUT, and DELETE. Resources can represent both concrete state like a database record or abstract state like a service element. REST services expose resources through a uniform interface and are stateless, cacheable, and layered.
Rest
RestArnon Rotem-Gal-Oz REST (Representational State Transfer) is an architectural style for building distributed systems. It uses stateless operations to manipulate representations of resources through a standardized interface and uniform identification of resources. Common REST implementations use HTTP methods like GET, PUT, POST and DELETE to operate on resources identified in requests by URIs. REST aims to provide a simple and lightweight interface between components to improve scalability for distributed systems.
More from Yohei Yamamoto (8)
WebAPIのこれまでとこれから
WebAPIのこれまでとこれからYohei Yamamoto 2014-07-11 API Meetup #1
http://api-meetup.doorkeeper.jp/events/12768
Ad
Recently uploaded (20)
Cybersecurity Fundamentals: Apprentice - Palo Alto Certificate
Cybersecurity Fundamentals: Apprentice - Palo Alto CertificateVICTOR MAESTRE RAMIREZ Cybersecurity Fundamentals: Apprentice - Palo Alto Certificate
Evaluation Challenges in Using Generative AI for Science & Technical Content
Evaluation Challenges in Using Generative AI for Science & Technical ContentPaul Groth Evaluation Challenges in Using Generative AI for Science & Technical Content.
Foundation Models show impressive results in a wide-range of tasks on scientific and legal content from information extraction to question answering and even literature synthesis. However, standard evaluation approaches (e.g. comparing to ground truth) often don't seem to work. Qualitatively the results look great but quantitive scores do not align with these observations. In this talk, I discuss the challenges we've face in our lab in evaluation. I then outline potential routes forward.
Protecting Your Sensitive Data with Microsoft Purview - IRMS 2025
Protecting Your Sensitive Data with Microsoft Purview - IRMS 2025Nikki Chapple Session | Protecting Your Sensitive Data with Microsoft Purview: Practical Information Protection and DLP Strategies
Presenter | Nikki Chapple (MVP| Principal Cloud Architect CloudWay) & Ryan John Murphy (Microsoft)
Event | IRMS Conference 2025
Format | Birmingham UK
Date | 18-20 May 2025
In this closing keynote session from the IRMS Conference 2025, Nikki Chapple and Ryan John Murphy deliver a compelling and practical guide to data protection, compliance, and information governance using Microsoft Purview. As organizations generate over 2 billion pieces of content daily in Microsoft 365, the need for robust data classification, sensitivity labeling, and Data Loss Prevention (DLP) has never been more urgent.
This session addresses the growing challenge of managing unstructured data, with 73% of sensitive content remaining undiscovered and unclassified. Using a mountaineering metaphor, the speakers introduce the “Secure by Default” blueprint—a four-phase maturity model designed to help organizations scale their data security journey with confidence, clarity, and control.
🔐 Key Topics and Microsoft 365 Security Features Covered:
Microsoft Purview Information Protection and DLP
Sensitivity labels, auto-labeling, and adaptive protection
Data discovery, classification, and content labeling
DLP for both labeled and unlabeled content
SharePoint Advanced Management for workspace governance
Microsoft 365 compliance center best practices
Real-world case study: reducing 42 sensitivity labels to 4 parent labels
Empowering users through training, change management, and adoption strategies
🧭 The Secure by Default Path – Microsoft Purview Maturity Model:
Foundational – Apply default sensitivity labels at content creation; train users to manage exceptions; implement DLP for labeled content.
Managed – Focus on crown jewel data; use client-side auto-labeling; apply DLP to unlabeled content; enable adaptive protection.
Optimized – Auto-label historical content; simulate and test policies; use advanced classifiers to identify sensitive data at scale.
Strategic – Conduct operational reviews; identify new labeling scenarios; implement workspace governance using SharePoint Advanced Management.
🎒 Top Takeaways for Information Management Professionals:
Start secure. Stay protected. Expand with purpose.
Simplify your sensitivity label taxonomy for better adoption.
Train your users—they are your first line of defense.
Don’t wait for perfection—start small and iterate fast.
Align your data protection strategy with business goals and regulatory requirements.
💡 Who Should Watch This Presentation?
This session is ideal for compliance officers, IT administrators, records managers, data protection officers (DPOs), security architects, and Microsoft 365 governance leads. Whether you're in the public sector, financial services, healthcare, or education.
🔗 Read the blog: https://nikkichapple.com/irms-conference-2025/
ELNL2025 - Unlocking the Power of Sensitivity Labels - A Comprehensive Guide....
ELNL2025 - Unlocking the Power of Sensitivity Labels - A Comprehensive Guide....Jasper Oosterveld Sensitivity labels, powered by Microsoft Purview Information Protection, serve as the foundation for classifying and protecting your sensitive data within Microsoft 365. Their importance extends beyond classification and play a crucial role in enforcing governance policies across your Microsoft 365 environment. Join me, a Data Security Consultant and Microsoft MVP, as I share practical tips and tricks to get the full potential of sensitivity labels. I discuss sensitive information types, automatic labeling, and seamless integration with Data Loss Prevention, Teams Premium, and Microsoft 365 Copilot.
AI Trends - Mary Meeker
AI Trends - Mary MeekerRazin Mustafiz Source: https://www.bondcap.com/reports/tai
Measuring Microsoft 365 Copilot and Gen AI Success
Measuring Microsoft 365 Copilot and Gen AI SuccessNikki Chapple Session | Measuring Microsoft 365 Copilot and Gen AI Success with Viva Insights and Purview
Presenter | Nikki Chapple 2 x MVP and Principal Cloud Architect at CloudWay
Event | European Collaboration Conference 2025
Format | In person Germany
Date | 28 May 2025
📊 Measuring Copilot and Gen AI Success with Viva Insights and Purview
Presented by Nikki Chapple – Microsoft 365 MVP & Principal Cloud Architect, CloudWay
How do you measure the success—and manage the risks—of Microsoft 365 Copilot and Generative AI (Gen AI)? In this ECS 2025 session, Microsoft MVP and Principal Cloud Architect Nikki Chapple explores how to go beyond basic usage metrics to gain full-spectrum visibility into AI adoption, business impact, user sentiment, and data security.
🎯 Key Topics Covered:
Microsoft 365 Copilot usage and adoption metrics
Viva Insights Copilot Analytics and Dashboard
Microsoft Purview Data Security Posture Management (DSPM) for AI
Measuring AI readiness, impact, and sentiment
Identifying and mitigating risks from third-party Gen AI tools
Shadow IT, oversharing, and compliance risks
Microsoft 365 Admin Center reports and Copilot Readiness
Power BI-based Copilot Business Impact Report (Preview)
📊 Why AI Measurement Matters: Without meaningful measurement, organizations risk operating in the dark—unable to prove ROI, identify friction points, or detect compliance violations. Nikki presents a unified framework combining quantitative metrics, qualitative insights, and risk monitoring to help organizations:
Prove ROI on AI investments
Drive responsible adoption
Protect sensitive data
Ensure compliance and governance
🔍 Tools and Reports Highlighted:
Microsoft 365 Admin Center: Copilot Overview, Usage, Readiness, Agents, Chat, and Adoption Score
Viva Insights Copilot Dashboard: Readiness, Adoption, Impact, Sentiment
Copilot Business Impact Report: Power BI integration for business outcome mapping
Microsoft Purview DSPM for AI: Discover and govern Copilot and third-party Gen AI usage
🔐 Security and Compliance Insights: Learn how to detect unsanctioned Gen AI tools like ChatGPT, Gemini, and Claude, track oversharing, and apply eDLP and Insider Risk Management (IRM) policies. Understand how to use Microsoft Purview—even without E5 Compliance—to monitor Copilot usage and protect sensitive data.
📈 Who Should Watch: This session is ideal for IT leaders, security professionals, compliance officers, and Microsoft 365 admins looking to:
Maximize the value of Microsoft Copilot
Build a secure, measurable AI strategy
Align AI usage with business goals and compliance requirements
🔗 Read the blog https://nikkichapple.com/measuring-copilot-gen-ai/
Grannie’s Journey to Using Healthcare AI Experiences
Grannie’s Journey to Using Healthcare AI ExperiencesLauren Parr AI offers transformative potential to enhance our long-time persona Grannie’s life, from healthcare to social connection. This session explores how UX designers can address unmet needs through AI-driven solutions, ensuring intuitive interfaces that improve safety, well-being, and meaningful interactions without overwhelming users.
Multistream in SIP and NoSIP @ OpenSIPS Summit 2025
Multistream in SIP and NoSIP @ OpenSIPS Summit 2025Lorenzo Miniero Slides for my "Multistream support in the Janus SIP and NoSIP plugins" presentation at the OpenSIPS Summit 2025 event.
They describe my efforts refactoring the Janus SIP and NoSIP plugins to allow for the gatewaying of an arbitrary number of audio/video streams per call (thus breaking the current 1-audio/1-video limitation), plus some additional considerations on what this could mean when dealing with application protocols negotiated via SIP as well.
Agentic AI Explained: The Next Frontier of Autonomous Intelligence & Generati...
Agentic AI Explained: The Next Frontier of Autonomous Intelligence & Generati...Aaryan Kansari Agentic AI Explained: The Next Frontier of Autonomous Intelligence & Generative AI
Discover Agentic AI, the revolutionary step beyond reactive generative AI. Learn how these autonomous systems can reason, plan, execute, and adapt to achieve human-defined goals, acting as digital co-workers. Explore its promise, key frameworks like LangChain and AutoGen, and the challenges in designing reliable and safe AI agents for future workflows.
Sticky Note Bullets:
Definition: Next stage beyond ChatGPT-like systems, offering true autonomy.
Core Function: Can "reason, plan, execute and adapt" independently.
Distinction: Proactive (sets own actions for goals) vs. Reactive (responds to prompts).
Promise: Acts as "digital co-workers," handling grunt work like research, drafting, bug fixing.
Industry Outlook: Seen as a game-changer; Deloitte predicts 50% of companies using GenAI will have agentic AI pilots by 2027.
Key Frameworks: LangChain, Microsoft's AutoGen, LangGraph, CrewAI.
Development Focus: Learning to think in workflows and goals, not just model outputs.
Challenges: Ensuring reliability, safety; agents can still hallucinate or go astray.
Best Practices: Start small, iterate, add memory, keep humans in the loop for final decisions.
Use Cases: Limited only by imagination (e.g., drafting business plans, complex simulations).
Create Your First AI Agent with UiPath Agent Builder
Create Your First AI Agent with UiPath Agent BuilderDianaGray10 Join us for an exciting virtual event where you'll learn how to create your first AI Agent using UiPath Agent Builder. This session will cover everything you need to know about what an agent is and how easy it is to create one using the powerful AI-driven UiPath platform. You'll also discover the steps to successfully publish your AI agent. This is a wonderful opportunity for beginners and enthusiasts to gain hands-on insights and kickstart their journey in AI-powered automation.
LSNIF: Locally-Subdivided Neural Intersection Function
LSNIF: Locally-Subdivided Neural Intersection FunctionTakahiro Harada Neural representations have shown the potential to accelerate ray casting in a conventional ray-tracing-based rendering pipeline. We introduce a novel approach called Locally-Subdivided Neural Intersection Function (LSNIF) that replaces bottom-level BVHs used as traditional geometric representations with a neural network. Our method introduces a sparse hash grid encoding scheme incorporating geometry voxelization, a scene-agnostic training data collection, and a tailored loss function. It enables the network to output not only visibility but also hit-point information and material indices. LSNIF can be trained offline for a single object, allowing us to use LSNIF as a replacement for its corresponding BVH. With these designs, the network can handle hit-point queries from any arbitrary viewpoint, supporting all types of rays in the rendering pipeline. We demonstrate that LSNIF can render a variety of scenes, including real-world scenes designed for other path tracers, while achieving a memory footprint reduction of up to 106.2x compared to a compressed BVH.
https://arxiv.org/abs/2504.21627
UiPath Community Berlin: Studio Tips & Tricks and UiPath Insights
UiPath Community Berlin: Studio Tips & Tricks and UiPath InsightsUiPathCommunity Join the UiPath Community Berlin (Virtual) meetup on May 27 to discover handy Studio Tips & Tricks and get introduced to UiPath Insights. Learn how to boost your development workflow, improve efficiency, and gain visibility into your automation performance.
📕 Agenda:
- Welcome & Introductions
- UiPath Studio Tips & Tricks for Efficient Development
- Best Practices for Workflow Design
- Introduction to UiPath Insights
- Creating Dashboards & Tracking KPIs (Demo)
- Q&A and Open Discussion
Perfect for developers, analysts, and automation enthusiasts!
This session streamed live on May 27, 18:00 CET.
Check out all our upcoming UiPath Community sessions at:
👉 https://community.uipath.com/events/
Join our UiPath Community Berlin chapter:
👉 https://community.uipath.com/berlin/
Nix(OS) for Python Developers - PyCon 25 (Bologna, Italia)
Nix(OS) for Python Developers - PyCon 25 (Bologna, Italia)Peter Bittner How do you onboard new colleagues in 2025? How long does it take? Would you love a standardized setup under version control that everyone can customize for themselves? A stable desktop setup, reinstalled in just minutes. It can be done.
This talk was given in Italian, 29 May 2025, at PyCon 25, Bologna, Italy. All slides are provided in English.
Original slides at https://slides.com/bittner/pycon25-nixos-for-python-developers
STKI Israel Market Study 2025 final v1 version
STKI Israel Market Study 2025 final v1 versionDr. Jimmy Schwarzkopf nnual (33 years) study of the Israeli Enterprise / public IT market. Covering sections on Israeli Economy, IT trends 2026-28, several surveys (AI, CDOs, OCIO, CTO, staffing cyber, operations and infra) plus rankings of 760 vendors on 160 markets (market sizes and trends) and comparison of products according to support and market penetration.
Offshore IT Support: Balancing In-House and Offshore Help Desk Technicians
Offshore IT Support: Balancing In-House and Offshore Help Desk Techniciansjohn823664 In today's always-on digital environment, businesses must deliver seamless IT support across time zones, devices, and departments. This SlideShare explores how companies can strategically combine in-house expertise with offshore talent to build a high-performing, cost-efficient help desk operation.
From the benefits and challenges of offshore support to practical models for integrating global teams, this presentation offers insights, real-world examples, and key metrics for success. Whether you're scaling a startup or optimizing enterprise support, discover how to balance cost, quality, and responsiveness with a hybrid IT support strategy.
Perfect for IT managers, operations leads, and business owners considering global help desk solutions.
Cognitive Chasms - A Typology of GenAI Failure Failure Modes
Cognitive Chasms - A Typology of GenAI Failure Failure ModesDr. Tathagat Varma My talk on Cognitive Chasms at the brownbag session inside Walmart
Jeremy Millul - A Talented Software Developer
Jeremy Millul - A Talented Software DeveloperJeremy Millul Jeremy Millul is a talented software developer based in NYC, known for leading impactful projects such as a Community Engagement Platform and a Hiking Trail Finder. Using React, MongoDB, and geolocation tools, Jeremy delivers intuitive applications that foster engagement and usability. A graduate of NYU’s Computer Science program, he brings creativity and technical expertise to every project, ensuring seamless user experiences and meaningful results in software development.
GDG Cloud Southlake #43: Tommy Todd: The Quantum Apocalypse: A Looming Threat...
GDG Cloud Southlake #43: Tommy Todd: The Quantum Apocalypse: A Looming Threat...James Anderson The Quantum Apocalypse: A Looming Threat & The Need for Post-Quantum Encryption
We explore the imminent risks posed by quantum computing to modern encryption standards and the urgent need for post-quantum cryptography (PQC).
Bio: With 30 years in cybersecurity, including as a CISO, Tommy is a strategic leader driving security transformation, risk management, and program maturity. He has led high-performing teams, shaped industry policies, and advised organizations on complex cyber, compliance, and data protection challenges.
UiPath Community Zurich: Release Management and Build Pipelines
UiPath Community Zurich: Release Management and Build PipelinesUiPathCommunity Ensuring robust, reliable, and repeatable delivery processes is more critical than ever - it's a success factor for your automations and for automation programmes as a whole. In this session, we’ll dive into modern best practices for release management and explore how tools like the UiPathCLI can streamline your CI/CD pipelines. Whether you’re just starting with automation or scaling enterprise-grade deployments, our event promises to deliver helpful insights to you. This topic is relevant for both on-premise and cloud users - as well as for automation developers and software testers alike.
📕 Agenda:
- Best Practices for Release Management
- What it is and why it matters
- UiPath Build Pipelines Deep Dive
- Exploring CI/CD workflows, the UiPathCLI and showcasing scenarios for both on-premise and cloud
- Discussion, Q&A
👨🏫 Speakers
Roman Tobler, CEO@ Routinuum
Johans Brink, CTO@ MvR Digital Workforce
We look forward to bringing best practices and showcasing build pipelines to you - and to having interesting discussions on this important topic!
If you have any questions or inputs prior to the event, don't hesitate to reach out to us.
This event streamed live on May 27, 16:00 pm CET.
Check out all our upcoming UiPath Community sessions at:
👉 https://community.uipath.com/events/
Join UiPath Community Zurich chapter:
👉 https://community.uipath.com/zurich/
Contributing to WordPress With & Without Code.pptx
Contributing to WordPress With & Without Code.pptxPatrick Lumumba Contributing to WordPress: Making an Impact on the Test Team—With or Without Coding Skills
WordPress survives on collaboration, and the Test Team plays a very important role in ensuring the CMS is stable, user-friendly, and accessible to everyone.
This talk aims to deconstruct the myth that one has to be a developer to contribute to WordPress. In this session, I will share with the audience how to get involved with the WordPress Team, whether a coder or not.
We’ll explore practical ways to contribute, from testing new features, and patches, to reporting bugs. By the end of this talk, the audience will have the tools and confidence to make a meaningful impact on WordPress—no matter the skill set.
Ad