Context-aware application development with FIWARE, used in the #CPBR8 workshop. It includes basic and advanced Orion topics, along with usage examples.
FIWARE Developers Week_ Introduction to Managing Context Information at Large...FIWARE
Introduction to Managing Context Information at Large Scale by Fermín Galán and Leandro Gullén (@leandrogullen @fermingalan) for Developers Week
www.fiware.org
FIWARE: Managing Context Information at large scaleFermin Galan
This presentation describes how context management is implemented in FIWARE platform, base don Orion Context Broker GEri. Both basic usage of Context Broker and advanced topics are included.
FIWARE Developers Week_ Introduction to Managing Context Information at Large...FIWARE
Introduction to Managing Context Information at Large Scale by Fermín Galán and Leandro Gullén (@leandrogullen @fermingalan) for Developers Week
www.fiware.org
FIWARE: Managing Context Information at large scaleFermin Galan
This presentation describes how context management is implemented in FIWARE platform, base don Orion Context Broker GEri. Both basic usage of Context Broker and advanced topics are included.
FIWARE NGSI: Managing Context Information at Large ScaleFIWARE
FIWARE NGSI: Managing Context Information at Large Scale, by Fermín Galán.
Orion Context Broker developing team. 1st FIWARE Summit, Málaga, Dec. 13-15, 2016.
NGSIv2 Overview for Developers That Already Know NGSIv1Fermin Galan
This document describes the novelties in NGSIv2 for people already familiar with NGSIv1. Thus, you would learn how to do the things you are familiar with NGSIv1 now in NGSIv2 as long as new and powerfull capabilities of the new version of the API. Some knowledge in NGSIv1 API is required.
A brief description to FIWARE Ecosystem and detailed one of the FIWARE IoT framework. Introduction to Orion Context Broker, IoT Agent - Ultralight 2.0 and Short Term Historic - Comet.
(MBL303) Build Mobile Apps for IoT Devices and IoT Apps for DevicesAmazon Web Services
Whether you are creating a mobile app that controls an IoT device (such as a wearable) or an IoT device that uses the mobile phone as the relay/hub to connect to the cloud, there are various design patterns to consider. In this session, we will focus on use cases and architectures for mobile phone and IoT-connected products that leverage proximal network protocols, Wi-Fi, or cellular to connect to the cloud for high-velocity and low-velocity telemetry or command and control.
FIWARE NGSI: Managing Context Information at Large ScaleFIWARE
FIWARE NGSI: Managing Context Information at Large Scale, by Fermín Galán.
Orion Context Broker developing team. 1st FIWARE Summit, Málaga, Dec. 13-15, 2016.
NGSIv2 Overview for Developers That Already Know NGSIv1Fermin Galan
This document describes the novelties in NGSIv2 for people already familiar with NGSIv1. Thus, you would learn how to do the things you are familiar with NGSIv1 now in NGSIv2 as long as new and powerfull capabilities of the new version of the API. Some knowledge in NGSIv1 API is required.
A brief description to FIWARE Ecosystem and detailed one of the FIWARE IoT framework. Introduction to Orion Context Broker, IoT Agent - Ultralight 2.0 and Short Term Historic - Comet.
(MBL303) Build Mobile Apps for IoT Devices and IoT Apps for DevicesAmazon Web Services
Whether you are creating a mobile app that controls an IoT device (such as a wearable) or an IoT device that uses the mobile phone as the relay/hub to connect to the cloud, there are various design patterns to consider. In this session, we will focus on use cases and architectures for mobile phone and IoT-connected products that leverage proximal network protocols, Wi-Fi, or cellular to connect to the cloud for high-velocity and low-velocity telemetry or command and control.
This is a complement of http://www.slideshare.net/fermingalan/fiware-managing-context-information-at-large-scale, including a set of basic and advanced exercises with Orion to be done by FIWARE Deverlopers Week participants.
[SOCRS2013]Differential Context Modeling in Collaborative FilteringYONG ZHENG
Abstract: Context-aware recommender systems (CARS) try to adapt their recommendations to users’ specific contextual situations. In many recommender systems, particularly those based on collaborative filtering (CF), the additional contextual constraints may lead to increased sparsity in the user preference data, thus fewer matches between the current user context and previous situations. Our earlier work proposed two approaches to deal with this problem – differential context relaxation (DCR) and differential context weighting (DCW) and we have successfully examined them using user-based collaborative filtering (UBCF). In this paper, we put DCR and DCW into one framework called differential context modeling (DCM). As a general framework, DCM is able to be applied to other recommendation algorithms other than UBCF. We expand the application of DCM to the other two CF approaches: item-based CF and slope one recommender. Predictive performances are evaluated based on two real-world data sets and experimental results demonstrate that applying DCM to those two algorithms is able to improve predictive accuracy compared with our baselines: context-free CF algorithms and contextual pre-filtering algorithms.
These are the slides of my PhD. thesis dissertation called "A Framework for Abstraction and Virtualization of Sensors in Mobile Context Aware Computing". It was presented on June 29 2015.
In this presentation we illustrate a novel context-aware mobile recommender system for places of interest (POIs). Unlike existing systems, which learn users’ preferences solely from their past ratings, it considers also their personality - using the Five Factor Model. Personality is acquired by asking users to complete a brief and entertaining questionnaire as part of the registration process, and is then exploited in: (1) an active learning module that actively acquires ratings-in-context for POIs that users are likely to have experienced, hence reducing the stress and annoyance to rate (or skip rating) items that the users don’t know; and (2) in the recommendation model that builds up on matrix factorization and therefore can be trained even if the users haven’t rated any items yet.
An online training course run by the FIWARE Foundation in conjunction with the i4Trust project. The core part of this virtual training camp (21-24 June 2021) covered all the necessary skills to develop smart solutions powered by FIWARE. It introduces the basis of Digital Twin programming using linked data concepts - JSON-LD and NGSI-LD and combines these with common smart data models for the sharing and augmentation of context data.
In addition, it covers the supplementary FIWARE technologies used to implement the common functions typically required when architecting a complete smart solution: Identity and Access Management (IAM) functions to secure access to digital twin data and functions enabling the interface with IoT and 3rd systems, or the connection with different tools for processing and monitoring current and historical big data.
This 12-hour online training course can be used to obtain a good understanding of FIWARE and NGSI Interfaces and form the basis of studying for the FIWARE expert certification.
Extending this core part, the virtual training camp adds introductory and deep-dive sessions on how FIWARE and iSHARE technologies, brought together under the umbrella of the i4Trust initiative, can be combined to provide the means for the creation of data spaces in which multiple organizations can exchange digital twin data in a trusted and efficient manner, collaborating in the creation of innovative services based on data sharing. In addition, SMEs and Digital Innovation Hubs (DIHs) that go through this complete training and are located in countries eligible under Horizon 2020 will be equipped with the necessary know-how to apply to the recently launched i4Trust Open Call.
The Roman Empire A Historical Colossus.pdfkaushalkr1407
The Roman Empire, a vast and enduring power, stands as one of history's most remarkable civilizations, leaving an indelible imprint on the world. It emerged from the Roman Republic, transitioning into an imperial powerhouse under the leadership of Augustus Caesar in 27 BCE. This transformation marked the beginning of an era defined by unprecedented territorial expansion, architectural marvels, and profound cultural influence.
The empire's roots lie in the city of Rome, founded, according to legend, by Romulus in 753 BCE. Over centuries, Rome evolved from a small settlement to a formidable republic, characterized by a complex political system with elected officials and checks on power. However, internal strife, class conflicts, and military ambitions paved the way for the end of the Republic. Julius Caesar’s dictatorship and subsequent assassination in 44 BCE created a power vacuum, leading to a civil war. Octavian, later Augustus, emerged victorious, heralding the Roman Empire’s birth.
Under Augustus, the empire experienced the Pax Romana, a 200-year period of relative peace and stability. Augustus reformed the military, established efficient administrative systems, and initiated grand construction projects. The empire's borders expanded, encompassing territories from Britain to Egypt and from Spain to the Euphrates. Roman legions, renowned for their discipline and engineering prowess, secured and maintained these vast territories, building roads, fortifications, and cities that facilitated control and integration.
The Roman Empire’s society was hierarchical, with a rigid class system. At the top were the patricians, wealthy elites who held significant political power. Below them were the plebeians, free citizens with limited political influence, and the vast numbers of slaves who formed the backbone of the economy. The family unit was central, governed by the paterfamilias, the male head who held absolute authority.
Culturally, the Romans were eclectic, absorbing and adapting elements from the civilizations they encountered, particularly the Greeks. Roman art, literature, and philosophy reflected this synthesis, creating a rich cultural tapestry. Latin, the Roman language, became the lingua franca of the Western world, influencing numerous modern languages.
Roman architecture and engineering achievements were monumental. They perfected the arch, vault, and dome, constructing enduring structures like the Colosseum, Pantheon, and aqueducts. These engineering marvels not only showcased Roman ingenuity but also served practical purposes, from public entertainment to water supply.
2024.06.01 Introducing a competency framework for languag learning materials ...Sandy Millin
http://sandymillin.wordpress.com/iateflwebinar2024
Published classroom materials form the basis of syllabuses, drive teacher professional development, and have a potentially huge influence on learners, teachers and education systems. All teachers also create their own materials, whether a few sentences on a blackboard, a highly-structured fully-realised online course, or anything in between. Despite this, the knowledge and skills needed to create effective language learning materials are rarely part of teacher training, and are mostly learnt by trial and error.
Knowledge and skills frameworks, generally called competency frameworks, for ELT teachers, trainers and managers have existed for a few years now. However, until I created one for my MA dissertation, there wasn’t one drawing together what we need to know and do to be able to effectively produce language learning materials.
This webinar will introduce you to my framework, highlighting the key competencies I identified from my research. It will also show how anybody involved in language teaching (any language, not just English!), teacher training, managing schools or developing language learning materials can benefit from using the framework.
The French Revolution, which began in 1789, was a period of radical social and political upheaval in France. It marked the decline of absolute monarchies, the rise of secular and democratic republics, and the eventual rise of Napoleon Bonaparte. This revolutionary period is crucial in understanding the transition from feudalism to modernity in Europe.
For more information, visit-www.vavaclasses.com
Acetabularia Information For Class 9 .docxvaibhavrinwa19
Acetabularia acetabulum is a single-celled green alga that in its vegetative state is morphologically differentiated into a basal rhizoid and an axially elongated stalk, which bears whorls of branching hairs. The single diploid nucleus resides in the rhizoid.
Operation “Blue Star” is the only event in the history of Independent India where the state went into war with its own people. Even after about 40 years it is not clear if it was culmination of states anger over people of the region, a political game of power or start of dictatorial chapter in the democratic setup.
The people of Punjab felt alienated from main stream due to denial of their just demands during a long democratic struggle since independence. As it happen all over the word, it led to militant struggle with great loss of lives of military, police and civilian personnel. Killing of Indira Gandhi and massacre of innocent Sikhs in Delhi and other India cities was also associated with this movement.
A Strategic Approach: GenAI in EducationPeter Windle
Artificial Intelligence (AI) technologies such as Generative AI, Image Generators and Large Language Models have had a dramatic impact on teaching, learning and assessment over the past 18 months. The most immediate threat AI posed was to Academic Integrity with Higher Education Institutes (HEIs) focusing their efforts on combating the use of GenAI in assessment. Guidelines were developed for staff and students, policies put in place too. Innovative educators have forged paths in the use of Generative AI for teaching, learning and assessments leading to pockets of transformation springing up across HEIs, often with little or no top-down guidance, support or direction.
This Gasta posits a strategic approach to integrating AI into HEIs to prepare staff, students and the curriculum for an evolving world and workplace. We will highlight the advantages of working with these technologies beyond the realm of teaching, learning and assessment by considering prompt engineering skills, industry impact, curriculum changes, and the need for staff upskilling. In contrast, not engaging strategically with Generative AI poses risks, including falling behind peers, missed opportunities and failing to ensure our graduates remain employable. The rapid evolution of AI technologies necessitates a proactive and strategic approach if we are to remain relevant.
Macroeconomics- Movie Location
This will be used as part of your Personal Professional Portfolio once graded.
Objective:
Prepare a presentation or a paper using research, basic comparative analysis, data organization and application of economic information. You will make an informed assessment of an economic climate outside of the United States to accomplish an entertainment industry objective.
How to Make a Field invisible in Odoo 17Celine George
It is possible to hide or invisible some fields in odoo. Commonly using “invisible” attribute in the field definition to invisible the fields. This slide will show how to make a field invisible in odoo 17.
Context-aware application development with FIWARE #CPBR8
1. Context-aware application development with
FIWARE
FIWARE Orion Context Broker REST API
February 3rd, 2015 – Campus Party Brazil
Contact twitter
@fermingalan
Contact email
fermin.galanmarquez@telefonica.com
2. Introduction
• Context Management in FIWARE
• Orion Context Broker
• Creating and pulling data
• Pushing data and notifications
• Convenience operations
Orion Context Broker
2
3. Context Management in FIWARE
The value of the attributes that
characterize entities relevant to
applications
3
API
Bus
• Location
• No. passengers
• Driver
• Licence plate
Person
• Name-Surname
• Birthday
• Preferences
• Location
• ToDo list
Shop
• Location
• Business name
• Franchise
• offerings
My Application
Context Information
4. Context Management in FIWARE
Context information may come from many sources using different
interfaces and protocols … but programmers should just care about
entities and their attributes …
4
A sensor in a
pedestrian street
The Public Bus
Transport Management
system
A person from his smartphone
It’s too hot!
What’s the current temperature?
Context
Information
Context
Information
Context
Information
5. Context Management in FIWARE
Get notified when an update on context information takes place
5
Bus = “X”, last_stop = “A”,
arrived= “Yes”
push
Notify me when bus “X”
arrives at the bus stop “A”
API
6. Context Management in FIWARE
Acting on devices can be as easy as changing the value of attributes
linked to its corresponding entity
6
Street lamp = “lamp1”, status= “on”
Street Lamp lamp1.status “on”
API
7. Orion Context Broker
• Main functions:
– Context availability management
– Context management
• HTTP and REST-based
– XML payload support
– JSON payload support
• Context in NGSI is based in an entity-attribute model:
7
Attributes
• Name
• Type
• Value
Entity
• EntityId
• EntityType
1 n
“has”
8. Orion Context Broker in a nutshell
8
Orion Context Broker
Context
Producers
Context
Consumers
subscriptions
update
query
notify
notify
update
update
DB
1026
1026
9. GET <cb_host>:1026/version
{
"orion" : {
"version" : "0.17.0",
"uptime" : "7 d, 21 h, 33 m, 39 s",
"git_hash" : "238c3642ad67899da7c1ff08aba4b5c846b4901a",
"compile_time" : "Mon Dec 1 11:27:18 CET 2014",
"compiled_by" : "fermin",
"compiled_in" : "centollo"
}
}
9
Orion Context Broker – check health
11. Context Broker operations: create & pull data
• Context Producers publish data/context elements by invoking the
updateContext operation on a Context Broker.
• Context Consumers can retrieve data/context elements by invoking the
queryContext operation on a Context Broker
11
Context Consumer
queryContext
Context Producer
updateContext
Context Broker
24. Context Broker operations: push data
• Context Consumers can subscribe to receive context information that satisfy
certain conditions using the subscribeContext. Such subscriptions may have
a duration.
• The Context Broker notifies updates on context information to subscribed
Context Consumers by invoking the notifyContext operation they export
24
subscription_id = subscribeContext (consumer, expr, duration)
Context Consumer
notifyContext (subscription_id, data/context)
Context Broker
Application
28. Convenience Operations
• They are equivalent to previous standard operations in functionality
• Avoid the need for POST-ing payloads in many cases or simplifying them
considerably
• Simple to write, more REST-like
• They are not a substitute but a complement to standard NGSI operations
• Four examples (there are many others):
– Entities
– Attributes
– Subscriptions
– Types
28
29. Convenience Operations – Example 1
Entities
• GET /v1/contextEntities/{entityID}
• Retrieves an entity
• POST /v1/contextEntities/{entityID}
• Creates an entity
• PUT /v1/contextEntities/{entityID}
• Updates an entity
• DELETE /v1/contextEntities/{entityID}
• Deletes an entity
30. Convenience Operations – Example 2
Attributes
• GET /v1/contextEntities/{entityID}/attributes/{attrID}
• Retrieves an attribute’s value
• POST /v1/contextEntities/{entityID}/attributes/{attrID}
• Creates a new attribute for an entity
• PUT /v1/contextEntities/{entityID}/attributes/{attrID}
• Updates an attribute’s value
• DELETE /v1/contextEntities/{entityID}/attributes/{attrID}
• Deletes an attribute
31. Convenience Operations – Example 3
Subscriptions
• POST /v1/contextSubscriptions
• Creates a subscription
• PUT /v1/contextSubscriptions/{subID}
• Updates a subscription
• DELETE /v1/contextSubscriptions/{subID}
• Cancel a subscription
32. Convenience Operations – Example 4
Entity Types
• GET /v1/contextTypes
• Retrieve a list of all entity types currently in Orion,
including their corresponding attributes
• GET /v1/contextTypes/{typeID}
• Retrieve attributes associated to an entity type
PRO TIP
GET /v1/contextTypes?collapse=true
Retrieves a list of all entity types without attribute info
37. Freeboard
• Orion freeboard connector
– https://github.com/telefonicaid/fiware-
dataviz/tree/develop/FreeBoard-Orion-Plugin
• Very easy to use! (even in your local machine)
• The fiware-dataviz repository includes
connector for other visualization tools, along with
documentation on how to use them
– orion2duckboard connector
– orion2cartodb connector
37
38. Weather Bot
• Running at FIWARE Campus stand
38
FIWARE
Lab
Cloud
IoTA
Orion
orionlive.fiware.org
Campus Party
Net
Internet
REST client REST client REST client
…
UDP 60001
orion2twitter
Internet
Internet
@FIWAREOrionLiveTCP 80
39. Hackathon Setup
39
IoTA-TT IoTA-LW
Orion
hackfest.testbed.fiware.org
TT TTTT
Campus Party
Net
User Device User DeviceUser Device
Internet
Contex-aware
application
Contex-aware
application
Contex-aware
application…
… …
TCP 1026
TCP 80 UDP 9500
FIWARE
LabCloud
Orion
IoTA-UL2.0
eidas4.testbed.fiware.orgTCP 1026
TCP 8002
Commands
API
TCP 5371
Internet
40. Orion Context Explorer
• Publicly available browser-based front-end for Orion
Context Broker
– Open source development by VM9
• Authentication integrated with FIWARE Lab account
• Have a look!
– http://orionexplorer.com/
40
42. • Pagination helps clients organize query and
discovery requests with a large number of
responses.
• Three URI parameters:
– limit
• Number of elements per page (default: 20, max: 1000)
– offset
• Number of elements to skip (default: 0)
– details
• Returns total elements (default: "off")
Pagination
42
43. Pagination
• Example, querying the first 100 entries:
POST <orion_host>:1026/v1/queryContext?limit=100&details=on
• The first 100 elements are returned, along with the following errorCode in
the response:
"errorCode": {
"code": "200",
"details": "Count: 322",
"reasonPhrase": "OK"
}
• Now we now there are 322 entities, we can keep querying the broker for
them:
– POST <orion_host>:1026/v1/queryContext?offset=100&limit=100
– POST <orion_host>:1026/v1/queryContext?offset=200&limit=100
– POST <orion_host>:1026/v1/queryContext?offset=300&limit=100
43
44. Compound Attribute Values
• An attribute can have a structured value. Vectors
and key-value maps are supported.
• It maps directly to JSON's objects and arrays.
44
45. Compound Attribute Values
• Example: we have
a car whose four
wheels' pressure
we want to
represent as a
compound
attribute for a car
entity. We would
create the car
entity like this:
{
"contextElements": [
{
"type": "Car",
"isPattern": "false",
"id": "Car1",
"attributes": [
{
"name": "tirePressure",
"type": "kPa",
"value": {
"frontRight": "120",
"frontLeft": "110",
"backRight": "115",
"backLeft": "130"
}
}
]
}
],
"updateAction": "APPEND"
}
45
54. Multitenancy
• Simple multitenant model based on
logical database separation.
• It eases tenant-based authorization
provided by other components.
• Just use an additional HTTP header
called "Fiware-Service", whose value
is the tenant name. Example:
Fiware-Service: Tenant1
Context
Broker
Tenant1
Tenant2
…
54
55. Entity Service Paths
• A service path is a hierarchical scope assigned to an entity
at creation time (with updateContext).
55
56. Entity Service Paths
• In order to use a service path we put in a new HTTP header
called “Fiware-ServicePath". For example:
Fiware-ServicePath: Madrid/Gardens/ParqueNorte/Parterre1
• Properties:
– A query on a service path will look only into the specified node
– Use "ParentNode/#" to include all child nodes
– Queries without Fiware-ServicePath resolve to "/#"
– Entities will fall in the "/" node by default
ParqueNorte
Parterre2Parterre1
56
57. Entity Service Paths
• Properties (continued):
– You can OR a query using a comma (,)
operator in the header
• For example, to query all street lights that are either in
ParqueSur or in ParqueOeste you would use:
ServicePath: Madrid/Gardens/ParqueSur,
Madrid/Gardens/ParqueOeste
• You can OR up to 10 different scopes.
– Maximum scope levels: 10
• Scope1/Scope2/.../Scope10
– You can have the same element IDs in
different scopes (be careful with this!)
– You can't change scope once the element is
created
– One entity can belong to only one scope
– It works not only with queries, but also with
subscriptions/notifications
ParqueNorte
Parterre1
light1
light1
A B
A or B
57
60. Integration with existing systems
• Context adapters will be developed to interface with existing systems (e.g.,
municipal services management systems in a smart city) acting as Context
Providers, Context Producers, or both
• Some attributes from a given entity may be linked to a Context Provider
while other attributes may be linked to Context Producers
60
queryContext (e1,
attr1, attr2)
Context Provider
queryContext (e1,
attr1)
Context Consumer
updateContext (e1,
attr2)
Application
Context Broker
System BSystem A
61. Integration with sensor networks
• The backend IoT Device Management GE enables creation and
configuration of NGSI IoT Agents that connect to sensor networks
• Each NGSI IoT Agent can behave as Context Consumers or Context
Providers, or both
61
FIWARE Context Broker
IoT
Agent-1
IoT
Agent-2
IoT
Agent-n
IoT Agent
Manager
create/monitor
FIWARE Backend IoT
Device Management
OMA NGSI API (northbound interface)
(southbound interfaces)
MQTTETSI M2M IETF CoAP
62. 62
• Federation of infrastructures (private/public regions)
• Automated GE deploymentCloud
• Complete Context Management Platform
• Integration of Data and Media ContentData
•Easy plug&play of devices using multiple protocols
•Automated Measurements/Action Context updatesIoT
•Visualization of data (operation dashboards)
•Publication of data sets/servicesApps
•Easy support of UIs with advanced web-based 3D and AR
capabilities
•Visual representation of context information.
Web UI
•Advanced networking capabilities (SDN) and Middleware
•Interface to robotsI2ND
•Security Monitoring
•Built-in Identity/Access/Privacy ManagementSecurity
Context Management in FIWARE
63. FI-WARE Context/Data Management Platform
63
Context/Data Management Platform
Applications
OMA NGSI-9/10
Processing/Analysis
Algorithms
Gathered data is
injected for
processing/analysis
Distributed
Context
Sources Complex Event
Processing
(PROTON)
BigData
(COSMOS)
Processed data is
injected for
processing/analysi
s
Data generated either by CEP
or BigData is published
Gathered data injected
for CEP-like processing
Direct
bigdata
injection
Programming of
rules
Editor's Notes
1. En la primera slide poned una lista de puntos de lo que se puede hacer con ese GE/set de GEs. Me refiero en plan titulares, sin muchas explicaciones.
2. Mostrad un ejemplo representativo de uno o varios de los puntos anteriores.
Recordad: si lo hacéis como demo, poned slides con capturas y explicaciones también (así sirve también por si la demo os falla en ese momento ;-) ).
3. Mostrad un enlace donde pondremos esta semana las slides de la Campus que tienen los detalles de todos los puntos mencionados en 1.
(Poned la lista de ficheros pero dejad el enlace en blanco que ya lo pondremos a última hora).
Orion Context Broker is an implementation of a context information broker with persistent storage
It implements OMA NGSI9/10 specification
NGSI9 is about context information availability (i.e. sources of context information) management
NGSI10 is about context information itself
Do the following sequence (showing the XML)
registerContext Room1-temperature
updateContext Room1-temperture = 30ºC
queryContext Room1-temperature
updateContext Room1-temperture = 31ºC
queryContext Room1-temperature
1. En la primera slide poned una lista de puntos de lo que se puede hacer con ese GE/set de GEs. Me refiero en plan titulares, sin muchas explicaciones.
2. Mostrad un ejemplo representativo de uno o varios de los puntos anteriores.
Recordad: si lo hacéis como demo, poned slides con capturas y explicaciones también (así sirve también por si la demo os falla en ese momento ;-) ).
3. Mostrad un enlace donde pondremos esta semana las slides de la Campus que tienen los detalles de todos los puntos mencionados en 1.
(Poned la lista de ficheros pero dejad el enlace en blanco que ya lo pondremos a última hora).
Do the following sequence (showing the XML)
registerContext Room1-temperature
updateContext Room1-temperture = 30ºC
queryContext Room1-temperature
updateContext Room1-temperture = 31ºC
queryContext Room1-temperature
Do the following sequence (showing the XML)
registerContext Room1-temperature
updateContext Room1-temperture = 30ºC
queryContext Room1-temperature
updateContext Room1-temperture = 31ºC
queryContext Room1-temperature
Do the following sequence (showing the XML)
registerContext Room1-temperature
updateContext Room1-temperture = 30ºC
queryContext Room1-temperature
updateContext Room1-temperture = 31ºC
queryContext Room1-temperature
Do the following sequence (showing the XML)
registerContext Room1-temperature
updateContext Room1-temperture = 30ºC
queryContext Room1-temperature
updateContext Room1-temperture = 31ºC
queryContext Room1-temperature
Do the following sequence (showing the XML)
registerContext Room1-temperature
updateContext Room1-temperture = 30ºC
queryContext Room1-temperature
updateContext Room1-temperture = 31ºC
queryContext Room1-temperature
Do the following sequence (showing the XML)
registerContext Room1-temperature
updateContext Room1-temperture = 30ºC
queryContext Room1-temperature
updateContext Room1-temperture = 31ºC
queryContext Room1-temperature
Do the following sequence (showing the XML)
registerContext Room1-temperature
updateContext Room1-temperture = 30ºC
queryContext Room1-temperature
updateContext Room1-temperture = 31ºC
queryContext Room1-temperature
Do the following sequence (showing the XML)
registerContext Room1-temperature
updateContext Room1-temperture = 30ºC
queryContext Room1-temperature
updateContext Room1-temperture = 31ºC
queryContext Room1-temperature
Do the following sequence (showing the XML)
registerContext Room1-temperature
updateContext Room1-temperture = 30ºC
queryContext Room1-temperature
updateContext Room1-temperture = 31ºC
queryContext Room1-temperature
Do the following sequence (showing the XML)
registerContext Room1-temperature
updateContext Room1-temperture = 30ºC
queryContext Room1-temperature
updateContext Room1-temperture = 31ºC
queryContext Room1-temperature
Do the following sequence (showing the XML)
registerContext Room1-temperature
updateContext Room1-temperture = 30ºC
queryContext Room1-temperature
updateContext Room1-temperture = 31ºC
queryContext Room1-temperature
Do the following sequence (showing the XML)
registerContext Room1-temperature
updateContext Room1-temperture = 30ºC
queryContext Room1-temperature
updateContext Room1-temperture = 31ºC
queryContext Room1-temperature
Do the following sequence (showing the XML)
registerContext Room1-temperature
updateContext Room1-temperture = 30ºC
queryContext Room1-temperature
updateContext Room1-temperture = 31ºC
queryContext Room1-temperature
Do the following sequence (showing the XML)
registerContext Room1-temperature
updateContext Room1-temperture = 30ºC
queryContext Room1-temperature
updateContext Room1-temperture = 31ºC
queryContext Room1-temperature
Do the following sequence (showing the XML)
registerContext Room1-temperature
updateContext Room1-temperture = 30ºC
queryContext Room1-temperature
updateContext Room1-temperture = 31ºC
queryContext Room1-temperature