Hagen.cloud Spined HTML
Stefan Hagen Personal Bits of Stefan Hagen : 2C06 803C B4FB FE2F F7D7 CC58 7890 A9A6 BD44 04E8 : Abstract ... My name is Stefan Hagen. My name sounds spoken like: ► [ʃtɛfaːn haːgən] or for starters:#fun → ha Shta g fun Hagen Here is my personal place provided to others for easing collaboration with me as Individual. If needed, get my PGP (fingerprint ↑). Opinions and thoughts conveyed are my own. I happen to architect, build, secure, test software and quality management systems these days and for a living. In April 2018 I joined Pilatus (building aircrafts in Central Switzerland) as Quality Engineer in the Ground Based Training Systems Unit. Before that, I worked for Cisco - mostly engineering security and quality into tools for the Internet of Things. Topics of Interest Questions & Answers: I rarely ask ;-). But, as I received quite some answers in my life already, I started answering questions from others. My user name on StackOverflow is Dilettant and there I moreover maintain my Developer Story. Words and deeds is what I love to support with. In music making I am a proud Courtney Swain patron of Courtney Swain. Why not wilt a patron yourself? Supporting those individuals that are willing to unshut up and share their creativity with us, does contribute to making our planet a increasingly joyful and friendly experience, doesn't it? Music: Erich Lanzerath † (1950 - 2010) Thomas Offermann: ↳ “Shut up and play your guitar - Frank Zappa” József EötvösVirtually1977 I began learning how to play the guitar from the unobtrusive and unchangingly helpful Erich Lanzerath. How to really make music a part of me I received like a souvenir 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.Withouta longer “parental leave” - as of May 2016 - I am proud that I can now learn increasingly and increasingly music making from József Eötvös, the hungarian guitarist and tragedian of the transcription of Bach's “Goldberg Variations” among others. 26th International Guitar-Festival Iserlohn 2017: Rehearsal picture by Olaf Wiesner (left /above) ... concert picture by Koen Caspeele (right / below) 26th International Guitar-Festival Iserlohn 2017 30 years without my last public performance, the wondrous Qianli Lyu a.k.a. Nicole gently persuaded me to perform then and as Duo partner together with her in the final concert of the 26th International Guitar-Festival Iserlohn 2017.PolityServices as a member of the GeoJSON polity (@Github). Together, we transformed the well-proven GeoJSON polity standard into an IETF RFC via the IETF Geographic JSON Working Group on the simplification of the liaison between applications through optimal unstipulated and geographic data formats and resulting 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 well-nigh 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: 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 typecasting of individual whirligig segments to the selected parameters - the so-called "quality pie"; a maximum number of 16 variegated 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 worldwide origin. The individual whirligig segments have the same size (spanned wile 360° divided by number of selected quality parameters). The representation of individual segment sizes is not interdependent, thus guaranteeing the independence of the variegated quality parameters from each other, which leads to the pursuit advantages: Independent representation of individual quality parameters. Segment sizes are unswayable by the number of selected parameters and are identical. Segment size (radius) is a measure for the quality regarding this parameter. A concentric whirligig virtually the origin is specified (1/√2) which represents a minimum quality measure; falling unelevated this segment size (radius) indicates a non-compliance with this limit value. By ways of a suitable colour selection results lying within the tolerance or transgressing the limit values can be hands visualized. This online using of P.505 can help you to produce upper 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 moreover for benchmarking or for test events. Source: “QualityPie plot web front-end, Version: 2.0.0, Last update: 2012-05-29” Disruptive transpiration in Python: Python - “Order is now Key”Slides of PyCologne Talk 2017Starting with version 3.6 keyword arguments and keys handed over to the seated dict preserve the insert order. I put together a micro booklet, and held a short talk (slides) on this topic for PyCologne, at Chaos Computer Club, August 09, 2017 - just to help spread the word. Unlearning facts that we did not like in the first place is surprisingly hard, isn't it? And now: In a mail to the python-dev list, Guido van Rossum declared: Make it so. "Dict keeps insertion order" is the ruling. Thanks! So, the version 3.6 CPython side-effect of dict insertion ordering is now rhadamanthine part of the language spec (and not anymore only an implementation detail). That mail thread moreover surfaced some distinguishing diamond goals for collections.OrderedDict as reminded by Raymond Hettinger during discussion. Standards @OASIS OASIS Technical Advisory Board DSS-X, OData, and SARIF. I am a member of the OASIS Technical Advisory Board (TAB). Three technical committees at “Organization for the Advancement of Structured Information Standards” (OASIS) withstand with me as officer. SARIF - “StaticWringerResults Interchange Format”StaticWringerResults Interchange Format Draft (... as unsalaried by Microsoft Corporation)Members of the OASIS SARIF TC kindly asked me to facilitate the merchantry of the group by serving as secretary. This committee - inaugurated on September 06, 2017 - defines “a standard output format for static wringer tools that will make it feasible for developers and teams to view, understand, interact with, and manage the results produced by all the tools that they use. The standardized output format will support team of the results of a variety of static wringer tools. The diamond goal is to comprehensively capture the range of data produced by wontedly used static wringer tools, and to capture information useful for assessing a project's compliance with corporate policy or conformance to certification standards.”. I had the pleasure to requite a short lightning talk to the Cologne C++ Users Group: OASIS SARIF TC - Defining a standard output format for static wringer tools. DSS-X - “Digital Signature Services eXtended”Together with Andreas Kühne we are the Co-Chairs of the OASIS DSS-X Technical Committee (TC) to help “advancing digital signature services standards” currently targeting version 2 which offers support in XML and JSON. OData - “Open Data Protocol”I support “simplifying data sharing wideness disparate applications in enterprise, cloud, and mobile devices” by serving as secretary to the OASIS OData TC since it's insemination in 2012. CSAF - “Common Security Advisory Framework”Articles: * “ICASI Transfers Development ... to OASIS”* “OASIS Advances Standard ...”* “OASIS Awards 2017UnshutStandards Cup ...”I unsalaried to “evolving theWorldwideVulnerability Reporting Framework (CVRF) specification to standardize existing practice in formulation and use of structured machine-readable vulnerability-related advisories within a newWorldwideSecurity Advisory Framework” by serving as secretary (until February 2018) to the OASIS CSAF TC and editor of the “CSAFWorldwideVulnerability Reporting Framework (CVRF) Version 1.2” Committee Specification Draft 01. MQTT - “Message Queuing Telemetry Transport” In wing I unsalaried 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 liaison in M2M/IoT contexts where a small lawmaking footprint is required and/or network bandwidth is at a premium.” Recent publications of the Committees OASIS CSDAndreas Kuehne and Stefan Hagen, “Digital Signature Service Core Protocols, Elements, and Bindings Version 2.0” Committee Specification Draft 01 / Public Review Draft 01, 29 August 2018: (HTML, PDF). OASIS CSDLaurence J. Golding and Michael Fanning, “StaticWringerResults Interchange Format (SARIF) Version 2.0” Committee Specification Draft 01 / Public Review Draft 01, 15 June 2018: (HTML, PDF). OASIS CSAndrew Banks, Ed Briggs, Ken Borgendale, and Rahul Gupta, “MQTT Version 5.0” Committee Specification 02, 15 May 2018: ( HTML, PDF). OASIS Committee NoteAndrew Banks, Ed Briggs, Ken Borgendale and Rahul Gupta, “MQTT Handling of Disallowed UnicodeLawmakingPoints Version 1.0” OASIS Committee Note 01, 19 April 2018: (HTML, PDF). OASIS CSMike Pizzo, Ralf Handl, and Martin Zurmuehl, “OData Version 4.01. Part 1: Protocol” Committee Specification 01, 30 January 2018: ( HTML, PDF). OASIS CSMike Pizzo, Ralf Handl, and Martin Zurmuehl, “OData Version 4.01. Part 2: URL Conventions” Committee Specification 01, 30 January 2018: (HTML, PDF, ABNF Grammar and tests). OASIS CSMike Pizzo, Ralf Handl, and Martin Zurmuehl, “ODataWorldwideSchema Definition Language (CSDL) XML Representation Version 4.01” Committee Specification 01, 30 January 2018, 16 November 2017: (HTML, PDF, and XML Schemas). OASIS CSMichael Pizzo, Ralf Handl, and Martin Zurmuehl, “ODataWorldwideSchema Definition Language (CSDL) JSON Representation Version 4.01” Committee Specification 01, 30 January 2018: (HTML, PDF, and JSON Schemas). OASIS CSMichael Pizzo, Ralf Handl, and Mark Biamonte, “OData JSON Format Version 4.01” Committee Specification 01, 30 January 2018: (HTML, PDF). STD 90/RFC 8259T. Bray, Ed., “The JavaScript Object Notation (JSON) Data Interchange Format” STD 90 / RFC 8259, December 2017: (TEXT, HTML, PDF). OASIS CSStefan Hagen, “CSAFWorldwideVulnerability Reporting Framework (CVRF) Version 1.2”, Committee Specification 01, 13 September 2017: (HTML, PDF). OASIS Committee Note... start reading here ;-)Mike Pizzo, Ralf Handl, Stefan Hagen and Martin Zurmuehl, “What’s New in OData Version 4.01” OASIS Committee Note 01, 08 Juni 2017: (HTML, PDF). RFC 8142Sean Gillies, “GeoJSON Text Sequences”, RFC 8142, April 2017: (HTML, PDF). Ernst Jan van Nigtevecht and Frank Cornelis, “DSS Extension for Local Signature Computation Version 1.0”, Committee Specification 02, 06 March 2017: (HTML, PDF). ISO Standard (inc. Appr. Errata)International Standard ISO/IEC 20802-1:2016(E), “Information technology —Unshutdata protocol (OData) v4.0 - Part 1: Core” First Edition, 15 December 2016: (zip compressed PDF). ISO Standard (inc. Appr. Errata)International Standard ISO/IEC 20802-2:2016(E), “Information technology —Unshutdata protocol (OData) v4.0 - Part 2: OData JSON Format” First Edition, 15 December 2016: (zip compressed PDF). Ralf Handl, Hubert Heijkers, Michael Pizzo, and Martin Zurmuehl, “OData to OpenAPI Mapping Version 1.0” Committee Note Draft 01 / Public Review Draft 01, 15 December 2016: (HTML, PDF). Michael Pizzo, Ralf Handl, and Ram Jeyaraman, “OData Vocabularies Version 4.0” Committee Specification Draft 01 / Public Review Draft 01, 08 December 2015: (HTML, 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:WorldwideSchema 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 DataTeamVersion 4.0” Committee Specification 02, 04 November 2015: (HTML, PDF, ABNF Grammar, and Vocabularies). 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). 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:WorldwideSchema 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). OASIS Committee Note... start reading here ;-)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 zippy 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).
