Presentation of the paper "On Using JSON-LD to Create Evolvable RESTful Services" at the 3rd International Workshop on RESTful Design (WS-REST 2012) at WWW2012 in Lyon, France
Hydra: A Vocabulary for Hypermedia-Driven Web APIsMarkus Lanthaler
Presentation of the paper "Hydra: A Vocabulary for Hypermedia-Driven Web APIs" at the 6th Workshop on Linked Data on the Web (LDOW2013) at the WWW2013 in Rio de Janeiro, Brazil
JSON-LD is a set of W3C standards track specifications for representing Linked Data in JSON. It is fully compatible with the RDF data model, but allows developers to work with data entirely within JSON.
More information on JSON-LD can be found at http://json-ld.org/
Model Your Application Domain, Not Your JSON StructuresMarkus Lanthaler
Presentation of the paper "Model Your Application Domain, Not Your JSON Structures" at the 4th International Workshop on RESTful Design (WS-REST 2013) at the WWW2013 in Rio de Janeiro, Brazil
The document discusses PostgreSQL's roadmap for supporting JSON data. It describes how PostgreSQL introduced JSONB in 2014 to allow binary storage and indexing of JSON data, providing better performance than the text-based JSON type. The document outlines how PostgreSQL has implemented features from the SQL/JSON standard over time, including JSON path support. It proposes a new Generic JSON API (GSON) that would provide a unified way to work with JSON and JSONB data types, removing duplicated code and simplifying the addition of new features like partial decompression or different storage formats like BSON. GSON would help PostgreSQL work towards a single unified JSON data type as specified in SQL standards.
This document discusses how to achieve scale with MongoDB. It covers optimization tips like schema design, indexing, and monitoring. Vertical scaling involves upgrading hardware like RAM and SSDs. Horizontal scaling involves adding shards to distribute load. The document also discusses how MongoDB scales for large customers through examples of deployments handling high throughput and large datasets.
Hydra: A Vocabulary for Hypermedia-Driven Web APIsMarkus Lanthaler
Presentation of the paper "Hydra: A Vocabulary for Hypermedia-Driven Web APIs" at the 6th Workshop on Linked Data on the Web (LDOW2013) at the WWW2013 in Rio de Janeiro, Brazil
JSON-LD is a set of W3C standards track specifications for representing Linked Data in JSON. It is fully compatible with the RDF data model, but allows developers to work with data entirely within JSON.
More information on JSON-LD can be found at http://json-ld.org/
Model Your Application Domain, Not Your JSON StructuresMarkus Lanthaler
Presentation of the paper "Model Your Application Domain, Not Your JSON Structures" at the 4th International Workshop on RESTful Design (WS-REST 2013) at the WWW2013 in Rio de Janeiro, Brazil
The document discusses PostgreSQL's roadmap for supporting JSON data. It describes how PostgreSQL introduced JSONB in 2014 to allow binary storage and indexing of JSON data, providing better performance than the text-based JSON type. The document outlines how PostgreSQL has implemented features from the SQL/JSON standard over time, including JSON path support. It proposes a new Generic JSON API (GSON) that would provide a unified way to work with JSON and JSONB data types, removing duplicated code and simplifying the addition of new features like partial decompression or different storage formats like BSON. GSON would help PostgreSQL work towards a single unified JSON data type as specified in SQL standards.
This document discusses how to achieve scale with MongoDB. It covers optimization tips like schema design, indexing, and monitoring. Vertical scaling involves upgrading hardware like RAM and SSDs. Horizontal scaling involves adding shards to distribute load. The document also discusses how MongoDB scales for large customers through examples of deployments handling high throughput and large datasets.
This document discusses Open Policy Agent (OPA), an open source general-purpose policy engine. It provides examples of how OPA can be used to enforce various types of policies across complex environments in a flexible way. OPA treats policy decisions as separate from enforcement, stores policies and data in-memory, and uses partial evaluation and indexing to evaluate policies efficiently. It allows policies to be written declaratively using Rego and enforced for services, infrastructure, and other resources regardless of how they are implemented. The document demonstrates examples of using OPA for authorization, RBAC, and other policies across multiple domains.
Stop Reinventing the Wheel! Use Linked Data to Build Better APIsMarkus Lanthaler
The document contains nutrition information for a food item including 667 calories, 9g of protein and 49g of carbohydrates. It also shows examples of representing nutrition information using HTML, JSON-LD and schema.org syntax.
The document describes a concert event for the band CAKE performing live at the APIcon 2014 conference on May 28, 2014 from 8pm to 11pm at the Hilton San Francisco Union Square hotel.
This talk introduces Spring's REST stack - Spring MVC, Spring HATEOAS, Spring Data REST, Spring Security OAuth and Spring Social - while refining an API to move higher up the Richardson maturity model
Intro to MongoDB
Get a jumpstart on MongoDB, use cases, and next steps for building your first app with Buzz Moschetti, MongoDB Enterprise Architect.
@BuzzMoschetti
Vladimir Tsukur presented on hypermedia APIs and HATEOAS. He discussed REST, the Richardson Maturity Model, CRUD vs more advanced APIs, and link relations. He demonstrated Mason, a proposed hypermedia format that uses controls and namespaces to define available state transitions and link semantics.
This document provides an introduction and overview of Open Policy Agent (OPA). It discusses how OPA can be used to add fine-grained policy controls to other projects. Key points include:
- OPA allows integrating policy decisions from a project into OPA and offloading policy logic. Policies can be authored in OPA and decisions retrieved.
- Policies are invoked by sending decision requests to OPA APIs. The input is JSON and the response is also JSON.
- Simple policies involve looking up values, comparing values, assigning variables, and creating rules with heads and bodies. Rules with the same head are OR'd together.
- Policies can handle arrays and iteration by using an
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.
This document provides an overview and introduction to Elasticsearch. It discusses the speaker's experience and community involvement. It then covers how to set up Elasticsearch and Kibana locally. The rest of the document describes various Elasticsearch concepts and features like clusters, nodes, indexes, documents, shards, replicas, and building search-based applications. It also discusses using Elasticsearch for big data, different search capabilities, and text analysis.
"SPARQL Cheat Sheet" is a short collection of slides intended to act as a guide to SPARQL developers. It includes the syntax and structure of SPARQL queries, common SPARQL prefixes and functions, and help with RDF datasets.
The "SPARQL Cheat Sheet" is intended to accompany the SPARQL By Example slides available at http://www.cambridgesemantics.com/2008/09/sparql-by-example/ .
1. The document discusses GraphQL, an API query language created by Facebook. It introduces GraphQL concepts like queries, mutations, and subscriptions.
2. An example compares fetching data from a REST API versus a GraphQL API. GraphQL allows fetching all required data with a single request, whereas REST requires multiple requests.
3. React and GraphQL are a good fit because GraphQL is declarative, allowing developers to focus on what data is needed rather than how to fetch it. Popular GraphQL clients like Apollo make fetching data even more declarative.
These are slides from our Big Data Warehouse Meetup in April. We talked about NoSQL databases: What they are, how they’re used and where they fit in existing enterprise data ecosystems.
Mike O’Brian from 10gen, introduced the syntax and usage patterns for a new aggregation system in MongoDB and give some demonstrations of aggregation using the new system. The new MongoDB aggregation framework makes it simple to do tasks such as counting, averaging, and finding minima or maxima while grouping by keys in a collection, complementing MongoDB’s built-in map/reduce capabilities.
For more information, visit our website at http://casertaconcepts.com/ or email us at info@casertaconcepts.com.
This document provides an overview of advanced operations in NGSI-LD (Next Generation SI-LD), including:
- Specific headers used in NGSI-LD requests
- Supported content types and best practices for JSON-LD payloads
- Examples of temporal queries, geoqueries, and language maps
- Details on pagination, time limiting queries, and supported response formats
The document discusses vulnerabilities in JSON Web Tokens (JWT). It begins by introducing JWTs and their typical uses. It then covers the JWT format and components like the header, payload, and signature. Various signing algorithms are presented. Attacks like open redirects, header injection, and algorithm downgrades are demonstrated through abusing the "jku" and "x5u" parameters. Recommendations are provided like using strong keys, reviewing libraries, enforcing algorithms, and testing for vulnerabilities. In conclusion, JWTs are complex and insecure by design, so careful implementation and testing is needed.
NGSI-LD provides a more complex data model than NGSIv2 by introducing properties, relationships, and additional metadata. It evolves NGSIv2 to support linked data by making payloads valid JSON-LD. This allows for a navigable knowledge graph compared to the simpler NGSIv2 model. The document discusses the differences between the two models and provides examples of creating and reading entity data in each.
This document provides an agenda for discussing JavaScript ES6 features such as promises, arrow functions, constants, modules, classes, transpilation, default parameters, and template strings. It also discusses how to use ES6 today via transpilation with tools like Babel and Traceur, and which companies are using ES6 and those transpilation tools.
The document discusses JSON (JavaScript Object Notation), which is a lightweight format for exchanging data between a client and server. It notes that JSON is easy for humans to read and write, and easy for machines to parse and generate. The document outlines the syntax of JSON, including that objects use curly braces, members use key-value pairs separated by commas, and arrays use square brackets. It also discusses parsing and accessing JSON data.
The Document Object Model (DOM) is a standard for representing and interacting with objects in HTML, XML and SVG documents. It defines the logical structure of documents and the way a document is accessed and manipulated. The DOM represents the document as nodes and objects, which can be manipulated programmatically by JavaScript to change the document structure, style and content. It allows dynamic access to and manipulation of page content that is useful for building interactive web applications. The DOM specification is developed by the W3C and provides a platform- and language-neutral interface that can be used across different web technologies.
Modern Security with OAuth 2.0 and JWT and Spring by Dmitry BuzdinJava User Group Latvia
Have you ever wondered how single-sign-on on sites like Google and Facebook works? Are you a fan of stateless application architectures? Do you want to learn how to put together a modern security approach for your next Spring Boot project? If the answer is yes, to anything above, then this session is for you. Dmitry will explain what is OAuth 2.0 and JWT, why are they popular, and how to integrate them in Java project.
JSON-LD provides a standard representation for expressing linked data using JSON objects. It allows objects to represent entities with keys as properties, and arrays to express property values. Contexts define terms and associate properties and values with IRIs. JSON-LD brings the benefits of linked data to web applications by mapping JSON structures to RDF triples.
Aligning Web Services with the Semantic Web to Create a Global Read-Write Gra...Markus Lanthaler
Presentation of the paper "Aligning Web Services with the Semantic Web to Create a Global Read-Write Graph of Data" gave at the 9th IEEE European Conference on Web Services (ECOWS 2011) in Lugano, Switzerland.
Despite significant research and development efforts, the vision of the Semantic Web yielding to a Web of Data has not yet become reality. Even though initiatives such as Linking Open Data gained traction recently, the Web of Data is still clearly outpaced by the growth of the traditional, document-based Web. Instead of releasing data in the form of RDF, many publishers choose to publish their data in the form of Web services. The reasons for this are manifold. Given that RESTful Web services closely resemble the document-based Web, they are not only perceived as less complex and disruptive, but also provide read-write interfaces to the underlying data. In contrast, the current Semantic Web is essentially read-only which clearly inhibits net-working effects and engagement of the crowd. On the other hand, the prevalent use of proprietary schemas to represent the data published by Web services inhibits generic browsers or crawlers to access and understand this data; the consequence are islands of data instead of a global graph of data forming the envisioned Semantic Web. We thus propose a novel approach to integrate Web services into the Web of Data by introducing an algorithm to translate SPARQL queries to HTTP requests. The aim is to create a global read-write graph of data and to standardize the mashup development process. We try to keep the approach as familiar and simple as possible to lower the entry barrier and foster the adoption of our approach. Thus, we based our proposal on SEREDASj, a semantic description language for RESTful data services, for making proprietary JSON service schemas accessible.
This document discusses Open Policy Agent (OPA), an open source general-purpose policy engine. It provides examples of how OPA can be used to enforce various types of policies across complex environments in a flexible way. OPA treats policy decisions as separate from enforcement, stores policies and data in-memory, and uses partial evaluation and indexing to evaluate policies efficiently. It allows policies to be written declaratively using Rego and enforced for services, infrastructure, and other resources regardless of how they are implemented. The document demonstrates examples of using OPA for authorization, RBAC, and other policies across multiple domains.
Stop Reinventing the Wheel! Use Linked Data to Build Better APIsMarkus Lanthaler
The document contains nutrition information for a food item including 667 calories, 9g of protein and 49g of carbohydrates. It also shows examples of representing nutrition information using HTML, JSON-LD and schema.org syntax.
The document describes a concert event for the band CAKE performing live at the APIcon 2014 conference on May 28, 2014 from 8pm to 11pm at the Hilton San Francisco Union Square hotel.
This talk introduces Spring's REST stack - Spring MVC, Spring HATEOAS, Spring Data REST, Spring Security OAuth and Spring Social - while refining an API to move higher up the Richardson maturity model
Intro to MongoDB
Get a jumpstart on MongoDB, use cases, and next steps for building your first app with Buzz Moschetti, MongoDB Enterprise Architect.
@BuzzMoschetti
Vladimir Tsukur presented on hypermedia APIs and HATEOAS. He discussed REST, the Richardson Maturity Model, CRUD vs more advanced APIs, and link relations. He demonstrated Mason, a proposed hypermedia format that uses controls and namespaces to define available state transitions and link semantics.
This document provides an introduction and overview of Open Policy Agent (OPA). It discusses how OPA can be used to add fine-grained policy controls to other projects. Key points include:
- OPA allows integrating policy decisions from a project into OPA and offloading policy logic. Policies can be authored in OPA and decisions retrieved.
- Policies are invoked by sending decision requests to OPA APIs. The input is JSON and the response is also JSON.
- Simple policies involve looking up values, comparing values, assigning variables, and creating rules with heads and bodies. Rules with the same head are OR'd together.
- Policies can handle arrays and iteration by using an
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.
This document provides an overview and introduction to Elasticsearch. It discusses the speaker's experience and community involvement. It then covers how to set up Elasticsearch and Kibana locally. The rest of the document describes various Elasticsearch concepts and features like clusters, nodes, indexes, documents, shards, replicas, and building search-based applications. It also discusses using Elasticsearch for big data, different search capabilities, and text analysis.
"SPARQL Cheat Sheet" is a short collection of slides intended to act as a guide to SPARQL developers. It includes the syntax and structure of SPARQL queries, common SPARQL prefixes and functions, and help with RDF datasets.
The "SPARQL Cheat Sheet" is intended to accompany the SPARQL By Example slides available at http://www.cambridgesemantics.com/2008/09/sparql-by-example/ .
1. The document discusses GraphQL, an API query language created by Facebook. It introduces GraphQL concepts like queries, mutations, and subscriptions.
2. An example compares fetching data from a REST API versus a GraphQL API. GraphQL allows fetching all required data with a single request, whereas REST requires multiple requests.
3. React and GraphQL are a good fit because GraphQL is declarative, allowing developers to focus on what data is needed rather than how to fetch it. Popular GraphQL clients like Apollo make fetching data even more declarative.
These are slides from our Big Data Warehouse Meetup in April. We talked about NoSQL databases: What they are, how they’re used and where they fit in existing enterprise data ecosystems.
Mike O’Brian from 10gen, introduced the syntax and usage patterns for a new aggregation system in MongoDB and give some demonstrations of aggregation using the new system. The new MongoDB aggregation framework makes it simple to do tasks such as counting, averaging, and finding minima or maxima while grouping by keys in a collection, complementing MongoDB’s built-in map/reduce capabilities.
For more information, visit our website at http://casertaconcepts.com/ or email us at info@casertaconcepts.com.
This document provides an overview of advanced operations in NGSI-LD (Next Generation SI-LD), including:
- Specific headers used in NGSI-LD requests
- Supported content types and best practices for JSON-LD payloads
- Examples of temporal queries, geoqueries, and language maps
- Details on pagination, time limiting queries, and supported response formats
The document discusses vulnerabilities in JSON Web Tokens (JWT). It begins by introducing JWTs and their typical uses. It then covers the JWT format and components like the header, payload, and signature. Various signing algorithms are presented. Attacks like open redirects, header injection, and algorithm downgrades are demonstrated through abusing the "jku" and "x5u" parameters. Recommendations are provided like using strong keys, reviewing libraries, enforcing algorithms, and testing for vulnerabilities. In conclusion, JWTs are complex and insecure by design, so careful implementation and testing is needed.
NGSI-LD provides a more complex data model than NGSIv2 by introducing properties, relationships, and additional metadata. It evolves NGSIv2 to support linked data by making payloads valid JSON-LD. This allows for a navigable knowledge graph compared to the simpler NGSIv2 model. The document discusses the differences between the two models and provides examples of creating and reading entity data in each.
This document provides an agenda for discussing JavaScript ES6 features such as promises, arrow functions, constants, modules, classes, transpilation, default parameters, and template strings. It also discusses how to use ES6 today via transpilation with tools like Babel and Traceur, and which companies are using ES6 and those transpilation tools.
The document discusses JSON (JavaScript Object Notation), which is a lightweight format for exchanging data between a client and server. It notes that JSON is easy for humans to read and write, and easy for machines to parse and generate. The document outlines the syntax of JSON, including that objects use curly braces, members use key-value pairs separated by commas, and arrays use square brackets. It also discusses parsing and accessing JSON data.
The Document Object Model (DOM) is a standard for representing and interacting with objects in HTML, XML and SVG documents. It defines the logical structure of documents and the way a document is accessed and manipulated. The DOM represents the document as nodes and objects, which can be manipulated programmatically by JavaScript to change the document structure, style and content. It allows dynamic access to and manipulation of page content that is useful for building interactive web applications. The DOM specification is developed by the W3C and provides a platform- and language-neutral interface that can be used across different web technologies.
Modern Security with OAuth 2.0 and JWT and Spring by Dmitry BuzdinJava User Group Latvia
Have you ever wondered how single-sign-on on sites like Google and Facebook works? Are you a fan of stateless application architectures? Do you want to learn how to put together a modern security approach for your next Spring Boot project? If the answer is yes, to anything above, then this session is for you. Dmitry will explain what is OAuth 2.0 and JWT, why are they popular, and how to integrate them in Java project.
JSON-LD provides a standard representation for expressing linked data using JSON objects. It allows objects to represent entities with keys as properties, and arrays to express property values. Contexts define terms and associate properties and values with IRIs. JSON-LD brings the benefits of linked data to web applications by mapping JSON structures to RDF triples.
Aligning Web Services with the Semantic Web to Create a Global Read-Write Gra...Markus Lanthaler
Presentation of the paper "Aligning Web Services with the Semantic Web to Create a Global Read-Write Graph of Data" gave at the 9th IEEE European Conference on Web Services (ECOWS 2011) in Lugano, Switzerland.
Despite significant research and development efforts, the vision of the Semantic Web yielding to a Web of Data has not yet become reality. Even though initiatives such as Linking Open Data gained traction recently, the Web of Data is still clearly outpaced by the growth of the traditional, document-based Web. Instead of releasing data in the form of RDF, many publishers choose to publish their data in the form of Web services. The reasons for this are manifold. Given that RESTful Web services closely resemble the document-based Web, they are not only perceived as less complex and disruptive, but also provide read-write interfaces to the underlying data. In contrast, the current Semantic Web is essentially read-only which clearly inhibits net-working effects and engagement of the crowd. On the other hand, the prevalent use of proprietary schemas to represent the data published by Web services inhibits generic browsers or crawlers to access and understand this data; the consequence are islands of data instead of a global graph of data forming the envisioned Semantic Web. We thus propose a novel approach to integrate Web services into the Web of Data by introducing an algorithm to translate SPARQL queries to HTTP requests. The aim is to create a global read-write graph of data and to standardize the mashup development process. We try to keep the approach as familiar and simple as possible to lower the entry barrier and foster the adoption of our approach. Thus, we based our proposal on SEREDASj, a semantic description language for RESTful data services, for making proprietary JSON service schemas accessible.
At Stormpath we spent 18 months researching API design best practices. Join Les Hazlewood, Stormpath CTO and Apache Shiro Chair, as he explains how to design a secure REST API, the right way. He'll also hang out for a live Q&A session at the end.
Sign up for Stormpath: https://api.stormpath.com/register
More from Stormpath: http://www.stormpath.com/blog
Les will cover:
REST + JSON API Design
Base URL design tips
API Security
Versioning for APIs
API Resource Formatting
API Return Values and Content Negotiation
API References (Linking)
API Pagination, Parameters, & Errors
Method Overloading
Resource Expansion and Partial Responses
Error Handling
Multi-tenancy
2011 4IZ440 Semantic Web – RDF, SPARQL, and software APIsJosef Petrák
The document discusses the Semantic Web and RDF data formats. It provides an overview of RDF syntaxes like RDF/XML, N3, N-Triples, RDF/JSON, and RDFa. It also discusses software APIs for working with RDF data in languages like Java, PHP, and Ruby. The document outlines handling RDF data using statement-centric, resource-centric, and ontology-centric models, as well as named graphs. It provides examples of reading RDF data from files and querying RDF data using SPARQL.
A Semantic Description Language for RESTful Data Services to Combat SemaphobiaMarkus Lanthaler
The document proposes a semantic description language (SEREDASj) to provide machine-readable descriptions of RESTful web services. It aims to address the lack of standards for describing REST APIs and help combat "semaphobia", the fear of semantics. The language builds on previous work but is tailored specifically for REST by focusing on simplicity and supporting many use cases including discovery and composition of RESTful services.
This document provides an overview of designing beautiful REST+JSON APIs. It discusses REST fundamentals like resources, methods, media types, and hypermedia as the engine of application state (HATEOAS). It covers best practices for API design like base URLs, versioning, resource formats, linking, pagination, and more. The goal is to help API providers design APIs that are easy for developers to consume while also being scalable and secure.
This document contains information from a Twitter engineering presentation about the Twitter API and core objects like users, timelines, tweets, and the social graph. It includes examples of user and tweet JSON structures, as well as screenshots and links to documentation, code samples, and visualizations related to analyzing tweets and trends on Twitter. The presentation encourages attendees to explore the Twitter API and contact Twitter engineers with any other questions.
Linked Data in Use: Schema.org, JSON-LD and hypermedia APIs - Front in Bahia...Ícaro Medeiros
In my talk I walk throgh Semantic Web initiatives, like RDF and SPARQL, linked data principles, discuss some implementation and adoption issues and talk about semantic annotation in HTML. Semantic annotation using the Schema.org vocabulary is demonstrated using both HTML 5 Microdata or JSON-LD input. There is a strong highlight in benefits seen in Google search results with Rich Snippets, Actions in Email, and Google Now with real examples.
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.
My presentation at SMX Milan 2015. New ways to compile and offer structured data to search engines for improved online visibility. Real life examples ready to use for websites and blogs.
This document summarizes SPARQL, the SPARQL query language used for querying and retrieving data stored in RDF format. It discusses key concepts such as RDF, terms, syntax, patterns, and constraints. RDF represents information as subject-predicate-object triples that can be queried using SPARQL. SPARQL allows constructing basic and complex graph patterns to match against the RDF graph. It also supports value filters, ordering, pagination and other solution modifiers. The document provides examples of SPARQL queries to retrieve data from RDF graphs based on different conditions and constraints.
This document discusses various techniques for handling form data submitted to servlets, including reading parameters, handling missing or malformed data, and filtering special characters.
It provides code examples of:
1) Reading individual and all parameters submitted via GET and POST.
2) Checking for missing parameters and using default values. It shows code for a resume posting site that uses default fonts/sizes if values are missing.
3) Filtering special HTML characters like < and > from parameter values before displaying them. It demonstrates a code sample servlet that properly filters values.
The document discusses strategies for handling missing or malformed data like using default values, redisplaying the form, and covering more advanced options using frameworks
New approaches to hypertext and REST in a mobile-first worldIsrael Shirk
The document discusses new approaches to hypertext and REST APIs in a mobile-first world. It proposes using JSON Hyperschema to define self-describing APIs and objects that can be interpreted across different devices through custom components. This allows the backend to remain the same while the frontend is laid out differently for each client type, enabling data-centric design on the server and render-focused clients.
AMS, API, RAILS and a developer, a Love StoryJoão Moura
A lot of people have being using Rails to develop both their internal or external API, but building a high quality API can be hard, and performance is a key point to achieve it.
I'll share my stories with APIs, and tell you how Active Model Serializer, component of Rails-API, helped me. AMS have being used across thousands of applications bringing convention over configuration to JSON generation.
This talk will give you a sneak peek of a new version of AMS that we have being working on, it's new cache conventions, and how it's being considered to be shipped by default in new Rails 5.
This document discusses using security data for incident response and customizing the ELSA (Enterprise Log Search and Archive) tool. It describes how ELSA allows searching across different data sources to provide context, such as building a timeline of events from various logs. It also explains how to extend ELSA through writing parsers, plugins, and transforms to integrate additional data sources and customize its functionality. The goal is to quickly understand security incidents by correlating all available information.
JLIFF: Where we are, and where we're goingChase Tingley
Presented at FEISGILTT 2017. An introduction to JLIFF, a JSON-based version of the XLIFF 2.x standard currently under development by the OASIS XLIFF-OMOS technical committee.
This document summarizes a presentation on Spring Data by Eric Bottard and Florent Biville. Spring Data aims to provide a consistent programming model for new data stores while retaining store-specific features. It uses conventions over configuration for mapping objects to data stores. Repositories provide basic CRUD functionality without implementations. Magic finders allow querying by properties. Pagination and sorting are also supported.
This document provides an introduction to linked data and RDF. It discusses:
1. The principles of linked data, which involve using URIs to identify things and including links to other related resources.
2. The goals of linked data, which are to transfer information between machines without loss of meaning by identifying data on the web using shared vocabularies and RDF.
3. An overview of RDF, which structures data as subject-predicate-object triples and can be serialized in formats like RDF/XML and Turtle to represent typed links between resources.
The document describes an event called "API Days NZ" that will take place from October 6-7, 2016 at the Viaduct Events Centre in Auckland, New Zealand. It provides details on the start and end dates, location, and offers ticket sales for early bird pricing between June 1 and August 31, 2016.
The document contains JSON-LD markup describing a music event taking place on November 6, 2014 at The Worksmans Club in Dublin, Ireland, including details about the location and offers. It also includes snippets describing collections of attendees and classes of objects with supported properties.
Why and How to Optimize Your Data Architecture for an Integrated FutureMarkus Lanthaler
The document contains nutrition information for a recipe including calories (667 kcal), protein (9g), and carbohydrates (49g). This information is formatted using schema.org vocabulary and syntax. The document also includes examples of using schema.org for other tasks like representing a collection of recipes and querying recipe data.
The Web 3.0 is just around the corner. Be prepared!Markus Lanthaler
This document contains nutrition information for a food item containing 667 calories, 9g of protein and 49g of carbohydrates. It also includes JSON snippets defining schema.org contexts, types, classes and collections for representing recipes and collections of recipes.
The document discusses the evolution of hypermedia APIs and their use of JSON-LD and Hydra to define operations on resources. It shows examples of representing an event and its attendees as JSON-LD documents with Hydra definitions for POST operations to add attendees. The document concludes by thanking attendees and providing contact information for questions.
Presentation of the paper "Creating 3rd Generation Web APIs with Hydra" at the 22nd Internation World Wide Web Conference (WWW2013) in Rio de Janeiro, Brazil
Presentation of the paper "A Web of Things to Reduce Energy Wastage" at the 10th IEEE International Conference on Industrial Informatics (INDIN 2012) in Beijing, China
Presentation of SAPS at the 1st International Workshop on the Information-Centric Web (IC-Web 2011) at the 11th IEEE/IPSJ International Symposium on Applications and the Internet (SAINT 2011) in Munich, Germany
The presentation will delve into the ASIMOV project, a novel initiative that leverages Retrieval-Augmented Generation (RAG) to provide precise, domain-specific assistance to telecommunications engineers and technicians. The session will focus on the unique capabilities of Milvus, the chosen vector database for the project, and its advantages over other vector databases.
Attending this session will give you a deeper understanding of the potential of RAG and Milvus DB in telecommunications engineering. You will learn how to address common challenges in the field and enhance the efficiency of their operations. The session will equip you with the knowledge to make informed decisions about the choice of vector databases, and how best to use them for your use-cases
Dev Dives: Mining your data with AI-powered Continuous DiscoveryUiPathCommunity
Want to learn how AI and Continuous Discovery can uncover impactful automation opportunities? Watch this webinar to find out more about UiPath Discovery products!
Watch this session and:
👉 See the power of UiPath Discovery products, including Process Mining, Task Mining, Communications Mining, and Automation Hub
👉 Watch the demo of how to leverage system data, desktop data, or unstructured communications data to gain deeper understanding of existing processes
👉 Learn how you can benefit from each of the discovery products as an Automation Developer
🗣 Speakers:
Jyoti Raghav, Principal Technical Enablement Engineer @UiPath
Anja le Clercq, Principal Technical Enablement Engineer @UiPath
⏩ Register for our upcoming Dev Dives July session: Boosting Tester Productivity with Coded Automation and Autopilot™
👉 Link: https://bit.ly/Dev_Dives_July
This session was streamed live on June 27, 2024.
Check out all our upcoming Dev Dives 2024 sessions at:
🚩 https://bit.ly/Dev_Dives_2024
this resume for sadika shaikh bca studentSadikaShaikh7
I am a dedicated BCA student with a strong foundation in web technologies, including PHP and MySQL. I have hands-on experience in Java and Python, and a solid understanding of data structures. My technical skills are complemented by my ability to learn quickly and adapt to new challenges in the ever-evolving field of computer science.
An invited talk given by Mark Billinghurst on Research Directions for Cross Reality Interfaces. This was given on July 2nd 2024 as part of the 2024 Summer School on Cross Reality in Hagenberg, Austria (July 1st - 7th)
Multimodal Retrieval Augmented Generation (RAG) with MilvusZilliz
We've seen an influx of powerful multimodal capabilities in many LLMs. In this talk, we'll vectorize a dataset of images and texts into the same embedding space, store them in Milvus, retrieve all relevant data using multilingual texts and/or images and input multimodal data as context into GPT-4o.
From 1M to 1B Features Per Second: Scaling ShareChat's ML Feature StoreScyllaDB
ShareChat's Ivan Burmistrov walks through how they built a low latency ML Feature Store based on ScyllaDB which initially failed to meet the scalability requirements and failed on 1 million features per second load, but has been successfully scaled 1000 times to handle 1 billing features per second without scaling the underlying database.
CNSCon 2024 Lightning Talk: Don’t Make Me Impersonate My IdentityCynthia Thomas
Identities are a crucial part of running workloads on Kubernetes. How do you ensure Pods can securely access Cloud resources? In this lightning talk, you will learn how large Cloud providers work together to share Identity Provider responsibilities in order to federate identities in multi-cloud environments.
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.
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.
Details of description part II: Describing images in practice - Tech Forum 2024BookNet Canada
This presentation explores the practical application of image description techniques. Familiar guidelines will be demonstrated in practice, and descriptions will be developed “live”! If you have learned a lot about the theory of image description techniques but want to feel more confident putting them into practice, this is the presentation for you. There will be useful, actionable information for everyone, whether you are working with authors, colleagues, alone, or leveraging AI as a collaborator.
Link to presentation recording and transcript: https://bnctechforum.ca/sessions/details-of-description-part-ii-describing-images-in-practice/
Presented by BookNet Canada on June 25, 2024, with support from the Department of Canadian Heritage.