The document describes the RoomWare server software, which acts as a central hub allowing various "devices" to communicate through message passing. The key points are:
1. Devices connect to the server via "mediators" that translate data between the device and server formats.
2. The server creates a "plugin" for each mediator to handle communication. Plugins subscribe to event and request lists to receive relevant messages.
3. Messages are distributed by the server "kernel" to the appropriate plugins based on subscriptions. This allows any device to communicate with any other device.
This plugin allows you to discover your ESX, Datastores and VM of your VMware architecture automatically. This plugin also has a lot of modules to monitor your virtual architecture. For more information visit the following webpage: http://pandorafms.com/index.php?sec=Library&sec2=repository&lng=en&action=view_PUI&id_PUI=269
CIS14: Trusted Tokens: An Identity Game ChangerCloudIDSummit
Steven Lewis,
Advanced Systems Engineering Corporation
(ASEC)
Real-world contextual use case scenarios and the associated
token standards, specifications, and integration approach to
implement interoperable trust chains and identity propagation
within and across operating environments.
Meet Remaiten : Malware Builds Botnet on Linux based routers and potentially ...APNIC
Meet Remaiten : Malware Builds Botnet on Linux based routers and potentially other (IoT) devices by Afifa Abbas.
A presentation given at APNIC 42's FIRST TC Security Session (2) session on Wednesday, 5 October 2016.
Developing IoT with Zephyr is a journey from hardware all the way to application. It involves multiple teams and expertise, from hardware to cloud and application development. This talk will cover the options for getting a Zephyr app connected (WiFi, Ethernet, Cellular), selecting the right data encoding (JSON/CBOR), securing the data transfer (DTLS/TLS), and choosing a protocol (HTTP/MQTT/COAP). But that’s not the end of the story, the cloud needs to manage devices allowed to connect, consume the data being received, open up options for using that data, and be aware of the continued state of the hardware. And once you have the data you need to build a user-facing application on top of it. Understanding this lifecycle will help us as developers to make good choices on what Zephyr provides, helping ensure successful IoT projects.
Creating responsive and interactive web applications has always been one of my hidden dreams. One of the biggest show stopper has been the communication between server and clients. The rise of websockets now open some space for a brand new kind of applications; but we need a library that makes things 'easy' for us and that is able to fall back on previous solutions when the latest technologies are not available.
Suddenly on the ASP.NET scene appears SignalR: a persistence connection abstraction library that helps ASP.NET developers deal with 'real time' client-server communication sceneries.
This plugin allows you to discover your ESX, Datastores and VM of your VMware architecture automatically. This plugin also has a lot of modules to monitor your virtual architecture. For more information visit the following webpage: http://pandorafms.com/index.php?sec=Library&sec2=repository&lng=en&action=view_PUI&id_PUI=269
CIS14: Trusted Tokens: An Identity Game ChangerCloudIDSummit
Steven Lewis,
Advanced Systems Engineering Corporation
(ASEC)
Real-world contextual use case scenarios and the associated
token standards, specifications, and integration approach to
implement interoperable trust chains and identity propagation
within and across operating environments.
Meet Remaiten : Malware Builds Botnet on Linux based routers and potentially ...APNIC
Meet Remaiten : Malware Builds Botnet on Linux based routers and potentially other (IoT) devices by Afifa Abbas.
A presentation given at APNIC 42's FIRST TC Security Session (2) session on Wednesday, 5 October 2016.
Developing IoT with Zephyr is a journey from hardware all the way to application. It involves multiple teams and expertise, from hardware to cloud and application development. This talk will cover the options for getting a Zephyr app connected (WiFi, Ethernet, Cellular), selecting the right data encoding (JSON/CBOR), securing the data transfer (DTLS/TLS), and choosing a protocol (HTTP/MQTT/COAP). But that’s not the end of the story, the cloud needs to manage devices allowed to connect, consume the data being received, open up options for using that data, and be aware of the continued state of the hardware. And once you have the data you need to build a user-facing application on top of it. Understanding this lifecycle will help us as developers to make good choices on what Zephyr provides, helping ensure successful IoT projects.
Creating responsive and interactive web applications has always been one of my hidden dreams. One of the biggest show stopper has been the communication between server and clients. The rise of websockets now open some space for a brand new kind of applications; but we need a library that makes things 'easy' for us and that is able to fall back on previous solutions when the latest technologies are not available.
Suddenly on the ASP.NET scene appears SignalR: a persistence connection abstraction library that helps ASP.NET developers deal with 'real time' client-server communication sceneries.
This presentation covers the current developments regarding privacy. It states that you are no longer anonymous and most of your whereabouts can be reconstructed.
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex ProofsAlex Pruden
This paper presents Reef, a system for generating publicly verifiable succinct non-interactive zero-knowledge proofs that a committed document matches or does not match a regular expression. We describe applications such as proving the strength of passwords, the provenance of email despite redactions, the validity of oblivious DNS queries, and the existence of mutations in DNA. Reef supports the Perl Compatible Regular Expression syntax, including wildcards, alternation, ranges, capture groups, Kleene star, negations, and lookarounds. Reef introduces a new type of automata, Skipping Alternating Finite Automata (SAFA), that skips irrelevant parts of a document when producing proofs without undermining soundness, and instantiates SAFA with a lookup argument. Our experimental evaluation confirms that Reef can generate proofs for documents with 32M characters; the proofs are small and cheap to verify (under a second).
Paper: https://eprint.iacr.org/2023/1886
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
2. Why change?
• Easier to develop and plugin new “Devices”
• More flexibility to connect anything to
anything
• No dependency on Java
• Stable RoomWare Server core / new
devices are developed outside the
RoomWare core
3. Offering freedom for all
• Everything is message based
• For the Server any RoomWare Device is
like any other RoomWare Device
• Any “Device” can address any other
“Device”
• Any “Device” can send messages to any
other “Device” to state their events, their
wishes and needs
4. Using sockets
• Sockets are “pipelines” over a TCP/IP connection
• They are bi-directional and platform independent
• They can be created in PhP, Java, Flash, C#, Python
and so forth
• They run locally without a Web Server
• They have a proper event-model for pushing data
from “A” to “B” and back
• They will be used to connect anything to anything,
using the RoomWare server as a switch
10. And Mediators
Device Device
M M
Device M RoomWare M Device
Server
M M
Device Device
11. Mediators
Events, Requests, Responses
Device M M Device
• Mediators translate the data to something
the other party can understand
• Communication is between mediators
12. Mediator
• Connects a “Device” with the RoomWare
server
• Translates “Device” data to XML
• Translate data from other sources to
actions in the “Device”
• Communicates to RW Server via Sockets
• Data is standard XML
• Communication is Bi-directional
• Event or Request based
• Device can be another RoomWare Server
13. Devices
Messages, instructions, data
Device Device
• Devices can be anything (sensors, web
sites, desktop applications, electronics,
readers) and communicate in any protocol
• Very likely they do not understand each
other without a Mediator
14. Messages
<request name="getbluetoothlist" context="" devicename="BT reader Room2">
<data>
</data> <event name="newbluetoothdevice" context="request" devicename="BT reade
</request>
<data>
</data>
</event>
• Each “Device” can send to- and recieve
messages from any other devices
• A message can be a Request, a Response or
an Event
• Each message can contain data and
instructions
15. Message types
• <event: sent by device, to all listeners
• <request: named request from one device to all
listeners. Has a “context”
• <response: named response from listener to a
request, sent only to requester. Reflexts the
context as given by request
16. Message header
• Headers: <event <request <response
• Header data:
• listener: name of request, response, event listener
• context: local context - used to split responses / link them to a
context
• mediatorname: logical name of mediator in mediator via mediator
definition XML
• For response
• destinationid: specific address of device to send response to
• By RoomWare kernal - always added to message
• sourceid: ID of device assigned by kernal
• timeposted: moment the RoomWare kernal passed the request /
response / event
17. Inner Workings
RoomWare Server
Kernel
The bridge between the mediator
Plugin
and the kernel
Software that mediates between the
Mediator
RoomWare server and the “Device”
Device Can be websites, readers, sensors, etc..
18. Plugins
Events, Requests, Responses
Device M P K P M Device
RoomWare
Server M Mediator
P Plugin
K Kernel
19. Plugins
• A Plugin represents a Mediator and via the
Mediator the RoomWare Device
• When Mediators connect to the
RoomWare Server they get their own
Plugin in the RoomWare Server
• Each Plugin recieves an unique number
from the RoomWare server for internal
communication
• Each Plugin is subscribed to one or more
lists to recieve Events and Requests
20. Plugin “A”
Event
Event Data
Event name
Event list
Event name
Subscriber Plugin “B”
Subscriber Plugin “D”
Subscriber Plugin “N”
22. Plugin “A”
Request
Request Data + Plugin ID Plugin “A”
Request name
Request list Data
Request name
Subscriber Plugin “B” Response
Subscriber Plugin “D” Response
Subscriber Plugin “N” Response
23. Request
• Are broadcasted to anyone who listens
• Have a return address
• Recieve a Response with the requested
data
24. The Kernel
Device Device
M M
P P
Device M P K
P P M Device
P P
M M
Device Device
RoomWare
Server
25. Kernel
• The Kernel is “Communication Central”
• It distributes the Messages to the right
Plugins
• It has no memory of what has happend
before
26. More details
• The next slides show how the plugin is
connected to the mediator and how
communication takes place
27. RoomWare Server
Post
Message
handler
Recieve
Socket
Plugin
Mediator
Socket
Post
Recieve Message Device Device
Device
handler handler driver
28. Mediators and Plugins
• The Mediator connects each “Device” to the
RoomWare
• Each Mediator consists of a Message Handler and a
Socket connector
• For each Mediator, the RoomWare server creates
a Plugin to deal with the internal communication
• The connection between a Mediator and a Plugin
is done via a Socket
• The Plugin sends and recieves Messages to and
from the Kernel and to and from the Mediator
• The Kernel acts like a mail man and handles the
actual distribution of messages between Plugins
29. RoomWare Server
Events, Requests, Responses
Plugin Plugin
Post Receive
Message Message
handler handler
Receive Post
Socket Socket
Kernel
Communication
Mediator Mediator
Events, Requests, Responses
“Device” “Device”
Messages, instructions, data
30. Flow
1. A “Device” is connected to a Mediator (software)
2. The Mediator creates a connection to the
RoomWare server via a Socket
3. The RoomWare Server creates a Plugin for the
Mediator
4. This Plugin is registered with a unique ID in the
Kernel
5. Each Mediator passes an XML definition to the
Plugin to state to which Events and Requests it
subscibes to
6. When Mediator “A” sends a relevant message for
Mediator “B” the Kernal will pass that message to
the Plugin of Mediator “B” based on the
subscription to different lists