Keio Virtual Sensor System based on Sensor- Over- XMPP
|
|
- Charles Boone
- 6 years ago
- Views:
Transcription
1 Keio Virtual Sensor System based on Sensor- Over- XMPP 1. Basic information Keio virtual sensor system is based on XMPP PubSub mechanism. Thus, we basically follow XMPP PubSub protocol (XEP- 0060: Publish- Subscribe html ). Please see the detail in above link. For extending the PubSub mechanism for publishing/subscribing sensor data, we use sensor- over- xmpp which is originally developed by Sensor Andrew Project in Carnegie Mellon University. Please see the detail: XEP- xxxx: Sensor- Over- XMPP Sensor Andrew: Tech- Report.pdf We extended SOX for treating WEB sensing, participatory sensing and etc. Please see the extended schema in appendix. 2. Process The process of virtual sensor data delivery is as following: 1) creating virtual sensor node as a pair of meta node and event node, 2) defining meta information to meta node, 3) publish sensor data to data node, and 4)subscribe the sensor node and getting data. 1) Creating virtual sensor node Firstly, we create two PubSub event nodes in XMPP server for virtual sensor node. We use a pair of two pubsub event nodes (name_meta node and name_data node) as a virtual sensor. The name_meta node is used for storing meta information of the sensor, and the name_data node is used for delivering actual sensor data. Example: Creating example sensor node which has three sensors GPS sensor, temperature and humidity sensor. At the first step, we simply create two pubsub nodes.
2 Send message to XMPP server: <auth mechanism="digest- MD5" xmlns="urn:ietf:params:xml:ns:xmpp- sasl"></auth> <response xmlns="urn:ietf:params:xml:ns:xmpp- sasl">y2hhcnnldd11dgytocx1c2vybmftzt0iz3vlc3qilg5vbmnlpsizmtu4mzg4mtm4iixuyz0wmdawmdawmsx jbm9uy2u9imhfunpyuc9swvplnwpgrlbgsxbmehpaaxltn096a043dvd1avpjrkqilgrpz2vzdc11cmk9inhtcha vc294lmh0lnnmyy5rzwlvlmfjlmpwiixtyxhidwy9nju1mzyscmvzcg9uc2u9y2y0odvlntfkowixmdu3owq3zg RhN2NmZTM5N2QwODAscW9wPWF1dGg=</response> <response xmlns="urn:ietf:params:xml:ns:xmpp- sasl"></response> //this is common message to communicate with XMPP server by specific user name and password <iq id='2qfcs- 9' to='pubsub.sox.ht.sfc.keio.ac.jp' type='set'> <create node='example_meta'/> //create pubsub node named example_meta <iq id='2qfcs- 10' to='pubsub.sox.ht.sfc.keio.ac.jp' type='set'> <create node='example_data'/> //create pubsub node named example_data We can also define access model to the node. For example, anyone(or limited users) can publish/subscribe the nodes. In this case, we set open access and publish model to two nodes. Send message to XMPP server: <iq id='2qfcs- 11' to='pubsub.sox.ht.sfc.keio.ac.jp' type='set'> <pubsub xmlns=" <configure node='example_meta'> <x xmlns='jabber:x:data' type='submit'><field var='pubsub#access_model' type='list- single'><value>open</value></field><field var='pubsub#max_items' type='text- single'><value>1</value></field><field var='pubsub#publish_model' type='list- single'><value>open</value></field></x> </configure> <iq id='2qfcs- 12' to='pubsub.sox.ht.sfc.keio.ac.jp' type='set'> <pubsub xmlns=" <configure node='example_data'> <x xmlns='jabber:x:data' type='submit'><field var='pubsub#access_model' type='list- single'><value>open</value></field><field var='pubsub#max_items' type='text- single'><value>1</value></field><field var='pubsub#publish_model' type='list- single'><value>open</value></field></x> </configure>
3 2) Defining meta information to meta node After two pubsub nodes for virtual sensor node are created, we define meta information to the sensor node. Example: define GPS sensor, temperature and humidity sensor to example sensor node. Send message to XMPP server: <iq id='2qfcs- 13' to='pubsub.sox.ht.sfc.keio.ac.jp' type='set'> <publish node='example_meta'> //send below message to example_meta node <item> <device name="example" id="example" type="outdoor weather"> //set device name and device type <transducer name="temperature" id="temperature" units="celius" minvalue="- 30.0" maxvalue="100.0" resolution="0.1"/> //set temperature sensor with meta information <transducer name="humidity" id="humidity" units="percent" minvalue="0.0" maxvalue="100.0"/> //set humidity sensor with meta information <transducer name="longitude" id="longitude" units="longitude"/> //set longitude sensor with meta information <transducer name="latitude" id="latitude" units="latitude"/> //set latitude sensor with meta information </device> </item> </publish> This meta information is stored to example_meta node. Thus, when a user would like to use the example sensor node, the user can understand what kinds of sensors are mounted to the node by getting above meta information from example_meta node. By using our Java library, we can achieve 1) creating node, and 2) define meta information processes by following simple code. SoxConnection con = new SoxConnection("sox.ht.sfc.keio.ac.jp", "guest", "miroguest", true); String nodename = "example"; //set device info and it's transducer meta data Device device = new Device(); device.setid(nodename); device.setdevicetype(devicetype.outdoor_weather); device.setname(nodename); List<Transducer> transducers = new ArrayList<Transducer>(); Transducer t = new Transducer(); t.setname("temperature"); t.setid("temperature"); t.setunits("celius");
4 t.setminvalue(- 30f); t.setmaxvalue(100f); t.setresolution(0.1f); transducers.add(t); Transducer t2 = new Transducer(); t2.setname("humidity"); t2.setid("humidity"); t2.setunits("percent"); t2.setminvalue(0f); t2.setmaxvalue(100f); t.setresolution(0.1f); transducers.add(t2); Transducer t3 = new Transducer(); t3.setname("longitude"); t3.setid("longitude"); t3.setunits("longitude"); transducers.add(t3); Transducer t4 = new Transducer(); t4.setname("latitude"); t4.setid("latitude"); t4.setunits("latitude"); transducers.add(t4); device.settransducers(transducers); //create node con.createnode(nodename, device, AccessModel.open,PublishModel.open); 3) Publish sensor data to the virtual sensor node After defining sensor meta information, actual sensor node (or corresponding process) sends sensor data to the virtual sensor node by publishing the data to name_data pubsub node). Example: publishing GPS sensor, temperature and humidity sensor data to example sensor node. Send message to XMPP server: <iq id='292ef- 9' to='pubsub.sox.ht.sfc.keio.ac.jp' type='set'> <publish node='example_data'> <item> <data> <transducervalue id="temperature" typedvalue="27.5" timestamp=" T02:47Z+09:00" rawvalue="27.5"/> <transducervalue id="humidity" typedvalue="85.1" timestamp=" T02:47Z+09:00" rawvalue="85.1"/> <transducervalue id="latitude" typedvalue=" " timestamp=" T02:47Z+09:00" rawvalue=" "/> <transducervalue id="longitude" typedvalue=" " timestamp=" T02:47Z+09:00" rawvalue=" "/> </data> </item> </publish>
5 By using our Java library, we can achieve publishing the data by following simple code. SoxConnection con = new SoxConnection("sox.ht.sfc.keio.ac.jp", true); SoxDevice soxdevice = new SoxDevice(con, "example"); List<TransducerValue> values = new ArrayList<TransducerValue>(); TransducerValue tvalue1 = new TransducerValue(); tvalue1.setid("temperature"); tvalue1.setrawvalue("27.5"); tvalue1.settypedvalue("27.5"); tvalue1.setcurrenttimestamp(); values.add(tvalue1); TransducerValue tvalue2 = new TransducerValue(); tvalue2.setid("humidity"); tvalue2.setrawvalue("80.3"); tvalue2.settypedvalue("80.3"); tvalue2.setcurrenttimestamp(); values.add(tvalue2); TransducerValue tvalue3 = new TransducerValue(); tvalue3.setid("latitude"); tvalue3.setrawvalue(" "); tvalue3.settypedvalue(" "); tvalue3.setcurrenttimestamp(); values.add(tvalue3); TransducerValue tvalue4 = new TransducerValue(); tvalue4.setid("longitude"); tvalue4.setrawvalue(" "); tvalue4.settypedvalue(" "); tvalue4.setcurrenttimestamp(); values.add(tvalue4); //publish the data soxdevice.publishvalues(values); 4) Subscribe the sensor node and getting data Once a user subscribe the sensor node, sensor data will be delivered automatic to the user from name_data pubsub node. User also can understand the detail of meta information of the data by getting the information from name_meta pubsub node. Example: getting meta information and subscribing example sensor node. Send message to XMPP server: <iq id='z5rl8-10' to='pubsub.sox.ht.sfc.keio.ac.jp' type='get'> <items node='example_meta' max_items='1'/> //get meta information from example_meta node <iq id='z5rl8-14' to='pubsub.sox.ht.sfc.keio.ac.jp' type='set'> <subscribe node='example_data' jid='guest@sox.ht.sfc.keio.ac.jp/smack'/> //subscribe
6 Recieve message from XMPP server: //Getting meta information from example_meta node <iq from='pubsub.sox.ht.sfc.keio.ac.jp' id='z5rl8-10' type='result'> <pubsub xmlns=' <items node='example_meta'> <item id='59082ef3956d4'> <device name='example' id='example' type='outdoor weather'> <transducer name='temperature' id='temperature' units='celius' minvalue='- 30.0' maxvalue='100.0' resolution='0.1'/> <transducer name='humidity' id='humidity' units='percent' minvalue='0.0' maxvalue='100.0'/> <transducer name='longitude' id='longitude' units='double'/> <transducer name='latitude' id='latitude' units='double'/> </device> </item> </items> //will receive published message from subscribed example_data node <message from='pubsub.sox.ht.sfc.keio.ac.jp' type='headline'> <event xmlns=' <items node='example_data'> <item id='590844c2c89f8'> <data> <transducervalue id='temperature' typedvalue='27.5' timestamp=' T03:09Z+09:00' rawvalue='27.5'/> <transducervalue id='humidity' typedvalue='85.1' timestamp=' T03:09Z+09:00' rawvalue='85.1'/> <transducervalue id='latitude' typedvalue=' ' timestamp=' T03:09Z+09:00' rawvalue=' '/> <transducervalue id='longitude' typedvalue=' ' timestamp=' T03:09Z+09:00' rawvalue=' '/> </data> </item> </items> </event> By using our Java library, we can achieve to subscribe the sensor node and receive the data by following simple code. public Subscribe() throws Exception { SoxConnection con = new SoxConnection("sox.ht.sfc.keio.ac.jp", "guest","miroguest", true); SoxDevice soxdevice = new SoxDevice(con, "example"); soxdevice.subscribe(); soxdevice.addsoxeventlistener(this); } public void handlepublishedsoxevent(soxevent e) { Device device = e.getdevice(); Transducer transducer = e.gettransducer(); TransducerValue value = e.gettransducervalue(); if (transducer!= null && device!= null && value!= null) { System.out.println("Device[name:" + device.getname() + ", type:"
7 } + device.getdevicetype().tostring() + "]"); System.out.println("Transducer[name:" + transducer.getname() + ", id:" + transducer.getid() + ", unit:" + transducer.getunits() + "]"); System.out.println("TransducerValue[id:" + value.getid() + ", rawvalue:" + value.getrawvalue() + ", typedvalue:" + value.gettypedvalue() + ", timestamp:" + value.gettimestamp() + "]"); } Result of above program: Device[name:example, type:outdoor_weather] Transducer[name:temperature, id:temperature, unit:celius] TransducerValue[id:temperature, rawvalue:27.5, typedvalue:27.5, timestamp: T03:09Z+09:00] Device[name:example, type:outdoor_weather] Transducer[name:humidity, id:humidity, unit:percent] TransducerValue[id:humidity, rawvalue:85.1, typedvalue:85.1, timestamp: T03:09Z+09:00] Device[name:example, type:outdoor_weather] Transducer[name:latitude, id:latitude, unit:double] TransducerValue[id:latitude, rawvalue: , typedvalue: , timestamp: T03:09Z+09:00] Device[name:example, type:outdoor_weather] Transducer[name:longitude, id:longitude, unit:double] TransducerValue[id:longitude, rawvalue: , typedvalue: , timestamp: T03:09Z+09:00] Appendix. 1) Sensor- Over- XMPP libraries (Java, Javascript, Python) and test tools 2) Sensor- Over- XMPP data schema (version Feb ) <?xml version='1.0' encoding='utf- 8'?> <xs:schema xmlns:xs=' targetnamespace=' xmlns=' elementformdefault='qualified'> <xs:annotation> <xs:documentation> The protocol documented by this schema is defined in XEP-????: </xs:documentation> </xs:annotation> <xs:element name='device'> <xs:sequence> <xs:element minoccurs='0' maxoccurs='unbounded' ref='transducer'/> <xs:element minoccurs='0' maxoccurs='unbounded' ref='geoloc' xmlns=' <xs:element minoccurs='0' maxoccurs='unbounded' ref='property'/>
8 </xs:sequence> <xs:attribute name='name' type='xs:string' use='required'/> <xs:attribute name='id' type='xs:string' use='required'/> <xs:attribute name='type' type='devicetype' use='required'/> <xs:attribute name='timestamp' type='xs:datetime' use='optional'/> <xs:attribute name='description' type='xs:string' use='optional'/> <xs:attribute name='serialnumber' type='xs:string' use='optional'/> <xs:simpletype name='devicetype'> <xs:restriction base="xs:string"> <xs:enumeration value='indoor weather'/> <xs:enumeration value='outdoor weather'/> <xs:enumeration value='hvac'/> <xs:enumeration value='occupancy'/> <xs:enumeration value='multimedia input'/> <xs:enumeration value='multimedia output'/> <xs:enumeration value='scale'/> <xs:enumeration value='vehicle'/> <xs:enumeration value='resource consumption'/> <xs:enumeration value='resource generation'/> <xs:enumeration value='participatory'/> <xs:enumeration value='other'/> </xs:restriction> </xs:simpletype> <xs:element name='transducer'> <xs:sequence> <xs:element minoccurs='0' maxoccurs='1' ref='geoloc' xmlns=' <xs:element minoccurs='0' maxoccurs='unbounded' ref='property'/> <xs:element minoccurs='0' maxoccurs='unbounded' ref='choicelist'/> </xs:sequence> <xs:attribute name='name' type='xs:string' use='required'/> <xs:attribute name='id' type='xs:string' use='required'/> <xs:attribute name='units' type='allowedunits' use='required'/> <xs:attribute name='unitscaler' type='xs:integer' default='0'/> <xs:attribute name='canactuate' type='xs:boolean' default='false'/> <xs:attribute name='hasownnode' type='xs:boolean' default='false'/> <xs:attribute name='transducertype' type='allowedtransducertype' use='optional'/> <xs:attribute name='transducertypename' type='xs:string' use='optional'/> <xs:attribute name='manufacturer' type='xs:string' use='optional'/> <xs:attribute name='partnumber' type='xs:string' use='optional'/> <xs:attribute name='serialnumber' type='xs:string' use='optional'/> <xs:attribute name='minvalue' type='xs:float' use='optional'/> <xs:attribute name='maxvalue' type='xs:float' use='optional'/> <xs:attribute name='resolution' type='xs:float' use='optional'/> <xs:attribute name='precision' type='xs:float' use='optional'/> <xs:attribute name='accuracy' type='xs:float' use='optional'/> <xs:element name='choicelist'> <xs:sequence> <xs:element minoccurs='0' maxoccurs='unbounded' ref='choice'/> </xs:sequence>
9 <xs:element name='choice'> <xs:attribute name='value' type='xs:string' use='required'/> <xs:attribute name='label' type='xs:string' use='optional'/> <xs:simpletype name='allowedtransducertype'> <xs:restriction base="xs:string"> <xs:enumeration value='temperature'/> <xs:enumeration value='illuminance'/> <xs:enumeration value='orientation'/> <xs:enumeration value='airpressure'/> <xs:enumeration value='windspeed'/> <xs:enumeration value='soundnoise'/> <xs:enumeration value='no'/> <xs:enumeration value='no2'/> <xs:enumeration value='co'/> <xs:enumeration value='co2'/> <xs:enumeration value='so2'/> <xs:enumeration value='ox'/> <xs:enumeration value='pm2.5'/> <xs:enumeration value='latitude'/> <xs:enumeration value='longitude'/> <xs:enumeration value='altitude'/> <xs:enumeration value='singlechoice'/> <xs:enumeration value='multiplechoice'/> <xs:enumeration value='freetext'/> <xs:enumeration value='freenumber'/> <xs:enumeration value='other'/> </xs:restriction> </xs:simpletype> <xs:simpletype name='allowedunits'> <xs:restriction base="xs:string"> <xs:enumeration value='meter'/> <xs:enumeration value='gram'/> <xs:enumeration value='second'/> <xs:enumeration value='ampere'/> <xs:enumeration value='kelvin'/> <xs:enumeration value='mole'/> <xs:enumeration value='candela'/> <xs:enumeration value='radian'/> <xs:enumeration value='steradian'/> <xs:enumeration value='hertz'/> <xs:enumeration value='newton'/> <xs:enumeration value='pascal'/> <xs:enumeration value='joule'/> <xs:enumeration value='watt'/> <xs:enumeration value='coulomb'/> <xs:enumeration value='volt'/> <xs:enumeration value='farad'/> <xs:enumeration value='ohm'/> <xs:enumeration value='siemens'/> <xs:enumeration value='weber'/> <xs:enumeration value='tesla'/> <xs:enumeration value='henry'/> <xs:enumeration value='lumen'/> <xs:enumeration value='lux'/> <xs:enumeration value='becquerel'/> <xs:enumeration value='gray'/> <xs:enumeration value='sievert'/>
10 <xs:enumeration value='katal'/> <xs:enumeration value='liter'/> <xs:enumeration value='square meter'/> <xs:enumeration value='cubic meter'/> <xs:enumeration value='meter per second'/> <xs:enumeration value='meter per second squared'/> <xs:enumeration value='reciprocal meter'/> <xs:enumeration value='kilogram per cubic meter'/> <xs:enumeration value='cubic meter per kilogram'/> <xs:enumeration value='ampere per square meter'/> <xs:enumeration value='ampere per meter'/> <xs:enumeration value='mole per cubic meter'/> <xs:enumeration value='candela per square meter'/> <xs:enumeration value='kilogram per kilogram'/> <xs:enumeration value='volt- ampere reactive'/> <xs:enumeration value='volt- ampere'/> <xs:enumeration value='watt second'/> <xs:enumeration value='percent'/> <xs:enumeration value='enum'/> <xs:enumeration value='lat'/> <xs:enumeration value='lon'/> <xs:enumeration value='string'/> <xs:enumeration value='image'/> </xs:restriction> </xs:simpletype> <xs:element name='property'> <xs:attribute name='name' type='xs:string' use='required'/> <xs:attribute name='value' type='xs:string' use='required'/> <xs:element name='data'> <xs:sequence> <xs:element minoccurs='0' maxoccurs='unbounded' ref='transducervalue'/> <xs:element minoccurs='0' maxoccurs='unbounded' ref='transducersetvalue'/> </xs:sequence> <xs:element name='transducervalue'> <xs:attribute name='id' type='xs:string' use='required'/> <xs:attribute name='typedvalue' type='xs:string' use='required'/> <xs:attribute name='timestamp' type='xs:datetime' use='required'/> <xs:attribute name='rawvalue' type='xs:string' use='optional'/> <xs:element name='transducersetvalue'> <xs:attribute name='id' type='xs:string' use='required'/> <xs:attribute name='typedvalue' type='xs:string' use='required'/> <xs:attribute name='rawvalue' type='xs:string' use='optional'/> </xs:schema>
Capability Advertisement Messages
Capability Advertisement Messages These sections describe schema definitions for the Capability Advertisement messages. Capability Advertisement Schema, page 1 Components of CCDL, page 2 Schema Definition,
More informationX3D Unit Specification Updates Myeong Won Lee The University of Suwon
X3D Unit Specification Updates Myeong Won Lee The University of Suwon 1 Units Specification ISO_IEC_19775_1_2008_WD3_Am1_2011_04_14 PDAM in ISO progress UNIT statement Defined in Core component UNIT statements
More informationOracle B2B 11g Technical Note. Technical Note: 11g_005 Attachments. Table of Contents
Oracle B2B 11g Technical Note Technical Note: 11g_005 Attachments This technical note lists the attachment capabilities available in Oracle B2B Table of Contents Overview... 2 Setup for Fabric... 2 Setup
More information/// Rapport. / Testdocumentatie nieuwe versie Register producten en dienstverlening (IPDC)
/// Rapport / Testdocumentatie nieuwe versie Register producten en dienstverlening (IPDC) / Maart 2017 www.vlaanderen.be/informatievlaanderen Informatie Vlaanderen /// Aanpassingen aan de webservices Dit
More informationExtensible Markup Language Processing
CHAPTER 2 Revised: June 24, 2009, This chapter describes the Extensible Markup Language (XML) process in the Common Object Request Broker Architecture (CORBA) adapter. XML and Components Along with XML,
More informationMWTM NBAPI WSDL and XSD Definitions
APPENDIXA This appendix describes the WSDL and XSD 1 (XML Schema Definition) definitions for MWTM 6.1.4 Northbound API (NBAPI): InventoryAPI.wsdl, page A-1 EventAPI.wsdl, page A-10 ProvisionAPI.wsdl, page
More informationMWTM 6.1 NBAPI WSDL and XSD Definitions
APPENDIXA This appendix describes the WSDL and XSD 1 (XML Schema Definition) definitions for MWTM 6.1 Northbound API (NBAPI): InventoryAPI.wsdl, page A-1 EventAPI.wsdl, page A-5 ProvisionAPI.wsdl, page
More informationAlwaysUp Web Service API Version 11.0
AlwaysUp Web Service API Version 11.0 0. Version History... 2 1. Overview... 3 2. Operations... 4 2.1. Common Topics... 4 2.1.1. Authentication... 4 2.1.2. Error Handling... 4 2.2. Get Application Status...
More informationMessages are securely encrypted using HTTPS. HTTPS is the most commonly used secure method of exchanging data among web browsers.
May 6, 2009 9:39 SIF Specifications SIF Implementation Specification The SIF Implementation Specification is based on the World Wide Web Consortium (W3C) endorsed Extensible Markup Language (XML) which
More informationCustom Data Access with MapObjects Java Edition
Custom Data Access with MapObjects Java Edition Next Generation Command and Control System (NGCCS) Tactical Operations Center (TOC) 3-D Concurrent Technologies Corporation Derek Sedlmyer James Taylor 05/24/2005
More informationCisco Prime Central 1.0 API Guide
Cisco Prime Central 1.0 API Guide Cisco Prime Central API Cisco Prime Central Information Model and API's to support the following features. Managed Elements and Equipment Inventory Object Create, Delete
More informationG16-02SE-A02.1-NUE112_SchedaContatto-Rev5 <?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/xmlschema"
More information
QosPolicyHolder:1 Erratum
Erratum Number: Document and Version: Cross References: Next sequential erratum number Effective Date: July 14, 2006 Document erratum applies to the service document QosPolicyHolder:1 This Erratum has
More informationOracle Enterprise Data Quality
Oracle Enterprise Data Quality Automated Loading and Running of Projects Version 9.0 January 2012 Copyright 2006, 2012, Oracle and/or its affiliates. All rights reserved. Oracle Enterprise Data Quality,
More informationApache UIMA Regular Expression Annotator Documentation
Apache UIMA Regular Expression Annotator Documentation Written and maintained by the Apache UIMA Development Community Version 2.3.1 Copyright 2006, 2011 The Apache Software Foundation License and Disclaimer.
More informationFall, 2005 CIS 550. Database and Information Systems Homework 5 Solutions
Fall, 2005 CIS 550 Database and Information Systems Homework 5 Solutions November 15, 2005; Due November 22, 2005 at 1:30 pm For this homework, you should test your answers using Galax., the same XQuery
More informationVDS Service Broker APIs
CHAPTER 2 This chapter describes the HTTPS RESTful APIs for VDS-SB and the XML schema. CDN Management API, page 2-1 BFQDN Management API BFQDN Policy API CDN Adaptation Policy API CDN Selection Policy
More informationDocument erratum applies to QosDevice:1. List other Erratum s or Documents that this change may apply to or have associated changes with
Erratum Number: Document and Version: Cross References: QosDevice:1 Erratum Next sequential erratum number Effective Date: July 14, 2006 Document erratum applies to QosDevice:1 List other Erratum s or
More informationRestricting complextypes that have mixed content
Restricting complextypes that have mixed content Roger L. Costello October 2012 complextype with mixed content (no attributes) Here is a complextype with mixed content:
More informationOracle Hospitality OPERA Web Self- Service Brochure Web Service Specification Version 5.1. September 2017
Oracle Hospitality OPERA Web Self- Service Brochure Web Service Specification Version 5.1 September 2017 Copyright 1987, 2017, Oracle and/or its affiliates. All rights reserved. This software and related
More informationDigital Signage Network Playlog Standards
Digital Signage Network Playlog Standards Version 1.1, August 23, 2006 Editor-In-Chief William Wu (DS-IQ) william.wu@ds-iq.com Editors Jeff Porter (Scala) jeff.porter@scala.com Steve Saxe (3M) sgsaxe@mmm.com
More informationProject Members: Aniket Prabhune Reenal Mahajan Mudita Singhal
CS-5604 Information Storage and Retrieval Project Report Scenario/Class Diagram Synthesis (American South 2) Project Members: Aniket Prabhune (aprabhun@vt.edu) Reenal Mahajan (remahaja@vt.edu) Mudita Singhal
More informationTargetTrack Remote Control Interface Document
TargetTrack Remote Control Interface Document Doppler Systems, LLC October 08, 2015 Revision B Contents Introduction... 2 IP Port... 2 Message Structure... 2 XML Messages... 2 Client to server message...
More informationAON Schemas. Archive Schema APPENDIXA
APPENDIXA This appendix contains schemas used by AMC. It includes the following: Archive Schema, page A-1 Programmatic Management Interface APIs, page A-15 Message Log Schemas, page A-26 Note This information
More informationPrivacy and Personal Data Collection Disclosure. Legal Notice
Privacy and Personal Data Collection Disclosure Certain features available in Trend Micro products collect and send feedback regarding product usage and detection information to Trend Micro. Some of this
More informationInformation Document Wind and Solar Power Forecasting ID # R
Information Documents are not authoritative. Information Documents are for information purposes only and are intended to provide guidance. In the event of any discrepancy between an Information Document
More informationGeneral Service Subscription Management Technical Specification
General Service Subscription Management Technical Specification Approved Version 1.0 20 Dec 2011 Open Mobile Alliance OMA-TS-GSSM-V1_0-20111220-A OMA-TS-GSSM-V1_0-20111220-A Page 2 (32) Use of this document
More informationTesting of Service Oriented Architectures A practical approach / APPENDIX V1.0
Testing of Service Oriented Architectures A practical approach / APPENDIX V1.0 Schahram Dustdar, Stephan Haslinger 1 Distributed Systems Group, Vienna University of Technology dustdar@infosys.tuwien.ac.at
More informationPISOA Interface Specification. Fall 2017 Release
PISOA Interface Specification Fall 2017 Release Version: 1.0 July 21, 2017 Revision History Date Version Description 07/21/2017 1.0 Initial document release related to the PISO Interfaces. RequestVERMeasurements
More informationCustomer Market Results Interface (CMRI) For RC Interface Specification. Version: 1.0.0
Customer Market Results Interface (CMRI) For RC Interface Specification Version: 1.0.0 November 1, 2018 Revision History Date Version Description 11/01/2018 1.0.0 Initial document release Page 2 of 10
More information[MS-TSWP]: Terminal Services Workspace Provisioning Protocol. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-TSWP]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationSpot Commercial Account Data Push
Spot Commercial Account Data Push Hari Gangadharan Version 1.0.1 Published on: Monday, January 06, 2008 Contributors Jonathan Beech Santhosh John 2008 THIS PAGE INTENTIONALLY LEFT BLANK Author: Hari Gangadharan
More informationOracle Utilities Opower Energy Efficiency Web Portal - Classic Single Sign-On
Oracle Utilities Opower Energy Efficiency Web Portal - Classic Single Sign-On Configuration Guide E84772-01 Last Update: Monday, October 09, 2017 Oracle Utilities Opower Energy Efficiency Web Portal -
More informationLevel of Assurance Authentication Context Profiles for SAML 2.0
2 3 4 5 Level of Assurance Authentication Context Profiles for SAML 2.0 Draft 01 01 April 2008 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 Specification URIs: This
More informationBiTXml. M2M Communications Protocol. Rel
BiTXml M2M Communications Protocol Rel. 2.0.3 Last revision: 2009-11-03 Index FOREWORDS... 4 FOREWORDS TO THE SECOND EDITION... 4 CHANGES... 5 INTRODUCTION... 7 1. REFERENCE MODEL... 8 2. BITXML V2 PROTOCOL
More informationIntellectual Property Rights Notice for Open Specifications Documentation
[MS-SSISPARAMS-Diff]: Intellectual Property Rights tice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats,
More informationUser Manual. HIPAA Transactions System Integration for Channel Partner Vendor. Version 15.2 May 2015
User Manual HIPAA Transactions System Integration for Channel Partner Vendor Version 15.2 May 2015 Trademarks and Copyrights Optum HIPAA Transactions System Integration Document Channel Partner Vendor
More informationeportfolio Interoperability XML Specification
eportfolio Interoperability XML Specification Version 1.0 DRAFT eportaro, Incorporated Updated: 29 January 2003 www.epixspec.org 2003 eportaro, Inc. Page i Notice 2003 eportaro Incorporated. All rights
More informationCisco Unity Connection Notification Interface (CUNI) API
Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 2018 Cisco Systems, Inc. All rights
More informationCWKS2CMDB Integration Guide
CWKS2CMDB Integration Guide Version 1.4.0 Contents 1. Introduction...3 1.1 Purpose...3 1.2 Assumptions...3 1.3 Components...3 2. Overview...4 2.1 CWKS2CMDB...4 2.2 EIE Transfer Data from RME Database to
More informationAutomated Load Forecast System (ALFS) For RC Interface Specification
Automated Load Forecast System (ALFS) For RC Interface Specification Version: 1.0 October 22, 2018 Revision History Date Version Description 10/23/2018 1.0 Initial document release related to the Load
More informationVDA Annex A KBL XML Schema
VDA-Recommendation 4964 Annex A 1 st Edition, November 2005 Page 1 of 20 Harness Description List (KBL) VDA Annex A KBL XML Schema 4964 This current recommendation is not binding and describes the information
More informationQVX File Format and QlikView Custom Connector
QVX File Format and QlikView Custom Connector Contents 1 QVX File Format... 2 1.1 QvxTableHeader XML Schema... 2 1.1.1 QvxTableHeader Element... 4 1.1.2 QvxFieldHeader Element... 5 1.1.3 QvxFieldType Type...
More informationValidation Language. GeoConnections Victoria, BC, Canada
Validation Language Submitted To: Program Manager GeoConnections Victoria, BC, Canada Submitted By: Jody Garnett Brent Owens Refractions Research Inc. Suite 400, 1207 Douglas Street Victoria, BC, V8W-2E7
More information[MS-SSISPARAMS-Diff]: Integration Services Project Parameter File Format. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-SSISPARAMS-Diff]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for
More informationThe following is a sample XML code from the HCSProductCatalog.wsdl file.
APPENDIXA This appendix contains sample WSDL and XSD files. It includes the following sections: HCSProductCatalog.wsdl File, page A-1 HCSProvision.xsd File, page A-27 HCSProvisionAsyncResponse.wsdl File,
More informationRequest for Comments: 4661 Category: Standards Track M. Lonnfors J. Costa-Requena Nokia September 2006
Network Working Group Request for Comments: 4661 Category: Standards Track H. Khartabil Telio E. Leppanen M. Lonnfors J. Costa-Requena Nokia September 2006 Status of This Memo An Extensible Markup Language
More information[MS-DPMDS]: Master Data Services Data Portability Overview. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-DPMDS]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationSMKI Repository Interface Design Specification TPMAG baseline submission draft version 8 September 2015
SMKI Repository Interface Design Specification DCC Public Page 1 of 21 Contents 1 Introduction 3 1.1 Purpose and Scope 3 1.2 Target Response Times 3 2 Interface Definition 4 2.1 SMKI Repository Portal
More informationSHS Version 2.0 SOAP-based Protocol Binding to SHS Concepts Försäkringskassan - Swedish Social Insurance Agency
SHS Concepts 1 (16) SHS Version 2.0 SOAP-based SHS Concepts Försäkringskassan - Swedish Social Insurance Agency Copyright 2012, 2013 Swedish Social Insurance Agency. All Rights Reserved. SHS Concepts 2
More informationQualys Cloud Platform v2.x API Release Notes
API Release Notes Version 2.37 February 20, 2019 Qualys Cloud Suite API gives you many ways to integrate your programs and API calls with Qualys capabilities. You ll find all the details in our user guides,
More information3GPP TS V ( )
Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; User Data Convergence (UDC); User Data Repository Access Protocol over the Ud interface;
More informationTED schemas. Governance and latest updates
TED schemas Governance and latest updates Enric Staromiejski Torregrosa Carmelo Greco 9 October 2018 Agenda 1. Objectives 2. Scope 3. TED XSD 3.0.0 Technical harmonisation of all TED artefacts Code lists
More informationWorkshare Compare Server 9.5.2
Workshare Compare Server 9.5.2 Developer Guide May 2018 9.5.2.4144 Workshare Compare Server 9.5 Developer Guide Table of Contents Chapter 1: Introduction...3 Introducing Workshare Compare Server... 4 Communicating
More informationPTS XML STANDARD GUIDELINE
PTS XML STANDARD GUIDELINE September 2012 Turkish Medicines & Medical Devices Agency, Department of Pharmaceutical Track & Trace System Söğütözü Mahallesi 2176 Sok. No: 5 P.K.06520 Çankaya, Ankara Phone:
More informationWork/Studies History. Programming XML / XSD. Database
Work/Studies History 1. What was your emphasis in your bachelor s work at XXX? 2. What was the most interesting project you worked on there? 3. What is your emphasis in your master s work here at UF? 4.
More informationPhysician Data Center API API Specification. 7/3/2014 Federation of State Medical Boards Kevin Hagen
7/3/2014 Federation of State Medical Boards Kevin Hagen Revision Description Date 1 Original Document 2/14/2014 2 Update with Degree search field 7/3/2014 Overview The Physician Data Center (PDC) offers
More informationQualys Cloud Suite API Release Notes
Qualys Cloud Suite API Release Notes Version 2.28 Qualys Cloud Suite API gives you ways to integrate your programs and API calls with Qualys capabilities. You ll find all the details in our documentation,
More informationXSD Reference For EXPRESS XML language
VTT-TEC-ADA-08 Page 1 SECOM Co., Ltd. / VTT Building and Transport Yoshinobu Adachi E-Mail: yoshinobu.adachi@vtt.fi VTT-TEC-ADA-08 XSD Reference For EXPRESS XML language 2002/02/11 1. INTRODUCTION... 2
More informationDataCapture API Version 6.0
DataCapture API Version 6.0 1 Document Control Document Location An electronic version of this document is available at: www.apxgroup.com and http://www.belpex.be/. Disclaimer This documentation is draft
More informationUPDATES TO THE LRIT SYSTEM. Report of the Drafting Group
E SUB-COMMITTEE ON NAVIGATION, COMMUNICATIONS AND SEARCH AND RESCUE 5th session Agenda item 4 21 ebruary 2018 Original: ENGLISH DISCLAIMER As at its date of issue, this document, in whole or in part, is
More information[MS-SSDL]: Store Schema Definition Language File Format. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-SSDL]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationBrief guide for XML, XML Schema, XQuery for YAWL data perspective
Brief guide for XML, XML Schema, XQuery for YAWL data perspective Carmen Bratosin March 16, 2009 1 Data perspective in YAWL YAWL engine files are XML based. Therefore, YAWL uses XML for data perspective
More informationPattern/Object Markup Language (POML): A Simple XML Schema for Object Oriented Code Description
Pattern/Object Markup Language (POML): A Simple XML Schema for Object Oriented Code Description Jason McC. Smith Apr 7, 2004 Abstract Pattern/Object Markup Language (or POML) is a simple XML Schema for
More information[MS-QDEFF]: Query Definition File Format. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-QDEFF]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationETSI TS V9.2.0 ( ) Technical Specification
Technical Specification Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; User Data Convergence (UDC); User data repository access protocol
More informationIntroduction Syntax and Usage XML Databases Java Tutorial XML. November 5, 2008 XML
Introduction Syntax and Usage Databases Java Tutorial November 5, 2008 Introduction Syntax and Usage Databases Java Tutorial Outline 1 Introduction 2 Syntax and Usage Syntax Well Formed and Valid Displaying
More informationITEMS FIXED SINCE V APPENDIX A... 4 APPENDIX B...
Release Notes GC-CAM Edit v9.4 Table of Contents NEW FEATURES... 2 GC-BASIC SUPPORT FOR COM OBJECTS - PRODUCT APPLICATION EXTENSION... 2 SELECT THIS NET / UNSELECT THIS NET... 2 ENHANCED FEATURES... 2
More information[MS-MSL]: Mapping Specification Language File Format. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-MSL]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationData Bus Client Interface Manager Interface Control Document
SunGuide SM : Data Bus Client Interface Manager Interface Control Document SunGuide-DB-CIM-ICD-1.0.0 Prepared for: Florida Department of Transportation Traffic Engineering and Operations Office 605 Suwannee
More informationPrivacy and Personal Data Collection Disclosure. Legal Notice
Privacy and Personal Data Collection Disclosure Certain features available in Trend Micro products collect and send feedback regarding product usage and detection information to Trend Micro. Some of this
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OTPCE]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More information[MS-QDEFF]: Query Definition File Format. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-QDEFF]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation ( this documentation ) for protocols,
More informationAdministering Oracle Enterprise Data Quality 12c (12.2.1)
[1]Oracle Fusion Middleware Administering Oracle Enterprise Data Quality 12c (12.2.1) E56642-01 October 2015 Describes how to administer Oracle Enterprise Data Quality. Oracle Fusion Middleware Administering
More informationSyntax XML Schema XML Techniques for E-Commerce, Budapest 2004
Mag. iur. Dr. techn. Michael Sonntag Syntax XML Schema XML Techniques for E-Commerce, Budapest 2004 E-Mail: sonntag@fim.uni-linz.ac.at http://www.fim.uni-linz.ac.at/staff/sonntag.htm Michael Sonntag 2004
More informationUNAVAILABILITY DOCUMENT UML MODEL AND SCHEMA
1 UNAVAILABILITY DOCUMENT UML MODEL AND SCHEMA 2017-01-27 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 Table of Contents 1 Objective...
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-MSL]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationarxiv: v1 [astro-ph.im] 5 Sep 2017
International Virtual Observatory Alliance VOEvent Transport Protocol Version v2.0 arxiv:1709.01264v1 [astro-ph.im] 5 Sep 2017 IVOA Recommendation 2017-07-21 Working group Data Access Layer / Time Domain
More information[MS-SSDL]: Store Schema Definition Language File Format. Intellectual Property Rights Notice for Open Specifications Documentation
[MS-SSDL]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More information<xs:element name="record" type="recordtype" maxoccurs="unbounded" /> </xs:sequence> </xs:complextype>
- -
More informationXML extensible Markup Language
extensible Markup Language Eshcar Hillel Sources: http://www.w3schools.com http://java.sun.com/webservices/jaxp/ learning/tutorial/index.html Tutorial Outline What is? syntax rules Schema Document Object
More informationSoftware Engineering Methods, XML extensible Markup Language. Tutorial Outline. An Example File: Note.xml XML 1
extensible Markup Language Eshcar Hillel Sources: http://www.w3schools.com http://java.sun.com/webservices/jaxp/ learning/tutorial/index.html Tutorial Outline What is? syntax rules Schema Document Object
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-OXSHRMSG]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More information!"#$%&'('$)*+,-.$/,-0'($12345$
"#$%&'('$)*+,-.$/,-0'($12345$ "#$%&'('$)*+,-.$/,-0'($12345$ E*139;F*>@)*94G-0=*14H56IJ*99GA6;1*JE1*I010J5@KG+31LM13:*1GN3:>*9N3O*1GP311ON9**2*1 ()*+,(-./0120134506 #$#F>1956I406-;7 F*;Q01;G+A$'RS$ 87N7A7
More informationMarkup Languages. Lecture 4. XML Schema
Markup Languages Lecture 4. XML Schema Introduction to XML Schema XML Schema is an XML-based alternative to DTD. An XML schema describes the structure of an XML document. The XML Schema language is also
More informationCreating and Modifying EAP-FAST Profiles for Distribution to Users
CHAPTER 4 Creating and Modifying EAP-FAST Profiles for Distribution to Users This chapter explains how configure EAP-FAST module profiles both by using a Group Policy Object editor and by modifying the
More informationXML / HTTP(s) NETIO M2M API protocols docs
XML / HTTP(s) NETIO M2M API protocols docs Protocol version: XML Version 2.0 Short summary XML / HTTP(s) protocol is a file-based M2M API protocol, where the NETIO device is a HTTP(s) server and the client
More informationAutomated Load Forecast System (ALFS) Interface Specification. Fall 2017 Release
Automated Load Forecast System (ALFS) Interface Specification Fall 2017 Release Version: 1.1 March 27, 2017 Revision History Date Version Description 03/01/2017 1.0 Initial document release related to
More informationPositioning Additional Constraints
Positioning Additional Constraints Issue XML Schema 1.1 allows additional constraints to be imposed on elements and attributes, above and beyond the constraints specified by their data type. Where should
More informationDFP Mobile Ad Network and Rich Media API
DFP Mobile Ad Network and Rich Media API v2.0, 12 June 2012 Background DFP Mobile is adopting a single open API for integrating with all ad networks and rich media vendors. This has the following benefits:
More informationApproaches to using NEMSIS V3 Custom Elements
NEMSIS TAC Whitepaper Approaches to using NEMSIS V3 Custom Elements Date August 17, 2011 July 31, 2013 (added section Restrictions, page 11) March 13, 2014 ( CorrelationID now reads CustomElementID as
More informationPolicy Support in Eclipse STP
Policy Support in Eclipse STP www.eclipse.org/stp By Jerry Preissler & David Bosschaert Agenda What is a policy? How can you work with the STP policy editor? Exercise 1 + 2 What can you do with policies?
More informationIODEF Data Model Status (progress from 03) <draft-ietf-inch-iodef-03>
IODEF Data Model Status (progress from 03) tracked @ https://rt.psg.com : inch-dm queue Roman Danyliw Wednesday, March 9. 2005 IETF 62, Minneapolis, USA Progress
More informationXEP-0337: Event Logging over XMPP
XEP-0337: Event Logging over XMPP Peter Waher mailto:peterwaher@hotmail.com xmpp:peter.waher@jabber.org http://www.linkedin.com/in/peterwaher 2017-09-11 Version 0.3 Status Type Short Name Deferred Standards
More informationConfiguring Capabilities Manager
Finding Feature Information, page 1 Prerequisites for, page 1 Information About Capabilities Manager, page 1 How to Configure Capabilities Manager, page 5 Additional References, page 8 Feature Information
More information4 Building a Data Exchange Connector
4 Building a Data Exchange Connector A Data Exchange Connector is a JMS server-based integration vehicle that helps you to build a bi-directional data exchange setup between Enterprise Manager and other
More informationTrustmark Framework Technical Specification
Trustmark Framework Technical Specification Version 1.2 November 6, 2017 Published by the Georgia Tech Research Institute under the Trustmark Initiative https://trustmarkinitiative.org/ Table of Contents
More informationAntenna Data Exchange File Format (ADX)
Antenna Data Exchange File Format (ADX) Technical Reference Version 1.2 Implementation Approval: : Tony Paul Position: RF Safety Compliance Coordinator Process Owner: : Mike Wood Position: Chairman - MCF
More information