YapyData

Abstract

Modern landscapes of information infrastructures are commonly designed and organized as stacks of runtime service environments. The technical architecture of the service stacks consists of a wide range of heterogenous landscapes of components frequently requiring adaptation and mediation. This requires frequently low-level stack access to communications data as well as persistently stored advanced data formats such as JSON, XML, and YAML, but also INI, and .properties files. The common mix of modern software landscapes with the integration of multiple apps in addition requires frequently the access to mixed syntaxes and their combined processing.

_images/systems-ids.png

Figure: Software Dependecy Layers zoom more…

The yapydata - Yet Another Pythoin Data - package provides mixed heterogeneous syntaxes of data structures, in-memory and/or from persistent sources. Therefore yapydata provides a collection of low-level modules supporting an abstract API decoupled from implementation details as well as syntactical differences. These are allocated within the software stack at the bare-level of the Python framework. See following section Blueprint for more details.

The package ‘YapyData’ is part of the set of packages of enumerations for efficient and fast operations of code variants for software and infrastructure stacks. For other stack layers refer to [machineids], [platformids], [pythonids], [resourceids], and [extensionids].

Refer also to the virtual package [enumerateit] for the overall IT stack enumeration.

Shortcuts

Application

Resources

Home

Online Documents

Runtime Repository

Downloads

Licenses

Product

Product Data

  • MISSION=The ‘yapydata provides miscellaneous low-level Python data access APIs.

  • AUTHOR=Arno-Can Uestuensoez

  • PROJECT=yapydata

  • COPYRIGHT=(C)2019 Arno-Can Uestuensoez

  • LICENSE=Artistic-License-2.0 + Forced-Fairplay-Constraints

  • VERSION=0.1.41

  • RELEASE=0.1.41

  • STATUS=Unknown

  • BUILDDATE=2019.12.18-12:49

profileinfoidx0 [xkcd] Support the OpenSource Authors

Modified Artistic License

The modified Artistic License is based on the ArtisticLicense2.0, but adds the amendmend of “Forced-Fairplay-Constraints” for peer-to-peer fairplay rules. The modification restricts, and even revokes the permission including the open source attribution in case of breaches, including the past.

License:ModifiedArtisticLicense2.0 = ArtisticLicense2.0 + Forced-Fairplay-Constraints
From Ingenieurbuero Arno-Can Uestuensoez
Name  ModifiedArtisticLicense2.0

This is perfectly allright, as you may refer to cases like the faith of Andreas Pavel [AndreasPavel], or even my own - UnifiedSessionsManager (C) 2008 Arno-Can Uestuensoez [UnifiedSessionsManager] - the first multivendor cloud management system, capable of distributed hybrid clouds including virtual desktops. The UnifiedSessionsManager was originally licensed as GPL3.

So the software is OpenSource as long as you comply to basic rules - else not.