Study Group 17 ASN.1 The importance of colour John Larmouth ISO ASN.1 Rapporteur Note, for best viewing, this presentation needs.

Slides:



Advertisements
Similar presentations
Language Specification using Metamodelling Joachim Fischer Humboldt University Berlin LAB Workshop Geneva
Advertisements

SDL+ The Simplest, Useful Enhanced SDL-Subset The documentation is the design, the design is the system! Copyright © SDL Task Force Consortium.
Cascading Style Sheets (CSS). Cascading Style Sheets With the explosive growth of the World Wide Web, designers and programmers quickly explored and reached.
CIS 375—Web App Dev II SOAP.
Poster Title Goes Here & Must Match Your Submitted Abstract Title Authors’ Names Goes Here (must match those on the submitted abstract) Affiliations go.
Copyright © 1998 by Addison Wesley Longman, Inc. 1 Chapter One Preliminaries, including –Why study PL concepts? –Programming domains –PL evaluation criteria.
UML and SDL Modeling Languages.
IEC Substation Configuration Language and Its Impact on the Engineering of Distribution Substation Systems Notes Dr. Alexander Apostolov.
Intermediate Level Course. Text Format The text styles, bold, italics, underlining, superscript and subscript, can be easily added to selected text. Text.
TAC Vista Security. Target  TAC Vista & Security Integration  Key customer groups –Existing TAC Vista users Provide features and hardware for security.
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 5: Restaurant.
1 CS 426 Senior Projects Chapter 19: Interfaces and Components [Arlow & Neustadt 2005] February 28, 2008.
Structure and formatting HTML pages Helen Treharne Department of Computing.
THE OBJECT-ORIENTED DESIGN WORKFLOW Interfaces & Subsystems.
1 CS 691z / 791z Topics on Software Engineering Chapter 17: Interfaces and Subsystems [Arlow & Neustadt, 2002] March 6, 2007.
Information Extraction from Documents for Automating Softwre Testing by Patricia Lutsky Presented by Ramiro Lopez.
McGraw-Hill The McGraw-Hill Companies, Inc., 2000 SNMP Simple Network Management Protocol.
® Eurostep.ESUKPC v0.1©Copyright Eurostep Limited An Introduction to ISO STEP Part 25 David Price.
Copyright © WebGiro AB, All rights reserved. E-Commerce Integration Meta-Framework Andrzej Bialecki Chief System Architect TM The.
CSC 8310 Programming Languages Meeting 2 September 2/3, 2014.
International Telecommunication Union ITU-T Study Group 17, Moscow, 30 March – 8 April 2005 New Recommendations on ODP Arve Meisingset Rapporteur Q15.
Method of Converting Resource definitions into XSD Group Name: WG3 (PRO) Source: Shingo Fujimoto, FUJITSU, Meeting Date:
CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Tuesday Class will start momentarily. Please Stand By … CS 8532: Advanced Software.
1 CIM User Group Conference Call december 8th 2005 Using UN/CEFACT Core Component methodology for EIC/TC 57 works and CIM Jean-Luc SANSON Electrical Network.
Workshop on Integrated Application of Formal Languages, Geneva J.Fischer Mappings, Use of MOF for Language Families Joachim Fischer Workshop on.
An Overview of MPEG-21 Cory McKay. Introduction Built on top of MPEG-4 and MPEG-7 standards Much more than just an audiovisual standard Meant to be a.
AML ASN.1 Markup Language A markup notation for ASN.1 values Copyright © 2001 Griffin Consulting, All Rights Reserved. Griffin Consulting 1625 Glenwood.
Introduction to MDA (Model Driven Architecture) CYT.
1 XML: an introduction David Nathan. 2 XML  an in-line markup system  single sequence of plain text only (but can be unicode)  equivalent to a tree.
Using the BLS Template (slide hidden from show; may be relocated or deleted) CORE slides – Presentation Title (slide 2) and Contact Info (slide 4) - are.
Possible elements of the technical standards Pre-sessional consultations on registries Bonn, 2-3 June 2002 Andrew Howard UNFCCC secretariat
Processing of structured documents Spring 2002, Part 2 Helena Ahonen-Myka.
Abstract Syntax Notation ASN.1 Week-5 Ref: “SNMP…” by Stallings (Appendix B)
Specializing and extending the UML
Knowledge Technologies March 2001 DataChannel, Inc Preserving Process Hyperlink-Based Workflow Representation W. Eliot Kimber, DataChannel, Inc.
Study Group 7/17 ASN.1 ASN.1: Past uses, new developments, and future prospects in security and e-commerce applications John Larmouth
A language to describe software texture in abstract design models and implementation.
RELATORS, ROLES AND DATA… … similarities and differences.
Customizing Aspen Templates TEC04 Elizabeth Lucchese.
Part VII: Design Continuous
Software testing techniques Software testing techniques Object-oriented software testing Presentation on the seminar Kaunas University of Technology.
TTCN-3 and ASN.1 interworking Analysis of backward compatibility in ASN.1 Géza Horváth TTCN-3 User Conference – 9 June 2011.
STEP Tutorial: “ Fundamentals of STEP” David Briggs, Boeing January 16, 2001 ® PDES, Inc NASA STEP Workshop step.nasa.gov.
Chapter 19: Interfaces and Components [Arlow and Neustadt, 2005] University of Nevada, Reno Department of Computer Science & Engineering.
All Presentation Material Copyright Eurostep Group AB ® A Meta-model of EXPRESS in UML for MOF and UML to EXPRESS David Price April 2002.
1. 2 Purpose of This Presentation ◆ To explain how spacecraft can be virtualized by using a standard modeling method; ◆ To introduce the basic concept.
UML Profile BY RAEF MOUSHEIMISH. Background Model is a description of system or part of a system using well- defined language. Model is a description.
Using DSDL plus annotations for Netconf (+) data modeling Rohan Mahy draft-mahy-canmod-dsdl-01.
Chapter 36 Network Management & SNMP. Network management monitors network related hardware & software; troubleshoot network problems Detects major failures.
Javascript Basic Concepts Presentation By: Er. Sunny Chanday Lecturer CSE/IT RBIENT.
Part 25 E2 EXPRESS/UML Walkthrough Seattle STEP October 2004.
Text2PTO: Modernizing Patent Application Filing A Proposal for Submitting Text Applications to the USPTO.
Study Group 17 ASN.1 John Larmouth ITU-T and ISO/IEC ASN.1 Rapporteur
PerfSONAR Schema and Topology Martin Swany. Schema Key Goals: Extensibility, Normalization, Readability Break representation of performance measurements.
ER Diagrams ● Many different notations are available ● From wikipedia:wikipedia: Entity-relationship modelwikipedia: Entity-relationship model ● How do.
9/21/2016 Presentation layer Abstract Syntax Notation #1 Basic Encoding Rules.
Fundamentals of Object Oriented Modeling
Poster Title Goes Here & Must Match Your Submitted Abstract Title
The ITU-T X.500 series and X.509 in a changing world
Object-oriented software testing
Introduction to XML History Concepts Well-formed XML
COPS Digital Expansion Project
The Process of Object Modeling
News from the wonderful world of directories
Chapter 19: Interfaces and Components
Overview of the ETSI Test Description Language
Poster Title Goes Here & Must Match Your Submitted Abstract Title
Interfaces and Components
Chapter 19: Interfaces and Components
Standards, Models and Language
Presentation transcript:

