Personal Bits of Stefan Hagen

A Few Sentences About Me

@Twitter    @LinkedIn   ...   @BandCamp@SoundCloud

My name is currently Stefan Hagen.
My name sounds spoken like:
[ʃtɛfaːn haːgən]
This here is a personal place provided to others for easing collaboration with me as Individual. Opinions and thoughts conveyed are my own.
I happen to architect, build, secure, and test software these days and for a living. As of November 2015, I passionately work for Cisco - mostly engineering security and quality into tools for the Internet of Things.

Topics of Interest

Disruptive change in Python: Python - “Order is now KeyStarting with version 3.6 (currently in 4th beta) keyword arguments and keys handed over to the built-in dict will preserve the insert order. I put together a micro booklet, just to help spread the word. Unlearning facts that we did not like in the first place is surprisingly hard, isn't it?

Music:
Erich Lanzerath † (1950 - 2010)

Thomas Offermann:
  ↳   “Shut up and play your guitar - Frank Zappa”

József Eötvös
Around 1977 I began learning how to play the guitar from the always humble and helpful Erich Lanzerath. How to really make music a part of me I received like a gift from Thomas Offermann during our lessons in the 80's, when he taught me play pieces from Leo Brouwer, Frank Zappa, J.S. Bach and others on the guitar. After a longer “parental leave” - as of May 2016 - I am proud that I can now learn more and more music making from József Eötvös, the hungarian guitarist and author of the transcription of Bach's “Goldberg Variations” among others.

A good thing: Non-Profit: “Bonner Tafel
  ↳   “Verteilen statt Vernichten
The initiative “Bonner Tafel” works according to the motto “distribute instead of destroy”. Volunteers collect / inside in and around Bonn a food that vendors would be forced to destroy or throw away. These provisions are passed through dispensaries to needy households and to non-profit institutions. Additional support through a monetary or in-kind donation is welcome. Regional volunteers are also often sought after and welcome.

Words and deeds CSAF, DSS-X, and OData.is what I love to support with. Three technical committees at “Organization for the Advancement of Structured Information Standards” (OASIS) bear with me as officer.

CSAF - “Common Security Advisory Framework”From November 2016 on, I contribute to “evolving the Common Vulnerability Reporting Framework (CVRF) specification to standardize existing practice in formulation and use of structured machine-readable vulnerability-related advisories within a new Common Security Advisory Framework” by serving as secretary to the OASIS CSAF TC.

DSS-X - “Digital Signature Services eXtended”Together with Juan Carlos Cruellas I chair the OASIS DSS-X Technical Committee (TC) to help “advancing digital signature services standards for XML” since 2007.

OData - “Open Data Protocol”I support “simplifying data sharing across disparate applications in enterprise, cloud, and mobile devices” by serving as secretary to the OASIS OData TC since it's formation in 2012.

MQTT - “Message Queuing Telemetry Transport” In addition I am contributing to the MQTT "next generation" a.k.a. v5 protocol within the OASIS MQTT TC: “Providing a lightweight publish/subscribe reliable messaging transport protocol suitable for communication in M2M/IoT contexts where a small code footprint is required and/or network bandwidth is at a premium.

AMQP-BINDMAP - “Advanced Message Queuing Protocol / Bindings and Mappings” Less frequently than I would like to, I support AMQP/Websockets specification at the OASIS AMQP-BINDMAP TC: “Defining bindings and mappings of AMQP wire-level messaging protocol for real-time data passing and business transactions”.

Independent of OASIS, I am a member of the GeoJSON community (@Github), GeoJSON the IETF JSON, and IETF Geographic JSON Working Groups on the simplification of the communication between applications through optimal general and geographic data formats and consistent processing expectations.

A picture: ... is worth a thousand words? Maybe, sometimes. A small snippet GeoJSON:

Quite elegant, right?


Abstract (from RFC 7946):
GeoJSON is a geospatial data interchange format based on JavaScript Object Notation (JSON). It defines several types of JSON objects and the manner in which they are combined to represent data about geographic features, their properties, and their spatial extents. GeoJSON uses a geographic coordinate reference system, World Geodetic System 1984, and units of decimal degrees.

A little tool: One-view visualization output from default config and data. One-view visualization output from technical template config and data. One-view visualization output from another config and data. One-view visualization output from a third config and data. QualityPie supports the methods recommended in “One-view visualization of speech quality measurement results” (Klemens P. F. Adler, Hans Wilhelm Gierlich and Joachim Pomy (Ed.)., ITU-T Recommendation P.505, 29 November 2005). Further details of Recommendation P.505 (2005) Amendment 1 (06/12) or follow the link to 'Quality Pie' inside the section Special Projects and Issues at the study group ITU-T SG 12.

Citing from the online tool's informative text:

The one-view visualization methodology is based on the allocation of individual circle segments to the selected parameters - the so-called "quality pie"; a maximum number of 16 different segments is considered here for practical reasons.

The total number of parameters represented determines the size of the individual segments in the quality pie. The axes are shown with a common origin. The individual circle segments have the same size (spanned angle 360° divided by number of selected quality parameters).

The representation of individual segment sizes is not interdependent, thus guaranteeing the independence of the different quality parameters from each other, which leads to the following advantages:

  • Independent representation of individual quality parameters.
  • Segment sizes are determined by the number of selected parameters and are identical.
  • Segment size (radius) is a measure for the quality regarding this parameter.
  • A concentric circle around the origin is defined (1/√2) which represents a minimum
    quality measure; falling below this segment size (radius) indicates a non-compliance
    with this limit value.
  • By means of a suitable colour selection results lying within the tolerance
    or transgressing the limit values can be easily visualized.

