JSON Schema is an extremely powerful, yet easily approachable, tool for describing data structures. In fact, the OpenAPI has embraced JSON Schema and currently uses it for describing the inputs/outputs of your APIs. JSON Schema is a technology that is often misunderstood and often used in ways that leave people scratching their heads when it does not work the way they expected. This talk will introduce JSON Schema from the ground up, complete with gotchas and best practices. In the end, the hope is that the attendee will see the value of JSON Schema and understand it well enough to use in their OpenAPI documents and even their own applications.
An XML schema describes the structure and elements of an XML document. It defines elements, attributes, data types, properties like required/optional, and relationships between elements. XML schema is more powerful than older DTD schemas as it allows defining data types and namespaces. Schemas are written in XML syntax, making them easy to read, write and process using standard XML tools. This document provides examples of simple and complex element definitions in an XML schema.
Cascading Style Sheets (CSS) allow separation of document content from document presentation and formatting. CSS defines how elements should be rendered on screen, paper, or other media. This document discusses CSS syntax, the different ways to insert CSS (external, internal, inline stylesheets), CSS selectors including type, class, ID and descendant selectors, and the cascading order of multiple style sheets. It also covers CSS features such as comments, declarations and properties, and media types for external stylesheets.
The document discusses XML schemas. It explains that an XML schema describes the structure of an XML document and is an alternative to DTDs. It is written in XML and supports data types and namespaces. The document provides examples of simple XML schemas defining elements and attributes, and using restrictions to define acceptable values for elements and attributes.
1. JavaScript inside Browser's Environment
- About Browsers
- Executing JavaScript
2. Working with Browser Objects
- Window
- Location
- History
- Navigator
- Screen
3. Document Object Model
4. Core DOM Objects
- Overview
- Node
- Document
- Element
- Attribute
5. HTML DOM Objects
6. DOM Travesal and Manipulations
- Seach element
- Change element
- Work with set of elements
7. Events
- Event types
- Event object
- Event Bubbling
8. jQuery basics
- Overview
- Selectors
9. HTML5 Demos
An XML schema defines the structure and elements of an XML document. It is an XML-based alternative to DTDs that allows defining element types, attributes, data types, defaults and restrictions. Schemas support namespaces, data types, extensibility and are written in XML, allowing the use of XML tools. Complex elements can contain child elements, text or both.
This document provides an overview of XML, including:
- XML is not a replacement for HTML, a presentation format, programming language, or network transfer protocol, but can be used with these.
- XML examples demonstrating tags, elements, attributes, and how XML documents form ordered trees.
- Key aspects of XML like namespaces, DTDs, schemas, and how XML documents are linked to external definitions.
XSL is a language used to describe how to display XML files in a browser. It can convert XML files into other formats like HTML. The most common use of XSL is to convert XML files into HTML that can be displayed in browsers. Key elements in XSL include xsl:template to match nodes, xsl:value-of to extract node values, xsl:for-each to iterate over nodes, and xsl:copy to copy nodes from the XML file to the output. An example shows using an XSL stylesheet to transform an XML file about a fitness center member into an HTML web page that displays the member's name, favorite color, and phone numbers.
This document provides an overview of XML Schema Definition (XSD). It discusses that XSD is used to describe and validate the structure and vocabulary of an XML document. It then provides an example of a simple XSD code and explains some of its key features, such as being extensible, supporting data types and namespaces. It also outlines the basic syntax of an XSD, including the required <schema> root element and optional attributes like targetNamespace. Finally, it demonstrates how to reference an external XSD from an XML document using schemaLocation.
Content:
- Structures
- Datatypes
References:
- Beginning XML, 5th Edition, Joe Fawcett, Liam R. E. Quin, Danny Ayers
- XML in a nutshell,3rd Edition, Elliotte Rusty Harold & W. Scott Means
- http://www.w3schools.com/
XML Schema provides a way to formally define and validate the structure and content of XML documents. It allows defining elements, attributes, and data types, as well as restrictions like length, pattern, and value ranges. DTD is more limited and cannot validate data types. XML Schema is written in XML syntax, uses XML namespaces, and provides stronger typing capabilities compared to DTD. It allows defining simple and complex element types, attributes, and restrictions to precisely describe the expected structure and values within XML documents.
- HTML (Hypertext Markup Language) is the standard markup language used to create web pages. It uses tags to define headings, paragraphs, lists, links, and other elements.
- HTML documents are made up of HTML elements like <html>, <head>, <body>, <h1>, <p>, <a>, which are delimited by angle brackets. Tags usually come in pairs with an opening and closing tag.
- CSS (Cascading Style Sheets) is used to control the style and layout of multiple web pages. It can be added to HTML documents through inline styles, internal stylesheets, or external stylesheets and is used to define things like colors, fonts, spacing.
The document discusses XML namespaces and XML schemas. It provides examples of using namespaces to differentiate between similarly named elements, such as <highschool:subject> and <medicine:subject>. It also compares defining an XML document using a DTD versus using an XML schema, and provides a sample schema for defining book information. Key differences between "ref" and "type" attributes in schemas are explained using an employee example.
The Document Object Model (DOM) is a standard for representing XML and HTML documents as a navigable tree structure. Every object in the DOM tree is a node, with different node types like elements, text, and documents. The DOM allows developers to navigate and interact with an XML or HTML document by treating it as a tree of nodes.
The document discusses XML document structure and XML schema. It provides information on the key components of an XML document including the XML declaration, document type declaration, element data, attribute data, and character data. It then describes XML schema in detail, explaining that it defines the structure of an XML document. Key aspects of XML schema covered include elements, attributes, simple vs complex types, and restrictions.
XML Schema is an XML-based alternative to DTDs that defines the structure and legal elements and attributes of an XML document. An XML Schema describes elements, attributes, data types, restrictions, and more. Schemas are more powerful than DTDs and support namespaces, data types, extensibility, and validation of XML documents.
XML Schema defines rules for encoding documents in a machine-readable format. It allows data exchange between systems independently of programming languages. XML Schema defines elements, attributes, and data types to structure XML documents. It provides more data typing capabilities than DTDs. Namespaces are used to avoid element name conflicts between different XML vocabularies. User-defined types can restrict built-in types or create new complex types from simple types to structure application-specific data.
Web front end development introduction to html css and javascriptMarc Huang
This document provides an introduction to HTML, CSS, and JavaScript for building websites. It discusses how websites work by connecting clients and servers, and compares making a website to writing a book by organizing content into pages. The document then covers the basic purposes and syntax of HTML for creating page content, CSS for styling, and JavaScript for interactivity. It provides many code examples and explains common elements, properties, and methods in each language to demonstrate basic front-end web development concepts and tools.
Presentation on various definitions for JSON including JSON-RPC, JSPON, JSON Schema, JSONP and tools for working these definitions including Persevere client and server..
The document discusses interoperable JavaScript-based client/server web applications using REST, JSON, JSON Schema, JSONQuery, Comet, and frameworks like Dojo and Persevere. Key aspects covered include service-oriented architectures, REST principles, JSON referencing, JSON Schema, querying data via JSONPath and JSONQuery, and live data notifications with REST channels and Comet.
This document provides an overview of working with JSON documents. It discusses JSON structure, validating JSON, querying and transforming JSON, and converting between JSON and XML formats. Validation can check for well-formedness and validate against a JSON schema. JSON can be queried using pointers, JSONiq, or XPath, and transformed with JavaScript, XSLT, or XQuery. Conversion between JSON and XML can be done programmatically or with online tools.
Oxygen provides a specialized JSON and JSON Schema editor with a variety of editing features, helper views, and useful tools. In this presentation you will see an overview of the JSON support, as well as the new additions, such as:
- An instance generator from a JSON Schema
- XSD to JSON schema converter
- Generate JSON Schema from JSON instance
- JSON Schema annotations
- Schematron validation for JSON
The document discusses JSON (JavaScript Object Notation), including:
- JSON is a language-independent way to specify objects as name-value pairs.
- JSON syntax uses braces {} for objects and brackets [] for arrays. Values can include strings, numbers, booleans, null, objects, and arrays.
- The JavaScript eval() method can compile and execute a JSON string, returning the described object. However, this breaks language independence and JSON cannot represent methods.
- JSON and XML are both human-readable but have different syntaxes. JSON is less verbose and can be parsed by eval(), while XML can be validated.
This document provides a tutorial on JSON (JavaScript Object Notation). It begins with a basic JSON example of an employee data object with an array of records. It then explains that JSON is a lightweight data format that is easy to read/write and can be parsed by JavaScript. The document covers JSON syntax rules, data types, objects, arrays, and how JSON uses JavaScript syntax. It provides examples of using JSON with HTTP requests, function files, and SQL queries. The goal is to teach how to read JSON data from a web server and display it in a web page.
This document provides an introduction to JSON (JavaScript Object Notation), including what it is, its data structure, how to send and receive JSON data at both the client and server sides, and resources for further information. The key points covered are:
- JSON is a lightweight data format that is easy for humans and machines to read/write and is independent of programming languages.
- JSON data is structured as either a collection of name/value pairs (objects) or an ordered list of values (arrays).
- JSON can be converted to and from JavaScript objects using functions like eval() and JSON.parse().
- At the server, JSON data can be generated from objects and sent to clients, then parsed at the
Understand about what JSON is
Understand the difference between JSON and XML
Understand the context of using JSON with AJAX
Know how to read and write JSON data using PHP
This document provides an overview of JSON (JavaScript Object Notation) including what it is, why it is used, its syntax, examples comparing it to XML, where it can be used, and how to use it in JavaScript. JSON is a lightweight data format that is easy for humans to read and write and easy for machines to parse and generate. It is often used to transmit data between a server and web application.
Slides for Tom Marrs BJUG talk on 2/12/2013. See http://boulderjug.org/2013/01/tuesday-february-12-2013-a-night-with-tom-marrs-covering-json-and-rest.html
This presentation deals with every possible topics under JSON (JavaScript Object Notation) which every web developers should know.
It is presented by Rajasekhar who works at United Online as a Web Developer
JSON is a lightweight data-interchange format that is easy for humans to read and write and for machines to parse and generate. It is built on two structures: a collection of name/value pairs and an ordered list of values. JSON is text-based and language independent, yet closely resembles JavaScript object syntax. It is used primarily to transmit data between a server and web application, serving as an alternative to XML. Compared to XML, JSON is simpler, faster and easier to use.
JSON (JavaScript Object Notation) is a lightweight data format that is easy for humans to read and write and for machines to parse and generate. It is built on two structures: a collection of name/value pairs and an ordered list of values. JSON is primarily used to transmit data between a web server and web application, and it is the most common data format used for asynchronous browser/server communication using AJAX.
JSON is a lightweight data-interchange format that is easy for humans to read and write and for machines to parse and generate. It is built on two structures: a collection of name/value pairs and an ordered list of values. JSON is widely used to transmit data between a server and web application, and has largely become the default format for asynchronous browser/server communication. While easy for machines to parse and generate, it is also readable by humans.
JSON is a lightweight data-interchange format that is easy for humans to read and write and for machines to parse and generate. It is built on two structures: a collection of name/value pairs and an ordered list of values. JSON is widely used to transmit data between a server and web application, and has largely become the default format for asynchronous browser/server communication. While easy for machines to parse and generate, it is also readable by humans.
Presented on 10/11/12 at the Boston Elasticsearch meetup held at the Microsoft New England Research & Development Center. This talk gave a very high-level overview of Elasticsearch to newcomers and explained why ES is a good fit for Traackr's use case.
Similar to LF_APIStrat17_Embracing JSON Schema (20)
LF_APIStrat17_OWASP’s Latest Category: API UnderprotectionLF_APIStrat
OWASP’s 2017 top ten adds a new category called 'underprotected APIs', reflecting the growth of RESTful Web APIs and richer front-end clients which stress current security and access authorization approaches. You’ll learn about potential threats resulting from undersecured Web APIs and techniques to strengthen your API security posture. You'll gain a clear understanding of user authorization via OAuth2, software authorization via static API keys and the critical interplay between them. Of particular concern are mobile API consumers whose code is statically published with secrets which are often poorly concealed. Practical advice with code examples will show how to improve mobile API security. TLS is necessary but insufficient to fully secure client-server communications. Certificate pinning is explained with code examples to show how to strengthen channel communications. Some advanced techniques will be discussed such as app hardening, white box cryptography and mobile app attestation. You should gain a good understanding of the underprotected API problem, with some immediately practical tips to improve your API security posture and a sense of emerging tools and technologies that enable a significant step change in API security.
LF_APIStrat17_Creating Communication Applications using the Asterisk RESTFul ...LF_APIStrat
The document provides an overview of the Asterisk RESTful Interface (ARI) and demonstrates how to build communication applications using ARI. It discusses the history and purpose of ARI and compares it to other Asterisk APIs like AGI and AMI. The document then demonstrates connecting to ARI via a WebSocket connection to receive events and making REST requests to play audio on a channel. It provides examples of the resources and categories available in the ARI specification.
LF_APIStrat17_Super-Powered REST API TestingLF_APIStrat
Let's talk testing. You know you should do it, but you probably don't enjoy it very much. I'll try to change your mind about that by showing you just how easy – and fun – it can be to test REST APIs. Whether you prefer the command line, a text editor, or a GUI, I'll show you tools that will fit nicely into your workflow.
In this workshop, you'll get hands-on experience with multiple API testing tools. We'll test the same API in each tool to compare the differences between them, including features, limitations, and ease of use. So bring your laptop, or just watch me. Either way, I'll send you home with sample code, working demos, and a better understanding of API testing.
LF_APIStrat17_How Mature are You? A Developer Experience Maturity ModelLF_APIStrat
How confident are you that your developer experience matches the expectations of your customers? How can you judge if you’re providing an adequate or best-in-class experience? What about your competition? How do you compare?
We had the same questions at Arity, and so developed a maturity model for API programs. Based on a year of user testing with developers, this model covers categories such as support and documentation.
This maturity model helps you focus your time and effort on the areas that will provide the greatest value for your customers. It’s a way to distill all the elements of the developer experience into an easily consumable document to give to stakeholders, helping you explain why the things you do as a manager of the developer community translate to increased sales for your organization.
We’ll go through the model together so you can score your company’s program. You’ll leave the session with a score and roadmap of how this can help you influence your stakeholders.
LF_APIStrat17_Connect Your RESTful API to Hundreds of Others in Minutes (Zapi...LF_APIStrat
You may have seen the articles or blog posts claiming something outrageous like how you can connect to hundreds of other Apps and enable thousands of use cases within a few hours of development.
They’re true. In this workshop, the Left Hook team will walk you through how to connect your App to hundreds of others on Zapier’s platform in a matter of minutes. There are a few big asterisks to achieve this speed: 1) Your API needs to be RESTful using either API token or OAuth2.0; 2) You’ll need to choose only a few basic use cases; 3) You need to be comfortable in a Node.js environment; 4) You need to be comfortable using a CLI tool.
LF_APIStrat17_Things I Wish People Told Me About Writing DocsLF_APIStrat
"Have you ever read a piece of API documentation and thought it was a mess? Maybe it was incomplete, badly organized, or in general just not great. There’s a good chance it was quickly thrown together by someone who had no idea what they were doing. In this talk, we will discuss the things Taylor wished she knew before starting to dive into the world of writing docs and developer focused content.
We will discuss how people actually read documentation, different types of docs and when they are appropriate, and docs navigation techniques using design principles. Also, we will learn more about the importance of focusing on language, including why naming matters and error messages as a form of documentation. Lastly, we will talk about tools and tactics to enable other team members to write documentation."
LF_APIStrat17_Lifting Legacy to the Cloud on API BoostersLF_APIStrat
Congratulations, you have a project to migrate a large legacy software system to the cloud. Also it needs some updates and the clients have a whole list of feature requests. Are you experiencing feelings of dread or exciting visions of the possibilities? The good news is that it can and should be the latter. The Open API ecosystem makes it easier than ever to take on a project like this and be successful. In this talk Seth will introduce his team’s ongoing migration project as a case study. He will discuss the primary benefits of open APIs as part of the migration and how they contribute to velocity, visibility, team focus, and feature development. He will examine strategies for identifying APIs, validating APIs, and integrating APIs into a legacy migration project. He will then discuss the layers of a legacy application that APIs can be used to address (hint: more than you may think).
LF_APIStrat17_Contract-first API Development: A Case Study in Parallel API Pu...LF_APIStrat
The idea of designing an API first, then having both the publishing developer teams and consuming client developer teams do their work in parallel is a pattern that the standards & tooling of the Open API ecosystem make worth considering. However, this approach is not without its challenges especially when it comes to governance and communication.
This session will present a real-world case study where this approach was executed successfully, going over how the work, teams, and deliverables were structured and presenting lessons learned that will be useful to anyone else considering this working model.
LF_APIStrat17_Don't Repeat Yourself - Your API is Your DocumentationLF_APIStrat
"If you find yourself maintaining a set of documents explaining the use of your API, you haven't finished it's design yet. This talk will compare various strategies with examples, while discussing ways to determine the most appropriate method for your API.
We will explore OAS (Swagger), Json-LD, Schema.org, HAL, Hydra, Siren, Semantic profiles, and other formats while comparing their relative strengths and weaknesses. After these options, we will arm you with a series of questions which direct you to the appropriate tool for your API.
Discover how you can save considerable time and headaches by incorporating a self documenting method in your API design."
LF_APIStrat17_How We Doubled the Velocity of Our Developer Experience TeamLF_APIStrat
We ruthlessly prioritize everything we do and automate away anything we have to do more than a couple times. This has helped the SendGrid DX team to maintain libraries for 7 different programming languages and their github communities with a single engineer. We challenge ourselves to always be working on the highest impact items for our users. Our goals are to maintain engagement with our developer community, manage our libraries at the highest possible level, all while sustaining our lean team.
LF_APIStrat17_API Marketing: First Comes Usability, then DiscoverabilityLF_APIStrat
This document discusses strategies for increasing API discoverability and developer onboarding. It recommends focusing first on usability by improving documentation, API definitions, and developer portals. It also stresses the importance of visibility strategies like SEO, metadata standards, and profiling APIs in directories. Finally, it highlights advocacy approaches like evangelism, community building, and thought leadership content to promote APIs. The overall message is that a balanced approach across usability, visibility, and advocacy is key to making APIs discoverable and attracting developers.
LF_APIStrat17_Standing Taller with Technology: APIs, IoT, and the Digital Wor...LF_APIStrat
How can we extend everyone's technological reach, no matter where they're starting from? How can IT become a platform that lets everyone stand taller? I'll talk about the critical role APIs play in creating more digital workforces. As organizations spend billions on various digital transformation efforts, they need to empower more of their people, not just developers and IT staff, to understand and interact with their data and technologies through APIs. The key is providing tools to people that make APIs more accessible to more people. APIs enable all sorts of combinations and linkages between data and technologies, and giving people streamlined access to APIs enables them to combine and extend their own expertise in innovative ways. Illustrative examples from working in IoT and APIs include academic research projects in many disciplines and business implementations across industries.
The document discusses versioning challenges for open source services deployed across multiple cloud platforms. It describes typical REST API versioning that works for single vendors but breaks down when different teams develop and deploy the software. The document introduces the concept of microversions to allow incremental feature updates while maintaining backwards compatibility. It also questions how to manage raising minimum versions and backwards compatibility over time.
LF_APIStrat17_I Believe You But My Enterprise Don't: Adopting Open Standards ...LF_APIStrat
To many of us in the API community, open standards seem like a no-brainer: they promote interoperability, extensibility, and longevity, all while helping you reap the benefits of being part of a larger ecosystem. These benefits include greater and more rapid adoption by developers and being in sync with and a contributor to best practices. But what happens when the clients consuming your APIs are enterprise healthcare companies, whose teams will develop integrations with your APIs regardless of best practices and who want things done their way rather than the open standard way? This talk draws on the speaker’s experiences integrating with enterprise healthcare systems to illustrate the value of projects such as the Open API Specification, open data model standards (e.g. Open Referral), and hypermedia formats, and how to communicate these benefits to reluctant enterprise clients.
Disclaimer: This talk is about the models, processes, and algorithms that power machine learning APIs rather than about the API itself.
Machine learning is fast becoming ubiquitous, from large enterprises to small startups. In this talk, we’ll embark on a journey with a small risk management startup, and we’ll talk about how snowflakes & trees and chickens & eggs came together to help the startup implement its own flavor of machine learning. This is the story of the cold decision tree and how it solved the cold start problem.
LF_APIStrat17_Getting Your API House In OrderLF_APIStrat
"Is your organization getting maximum impact from the technical talent and API experience that you already have? What is stopping you from turning that potential into results?
Ryan will share some of the steps that that GSA is taking in implementing an agency-wide API Strategy. Early successes include publishing API Standards, reviving an internal API Working Group, and creating an API documentation template and reference prototype API.
Learn about the journey that GSA is on, and how you can apply similar strategies across your organization."
LF_APIStrat17_Diving Deep into the API Ocean with Open Source Deep Learning T...LF_APIStrat
"The world is full of seas of data. Some of these seas are created and exchanged by APIs; some of them are even about APIs. Since 2014, APImetrics has accumulated over 100 GB of data on API test calls made to over 5000 API endpoints by agents deployed in cloud locations on 5 continents.
There's a huge amount of insight trapped at the bottom of that sea of (in our case unlabelled) data. Getting at it would've been nearly impossible before the emergence of powerful open source deep learning libraries in the mid-2010s.
APImetrics will share how we chose a deep learning library and the data munging we did to get our data to work with the library. We will explain how we were able carry out unsupervised and semi-supervised learning and discuss the insights on global API performance and quality we were able to dredge from the bottom of our sea of data. We'll provide pointers on how organizations, from startups like APImetrics to megacorporations, can use deep learning to create oceans of knowledge from their own seas of data."
LF_APIStrat17_Supporting SDKs in 7 Different Programming Languages While Main...LF_APIStrat
Many companies that provide an API also include SDKs. In this talk, learn from SendGrid’s Developer Experience Engineer, Elmer Thomas about how he re-built their 7 open source SDKs (Python, PHP, C#, Ruby, Node.js, Java and Go) to support 233 API endpoints. This tale involves automated integration test creation and execution with a Swagger/OAI powered mock API server, documentation, code, examples, CLAs, backlogs and sending out swag along with some insights on what should not be automated, like HTTP clients. He will dig into the technologies that made these automations possible along with lessons learned from the various programming communities.
"Despite open data's potential to change the world, it seems that developers and open data providers are constantly in an uphill battle to make open data not only available, but usable and actively used. The obstacles facing open data’s growth and adoption vary from technical infrastructure concerns, including maintenance, APIs, open data formats, to societal ones, including the ethical and security challenges of open data and the political climate shift in some countries causing antagonism towards open data.
In this talk, Shelby Switzer will dive into the origins and current state of open data globally and in the US, using concrete stories to illustrate the value of open data and its potential impact on our communities, governments, and businesses. She will explore the challenges facing the open data ecosystem, and discuss how key open source projects and standards, including Open API, have the potential to be instrumental in changing the game and positively impacting the open data movement."
LF_APIStrat17_Practical DevSecOps for APIsLF_APIStrat
In DevSecOps “shift left” applies to application security too: developers should commit to provide API security at the earliest stages of development.
In this session, Isabelle will propose an innovative strategy to address API security, in which developers collaborate with security teams and bring their business knowledge of the APIs to:
1/ Assess the API risk in terms of data and operation sensitivity
2/ Specify the input/output data formats
3/ Describe the application flow logic From the data gathered previously, tools can then generate automatically the appropriate security policies, respecting the rules set by the security teams.
Isabelle will also explain how the CI/CD pipeline can leverage a containerized PEP (Policy Enforcement Point) in the different testing / QA / Pre-Production / Production environments.
How Netflix Builds High Performance Applications at Global ScaleScyllaDB
We all want to build applications that are blazingly fast. We also want to scale them to users all over the world. Can the two happen together? Can users in the slowest of environments also get a fast experience? Learn how we do this at Netflix: how we understand every user's needs and preferences and build high performance applications that work for every user, every time.
Quantum Communications Q&A with Gemini LLM. These are based on Shannon's Noisy channel Theorem and offers how the classical theory applies to the quantum world.
GDG Cloud Southlake #34: Neatsun Ziv: Automating AppsecJames Anderson
The lecture titled "Automating AppSec" delves into the critical challenges associated with manual application security (AppSec) processes and outlines strategic approaches for incorporating automation to enhance efficiency, accuracy, and scalability. The lecture is structured to highlight the inherent difficulties in traditional AppSec practices, emphasizing the labor-intensive triage of issues, the complexity of identifying responsible owners for security flaws, and the challenges of implementing security checks within CI/CD pipelines. Furthermore, it provides actionable insights on automating these processes to not only mitigate these pains but also to enable a more proactive and scalable security posture within development cycles.
The Pains of Manual AppSec:
This section will explore the time-consuming and error-prone nature of manually triaging security issues, including the difficulty of prioritizing vulnerabilities based on their actual risk to the organization. It will also discuss the challenges in determining ownership for remediation tasks, a process often complicated by cross-functional teams and microservices architectures. Additionally, the inefficiencies of manual checks within CI/CD gates will be examined, highlighting how they can delay deployments and introduce security risks.
Automating CI/CD Gates:
Here, the focus shifts to the automation of security within the CI/CD pipelines. The lecture will cover methods to seamlessly integrate security tools that automatically scan for vulnerabilities as part of the build process, thereby ensuring that security is a core component of the development lifecycle. Strategies for configuring automated gates that can block or flag builds based on the severity of detected issues will be discussed, ensuring that only secure code progresses through the pipeline.
Triaging Issues with Automation:
This segment addresses how automation can be leveraged to intelligently triage and prioritize security issues. It will cover technologies and methodologies for automatically assessing the context and potential impact of vulnerabilities, facilitating quicker and more accurate decision-making. The use of automated alerting and reporting mechanisms to ensure the right stakeholders are informed in a timely manner will also be discussed.
Identifying Ownership Automatically:
Automating the process of identifying who owns the responsibility for fixing specific security issues is critical for efficient remediation. This part of the lecture will explore tools and practices for mapping vulnerabilities to code owners, leveraging version control and project management tools.
Three Tips to Scale the Shift Left Program:
Finally, the lecture will offer three practical tips for organizations looking to scale their Shift Left security programs. These will include recommendations on fostering a security culture within development teams, employing DevSecOps principles to integrate security throughout the development
Coordinate Systems in FME 101 - Webinar SlidesSafe Software
If you’ve ever had to analyze a map or GPS data, chances are you’ve encountered and even worked with coordinate systems. As historical data continually updates through GPS, understanding coordinate systems is increasingly crucial. However, not everyone knows why they exist or how to effectively use them for data-driven insights.
During this webinar, you’ll learn exactly what coordinate systems are and how you can use FME to maintain and transform your data’s coordinate systems in an easy-to-digest way, accurately representing the geographical space that it exists within. During this webinar, you will have the chance to:
- Enhance Your Understanding: Gain a clear overview of what coordinate systems are and their value
- Learn Practical Applications: Why we need datams and projections, plus units between coordinate systems
- Maximize with FME: Understand how FME handles coordinate systems, including a brief summary of the 3 main reprojectors
- Custom Coordinate Systems: Learn how to work with FME and coordinate systems beyond what is natively supported
- Look Ahead: Gain insights into where FME is headed with coordinate systems in the future
Don’t miss the opportunity to improve the value you receive from your coordinate system data, ultimately allowing you to streamline your data analysis and maximize your time. See you there!
Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Em...Erasmo Purificato
Slide of the tutorial entitled "Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Emerging Trends" held at UMAP'24: 32nd ACM Conference on User Modeling, Adaptation and Personalization (July 1, 2024 | Cagliari, Italy)
Sustainability requires ingenuity and stewardship. Did you know Pigging Solutions pigging systems help you achieve your sustainable manufacturing goals AND provide rapid return on investment.
How? Our systems recover over 99% of product in transfer piping. Recovering trapped product from transfer lines that would otherwise become flush-waste, means you can increase batch yields and eliminate flush waste. From raw materials to finished product, if you can pump it, we can pig it.
Implementations of Fused Deposition Modeling in real worldEmerging Tech
The presentation showcases the diverse real-world applications of Fused Deposition Modeling (FDM) across multiple industries:
1. **Manufacturing**: FDM is utilized in manufacturing for rapid prototyping, creating custom tools and fixtures, and producing functional end-use parts. Companies leverage its cost-effectiveness and flexibility to streamline production processes.
2. **Medical**: In the medical field, FDM is used to create patient-specific anatomical models, surgical guides, and prosthetics. Its ability to produce precise and biocompatible parts supports advancements in personalized healthcare solutions.
3. **Education**: FDM plays a crucial role in education by enabling students to learn about design and engineering through hands-on 3D printing projects. It promotes innovation and practical skill development in STEM disciplines.
4. **Science**: Researchers use FDM to prototype equipment for scientific experiments, build custom laboratory tools, and create models for visualization and testing purposes. It facilitates rapid iteration and customization in scientific endeavors.
5. **Automotive**: Automotive manufacturers employ FDM for prototyping vehicle components, tooling for assembly lines, and customized parts. It speeds up the design validation process and enhances efficiency in automotive engineering.
6. **Consumer Electronics**: FDM is utilized in consumer electronics for designing and prototyping product enclosures, casings, and internal components. It enables rapid iteration and customization to meet evolving consumer demands.
7. **Robotics**: Robotics engineers leverage FDM to prototype robot parts, create lightweight and durable components, and customize robot designs for specific applications. It supports innovation and optimization in robotic systems.
8. **Aerospace**: In aerospace, FDM is used to manufacture lightweight parts, complex geometries, and prototypes of aircraft components. It contributes to cost reduction, faster production cycles, and weight savings in aerospace engineering.
9. **Architecture**: Architects utilize FDM for creating detailed architectural models, prototypes of building components, and intricate designs. It aids in visualizing concepts, testing structural integrity, and communicating design ideas effectively.
Each industry example demonstrates how FDM enhances innovation, accelerates product development, and addresses specific challenges through advanced manufacturing capabilities.
AC Atlassian Coimbatore Session Slides( 22/06/2024)apoorva2579
This is the combined Sessions of ACE Atlassian Coimbatore event happened on 22nd June 2024
The session order is as follows:
1.AI and future of help desk by Rajesh Shanmugam
2. Harnessing the power of GenAI for your business by Siddharth
3. Fallacies of GenAI by Raju Kandaswamy
How RPA Help in the Transportation and Logistics Industry.pptxSynapseIndia
Revolutionize your transportation processes with our cutting-edge RPA software. Automate repetitive tasks, reduce costs, and enhance efficiency in the logistics sector with our advanced solutions.
UiPath Community Day Kraków: Devs4Devs ConferenceUiPathCommunity
We are honored to launch and host this event for our UiPath Polish Community, with the help of our partners - Proservartner!
We certainly hope we have managed to spike your interest in the subjects to be presented and the incredible networking opportunities at hand, too!
Check out our proposed agenda below 👇👇
08:30 ☕ Welcome coffee (30')
09:00 Opening note/ Intro to UiPath Community (10')
Cristina Vidu, Global Manager, Marketing Community @UiPath
Dawid Kot, Digital Transformation Lead @Proservartner
09:10 Cloud migration - Proservartner & DOVISTA case study (30')
Marcin Drozdowski, Automation CoE Manager @DOVISTA
Pawel Kamiński, RPA developer @DOVISTA
Mikolaj Zielinski, UiPath MVP, Senior Solutions Engineer @Proservartner
09:40 From bottlenecks to breakthroughs: Citizen Development in action (25')
Pawel Poplawski, Director, Improvement and Automation @McCormick & Company
Michał Cieślak, Senior Manager, Automation Programs @McCormick & Company
10:05 Next-level bots: API integration in UiPath Studio (30')
Mikolaj Zielinski, UiPath MVP, Senior Solutions Engineer @Proservartner
10:35 ☕ Coffee Break (15')
10:50 Document Understanding with my RPA Companion (45')
Ewa Gruszka, Enterprise Sales Specialist, AI & ML @UiPath
11:35 Power up your Robots: GenAI and GPT in REFramework (45')
Krzysztof Karaszewski, Global RPA Product Manager
12:20 🍕 Lunch Break (1hr)
13:20 From Concept to Quality: UiPath Test Suite for AI-powered Knowledge Bots (30')
Kamil Miśko, UiPath MVP, Senior RPA Developer @Zurich Insurance
13:50 Communications Mining - focus on AI capabilities (30')
Thomasz Wierzbicki, Business Analyst @Office Samurai
14:20 Polish MVP panel: Insights on MVP award achievements and career profiling
INDIAN AIR FORCE FIGHTER PLANES LIST.pdfjackson110191
These fighter aircraft have uses outside of traditional combat situations. They are essential in defending India's territorial integrity, averting dangers, and delivering aid to those in need during natural calamities. Additionally, the IAF improves its interoperability and fortifies international military alliances by working together and conducting joint exercises with other air forces.
Navigating Post-Quantum Blockchain: Resilient Cryptography in Quantum Threatsanupriti
In the rapidly evolving landscape of blockchain technology, the advent of quantum computing poses unprecedented challenges to traditional cryptographic methods. As quantum computing capabilities advance, the vulnerabilities of current cryptographic standards become increasingly apparent.
This presentation, "Navigating Post-Quantum Blockchain: Resilient Cryptography in Quantum Threats," explores the intersection of blockchain technology and quantum computing. It delves into the urgent need for resilient cryptographic solutions that can withstand the computational power of quantum adversaries.
Key topics covered include:
An overview of quantum computing and its implications for blockchain security.
Current cryptographic standards and their vulnerabilities in the face of quantum threats.
Emerging post-quantum cryptographic algorithms and their applicability to blockchain systems.
Case studies and real-world implications of quantum-resistant blockchain implementations.
Strategies for integrating post-quantum cryptography into existing blockchain frameworks.
Join us as we navigate the complexities of securing blockchain networks in a quantum-enabled future. Gain insights into the latest advancements and best practices for safeguarding data integrity and privacy in the era of quantum threats.
The DealBook is our annual overview of the Ukrainian tech investment industry. This edition comprehensively covers the full year 2023 and the first deals of 2024.
2. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
What is JSON Schema?
3. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
What is JSON Schema?
“JSON Schema is a vocabulary that allows you to
annotate and validate JSON documents.”
http://json-schema.org
4. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
What is JSON Schema?
“JSON Schema is a language-agnostic
description format for data structures, their
constraints and relationships.”
Jeremy Whitlock
5. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
Simplicity Readability Language Agnostic
JSON is essentially a simple way to
represent a dict/map/… of key/value
pairs, where the values can be 1 of 6
types.
The same JSON representation is
easily consumed by humans and
machines alike.
Most languages have native support
for JSON and/or a plethora of libraries
for consuming/producing JSON.
JSON Schema
6. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
Actual Historical Photo*
{
"message": "Ron was here!"
}
* Not really
7. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
Description Relationships/Reuse Constraints/Validation
JSON Schema provides everything
necessary to describe data structures
regardless of their complexity.
Understanding the relationships of
more complex data structures is easy
using JSON Schema.
The same document describing your
data structures can contain
constraints that will be used by JSON
Schema libraries to do validation for
you.
JSON Schema
8. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
JSON Schema Example
9. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
JSON Schema Example
{
"title": "Submit APIStrat proposal",
"completed": true
}
TO BE CONTINUED...
10. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
Disclaimer
All JSON Schema examples are in JSON but DO
NOT get too stuck on the JSON bit, JSON is not
required. In fact, anything that could be converted
to a JSON representation would work. For
example, YAML or a Go struct or Java Beans...
11. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
JSON Schema
{ }
12. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
$schema id
Used to identify the document as a
JSON Schema document, this property
value is a URL to the JSON Schema
standard your document will be using.
Used to uniquely identify your JSON
Schema document, this property value
is a URL to where your JSON Schema
document will be served. (This value
has an impact on reuse, discussed
later.)
JSON Schema - Document Metadata
13. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
JSON Schema Example
{
"$schema": "http://json-schema.org/schema#",
"id": "http://example.com/schemas/todo.json"
}
14. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
JSON Schema - Types
simple complex
● boolean
● integer*
● null
● number
● string
● array
● object
* Not a JSON type, specific to JSON Schema
15. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
JSON Schema Example
{
"$schema": "http://json-schema.org/schema#",
"id": "http://example.com/schemas/todo.json",
"type": "object"
}
16. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
JSON Schema Example
{
"$schema": "http://json-schema.org/schema#",
"id": "http://example.com/schemas/todo.json",
"type": "object",
"properties": {
"title": {
"type": "string"
},
"completed": {
"type": "boolean"
}
}
}
18. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
JSON Schema - Constraints and Formats
Constraints Formats
Used to apply limitations or
restrictions on the value represented in
the JSON Schema. For example,
restricting the maximum number of
characters in a string value.
Used to indicate the value is a more
specialized version of the specified
type. For example, indicating that a
string value is an email address.
19. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
JSON Schema Example
{
"$schema": "http://json-schema.org/schema#",
"id": "http://example.com/schemas/todo.json",
"type": "object",
"properties": {
"title": {
"type": "string",
"maxLength": 32
"minLength": 3
},
"completed": {
"type": "boolean"
}
},
"additionalProperties": false,
"required": ["title", "completed"]
}
21. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
JSON Schema - Validation
* Not really
22. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
JSON Schema - Reuse
Composition Definitions References
Combining multiple separate schemas
into one, more complex schema.
There is a convention that if your
JSON Schema document has multiple
schemas in it, you nest them within a
root property named "definitions" and
use references to them.
Pointers to other schemas, whether in
the same document or in another
document, to avoid duplication.
23. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
JSON Schema - Definitions
The definitions property at the root
of a JSON Schema document is a
key/value pair where the key is the
human-friendly name of the schema
and the value is a schema.
{
"$schema": "http://json-schema.org/schema#",
"id": "http://example.com/schemas/todo-types.json",
"definitions": {
"Password": {
"type": "string",
// Omitted for brevity
},
"User": {
"type": "object",
// Omitted for brevity
},
"Todo": {
"type": "object",
// Omitted for brevity
}
}
}
Yes, I know comments aren't allowed in JSON...
24. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
JSON Schema - References
References are a special JSON
object that has a $ref property in it
whose value is a JSON Pointer (URI)
to another location in the same file,
another file in its entirety or specific
location within another file.
{
"$schema": "http://json-schema.org/schema#",
"id": "http://example.com/schemas/todo-items.json",
"definitions": {
"Todo": {
"type": "object",
"properties": {
"owner": {
"$ref": "person.json"
},
"created": {
"$ref": "types.json#/definitions/Timestamp"
},
// Omitted for brevity
}
},
}
"type": "array",
"items": {
"$ref": "#/definitions/Todo
},
// Omitted for brevity
}
Yes, I know comments aren't allowed in JSON...
25. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
JSON Schema - Composition
allOf ● An array of schemas
● The data must validate against all schemas
anyOf ● An array of schemas
● The data must validate against at least one schema
oneOf ● An array of schemas
● The data must validate against only one schema
not* ● A subschema
● The data must not validate against the subschema
* not is not really a composition property but it's typically documented alongside the others
26. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
JSON Schema - Miscellaneous
Schema Metadata Default Values
The title and description properties
can be used on any schema to give it a
human readable name and description
of what the schema represents.
Sometimes your data structures have
optional values and using a default
property allows you to fill in the gaps
when the values are not provided
27. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
Using JSON Schema
● Code generation
● Contract enforcement
● Documentation generation
● Interface design
28. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
Using JSON Schema - OpenAPI
29. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
Using JSON Schema - Resources
JSON Homepage/Reference - http://www.json.org/
JSON Schema Tooling - http://json-schema.org/implementations.html
JSON Schema Homepage - http://json-schema.org/
Understanding JSON Schema Book - https://spacetelescope.github.io/understanding-json-schema/
JSON Schema Online Editor - https://jsonschema.net/#/editor
30. Source: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis non erat sem
The End
No...I'm not really signing autographs. They wouldn't be worth the paper they are written on. ;)