Creating an Elementary Code Base for the BASICS #23
babbltd-admin
announced in
Company Notes
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This note is supported by Note for Early Contributors i #20.
The purpose of the Basics System is to make essential business tools accessible to people of all ages and abilities, across the widest variety of devices and operating systems. Basics is a product name for the "Business Assistance System" which London Street is establishing and gradually opening up to the public. The foundation and main focus of Basic's codebase is mobile, with priority placed on the constraints and limits of rudimentary cellular phones and handheld devices. Their limited computing and rendering capabilities directly inform the architecting and coding for each part of the System. The real-world commitment driving the creation of Basics, against which additions and changes to the system are tested, is the Aggregate Electricity Requirement for sets of actions and daily use.
When physical testing is not feasible, a few general maxims shall guide the coding of the system and its applications. Below is a short initial list, subject to adjustment based on Team consensus.
These and others can be found in Maxims to Code By, in Team Discussions.
The code base will have many aspects, but its levels of operation can be boiled down to an initial list of 8:
Briefly, in the same order, these levels represent:
Why in the world USSD?
First, a snippet to define USSD:
Article about USSD (MMI and Application Modes)
Research into USSD continues in the Research Repo, under Technical References.
USSD + BASICS
USSD is relevant to the creation of BASICS because it represents so far, the most universal mode of access. USSD is not dependent on a data plan because it initiates direct connections to services via their telco. Handling a USSD session made to your service code is as easy as implementing a script on your web server that handles HTTP POST requests.
For Basics, the logical numbered menu system that USSD requires is internalized as a model for architecting and documenting the system and application menus. This immediately spills over into the syntax and naming conventions used to code Basics using several complimentary languages.
vCard Format Specification (2011)
https://www.rfc-editor.org/rfc/rfc6350
vCard Elements (2019)
https://www.iana.org/assignments/vcard-elements/vcard-elements.xhtml
xCard: vCard XML Representation (2011)
https://datatracker.ietf.org/doc/html/rfc6351
Standard for the Format of ARPA Network Text Messages (1977)
https://www.rfc-editor.org/rfc/rfc733
Internet Message Format (2008)
https://www.rfc-editor.org/rfc/rfc5322
Augmented BNF for Syntax Specifications (2008)
https://www.rfc-editor.org/rfc/rfc5234
Calendar Attributes for vCard and LDAP
https://www.rfc-editor.org/rfc/rfc2739
Beta Was this translation helpful? Give feedback.
All reactions