The document discusses Resource Description Framework (RDF) and its role in representing data on the Semantic Web. It provides examples of how RDF can represent relationships between resources through triples and graphs, and compares this to how the same information would be represented in XML. It also discusses RDF Schema (RDFS) and the Ontology Web Language (OWL) as languages used to build ontologies that can express richer relationships between resources on the Semantic Web.
The document discusses stateless authentication using OAuth2 and JWT, explaining the concepts of authentication, authorization, and single sign-on (SSO). It provides an in-depth look at OAuth2, detailing its actors, various grant flows, and the implementation of JWT as a token standard for secure authorization. Additionally, it outlines how to implement OAuth2 services, the differences between grant types, and the necessary setup for stateless authorization.
The document discusses the architecture of the web and REST APIs, detailing the significance of URIs in addressing resources and providing guidelines for designing user-friendly APIs. It emphasizes the importance of consistent URI structures, request methods, response codes, and proper use of metadata in HTTP communication. Additionally, it highlights the distinctions between various media types and formats, including XML and JSON, for data representation in web services.
The document summarizes a presentation given by Alex Borysov and Mykyta Protsenko comparing gRPC and REST. It provides an overview of gRPC, describing it as a high performance RPC framework. It then discusses some issues with REST including heterogeneous data formats and service discovery. Examples are given of implementing a sample aggregator service using both REST and gRPC to illustrate their differences.
- REST (Representational State Transfer) uses HTTP requests to transfer representations of resources between clients and servers. The format of the representation is determined by the content-type header and the interaction with the resource is determined by the HTTP verb used.
- The four main HTTP verbs are GET, PUT, DELETE, and POST. GET retrieves a representation of the resource and is safe, while PUT, DELETE, and POST can modify the resource's state in atomic operations.
- Resources are abstract concepts acted upon by HTTP requests, while representations are the actual data transmitted in responses. The representation may or may not accurately reflect the resource's current state.
Building RESTful Java Applications with EMFKenn Hussey
?
The document discusses building RESTful Java applications using the Eclipse Modeling Framework (EMF). It explains REST principles, CRUD operations, and provides an overview of the EMF, including its history and structure with a focus on ecore models. It also describes how to create models, including practical examples and generated code.
High Performance, Scalable MongoDB in a Bare Metal CloudMongoDB
?
This document summarizes the results of performance testing MongoDB deployments on bare metal cloud instances compared to public cloud instances. Small, medium, and large tests were conducted using different hardware configurations and data set sizes. The bare metal cloud instances consistently outperformed the public cloud instances, achieving higher operations per second, especially at higher concurrency levels. The document attributes the performance differences to the dedicated, tuned hardware resources of the bare metal instances compared to the shared resources of public cloud virtual instances.
Hyperledger Fabric practice material for Korea Polytechnics students
- Build Your First Network
- Chaincode Development
- Chaincode Devolopment via IBM Blockchain Platform
- Balance Transfer
- Vote system example using 'Balance Transfer' tutorial
This document discusses best practices for REST APIs. It recommends using HTTP methods appropriately, with GET for retrieving resources, POST for creating, PUT for updating entirely and PATCH for partial updates, and DELETE for removing. It also suggests making APIs intuitive, hypermedia-driven, versioned, discoverable and secured. Resources should be addressable and have clear relationships defined between them.
O documento explora como testar APIs em um contexto de pedidos de restaurantes, utilizando uma analogia com gar?om e pratos, descrevendo os tipos de testes, métodos HTTP e códigos de resposta. Métodos como GET, POST, PUT e DELETE s?o analisados com exemplos práticos de requisi??es e respostas. Ferramentas como Postman e Apache JMeter s?o sugeridas para realizar esses testes.
Introduction to question answering for linked data & big dataAndre Freitas
?
This document discusses question answering (QA) systems in the context of big data and heterogeneous data scenarios. It outlines the motivation and challenges for developing natural language interfaces for databases. The document covers the basic concepts and taxonomy of QA systems, including question types, answer types, data sources, and domains. It also discusses the anatomy and components of a typical QA system.
The document discusses stateless authentication using OAuth2 and JWT, explaining the concepts of authentication, authorization, and single sign-on (SSO). It provides an in-depth look at OAuth2, detailing its actors, various grant flows, and the implementation of JWT as a token standard for secure authorization. Additionally, it outlines how to implement OAuth2 services, the differences between grant types, and the necessary setup for stateless authorization.
The document discusses the architecture of the web and REST APIs, detailing the significance of URIs in addressing resources and providing guidelines for designing user-friendly APIs. It emphasizes the importance of consistent URI structures, request methods, response codes, and proper use of metadata in HTTP communication. Additionally, it highlights the distinctions between various media types and formats, including XML and JSON, for data representation in web services.
The document summarizes a presentation given by Alex Borysov and Mykyta Protsenko comparing gRPC and REST. It provides an overview of gRPC, describing it as a high performance RPC framework. It then discusses some issues with REST including heterogeneous data formats and service discovery. Examples are given of implementing a sample aggregator service using both REST and gRPC to illustrate their differences.
- REST (Representational State Transfer) uses HTTP requests to transfer representations of resources between clients and servers. The format of the representation is determined by the content-type header and the interaction with the resource is determined by the HTTP verb used.
- The four main HTTP verbs are GET, PUT, DELETE, and POST. GET retrieves a representation of the resource and is safe, while PUT, DELETE, and POST can modify the resource's state in atomic operations.
- Resources are abstract concepts acted upon by HTTP requests, while representations are the actual data transmitted in responses. The representation may or may not accurately reflect the resource's current state.
Building RESTful Java Applications with EMFKenn Hussey
?
The document discusses building RESTful Java applications using the Eclipse Modeling Framework (EMF). It explains REST principles, CRUD operations, and provides an overview of the EMF, including its history and structure with a focus on ecore models. It also describes how to create models, including practical examples and generated code.
High Performance, Scalable MongoDB in a Bare Metal CloudMongoDB
?
This document summarizes the results of performance testing MongoDB deployments on bare metal cloud instances compared to public cloud instances. Small, medium, and large tests were conducted using different hardware configurations and data set sizes. The bare metal cloud instances consistently outperformed the public cloud instances, achieving higher operations per second, especially at higher concurrency levels. The document attributes the performance differences to the dedicated, tuned hardware resources of the bare metal instances compared to the shared resources of public cloud virtual instances.
Hyperledger Fabric practice material for Korea Polytechnics students
- Build Your First Network
- Chaincode Development
- Chaincode Devolopment via IBM Blockchain Platform
- Balance Transfer
- Vote system example using 'Balance Transfer' tutorial
This document discusses best practices for REST APIs. It recommends using HTTP methods appropriately, with GET for retrieving resources, POST for creating, PUT for updating entirely and PATCH for partial updates, and DELETE for removing. It also suggests making APIs intuitive, hypermedia-driven, versioned, discoverable and secured. Resources should be addressable and have clear relationships defined between them.
O documento explora como testar APIs em um contexto de pedidos de restaurantes, utilizando uma analogia com gar?om e pratos, descrevendo os tipos de testes, métodos HTTP e códigos de resposta. Métodos como GET, POST, PUT e DELETE s?o analisados com exemplos práticos de requisi??es e respostas. Ferramentas como Postman e Apache JMeter s?o sugeridas para realizar esses testes.
Introduction to question answering for linked data & big dataAndre Freitas
?
This document discusses question answering (QA) systems in the context of big data and heterogeneous data scenarios. It outlines the motivation and challenges for developing natural language interfaces for databases. The document covers the basic concepts and taxonomy of QA systems, including question types, answer types, data sources, and domains. It also discusses the anatomy and components of a typical QA system.
The document is a tutorial from the EMW Wikiconference discussing Wikidata as a free knowledge base, detailing its goals and structure, including items, properties, and statements. It explains how to edit Wikidata and introduces its API, querying with SPARQL, and various projects built on Wikidata. Additionally, it covers classification, causation modeling, and practical examples involving politicians and historical events.
The document describes several papers on deep learning models for natural language processing tasks that utilize memory networks or attention mechanisms. It begins with references to seminal papers on end-to-end memory networks and dynamic memory networks. It then provides examples of tasks these models have been applied to, such as question answering, and summarizes the training procedures and architectures of memory networks and dynamic memory networks. Finally, it discusses extensions like utilizing episodic memory with multiple passes over the inputs and attention mechanisms.
The document discusses the author's experience working at a startup company. It describes the startup office environment and culture, which emphasizes an agile and flexible work style. The author advises readers to take chances and get experience working at startups early in their careers to help them learn and grow professionally. They should start small with projects but work steadily to build skills and experience.
18. 18
??
?? ???
label description ??? ??
Q2 Earth
third planet closest to the
Sun in the Solar System
?? ???? ?? ??
Q42 Douglas Adams English writer ???? ??? ??? ??
Q64 Berlin
capital city and state of Ge
rmany
??? ??? ??
Q80 Tim Berners-Lee Web developer ? ????
Q148
People's Republic
of China
state in East Asia ???????
????? ?? (+ a.k.a.
“??”)
Q153 ethanol type of alcohol compound ???
Q316 love
strong, positive emotion b
ased on affection
??
Q405 Moon
only natural satellite of Ear
th
? ??? ????
Q897511 cryptanalysis science ????
Q4489310 Turing reduction
2015-11-20 ?? ? ?
Q ?? ????? ????
?? ? ??? http://www.wikidata.org/wiki/Wikidata:Tours/ko
35. 35
????? SPARQL ?? #1
PREFIX wikibase: <http://wikiba.se/ontology#>
PREFIX wd: <http://www.wikidata.org/entity/>
PREFIX wdt: <http://www.wikidata.org/prop/direct/>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
SELECT ?politician ?cause ?politician_label ?cause_of_death_label WHERE {
?politician wdt:P106 wd:Q82955 . # find items that have "occupation
(P106): politician (Q82955)"
?politician wdt:P509 ?cause . # with a P509 (cause of death) claim
?cause wdt:P279* wd:Q12078 . # ... where the cause is a subclass
of (P279*) cancer (Q12078)
# ?politician wdt:P39 wd:Q11696 . # Uncomment this line to include only
U.S. Presidents
OPTIONAL {?politician rdfs:label ?politician_label filter
(lang(?politician_label) = "en") .}
OPTIONAL {?cause rdfs:label ?cause_of_death_label filter
(lang(?cause_of_death_label) = "en").}
}
ORDER BY ASC (?politician)
Total results: 557, duration: 633 ms.
??? ??? ??? ??
politician cause politician_label cause_of_death_label
Q1027427 Q189588 John R. Fellows stomach cancer
Q1028400 Q3242950Károly Grósz kidney cancer
Q10320767Q189588 Luiz Gushiken stomach cancer
Q10376143Q47912 Sérgio Guerra lung cancer
Q1064774 Q47912 Charles Hayes lung cancer
Q10664 Q188874 Neville Chamberlain colorectal cancer
Q10664 Q5526839Neville Chamberlain gastrointestinal cancer
….
??? Q: politician (Q82955), cancer (Q12078)
??? P: occupation (P106), subclass of (P279), cause of death (P509)
36. 36
????? SPARQL ?? #2
PREFIX wikibase: <http://wikiba.se/ontology#>
PREFIX wd: <http://www.wikidata.org/entity/>
PREFIX wdt: <http://www.wikidata.org/prop/direct/>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX p: <http://www.wikidata.org/prop/>
PREFIX q: <http://www.wikidata.org/prop/qualifier/>
PREFIX v: <http://www.wikidata.org/prop/statement/>
SELECT DISTINCT ?city ?cityLabel ?mayor ?mayorLabel WHERE {
?city wdt:P31/wdt:P279* wd:Q515 . # find instances of subclasses of city
?city p:P6 ?statement . # with a P6 (head of goverment) statement
?statement v:P6 ?mayor . # ... that has the value ?mayor
?mayor wdt:P21 wd:Q6581072 . # ... where the ?mayor has P21 (sex or gender)
female
FILTER NOT EXISTS { ?statement q:P582 ?x } # ... but the statement has no P582
(end date) qualifier
# Now select the population value of the ?city
# (wdt: properties use only statements of "preferred" rank if any, usually meaning
"current population")
?city wdt:P1082 ?population .
# Optionally, find English labels for city and mayor:
SERVICE wikibase:label {
bd:serviceParam wikibase:language "en" .
}
} ORDER BY DESC(?population) LIMIT 10
Total results: 10, duration: 7180 ms.
city cityLabel mayor mayorLabel
Q2807 Madrid Q19592761 Manuela Carmena
Q90 Paris Q2851133 Anne Hidalgo
Q16555 Houston Q213847 Annise Parker
Q1563 Havana Q6774124 Marta Hernández Romero
Q270 Warsaw Q271902 Hanna Gronkiewicz-Waltz
Q1492 Barcelona Q4779594 Ada Colau
Q472 Sofia Q444718 Yordanka Fandakova
Q1085 Prague Q18104657 Adriana Krná?ová
Q365 Cologne Q19285371 Henriette Reker
Q23197 Nashville Q16164719 Megan Barry
????? ???? ?? ? ?? ?? TOP 10
??? Q: city (Q515), female (Q6581072)
??? P: instance of (P31), subclass of (P279), head of government (P6),
sex or gender (P21), end time (P582), population (P1082)