Study Group 17 ASN.1 The importance of colour John Larmouth ISO ASN.1 Rapporteur Note, for best viewing, this presentation needs the Dom Casual and Brush Script fonts. Study Group 17 ASN.1

Black and White is bad! n The Black and White Minstrel Show n Black and White TVs n The latest Nokia phone!

Study Group 17 ASN.1 Colour is good! n The deep blue of the sky n Sunlight shining on the ground n Leaves in the Autumn n Printers and photocopiers n Colouring illuminates!

Study Group 17 ASN.1 What is colouring? n Colouring is the application of detail to a specification n For some, not necessary n For others, important

Study Group 17 ASN.1 What is SDL, UML, UBL about? n They are about easy specification of distributed processes n The are about the semantics (and sequences) of the messages that are exchanged in a protocol

Study Group 17 ASN.1 What is not necessary? (Or is it?) n Notation used to define the syntax of messages (ASN.1, XSD specification, table notation) n Detailed syntax specification n Control of encodings n Extensibility identification n Sub-typing (constraints)

Study Group 17 ASN.1 Business processes matter! But bits on the line matter as well! n How much can be automated? n How much help is needed? n How to provide that help?

Study Group 17 ASN.1 The ASN.1 colouring concept n Used in XCN n Used in ECN n A separate specification at a different level of detail, but closely linked to the higher-level specification