This online application of P.505 can help you to produce high quality graphs for your individual set of parameters. It is intended to support the use of this methodology in the field, e.g. for recurring reporting task, but also for benchmarking or for test events.

Source: “QualityPie plot web front-end, Version: 2.0.0, Last update: 2012-05-29”

Latest lecture: “Data, Management, Decision Oriented” at the European University of Applied Sciences, Neuss in June/August, 2013.

Questions & Answers: Asking questions may not be my strength ;-), Why practice :?) - Any personal contribution of this user is distributed under the MIT license. All opinions expressed only on behalf of himself. but as I received quite some answers in my life already, I started answering other peoples questions. On StackOverflow I am known as Dilettant.

Recent publications of the Committees

Internet Draft (in public review)Sean Gillies, “GeoJSON Text Sequences” draft-gillies-geojson-text-seq, Rev. 02, 19 September 2016: (TXT, PDF).

John Fallows, David Ingham, and Robert Godfrey, “Advanced Message Queuing Protocol (AMQP) WebSocket Binding (WSB) Version 1.0” Committee Specification 01, 16 August 2016: (HTML, PDF, editable source).

RFC 7946:
  ↳   “Sean Gillies' Blog Entry
Howard Butler, Martin Daly, Alan Doyle, Sean Gillies, Stefan Hagen, and Tim Schaub, “The GeoJSON Format” RFC 7946, August 2016 (DOI: http://dx.doi.org/10.17487/RFC7946): (TEXT, HTML, PDF).

OASIS Standard (inc. Appr. Errata)Mike Pizzo, Ralf Handl, and Martin Zurmuehl, “OData Version 4.0. Part 1: Protocol Plus Errata 03” OASIS Standard incorporating Approved Errata 03, 02 June 2016: ( HTML, PDF).

OASIS Standard (inc. Appr. Errata)Mike Pizzo, Ralf Handl, and Martin Zurmuehl, “OData Version 4.0. Part 2: URL Conventions Plus Errata 03” OASIS Standard incorporating Approved Errata 03, 02 June 2016: (HTML, PDF).

OASIS Standard (inc. Appr. Errata)Mike Pizzo, Ralf Handl, and Martin Zurmuehl, “OData Version 4.0. Part 3: Common Schema Definition Language (CSDL) Plus Errata 03” OASIS Standard incorporating Approved Errata 03, 02 June 2016: (HTML, PDF).

OASIS Standard (inc. Appr. Errata)Ralf Handl, Mike Pizzo, and Mark Biamonte, “OData JSON Format Version 4.0 Plus Errata 03” OASIS Standard incorporating Approved Errata 03, 02 June 2016: (HTML, PDF).

Ralf Handl, Hubert Heijkers, Gerald Krause, Michael Pizzo, and Martin Zurmuehl, “OData Extension for Data Aggregation Version 4.0” Committee Specification 02, 04 November 2015: (HTML, PDF, ABNF Grammar, and Vocabularies).

Ernst Jan van Nigtevecht and Frank Cornelis, “DSS Extension for Local Signature Computation Version 1.0”, Committee Specification 01, 27 July 2015: (HTML, PDF).

RFC 7493Tim Bray, Ed., “The I-JSON Message Format” RFC 7493, 22 March 2015: (TEXT, HTML, PDF).

RFC 7464Nico Williams, “JavaScript Object Notation (JSON) Text Sequences” RFC 7464, 25 February 2015: (TEXT, HTML, PDF).

RFC 7159T. Bray, Ed., “The JavaScript Object Notation (JSON) Data Interchange Format” RFC 7159, March 2014: (TEXT, HTML, PDF).

OASIS StandardMike Pizzo, Ralf Handl, and Martin Zurmuehl, “OData Version 4.0 Part 1: Protocol” OASIS Standard, 24 February 2014: (HTML, PDF).

OASIS StandardMike Pizzo, Ralf Handl, and Martin Zurmuehl, “OData Version 4.0 Part 2: URL Conventions” OASIS Standard, 24 February 2014: (HTML, PDF).

OASIS StandardMike Pizzo, Ralf Handl, and Martin Zurmuehl, “OData Version 4.0 Part 3: Common Schema Definition Language (CSDL)” OASIS Standard, 24 February 2014: (HTML, PDF).

OASIS StandardRalf Handl, Mike Pizzo, and Mark Biamonte, “OData JSON Format Version 4.0” OASIS Standard, 24 February 2014: (HTML, PDF).

Mike Pizzo, Ralf Handl, Stefan Drees and Martin Zurmuehl, “What's New in OData Version 4.0” OASIS Committee Note 01, 15 August 2013: (HTML, PDF).

Martin Zurmuehl, Mike Pizzo, and Ralf Handl, “OData Atom Format Version 4.0” OASIS Committee Specification 01, 14 August 2013: (HTML, PDF).

Detlef Hühnlein, “OASIS DSS v1.0 Profile for Comprehensive Multi-Signature Verification Reports” Version 1.0, OASIS Committee Specification 01, 12 November 2010: (HTML, PDF).

Ezer Farhi (In Memory of Uri Resnitzky, ARX, an active member of OASIS DSS-X Committee), “Visible Signature Profile of the OASIS Digital Signature Services” Version 1.0, OASIS Committee Specification 01, 8 May 2010: (HTML, PDF).

Pim van der Eijk and Ernst Jan van Nigtevecht, “OASIS ebXML Messaging Transport Binding for Digital Signature Services” Version 1.0, OASIS Committee Specification 01, 11 April 2007: (HTML, PDF).

OASIS StandardStefan Drees et al., “Digital Signature Service Core Protocols, Elements, and Bindings” Version 1.0, OASIS Standard, 11 April 2007: (HTML, PDF).