1 / 28

Presentation on Smart Graphics

Presentation on Smart Graphics Frank Farance, Farance Inc. +1 212 486 4700 frank@farance.com Framework For Smart Graphics AGR numbers are strawmen Joint activities: IEEE 1484.7 Tool/Agent Communication AICC Smart Graphics Working Group Related activities:

oshin
Télécharger la présentation

Presentation on Smart Graphics

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. Presentation on Smart Graphics Frank Farance, Farance Inc. +1 212 486 4700frank@farance.com Presentation on Smart Graphics, F. Farance

  2. Framework For Smart Graphics • AGR numbers are strawmen • Joint activities: • IEEE 1484.7 Tool/Agent Communication • AICC Smart Graphics Working Group • Related activities: • ISO/IEC JTC1 SC25 WG1: ISO 15067-1 • Data and Control Transfer Protocol • ISO/IEC JTC1 SC32 WG2: ISO 20944 • Metadata Query Service (API features) • DMSO HLA: Simulation Presentation on Smart Graphics, F. Farance

  3. A Sample Smart Graphic Conceptual Model: Communicating over a bus Implementations: Can use APIs, protocols,shared memory, etc., to communicate Presentation on Smart Graphics, F. Farance

  4. Smart Graphics Codings, Data Elements Topic-SpecificInformative Wording Topic-SpecificNormative Wording Requirements Cross-TopicCodings: e.g., XML Various Standards Functionality Cross-Topic APIs:Normative WordingJava, JavaScript,C/C++, Perl, Tcl, VB Conceptual Model Cross-Topic Protocolse.g.: Session Layers Cross-Topic APIsInformative Wording Various Standards Semantics Bindings: APIs Bindings: Codings Bindings: Protocols Encodings: VariousCommunication Layers Encodings:Data Formats Encodings:Calling Conventions Presentation on Smart Graphics, F. Farance 

  5. AGR101: API/Environment • Main requirements/features: • Session establishment, data transfer, subscription/multicast • Example (not exact syntax): H = connect ("altimeter 1", "ARINC", "10 samples/sec"); V = getvalue(H,”atimiter_setting"); putvalue(H,"altitude", 14250); Presentation on Smart Graphics, F. Farance

  6. API/Environment Issues Environment Typical Messages: - Connect - GetValue/PutValue - Publish/Subscribe - Probe features Presentation on Smart Graphics, F. Farance

  7. AGR102: Transactions • Main requirements/features: • Describing common transactions • Examples: • Definition of initiation and termination of graphics objects • Common data structures in objects • Common operations: render, repaint, print, start, stop, restart Presentation on Smart Graphics, F. Farance

  8. Transactions Typical Transaction Definitions: - Initiation - Termination - Render - Repaint - Print - Start, Stop, Restart - Error handling Presentation on Smart Graphics, F. Farance

  9. AGR103: Protocol Configuration • Main requirements/features: • Setting up “protocol stack” • How is connection specified • Need to handle standalone/nomadic access • Session establishment, data transfer, subscription/multicast Presentation on Smart Graphics, F. Farance

  10. Protocol Configuration Protocol stack, e.g., ARINC, TCP/IP Implementations: Can use APIs, protocols, etc., to communicate Presentation on Smart Graphics, F. Farance

  11. AGR104: Element Conversion • Main requirements/features: • Translation of units, e.g., inches <=> meters • Formal definition of units • Reference to ISO definitions • Registration of units Presentation on Smart Graphics, F. Farance

  12. Element Conversion Dynamic conversion of elements Presentation on Smart Graphics, F. Farance

  13. AGR105: Performance Negotiation • Requirements and features: • How to probe and determine what features are available • Useful for determining real-time performance, e.g., how many samples can send/receive per second Presentation on Smart Graphics, F. Farance

  14. Performance Negotation Determination of network/deviceperformance parameters Presentation on Smart Graphics, F. Farance

  15. AGR2xx: Device Specifications • Data elements and parameter specifications for devices (examples): • AGR201 (altimeter) • AGR202 (flight management computer) • AGR203 (multifunction knob) • AGR204 (device X) • AGR205 (device ...) • Would specify data elements, semantics Presentation on Smart Graphics, F. Farance

  16. Relationship to ISO 15067-1 • Development in ISO/IEC JTC1 SC25 WG1 • Collaboration with IEEE 1484.15 Data Interchange Protocols (learning technology-specific) • Can use variety of encodings, e.g., XML, ASN.1, ARINC Presentation on Smart Graphics, F. Farance

  17. ISO 15067-1 Protocol Topic-SpecificInformative Wording Topic-SpecificNormative Wording Requirements Cross-TopicCodings: e.g., XML Various Standards Functionality Cross-Topic APIs:Normative WordingJava, JavaScript,C/C++, Perl, Tcl, VB Conceptual Model Cross-Topic Protocolse.g.: Session Layers Cross-Topic APIsInformative Wording Various Standards Semantics Bindings: APIs Bindings: Codings Bindings: Protocols Encodings: VariousCommunication Layers Encodings:Data Formats Encodings:Calling Conventions Presentation on Smart Graphics, F. Farance 

  18. ISO 15067-1, Protocol-Based Using ISO 15067-1 (DCTP) to Communicate Presentation on Smart Graphics, F. Farance

  19. DCTP Overview • Data and Control Transfer Protocol • Intended to be 2-way • Intended to be low cost, low bandwidth • Incorporates many security technologies • Working with IBM, Siemens, BT, Telcordia (formerly Bellcore), University of Colorado Presentation on Smart Graphics, F. Farance

  20. DCTP Main Features • Multiple sessions, views, sub-views • Nomadic sessions for roaming, sometimes-connected learners • Reliable multicast • Pluggable security • Low interactivity • Encoding negotiations, e.g., ASN.1, XML, ARINC are possible • DCTP is not an API Presentation on Smart Graphics, F. Farance

  21. Collaboration WithISO/IEC JTC1 SC25 WG1 • “Home electronic systems” • Exist for 10 years • For DCTP, merge work done at BT Labs • Experience in: • Multicast features • Firewall/gateway bridges/tunnels • Multimedia • Security/privacy • Incorporation into products Presentation on Smart Graphics, F. Farance

  22. Relationship to ISO 20944 • Development in ISO/IEC JTC1 SC32 WG2 • Binding to many languages: C, C++, Java, JavaScript, VB, Perl, Tcl, LISP Presentation on Smart Graphics, F. Farance

  23. ISO 20944 Metadata Query Service Is “API-Like” Topic-SpecificInformative Wording Topic-SpecificNormative Wording Requirements Cross-TopicCodings: e.g., XML Various Standards Functionality Cross-Topic APIs:Normative WordingJava, JavaScript,C/C++, Perl, Tcl, VB Conceptual Model Cross-Topic Protocolse.g.: Session Layers Cross-Topic APIsInformative Wording Various Standards Semantics Bindings: APIs Bindings: Codings Bindings: Protocols Encodings: VariousCommunication Layers Encodings:Data Formats Encodings:Calling Conventions Presentation on Smart Graphics, F. Farance 

  24. ISO 20944, API-Based Using ISO 20944 Metadata Query Service (MQS)For API communication Presentation on Smart Graphics, F. Farance

  25. Conceptual Model (High Level) • #1: Connect to repository; query metadata/data of repository • #2: Determine what data to access (via metadata) and how to access • #3: Data exchange Presentation on Smart Graphics, F. Farance

  26. Conceptual Model (Low Level) • Connect to repository • Negotiate parameters (security, formats, etc.) • Navigate the repository • Get and put information • Merge data/metadata/props namespace • Miscellaneous data mgmt. operations Presentation on Smart Graphics, F. Farance

  27. Semantics Summary • Currently being refined, based on SDA API, LQS, DCTP, etc. • Work being harmonized with ISO 15067-1 (DCTP being incorporated) • Early draft of MQS document in 2000-11 Presentation on Smart Graphics, F. Farance

  28. Summary • Further drafts by 2000-12 • Collaboration with graphics vendors, discussion at 2001-01 AICC meeting • Demonstration of “portability” Presentation on Smart Graphics, F. Farance

More Related