Study Group 17 ASN.1 Example 1 – XCN colouring ASN.1: TraceCollection ::= SEQUENCE { version UTF8String DEFAULT "1.0”, collectionBeginTimeDateTime, vendorUTF8String OPTIONAL, senderSender OPTIONAL, callsSEQUENCE SIZE (1..MAX) OF call Call } Colouring for XML: ATTRIBUTE version, collectionBeginTime IN TraceCollection

Study Group 17 ASN.1 Example 2 – ECN colouring ASN.1: Sequence2 ::= SEQUENCE{ component1BOOLEAN OPTIONAL, component2INTEGER, component3VisibleStringOPTIONAL } Colouring for ECN: RENAME #OPTIONAL AS #Sequence2-optional IN #Sequence2 -- #Sequence2-optional is a special encoding for optionality -- #Sequence2-optional is a special encoding for optionality -- Other optionals encode in the normal way. -- Other optionals encode in the normal way.

Study Group 17 ASN.1 What is colouring? (1) Colouring is the application of detail that is irrelevant in the development of the base specification. Colouring is the application of detail that is irrelevant in the development of the base specification.

Study Group 17 ASN.1 What is colouring? (2) But detail that is essential for the efficient generation of lower-level specifications, down to encodings But detail that is essential for the efficient generation of lower-level specifications, down to encodings

Study Group 17 ASN.1 What can colouring be used for? n Ranges and subtypes (minimum set of abstract values) n Extensibility needs n Processing Instructions (low level control)

Study Group 17 ASN.1 Different targets for colouring in ASN.1 n BER needs tags n PER needs clear extensibility requirements and sub-typing n XML needs attribute and TEXT and UNTAGGED etc n ECN needs identification of specially-encoded constructors

Study Group 17 ASN.1 Requirements Analysis Top-level design – SDL, UML, UBL (only essential info?) ECN PER BER XER Possible implementation routes XSD ASN.1 Tables BNF Possible implementation routes Detail is needed at each level. How to add it without confusing the simple design? How to add it without confusing the simple design? Add detail with colouring.

Study Group 17 ASN.1 The W-5 n Who will provide the details? (Relevant experts) n Why do we want details as well as top- level design? (The details matter) n Where do we record the details? (Embedded, Colouring, Boxes) n What details need to be included? (Anything necessary for efficient lower-layer mappings) n Which implementation mappings? (Detail for several notations, several encodings)

Study Group 17 ASN.1 But three is good! n The three ages of man n The three fates n The three faces of Buddha n The three fundamental forces

Study Group 17 ASN.1 The three experts n Domain (business) experts n Notation experts ASK FOR MORE DETAIL on sub-typing, extensibility n Encoding experts ASK FOR MORE DETAIL on bandwidth needs, readability, encoding choices This all needs adding to the base specification - perhaps the colouring metaphor will help

Study Group 17 ASN.1 Colouring n An architectural concept n Has proved useful in ASN.1 n Part of information hiding n Keeps top-level independent of lower layer implementation n Ensures lower layer details needed for efficient operation can be easily provided Colour is good!