Developers who work with physical quantities (e.g. in scientific, engineering, medical, manufacturing domains or general business) need to be able to handle measurements of these quantities in their programs.
The Irish Software Show, ( http://epicenter.ie ) Werner Keil: UCUM
Developers who work with physical quantities (such as developers in the scientific, engineering, medical, and manufacturing domains) need to be able to handle measurements of these quantities in their programs.
Inadequate models of physical measurements can lead to significant programmatic errors.
In particular, the practice of modeling a measure as a simple number with no regard to the units it represents creates fragile code. Another developer or another part of the code may misinterpret the number as representing a different unit of measurement. For example, it may be unclear whether a person's weight is expressed in pounds, kilograms, or stones.
Problems multiply once a client has to communicate with one or more servers or services in a Cloud.
This session provides an overview of the UCUM standard and related interoperability efforts like UnitML by OASIs. It also outlines various implementations based on Eclipse, Java Mobile (JSR-256) or OSGi, just to name the most common examples. And looks at ways, different platforms, e.g. .NET/F# and JVM based languages can exchange measurements preserving their value and units.
http://epicenter.ie/2010.html?zone_id=20&mode=agenda&session=143#session
Standards for the Future of Java EmbeddedWerner Keil
The document discusses standards for Java in embedded systems. It covers sensors, machine-to-machine communication, near field communication, security, and questions from the audience. The speaker is introduced as a consultant and open source evangelist who leads several projects related to units of measurement in Java. Examples are given of disasters caused by unit conversion errors, and several past efforts to standardize units of measurement in Java are summarized.
The Eclipse M2M IWG and Standards for the Internet of ThingsWerner Keil
This session highlights how the M2M IWG can play a role in the Internet of Things and Distributed Sensor Web as well as related technologies like Smart Home, Automotive or Transport/Logistics (allowing containers to automatically notify you if e.g. their temperature changes beyond a healthy range;-) We demonstrate how existing Java standards like JSR 256 (Mobile Sensor API) can be improved or replaced towards a new generation of Java Embedded and Mobile.
Taking technologies like the IEEE 1451 "Smart Sensor" standard into consideration, as well as OGC standards like SensorML or The Unified Code for Units of Measurement (UCUM) allowing type and context safe data transfer using various formats and protocols, whether it is XML, JSON or specific M2M protocols like MQTT or OMA-DM.
geecon 2013 - Standards for the Future of Java EmbeddedWerner Keil
This session highlights how Java Embedded can play a role in the Internet of Things and Distributed Sensor Web as well as related technologies like Smart Home or Automotive. We demonstrate how existing Java standards like JSR 256 (Mobile Sensor API) can be modernized and improved towards a new generation of Java Embedded and Mobile. Taking technologies like the IEEE 1451 "Smart Sensor" standard into consideration, as well as OGC standards like SensorML or The Unified Code for Units of Measurement (UCUM) allowing type and context safe data transfer using various formats and protocols, whether it is XML, JSON or specific M2M protocols like MQTT as well as new JSRs like 360 (CLDC 8) and 361 (Java ME Embedded)
JSR 363 - The Answer to Life Science and the Internet of EverythingWerner Keil
Developers who work with quantities (sensor reading from edge devices, scientific, engineering, medical, or manufacturing) need to handle measurements of these quantities in their programs. Inadequate models of physical measurements can lead to programmatic errors. In particular when modelling a measurement as a simple number with no regard to the units it represents creates fragile code. Another developer or part of the system can misinterpret the number as a different unit. For example, it may be unclear whether a person's mass is expressed in pounds, kilograms, or stones. A human reading „10°C“, „10 C“ or simply „10 Degrees“ may interpret each of those correctly. For M2M communication, unless a program contains a „Babel Fish“, such ambiguity would not be acceptable.
Don’t Panic: After programming languages like Ada, C++, Eiffel or F# added type-safe Unit support already, JSR 363, Units of Measurement API will add similar support to the Java Platform, making it competitive for M2M in the Internet of Things with strong emphasis on sensors.
This session provides an overview of popular use cases for the Units of Measurement JSR and implementations on both Java ME 8 Embedded (CLDC 8) and Java SE 8. A Hitchhiker’s guide across places where this JSR helps improve data quality or save lives by ensuring e.g. a patient receives the correct dosage of medicine or smart homes and similar energy saving measures prevents Earth from being destroyed by Global Warming (rather than waiting for a Vogon express route ;-)
M4M 2 the Rescue of M2M - Eclipse DemoCamps Kepler 2013Werner Keil
M4M or Measure 4 Measure, ever since Shakespeare's play with the same name we know, people can be mistaken for one another. A Duke (like the beloved Java mascot) claims to be a monk, the head of a dead pirate is presented to be that of the young hero. So can important information like Units of Measurement be misinterpreted. While humans reading 10°C, 10 C or 10 Degree Celsius, each of those could be interpreted and understood well enough. For M2M communication, unless a program is provided with a large glossary of alternate terms, only ONE of these would be acceptable.
This is where the Unified Code for Units of Measurement (UCUM) among similar approaches like UnitsML, SensorML or a few others are vital for error-free M2M transactions, not just between sensors or measurement devices, but also and especially vehicles or distributed devices.
OSGi Measurement has been around for some time (R3) but never gained as much momentum, as many other bundles of OSGi did. Except for very few use cases in the Embedded or Automotive sector it is practically unused and based on statements by its contributors in the OSGi Alliance to be considered legacy with no plans continue development.
After a brief overview of common M2M errors from Gimli to Mars, This session provides an overview of OSGi Measurement, Eclipse OUMo, what they have in common and where the differences lie. Although most of today's OSGi containers are capable of dealing with units or measurement better and more reliable with UOMo, both can where necessary also exchange information and collaborate. E.g. if legacy devices and code cannot be easily replaced. For this We'll take a look at interoperability between different systems or with other unit technologies and languages like F#, Fantom, Python or Lua.
Standards for the Future of Java Embedded (16:9)Werner Keil
This document discusses standards for the future of Java embedded and summarizes a presentation on the topic. It covers sensors, historic IT errors caused by issues with units of measurement, the Sensor Web and related standards, and JavaCard. SensorML is described as the cornerstone for describing sensors in the Sensor Web. An example SensorML snippet is also provided.
The Irish Software Show, ( http://epicenter.ie ) Werner Keil: UCUM
Developers who work with physical quantities (such as developers in the scientific, engineering, medical, and manufacturing domains) need to be able to handle measurements of these quantities in their programs.
Inadequate models of physical measurements can lead to significant programmatic errors.
In particular, the practice of modeling a measure as a simple number with no regard to the units it represents creates fragile code. Another developer or another part of the code may misinterpret the number as representing a different unit of measurement. For example, it may be unclear whether a person's weight is expressed in pounds, kilograms, or stones.
Problems multiply once a client has to communicate with one or more servers or services in a Cloud.
This session provides an overview of the UCUM standard and related interoperability efforts like UnitML by OASIs. It also outlines various implementations based on Eclipse, Java Mobile (JSR-256) or OSGi, just to name the most common examples. And looks at ways, different platforms, e.g. .NET/F# and JVM based languages can exchange measurements preserving their value and units.
http://epicenter.ie/2010.html?zone_id=20&mode=agenda&session=143#session
Standards for the Future of Java EmbeddedWerner Keil
The document discusses standards for Java in embedded systems. It covers sensors, machine-to-machine communication, near field communication, security, and questions from the audience. The speaker is introduced as a consultant and open source evangelist who leads several projects related to units of measurement in Java. Examples are given of disasters caused by unit conversion errors, and several past efforts to standardize units of measurement in Java are summarized.
The Eclipse M2M IWG and Standards for the Internet of ThingsWerner Keil
This session highlights how the M2M IWG can play a role in the Internet of Things and Distributed Sensor Web as well as related technologies like Smart Home, Automotive or Transport/Logistics (allowing containers to automatically notify you if e.g. their temperature changes beyond a healthy range;-) We demonstrate how existing Java standards like JSR 256 (Mobile Sensor API) can be improved or replaced towards a new generation of Java Embedded and Mobile.
Taking technologies like the IEEE 1451 "Smart Sensor" standard into consideration, as well as OGC standards like SensorML or The Unified Code for Units of Measurement (UCUM) allowing type and context safe data transfer using various formats and protocols, whether it is XML, JSON or specific M2M protocols like MQTT or OMA-DM.
geecon 2013 - Standards for the Future of Java EmbeddedWerner Keil
This session highlights how Java Embedded can play a role in the Internet of Things and Distributed Sensor Web as well as related technologies like Smart Home or Automotive. We demonstrate how existing Java standards like JSR 256 (Mobile Sensor API) can be modernized and improved towards a new generation of Java Embedded and Mobile. Taking technologies like the IEEE 1451 "Smart Sensor" standard into consideration, as well as OGC standards like SensorML or The Unified Code for Units of Measurement (UCUM) allowing type and context safe data transfer using various formats and protocols, whether it is XML, JSON or specific M2M protocols like MQTT as well as new JSRs like 360 (CLDC 8) and 361 (Java ME Embedded)
JSR 363 - The Answer to Life Science and the Internet of EverythingWerner Keil
Developers who work with quantities (sensor reading from edge devices, scientific, engineering, medical, or manufacturing) need to handle measurements of these quantities in their programs. Inadequate models of physical measurements can lead to programmatic errors. In particular when modelling a measurement as a simple number with no regard to the units it represents creates fragile code. Another developer or part of the system can misinterpret the number as a different unit. For example, it may be unclear whether a person's mass is expressed in pounds, kilograms, or stones. A human reading „10°C“, „10 C“ or simply „10 Degrees“ may interpret each of those correctly. For M2M communication, unless a program contains a „Babel Fish“, such ambiguity would not be acceptable.
Don’t Panic: After programming languages like Ada, C++, Eiffel or F# added type-safe Unit support already, JSR 363, Units of Measurement API will add similar support to the Java Platform, making it competitive for M2M in the Internet of Things with strong emphasis on sensors.
This session provides an overview of popular use cases for the Units of Measurement JSR and implementations on both Java ME 8 Embedded (CLDC 8) and Java SE 8. A Hitchhiker’s guide across places where this JSR helps improve data quality or save lives by ensuring e.g. a patient receives the correct dosage of medicine or smart homes and similar energy saving measures prevents Earth from being destroyed by Global Warming (rather than waiting for a Vogon express route ;-)
M4M 2 the Rescue of M2M - Eclipse DemoCamps Kepler 2013Werner Keil
M4M or Measure 4 Measure, ever since Shakespeare's play with the same name we know, people can be mistaken for one another. A Duke (like the beloved Java mascot) claims to be a monk, the head of a dead pirate is presented to be that of the young hero. So can important information like Units of Measurement be misinterpreted. While humans reading 10°C, 10 C or 10 Degree Celsius, each of those could be interpreted and understood well enough. For M2M communication, unless a program is provided with a large glossary of alternate terms, only ONE of these would be acceptable.
This is where the Unified Code for Units of Measurement (UCUM) among similar approaches like UnitsML, SensorML or a few others are vital for error-free M2M transactions, not just between sensors or measurement devices, but also and especially vehicles or distributed devices.
OSGi Measurement has been around for some time (R3) but never gained as much momentum, as many other bundles of OSGi did. Except for very few use cases in the Embedded or Automotive sector it is practically unused and based on statements by its contributors in the OSGi Alliance to be considered legacy with no plans continue development.
After a brief overview of common M2M errors from Gimli to Mars, This session provides an overview of OSGi Measurement, Eclipse OUMo, what they have in common and where the differences lie. Although most of today's OSGi containers are capable of dealing with units or measurement better and more reliable with UOMo, both can where necessary also exchange information and collaborate. E.g. if legacy devices and code cannot be easily replaced. For this We'll take a look at interoperability between different systems or with other unit technologies and languages like F#, Fantom, Python or Lua.
Standards for the Future of Java Embedded (16:9)Werner Keil
This document discusses standards for the future of Java embedded and summarizes a presentation on the topic. It covers sensors, historic IT errors caused by issues with units of measurement, the Sensor Web and related standards, and JavaCard. SensorML is described as the cornerstone for describing sensors in the Sensor Web. An example SensorML snippet is also provided.
M4M 2 the Rescue of M2M (Eclipse DemoCamp Trondheim)Werner Keil
M4M or Measure 4 Measure, ever since Shakespeare's play with the same name we know, people can be mistaken for one another. A Duke (like the beloved Java mascot) claims to be a monk, the head of a dead pirate is presented to be that of the young hero. So can important information like Units of Measurement be misinterpreted. While humans reading 10°C, 10 C or 10 Degree Celsius, each of those could be interpreted and understood well enough. For M2M communication, unless a program is provided with a large glossary of alternate terms, only ONE of these would be acceptable.
This is where the Unified Code for Units of Measurement (UCUM) among similar approaches like UnitsML, SensorML or a few others are vital for error-free M2M transactions, not just between sensors or measurement devices, but also and especially vehicles or distributed devices.
OSGi Measurement has been around for some time (R3) but never gained as much momentum, as many other bundles of OSGi did. Except for very few use cases in the Embedded or Automotive sector it is practically unused and based on statements by its contributors in the OSGi Alliance to be considered legacy with no plans continue development.
After a brief overview of common M2M errors from Gimli to Mars, This session provides an overview of OSGi Measurement, Eclipse OUMo, what they have in common and where the differences lie. Although most of today's OSGi containers are capable of dealing with units or measurement better and more reliable with UOMo, both can where necessary also exchange information and collaborate. E.g. if legacy devices and code cannot be easily replaced. For this We'll take a look at interoperability between different systems or with other unit technologies and languages like F#, Fantom, Python or Lua.
M4M 2 the Rescue of M2M - Eclipse DemoCamps Fall 2013Werner Keil
M4M or Measure 4 Measure, ever since Shakespeare's play with the same name we know, people can be mistaken for one another. A Duke (like the beloved Java mascot) claims to be a monk, the head of a dead pirate is presented to be that of the young hero. So can important information like Units of Measurement be misinterpreted. While humans reading 10°C, 10 C or 10 Degree Celsius, each of those could be interpreted and understood well enough. For M2M communication, unless a program is provided with a large glossary of alternate terms, only ONE of these would be acceptable.
This is where the Unified Code for Units of Measurement (UCUM) among similar approaches like UnitsML, SensorML or a few others are vital for error-free M2M transactions, not just between sensors or measurement devices, but also and especially vehicles or distributed devices.
OSGi Measurement has been around for some time (R3) but never gained as much momentum, as many other bundles of OSGi did. Except for very few use cases in the Embedded or Automotive sector it is practically unused and based on statements by its contributors in the OSGi Alliance to be considered legacy with no plans continue development.
This document discusses unit of measurement frameworks and errors caused by inconsistent unit usage. It provides examples of past disasters where unit conversion errors led to failures, such as the Mars Climate Orbiter that was destroyed due to a mix of metric and imperial units. The document advocates for type-safe unit of measurement support to prevent interface, arithmetic, and conversion errors. It introduces the Eclipse UOMo framework that provides this support across scientific, business, and currency domains through integration with standards like UCUM and ICU4J. The framework was demonstrated for applications involving monetary conversions.
After an looking back at the history of Eclipse OHF and its parts, we're going to learn what happened to them and why.
Beside those going a different path, mainly Open Health Tools (OHT) we take a closer look at the Legacy of OHF at Eclipse, mainly The Spatiotemporal Epidemiological Modeler (STEM) and Units of Measurement support from UOMo and related standards like the Unified Code for Units of Measure (UCUM)
M2M, Sensor Web, Observations and MeasurementsWerner Keil
M4M or Measure 4 Measure, ever since Shakespeare's play with the same name we know, people can be mistaken for one another. A Duke (like the beloved Java mascot) claims to be a monk, the head of a dead pirate is presented to be that of the young hero. So can important information like Units of Measurement be misinterpreted. While humans reading 10°C, 10 C or 10 Degree Celsius, each of those could be interpreted and understood well enough. For M2M communication, unless a program is provided with a large glossary of alternate terms, only ONE of these would be acceptable.
Slides of the JCP EC F2F in January 2014 proposing the idea of a Units of Measurement JSR, recently approved as JSR 363: https://jcp.org/en/jsr/detail?id=363
Groovy founder Guillaume Laforge built on top of the Java standard proposal for type safe Units of Measurements, JSR-275 with his case study of a Domain-Specific Language for unit manipulations some while ago.
Based on Unit-API the successor to JSR-275, and its leading Open Source implementation Eclipse UOMo together with Xtext/TS we'll see, how a similar DSL for unit manipulations could be created with Xtext. As well as other languages including Groovy or Scala.
The Quantified UOMo - Eclipse DemoCamp Trondheim 2015Werner Keil
The document discusses units of measurement in software and introduces the Quantified UOMo project. It provides an overview of prior work on units of measurement in APIs and frameworks. It then demonstrates the UOMo project, which provides a type-safe units of measurement library and implements the JSR-363 Units of Measurement API. Examples are given for uses in healthcare, fitness, smart homes, and quantified self-tracking.
ETSI TC MTS Contribution to Testing in IoT and Edge ComputingAxel Rennoch
The document discusses testing in IoT and edge computing. It motivates the need for standardized testing approaches given the high quality and confidence required for IoT and edge communication protocols and configurations. It envisions computing standards being accompanied by defined test scenarios and catalogs using standardized specification techniques. Existing testing approaches from domains like mobile networks can be applied, and work has been completed on test specifications for protocols like CoAP and MQTT. However, distributed and heterogeneous edge architectures present specific challenges for testing distributed systems, edge node management, and performance under resource restrictions at the IoT layer.
This document provides an introduction to wireless sensor networks (WSNs). It discusses the basic concepts and definitions of WSNs, including sensors, transducers, and actuators. It also describes popular sensor node platforms, standardization efforts like ZigBee and 6LoWPAN, and WSN architectures. The document is intended to discuss the objectives, concepts, platforms, standards, protocols, applications, and design factors of WSNs.
Semantically-Enabling the Web of Things: The W3C Semantic Sensor Network Onto...Laurent Lefort
Presentation of the SSN XG results at eResearch Australia 2011 https://eresearchau.files.wordpress.com/2012/06/74-semantically-enabling-the-web-of-things-the-w3c-semantic-sensor-network-ontology.pdf
Technology Insertion: A Well-Grounded Approach to Implementing Out of this Wo...Society of Women Engineers
The document discusses a methodology for incorporating new technologies into products and systems. It introduces Technology Readiness Levels (TRL), Integration Readiness Levels (IRL), and System Readiness Levels (SRL) as metrics to measure the maturity of individual technologies, their integration, and the overall system. The approach involves identifying customer needs, prioritizing technologies, and systematically maturing technologies from the component to system level. Examples are provided of NASA's use of TRLs and how Honeywell has incorporated new technologies like control moment gyros and vibration isolation mechanisms into spacecraft. The importance of integrating mature subsystems while following a systems engineering process is emphasized to achieve a high system readiness.
This document discusses the Open Platform for the Engineering of Critical Embedded Systems (OPEES) project. The main objectives of OPEES are to ensure long-term availability of open source tools for critical systems and support them for the entire lifecycle of very long-lived products, which can last up to 78 years. OPEES aims to build a sustainable ecosystem around these technologies by federating industrial users and service providers. This will help avoid vendor lock-in and allow common platforms to be shared. OPEES will implement additional features like community management, ecosystem development focused on industrial users, and processes for long-term support and maturity assessment of tools. The OPEES project involves 35 members from 5 European countries working to
This document discusses future directions for OpenSees. It outlines plans to release a Python interpreter for OpenSees in addition to the existing Tcl interpreter. It also discusses developing an integrated development environment called OpenSeesIDE that will include a file editor, interpreters and a 3D renderer. Finally, it describes a new organization called the SimCenter that will develop computational modeling and simulation applications using OpenSees, including applications for uncertainty quantification, performance based engineering and community resiliency.
Emerging standards and support organizations within engineering simulation Modelon
This document discusses emerging standards and support organizations within engineering simulation. It summarizes several key standards including SysML, Modelica, FMI, STEP, and OSLC. It discusses the goals and benefits of standards organizations like INCOSE and NAFEMS. The document advocates that engineers tie themselves to standards rather than specific tools to gain benefits like lower costs, improved competition between vendors, and increased ownership of models.
Michael K Bartosewcz is seeking a leadership position as a Senior Systems EO/IR Engineer and/or Program Manager on an EO/IR space flight hardware/software/algorithm program. He has significant experience in systems engineering and program management for C4ISR systems including SBIRS High, ABL, IKONOS, U-2 Multispectral Camera, and more. He has expertise in requirements analysis, system architecture analysis, interface definition, mission analysis, certification as a Thermal Vacuum/Vibration Test Engineer, and program/project management. He has a BS in Electrical Engineering from the University of Vermont and an MS in Physics from the University of Vermont.
The document provides an overview of RT-Middleware and RT-Component programming. It discusses the basic concepts of RT-Middleware, including that it is middleware for robot technology integration. RT-Components are the basic software units in RT-Middleware. The document outlines the benefits of the RT-Component model such as lifecycle management and data-centric communication. It also discusses RTC development workflows using tools like RTBuilder for code generation and CMake for building projects.
Eclipse plug-in development seminar held by the Bulgarian Java User group covering basic aspects of Eclipse plug-in development and the new stuff in e4
More info http://bit.ly/IOLtestsen -- Test Sentinel software runs automated testing in-house for DSL, Gfast, and Wireless including Broadband Forum’s ID337, ID337i2, TR-114, TR-100, and TR-067 test plans before applying for the Broadband Forum Gfast Certification Program.
Modeling and Simulation of Electrical Power Systems using OpenIPSL.org and Gr...Luigi Vanfretti
Title:
Modeling and Simulation of Electrical Power Systems using OpenIPSL.org and GridDyn
Presenters:
Luigi Vanfretti (RPI) & Philip Top (LNLL)
luigi.vanfretti@gmail.com, top1@llnl.gov
Abstract:
The Modelica language, being standardized and equation-based, has proven valuable for the for model exchange, simulation and even for model validation applications in actual power systems. These important features have been now recognized by the European Network of Transmission System Operators, which have adopted the Modelica language for dynamic model exchange in the Common Grid Model Exchange Standard (v2.5, Annex F).
Following previous FP7 project results, within the ITEA 3 openCPS project, the presenters have continued the efforts of using the Modelica language for power system modeling and simulation, by developing and maintaining the OpenIPSL library: https://github.com/SmarTS-Lab/OpenIPSL
This seminar first gives an overview of the origins of the OpenIPSL and it’s models, it contrasts it against typical power system tools, and gives an introduction the OpenIPSL library. The new project features that help in the OpenIPSL maintenance (use of continuous integration, regression testing, documentation, etc.) are also described.
Finally, the seminar will present current work at LNLL that exploits OpenIPSL in coordination with other tools including ongoing work integrating openIPSL models into GridDyn an open-source power system simulation tool, as well as a demos of the use of openIPSL libraries in GridDyn.
Bios:
Luigi Vanfretti (SMIEEE’14) obtained the M.Sc. and Ph.D. degrees in electric power engineering at Rensselaer Polytechnic Institute, Troy, NY, USA, in 2007 and 2009, respectively.
He was with KTH Royal Institute of Technology, Stockholm, Sweden, as Assistant 2010-2013), and Associate Professor (Tenured) and Docent (2013-2017/August); where he lead the SmarTS Lab and research group. He also worked at Statnett SF, the Norwegian electric power transmission system operator, as consultant (2011 - 2012), and Special Advisor in R&D (2013 - 2016).
He joined Rensselaer Polytechnic Institute in August 2017, to continue to develop his research at ALSETLab: http://alsetlab.com
His research interests are in the area of synchrophasor technology applications; and cyber-physical power system modeling, simulation, stability and control.
Philp Top (Lawrence Livermore National Lab)
PhD 2007 Purdue University. Currently a Research Engineer at Lawrence Livermore National Laboratory in Livermore, CA. Philip has been involved in several projects connected with the DOE effort on Grid Modernization including projects on modeling and simulation, co-simulation and smart grid data analytics. He is the principle developer on the open source power system simulation tool GridDyn, and a key contributor to the HELICS open source co-simulation framework.
The Civil Infrastructure Platform (CIP) proposes establishing an open source software platform to provide industrial grade software building blocks for critical infrastructure projects. The CIP will select and maintain open source components through long term support, focusing initially on a Linux kernel and core packages. It will be hosted by the Linux Foundation and aims to drive standardization and collaboration to reduce costs and improve quality for civil infrastructure systems.
Securing eHealth, eGovernment and eBanking with Java - DWX '21Werner Keil
The EU increases its cooperation on cyber defense to strengthen its resilience to cyber-attacks through the EU Cybersecurity Act and certification of products, services or applications. To be as well prepared as possible against hacker attacks or the distribution of "fake news", fake documents or transactions. Like a One Trillion Amazon refund or fake tax returns. The IT industry may use this mechanism to certify products like connected vehicles, government services or smart medical devices. Due to its platform independence, Java plays an important role, especially in web, cloud or enterprise environments. In addition the PSD2 regulation went into effect in 2019 to make payments more secure, boost innovation and help banking services adapt to new technologies.
This session shows use cases of the DSS Framework and solutions based on it, such as Digidoc4J. DSS (Digital Signature Services) is a Java framework for the creation and validation of electronic signatures. DSS supports the creation and validation of interoperable and secure electronic signatures in accordance with European legislation, in particular the eIDAS Regulation, as well as IT standards like OASIS DSS. We are going to demonstrate how different documents and services can be signed and verified. Securing the data exchange using standards like DICOM, HL7 to OCSI or PSD2 and XS2A.
OpenDDR and Jakarta MVC - JavaLand 2021Werner Keil
We experience a growing number of mobile phones, tablets, phablets, foldables, smart TV, watches or home assistants and similar devices flooding the market almost every day. If you want to create a responsive web application with the best user experience you need dynamic adaptive content according to all relevant aspects of your device. That’s the reason for Device Description Repositories (DDR).
This session provides an overview of the W3C DDR standard for Mobile Device recognition and the OpenDDR project. Followed by a live demo of extensions to Spring MVC and the Jakarta MVC standard, plus .NET using C# and VB.NET leveraging the power of OpenDDR to simplify the development of cross device web applications. All offer automatic device detection based on OpenDDR, configuration of user preferences, automatically forward to the most appropriate view for a particular device or device type. As well as device aware templates, view engines and more.
M4M 2 the Rescue of M2M (Eclipse DemoCamp Trondheim)Werner Keil
M4M or Measure 4 Measure, ever since Shakespeare's play with the same name we know, people can be mistaken for one another. A Duke (like the beloved Java mascot) claims to be a monk, the head of a dead pirate is presented to be that of the young hero. So can important information like Units of Measurement be misinterpreted. While humans reading 10°C, 10 C or 10 Degree Celsius, each of those could be interpreted and understood well enough. For M2M communication, unless a program is provided with a large glossary of alternate terms, only ONE of these would be acceptable.
This is where the Unified Code for Units of Measurement (UCUM) among similar approaches like UnitsML, SensorML or a few others are vital for error-free M2M transactions, not just between sensors or measurement devices, but also and especially vehicles or distributed devices.
OSGi Measurement has been around for some time (R3) but never gained as much momentum, as many other bundles of OSGi did. Except for very few use cases in the Embedded or Automotive sector it is practically unused and based on statements by its contributors in the OSGi Alliance to be considered legacy with no plans continue development.
After a brief overview of common M2M errors from Gimli to Mars, This session provides an overview of OSGi Measurement, Eclipse OUMo, what they have in common and where the differences lie. Although most of today's OSGi containers are capable of dealing with units or measurement better and more reliable with UOMo, both can where necessary also exchange information and collaborate. E.g. if legacy devices and code cannot be easily replaced. For this We'll take a look at interoperability between different systems or with other unit technologies and languages like F#, Fantom, Python or Lua.
M4M 2 the Rescue of M2M - Eclipse DemoCamps Fall 2013Werner Keil
M4M or Measure 4 Measure, ever since Shakespeare's play with the same name we know, people can be mistaken for one another. A Duke (like the beloved Java mascot) claims to be a monk, the head of a dead pirate is presented to be that of the young hero. So can important information like Units of Measurement be misinterpreted. While humans reading 10°C, 10 C or 10 Degree Celsius, each of those could be interpreted and understood well enough. For M2M communication, unless a program is provided with a large glossary of alternate terms, only ONE of these would be acceptable.
This is where the Unified Code for Units of Measurement (UCUM) among similar approaches like UnitsML, SensorML or a few others are vital for error-free M2M transactions, not just between sensors or measurement devices, but also and especially vehicles or distributed devices.
OSGi Measurement has been around for some time (R3) but never gained as much momentum, as many other bundles of OSGi did. Except for very few use cases in the Embedded or Automotive sector it is practically unused and based on statements by its contributors in the OSGi Alliance to be considered legacy with no plans continue development.
This document discusses unit of measurement frameworks and errors caused by inconsistent unit usage. It provides examples of past disasters where unit conversion errors led to failures, such as the Mars Climate Orbiter that was destroyed due to a mix of metric and imperial units. The document advocates for type-safe unit of measurement support to prevent interface, arithmetic, and conversion errors. It introduces the Eclipse UOMo framework that provides this support across scientific, business, and currency domains through integration with standards like UCUM and ICU4J. The framework was demonstrated for applications involving monetary conversions.
After an looking back at the history of Eclipse OHF and its parts, we're going to learn what happened to them and why.
Beside those going a different path, mainly Open Health Tools (OHT) we take a closer look at the Legacy of OHF at Eclipse, mainly The Spatiotemporal Epidemiological Modeler (STEM) and Units of Measurement support from UOMo and related standards like the Unified Code for Units of Measure (UCUM)
M2M, Sensor Web, Observations and MeasurementsWerner Keil
M4M or Measure 4 Measure, ever since Shakespeare's play with the same name we know, people can be mistaken for one another. A Duke (like the beloved Java mascot) claims to be a monk, the head of a dead pirate is presented to be that of the young hero. So can important information like Units of Measurement be misinterpreted. While humans reading 10°C, 10 C or 10 Degree Celsius, each of those could be interpreted and understood well enough. For M2M communication, unless a program is provided with a large glossary of alternate terms, only ONE of these would be acceptable.
Slides of the JCP EC F2F in January 2014 proposing the idea of a Units of Measurement JSR, recently approved as JSR 363: https://jcp.org/en/jsr/detail?id=363
Groovy founder Guillaume Laforge built on top of the Java standard proposal for type safe Units of Measurements, JSR-275 with his case study of a Domain-Specific Language for unit manipulations some while ago.
Based on Unit-API the successor to JSR-275, and its leading Open Source implementation Eclipse UOMo together with Xtext/TS we'll see, how a similar DSL for unit manipulations could be created with Xtext. As well as other languages including Groovy or Scala.
The Quantified UOMo - Eclipse DemoCamp Trondheim 2015Werner Keil
The document discusses units of measurement in software and introduces the Quantified UOMo project. It provides an overview of prior work on units of measurement in APIs and frameworks. It then demonstrates the UOMo project, which provides a type-safe units of measurement library and implements the JSR-363 Units of Measurement API. Examples are given for uses in healthcare, fitness, smart homes, and quantified self-tracking.
ETSI TC MTS Contribution to Testing in IoT and Edge ComputingAxel Rennoch
The document discusses testing in IoT and edge computing. It motivates the need for standardized testing approaches given the high quality and confidence required for IoT and edge communication protocols and configurations. It envisions computing standards being accompanied by defined test scenarios and catalogs using standardized specification techniques. Existing testing approaches from domains like mobile networks can be applied, and work has been completed on test specifications for protocols like CoAP and MQTT. However, distributed and heterogeneous edge architectures present specific challenges for testing distributed systems, edge node management, and performance under resource restrictions at the IoT layer.
This document provides an introduction to wireless sensor networks (WSNs). It discusses the basic concepts and definitions of WSNs, including sensors, transducers, and actuators. It also describes popular sensor node platforms, standardization efforts like ZigBee and 6LoWPAN, and WSN architectures. The document is intended to discuss the objectives, concepts, platforms, standards, protocols, applications, and design factors of WSNs.
Semantically-Enabling the Web of Things: The W3C Semantic Sensor Network Onto...Laurent Lefort
Presentation of the SSN XG results at eResearch Australia 2011 https://eresearchau.files.wordpress.com/2012/06/74-semantically-enabling-the-web-of-things-the-w3c-semantic-sensor-network-ontology.pdf
Technology Insertion: A Well-Grounded Approach to Implementing Out of this Wo...Society of Women Engineers
The document discusses a methodology for incorporating new technologies into products and systems. It introduces Technology Readiness Levels (TRL), Integration Readiness Levels (IRL), and System Readiness Levels (SRL) as metrics to measure the maturity of individual technologies, their integration, and the overall system. The approach involves identifying customer needs, prioritizing technologies, and systematically maturing technologies from the component to system level. Examples are provided of NASA's use of TRLs and how Honeywell has incorporated new technologies like control moment gyros and vibration isolation mechanisms into spacecraft. The importance of integrating mature subsystems while following a systems engineering process is emphasized to achieve a high system readiness.
This document discusses the Open Platform for the Engineering of Critical Embedded Systems (OPEES) project. The main objectives of OPEES are to ensure long-term availability of open source tools for critical systems and support them for the entire lifecycle of very long-lived products, which can last up to 78 years. OPEES aims to build a sustainable ecosystem around these technologies by federating industrial users and service providers. This will help avoid vendor lock-in and allow common platforms to be shared. OPEES will implement additional features like community management, ecosystem development focused on industrial users, and processes for long-term support and maturity assessment of tools. The OPEES project involves 35 members from 5 European countries working to
This document discusses future directions for OpenSees. It outlines plans to release a Python interpreter for OpenSees in addition to the existing Tcl interpreter. It also discusses developing an integrated development environment called OpenSeesIDE that will include a file editor, interpreters and a 3D renderer. Finally, it describes a new organization called the SimCenter that will develop computational modeling and simulation applications using OpenSees, including applications for uncertainty quantification, performance based engineering and community resiliency.
Emerging standards and support organizations within engineering simulation Modelon
This document discusses emerging standards and support organizations within engineering simulation. It summarizes several key standards including SysML, Modelica, FMI, STEP, and OSLC. It discusses the goals and benefits of standards organizations like INCOSE and NAFEMS. The document advocates that engineers tie themselves to standards rather than specific tools to gain benefits like lower costs, improved competition between vendors, and increased ownership of models.
Michael K Bartosewcz is seeking a leadership position as a Senior Systems EO/IR Engineer and/or Program Manager on an EO/IR space flight hardware/software/algorithm program. He has significant experience in systems engineering and program management for C4ISR systems including SBIRS High, ABL, IKONOS, U-2 Multispectral Camera, and more. He has expertise in requirements analysis, system architecture analysis, interface definition, mission analysis, certification as a Thermal Vacuum/Vibration Test Engineer, and program/project management. He has a BS in Electrical Engineering from the University of Vermont and an MS in Physics from the University of Vermont.
The document provides an overview of RT-Middleware and RT-Component programming. It discusses the basic concepts of RT-Middleware, including that it is middleware for robot technology integration. RT-Components are the basic software units in RT-Middleware. The document outlines the benefits of the RT-Component model such as lifecycle management and data-centric communication. It also discusses RTC development workflows using tools like RTBuilder for code generation and CMake for building projects.
Eclipse plug-in development seminar held by the Bulgarian Java User group covering basic aspects of Eclipse plug-in development and the new stuff in e4
More info http://bit.ly/IOLtestsen -- Test Sentinel software runs automated testing in-house for DSL, Gfast, and Wireless including Broadband Forum’s ID337, ID337i2, TR-114, TR-100, and TR-067 test plans before applying for the Broadband Forum Gfast Certification Program.
Modeling and Simulation of Electrical Power Systems using OpenIPSL.org and Gr...Luigi Vanfretti
Title:
Modeling and Simulation of Electrical Power Systems using OpenIPSL.org and GridDyn
Presenters:
Luigi Vanfretti (RPI) & Philip Top (LNLL)
luigi.vanfretti@gmail.com, top1@llnl.gov
Abstract:
The Modelica language, being standardized and equation-based, has proven valuable for the for model exchange, simulation and even for model validation applications in actual power systems. These important features have been now recognized by the European Network of Transmission System Operators, which have adopted the Modelica language for dynamic model exchange in the Common Grid Model Exchange Standard (v2.5, Annex F).
Following previous FP7 project results, within the ITEA 3 openCPS project, the presenters have continued the efforts of using the Modelica language for power system modeling and simulation, by developing and maintaining the OpenIPSL library: https://github.com/SmarTS-Lab/OpenIPSL
This seminar first gives an overview of the origins of the OpenIPSL and it’s models, it contrasts it against typical power system tools, and gives an introduction the OpenIPSL library. The new project features that help in the OpenIPSL maintenance (use of continuous integration, regression testing, documentation, etc.) are also described.
Finally, the seminar will present current work at LNLL that exploits OpenIPSL in coordination with other tools including ongoing work integrating openIPSL models into GridDyn an open-source power system simulation tool, as well as a demos of the use of openIPSL libraries in GridDyn.
Bios:
Luigi Vanfretti (SMIEEE’14) obtained the M.Sc. and Ph.D. degrees in electric power engineering at Rensselaer Polytechnic Institute, Troy, NY, USA, in 2007 and 2009, respectively.
He was with KTH Royal Institute of Technology, Stockholm, Sweden, as Assistant 2010-2013), and Associate Professor (Tenured) and Docent (2013-2017/August); where he lead the SmarTS Lab and research group. He also worked at Statnett SF, the Norwegian electric power transmission system operator, as consultant (2011 - 2012), and Special Advisor in R&D (2013 - 2016).
He joined Rensselaer Polytechnic Institute in August 2017, to continue to develop his research at ALSETLab: http://alsetlab.com
His research interests are in the area of synchrophasor technology applications; and cyber-physical power system modeling, simulation, stability and control.
Philp Top (Lawrence Livermore National Lab)
PhD 2007 Purdue University. Currently a Research Engineer at Lawrence Livermore National Laboratory in Livermore, CA. Philip has been involved in several projects connected with the DOE effort on Grid Modernization including projects on modeling and simulation, co-simulation and smart grid data analytics. He is the principle developer on the open source power system simulation tool GridDyn, and a key contributor to the HELICS open source co-simulation framework.
The Civil Infrastructure Platform (CIP) proposes establishing an open source software platform to provide industrial grade software building blocks for critical infrastructure projects. The CIP will select and maintain open source components through long term support, focusing initially on a Linux kernel and core packages. It will be hosted by the Linux Foundation and aims to drive standardization and collaboration to reduce costs and improve quality for civil infrastructure systems.
Securing eHealth, eGovernment and eBanking with Java - DWX '21Werner Keil
The EU increases its cooperation on cyber defense to strengthen its resilience to cyber-attacks through the EU Cybersecurity Act and certification of products, services or applications. To be as well prepared as possible against hacker attacks or the distribution of "fake news", fake documents or transactions. Like a One Trillion Amazon refund or fake tax returns. The IT industry may use this mechanism to certify products like connected vehicles, government services or smart medical devices. Due to its platform independence, Java plays an important role, especially in web, cloud or enterprise environments. In addition the PSD2 regulation went into effect in 2019 to make payments more secure, boost innovation and help banking services adapt to new technologies.
This session shows use cases of the DSS Framework and solutions based on it, such as Digidoc4J. DSS (Digital Signature Services) is a Java framework for the creation and validation of electronic signatures. DSS supports the creation and validation of interoperable and secure electronic signatures in accordance with European legislation, in particular the eIDAS Regulation, as well as IT standards like OASIS DSS. We are going to demonstrate how different documents and services can be signed and verified. Securing the data exchange using standards like DICOM, HL7 to OCSI or PSD2 and XS2A.
OpenDDR and Jakarta MVC - JavaLand 2021Werner Keil
We experience a growing number of mobile phones, tablets, phablets, foldables, smart TV, watches or home assistants and similar devices flooding the market almost every day. If you want to create a responsive web application with the best user experience you need dynamic adaptive content according to all relevant aspects of your device. That’s the reason for Device Description Repositories (DDR).
This session provides an overview of the W3C DDR standard for Mobile Device recognition and the OpenDDR project. Followed by a live demo of extensions to Spring MVC and the Jakarta MVC standard, plus .NET using C# and VB.NET leveraging the power of OpenDDR to simplify the development of cross device web applications. All offer automatic device detection based on OpenDDR, configuration of user preferences, automatically forward to the most appropriate view for a particular device or device type. As well as device aware templates, view engines and more.
How JSR 385 could have Saved the Mars Climate Orbiter - Zurich IoT Day 2021Werner Keil
The document discusses how using JSR-385 could have prevented the loss of the Mars Climate Orbiter spacecraft. It describes how the orbiter was launched in 1998 to study the Martian climate but was lost due to a failure to convert between metric and imperial units. Had JSR-385 been used to define physical quantities with consistent units, as it does now, this error may have been caught during development. The document then provides an overview of JSR-385 and how it can help define quantities, units, and perform unit conversions to prevent such errors.
OpenDDR and Jakarta MVC - Java2Days 2020 VirtualWerner Keil
We experience a growing number of mobile phones, tablets, phablets, foldables, smart TV, watches, or home assistants, and similar devices flooding the market almost every day. If you want to create a responsive web application with the best user experience you need dynamic adaptive content according to all relevant aspects of your device. That’s the reason for Device Description Repositories (DDR).
This session provides an overview of the W3C DDR standard for Mobile Device recognition and the OpenDDR project. Followed by a live demo of extensions to Spring MVC and the Jakarta MVC standard leveraging the power of OpenDDR to simplify the development of cross device web applications. Both offer automatic device detection based on OpenDDR, configuration of user preferences, automatically switch the path to the most appropriate view for a particular device or device type. As well as device aware templates, view engines, and more.
The amount of data collected by applications nowadays is growing at a scary pace. Many of them need to handle billions of users generating and consuming data at an incredible speed. Maybe you are wondering how to create an application like this? What is required? What works best for your project?
In this session we’ll compare popular Java and JVM persistence frameworks for NoSQL databases: Spring Data, Micronaut, Hibernate OGM, Jakarta NoSQL, and GORM. How do they compare, what are the strengths, weaknesses, differences, and similarities? We’ll show each of them with a selection of different NoSQL database systems (Key-Value, Document, Column, Graph).
The data load on applications has increased exponentially in recent years. We know the JVM (Java Virtual Machine) can cope with heavy loads very well yet we often come across the big dilemma: there are tons of persistence frameworks out there but which one performs best for my case? It would normally take ages to evaluate and choose the best fit for your use case. We’ve done those comparisons for you.
JCON 2020: Mobile Java Web Applications with MVC and OpenDDRWerner Keil
The document discusses mobile Java web applications using MVC frameworks and OpenDDR. It provides an overview of OpenDDR, comparing it to other device description repositories. It then discusses how to integrate OpenDDR into applications using Spring Mobile and Jakarta MVC, two popular MVC frameworks. The document ends with a link to demo the concepts discussed.
How JSR 385 could have Saved the Mars Climate Orbiter - JFokus 2020Werner Keil
In 1999, NASA lost the $125 million Mars Climate Orbiter as it went into orbital insertion. Due to a mismatch between US customary and SI units of measurements in one of the APIs, the spacecraft came too close to the planet, passed through the upper atmosphere and disintegrated. Sadly, this hasn’t been the only instance where a mismatch between units of measurements had catastrophic consequences, but it’s certainly one of the most spectacular and expensive ones.
How could this happen? The bad news: if you use primitive types to handle quantities in your code, due to the same practice at best, you’ve codified the unit in a variable name or database field, e.g. calling it lengthInMetres. Otherwise, you’re only relying on convention, just like Lockheed Martin and NASA did.
Join this talk to learn how JSR 385 can help you avoid $125 million mistakes, how it applies the 2019 redefinition of SI base units, and discover the immeasurable world of dimensions, units and quantities.
Money, Money, Money, can be funny with JSR 354 (Devoxx BE)Werner Keil
Maintenance Lead Werner Keil will present JSR 354 (Money and Currency). He will discuss the API from a developer as well as user perspective and share details on the design decisions behind the JSR. Monetary values are a key feature of many applications, yet the JDK provides little or no support.
The existing java.util.Currency class is strictly a structure used for representing current ISO-4217 currencies, but not associated values or custom currencies. The JDK also provides no support for monetary arithmetic or currency conversion, nor for a standard value type to represent a monetary amount.
The session will demonstrate how the JSR models monetary capabilities, monetary amounts, currencies, rounding, financial arithmetics as well as formatting and currency conversion in a platform independent and flexible manner.
The first part of the talk will focus on key concepts, improvements like Java 9/Jigsaw modularity and planned new features for a future release followed by a live coding session demonstrating the Money JSR in action.
Money, Money, Money, can be funny with JSR 354 (DWX 2019)Werner Keil
Maintenance Leads Werner Keil and Anatole Tresch will present JSR 354 (Money and Currency). They will discuss the API from a developer as well as user perspective and share details on the design decisions behind the JSR.
Monetary values are a key feature of many applications, yet the JDK provides little or no support. The existing java.util.Currency class is strictly a structure used for representing current ISO-4217 currencies, but not associated values or custom currencies. The JDK also provides no support for monetary arithmetic or currency conversion, nor for a standard value type to represent a monetary amount.
The session will demonstrate how the JSR models monetary capabilities, monetary amounts, currencies, rounding, financial arithmetics as well as formatting and currency conversion in a platform independent and flexible manner. The first part of the talk will focus on key concepts, improvements like Java 9/Jigsaw modularity and planned new features for a future release followed by a live coding session demonstrating the Money JSR in action.
NoSQL: The first New Jakarta EE Specification (DWX 2019)Werner Keil
Jakarta EE NoSQL is a framework and collection of tools that make integration between Java applications and NoSQL quick and easy—for developers as well as vendors. The API is easy to implement, so NoSQL vendors can quickly implement, test, and become compliant by themselves. And with its low learning curve and just a minimal set of artifacts, Java developers can start coding without having to worry about the complexity of specific NoSQL databases instead of their core aspects (such as graph or document properties). Built with functional programming in mind, it leverages all the features of Java 8 and above.
This session covers how the API is structured, how it relates to the multiple NoSQL database types, and how you can get started and involved in this open source technology and help the first new Jakarta EE specification evolve.
How JSR 385 could have Saved the Mars Climate Orbiter - Adopt-a-JSR DayWerner Keil
In 1999, NASA lost the $125 million Mars Climate Orbiter as it went into orbital insertion. Due to a mismatch between US customary and SI units of measurements in one of the APIs, the spacecraft came too close to the planet, passed through the upper atmosphere and disintegrated. Sadly, this hasn’t been the only instance where a mismatch between units of measurements had catastrophic consequences, but it’s certainly one of the most spectacular and expensive ones.
How could this happen? The bad news: if you use primitive types to handle quantities in your code, due to the same practice at best, you’ve codified the unit in a variable name or database field, e.g. calling it lengthInMetres. Otherwise, you’re only relying on convention, just like Lockheed Martin and NASA did.
Join this talk to learn how JSR 385 can help you avoid $125 million mistakes, how it applies the 2019 redefinition of SI base units, and discover the immeasurable world of dimensions, units and quantities.
Indroductory slides for the Adopt-a-JSR Day by Utrecht JUG
JNoSQL: The Definitive Solution for Java and NoSQL DatabasesWerner Keil
JNoSQL is a framework and collection of tools that make integration between Java applications and NoSQL quick and easy—for developers as well as vendors. The API is easy to implement, so NoSQL vendors can quickly implement, test, and become compliant by themselves. And with its low learning curve and just a minimal set of artifacts, Java developers can start coding by worrying not about the complexity of specific NoSQL databases but only their core aspects (such as graph or document properties). Built with functional programming in mind, it leverages all the features of Java 8. This session covers how the API is structured, how it relates to the multiple NoSQL database types, and how you can get started and involved in this open source technology.
Eclipse JNoSQL: The Definitive Solution for Java and NoSQL DatabasesWerner Keil
JNoSQL is a framework and collection of tools that make integration between Java applications and NoSQL quick and easy—for developers as well as vendors. The API is easy to implement, so NoSQL vendors can quickly implement, test, and become compliant by themselves. And with its low learning curve and just a minimal set of artifacts, Java developers can start coding by worrying not about the complexity of specific NoSQL databases but only their core aspects (such as graph or document properties). Built with functional programming in mind, it leverages all the features of Java 8. This session covers how the API is structured, how it relates to the multiple NoSQL database types, and how you can get started and involved in this open source technology.
Physikal - Using Kotlin for Clean Energy - KUG MunichWerner Keil
The document discusses a presentation about using Kotlin for clean energy. It introduces Physikal, a Kotlin library that provides extensions and functions for working with units of measurement based on JSR-363. Physikal allows for easy creation and manipulation of units, as well as conversions between different units like meters and feet. It also supports all common arithmetic operators on units. The presentation provides examples of how to use Physikal to add, convert, and perform comparisons between units.
Physikal - JSR 363 and Kotlin for Clean Energy - Java2Days 2017Werner Keil
This session will give you a brief overview of how Tenkiv and Nexus Brain use Kotlin and Physikal/JSR 363 to calculate the optimal usage of alternate energy sources and control solar power systems used for making clean water anywhere from Flint Michigan to Afghanistan.
Performance Monitoring for the Cloud - Java2Days 2017Werner Keil
Performance Monitoring tools like Performance Co-Pilot (PCP) existed almost longer than the World Wide Web. It was developed in the early 90s by SGI. Parts were made available open source from 2000 on, which led to a further spread of the tool. In recent years an active community formed and a variety of new features and enhancements were added. PCP is now part of Red Hat and SuSE Linux Enterprise editions and included in many other Linux distributions. Versions for other Unix variants, OS X and Windows also exist. This session compares popular Open Source Monitoring Tools like Performance Co-Pilot, StatsD, Dropwizard Metrics, Prometeus, MicroProfile Metrics or StatsD. How they each support Containers or Virtualization, share data with IT monitoring systems like Nagios or Zabbix, or process analyze and visualize it via Carbon, Graphite or Grafana/ElasticSerch.
With IoT it’s all about things and sensors. And when representing a temperature, for example, we normally have it as a float. But is this float in Celsius? Kelvin? This is one of the problems JSR 363 wants to solve: have all “real world” value and unit data represented in a standard way. This JSR is also very suitable for scientific applications, where data representation, conversion, and formatting are very important. In this session, you’ll see how developers as well as platform providers can leverage this JSR, coding a smart gas pump that reports its values by using Java standards. Come to meet JSR 363, Units of Measurement.
Java2Days - Security for JavaEE and the CloudWerner Keil
When we deploy existing applications to the cloud or build new applications for it, how do the applications change? How does the boundary of an application change? How does this change affect the security parameters? What are the security characteristics that need to be accounted for? This talk explores these and the following questions:
• What are the top security concerns when building for the cloud?
• How do we evolve the security JSR (375) in Java EE 8 for the cloud?
• What are the key security areas for the next-generation Java EE platform that can ease a developer’s path for cloud deployments?
Das Wachstum an Mobiltelefonen, Tablets und ähnlichen Geräten, die den Markt geradezu überschwemmen erleben wir Tag für Tag.
Die Spezifikation jedes Einzelnen genau zu verfolgen ist ein Knochenjob. Diese Mühe kann reduziert werden, wenn zur Verbesserung dasDevice Description Repository – kurz DDR - beigesteuert wird und Anwender dieses selbst verwaltet können.
Apache DeviceMap entstand als Kooperation von OpenDDR und anderen, um ein umfassendes Open Source Daten-Repository mit Geräteinformationen, Bilder und andere relevante Informationen für alle Arten von mobilen Geräten zu schaffen, Smartphones, Tablets, Smart-TV, u.dgl.
Das Projekt begann im Januar 2012, im Herbst 2012 wurden DDR APis für Java und .NET von OpenDDR beigesteuert. Im Herbst 2014 verließ DeviceMap erfolgreich den Apache Incubator. Die nächsten Schritte umfassen verbesserte Erkennung von Informationen im UserAgent String. Java Portlet 3.0 Integration via Apache Pluto. Sowie Crowd-Sourcing der Device Repository Daten und eine Speicher-Struktur, die langfristige Erhaltung und Pflege dieser Daten durch die Apache Gemeinde erlaubt.
The First IoT JSR: Units of Measurement - JUG Berlin-BrandenburgWerner Keil
Come to meet JSR 363 - Units of Measurement! It's the first JSR targeted to help you work with IoT devices, tackling sensors and measurements in a standard way. We all know that when representing a temperature, for example, we normally have it as a float. But, is this float in Celsius? Fahrenheit? Kelvin? This is one of the problems this JSR wants to solve: have all "real world" value and unit data represented in a standard way. This JSR is also very suitable for scientific applications, where data representation, conversion and formatting is very important.
In this presentation, we'll see how both developers and platform providers can leverage this JSR, coding for a smart home or smart gas pump that reports its values in a standard way. As well as other use cases and actual embedded devices like Raspberry Pi or Intel Edison.
And this JSR is still in the making. Be first hand witness of the JSR 363 Public Draft (due around Nov) and learn how YOU can get involved and help Java grow in the IoT space! We'll explore how JSRs work and how you can get involved in the JCP and work with this and other JSRs.
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
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.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Building RAG with self-deployed Milvus vector database and Snowpark Container...Zilliz
This talk will give hands-on advice on building RAG applications with an open-source Milvus database deployed as a docker container. We will also introduce the integration of Milvus with Snowpark Container Services.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
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.
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
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
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
6. NASA “Star Wars” Initiative, 1983
23rd March 1983. Ronald Reagan
announces SDI (or “Star Wars”): ground-
based and space-based systems to
protect the US from attack by strategic
nuclear ballistic missiles.
7. 1985
Mirror on underside of SDI Experiment:
shuttle
The Plan
Big mountain in Hawaii
38. Links
Eclipse – Project UOMo
http://www.eclipse.org/uomo/
Units of Measurement API
http://www.unitsofmeasurement.org
UCUM
http://www.unitsofmeasure.org