1 / 21

Lower case ubiquitous web architecture and its implementations

Lower case ubiquitous web architecture and its implementations . Satoru TAKAGI ● , Katsunori SHINDO, Jun YAMADA, Ken SAKAMURA YRP Ubiquitous Networking Laboratory. Our objectives. Establishment of ubiquitous computing environment as social infrastructure with the following features:

ralph
Télécharger la présentation

Lower case ubiquitous web architecture and its implementations

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lower case ubiquitous web architecture and its implementations Satoru TAKAGI●, Katsunori SHINDO, Jun YAMADA, Ken SAKAMURA YRP Ubiquitous Networking Laboratory

  2. Our objectives Establishment of ubiquitous computing environment as social infrastructure with the following features: • Real-time Communication Protocols • Security • Ultra Tiny Computers • Effortless Operation • Human Friendly Interface • Calm Computing • Cooperative Processing

  3. Ultra Tiny Computers Ultra Tiny Computers

  4. Ultra Tiny ComputersHARDWARE Reference specifications of small computer hardware for ubiquitous computing pT-Engine μT-Engine T-Engine T-Engine Ubiquitous Communicator

  5. Ultra Tiny ComputersSOFTWARE T-Kernel : Open source real-time operating system http://www.t-engine.org/T-Kernel/tkernel_e.html

  6. Ubiquitous ID Ubiquitous ID “ucode” Various network infrastructures

  7. Ubiquitous ID “ucode” Architecture Features of ucode (Ubiquitous CODE) architecture • Identifier that can be put on all things • Machine readable (128 bit binary code) • Meaning-less number (Not based on MAC address etc.) • It can number all things at random if necessity

  8. Ubiquitous ID “ucode” Architecture 2 • Data model (It is named UCR.: UCode Relation) • Compatible with RDF • Recognizable as URI (It corresponds to Resource of RDF. ) ucode:A0DC3-45DA-25Df-8375-90AC-BEA0-98C9-34FC • Variety of ucode • Virtual ucode　：It is ucode numbered to concept. • Relation ucode : It is ucode numbered to relation.(It corresponds to property of RDF. And it can quote the vocabulary for RDF. ) • Real ucode　：　 It is ucode numbered to real thing. Example Relation ucode A Real ucode 1 This apple Real ucode 2 That farm Relation ucode A dc:creator Relation ucode B Sweetness Viatual ucode α Good Real ucode 1 Real ucode 2 Virtual ucode α Relation ucode B

  9. Real ucode Examples of real ucode containers Active RFID Tag “Dice” Active IR-tag Passive RFID Tag “μ-chip” 2-dimensional bar-code

  10. Valuable features of WWW for our objectives • It is based on social infrastructure for the people by circulation of the presentation data. (html, SVG etc.) • It is not based on machine understandable data. • It interoperates with all information systems with both loose and sloppy coupling. (by meaning-less hyper-link) • It does not require completeness of data and systems.

  11. Ubiquitous web platform configurationanalogized from WS Semantics Presentation Human Machine Interface Huge & Abstract http://www2005.org/panels/#PA09 Protocol SOAP HTTP MAIL SOA UDDI WSDL XML Schema XML (DOM) IRI

  12. Requirements for light weight ubiquitous information platform • Embeddability for general web presentation data • Scalability from rudimentary light implementations to more advanced implementations • Scalability from sloppy applications to stricter systems

  13. Two methods for service resolutionto achieve context awareness User’s context information 　　　：Information like CC/PP, FOAF Server Side Resolution (good functionality and quality) common data structure UCR (RDF) Client Side Resolution (good security and liberty) Service Menu 　　　：Information like RSS Resolve interactively Presentation data common data structure WEB Content Browse Server Client ucode relation management server ucode relation aware web browser Scalability Metadata for available services Context of user Embeddability

  14. Lower case ubiquitous web platform configuration Protocol SPARQL REST HTTP MAIL File Prsentation (X)HTML SVG SMIL XForms etc.. Rules ・・・・・ Ontology (OWL) Vocabulary Dublin Core RSS, CC/PP, FOAF Geo Vocab. etc. Scalability Embeddability Metadata/Semantics RDF Markup XML (SAX2.0) IRI (URL , ucode , uuid etc.)

  15. Application of semantic web to Geographic Information Systems SVG map presentation with spatial metadata • It is based on valuable features of WWW. • It is possible to process by GIS. • http://esw.w3.org/topic/GeoMetadataOverSvg Vocabularies: • UCR – Spatial Metadata: Vocabulary for basic spatial metadata based on W3C basic geo vocabulary. • UCR – Spatial Network:Vocabulary for the spatial network. It enhances the above-mentioned vocabulary. And it suits with the logical network structure of RDF. • UCR – Spatial Accessibility:Vocabulary to express spatial accessibility for mover such as pedestrian, handicapped person, etc.

  16. DEMO Client-side Service Resolution that uses • XML (SAX2.0) Parser • 30KBytes loading module (“C” code) • RDF/XML Parser andObject Manager with Basic Query Interface • 28KBytes loading module (“C” code) Content browser • UCR(RDF) and SVG

  17. Configuration of demo software Client SVG viewer UCR viewer Spatial resolver General purpose (sloppy) resolver XForms processor UCR object manager XML(SAX) parser Real ucode reader Map Server UCR management server A spatial thing with real ucode

  18. Thank you.

  19. Embedding of UCR data into SVG (map presentation) • It makes relation between UCR data and graphic element of SVG. • UCR data is embedded into SVG content as meta data. Graphic element SVG Map Content UCR Data Ｆａｃｉｌｉｔｙ B Embed Facility A

  20. UCR-Spatial Metadata • Basic information about spatial thing • Spatial reference • Latitude, Longitude, Altitude (Spatial Coordinates) • (Spatial) Address • Spatial categories • Station, Walkway,Post officeetc. • Based on Basic Geo Vocabulary (W3C Semantic Web Interest Group) Facility A ug:place geo:SpatialThing rdf:type ug:iso6709 +35.115+135.123/ ug:category dc:relation ug:radius 1m ug:shop SVG graphic element etc.

  21. UCR – Spatial Network • Spatial network information • Node class • Link class • Length,One-way etc. • Inclusion (hasPart property) • It suits with the logical network structure of RDF. ug:length 10m “Shop D” “Walkway p” ug:hasPart ug:Link rdf:type reification ug:Node rdf:type “Post Office B” ug:Node “Station A” ug:link rdf:type ug:Node ug:link ug:link reification reification ug:Link ug:Node “Underpass q” rdf:type “Walkway r” Shop C ug:Link rdf:type rdf:type ug:Link ug:Node

More Related