Information Architecture δMuse

Information Architecture [δMuse Comments/Notes, not edits/post]
               https://en.wikipedia.org/wiki/Information_architecture (caused the δMuse visit)

Information Architecture (IA)

Information Services (Analysis, Simulations, Production, Libraries, Relationships, Collaboration ...)
               NOTE:  Security Defined by Information Object Governance and Structured Linkages
Information Management (Administration, Maintenance, Registries, Aggregation, Governance ...)
               NOTE:  Virtual Security Defined by Owners, Stakeholders, Creators, Purposes, Threats ...
Platforms/Systems (Linkages, Exchanges, Warehouses, Distributions, Infrastructure ...)
               NOTE:  Physical Security Defined by Monitoring, Restrictions, Stealth (DarkNameNetworks) ...
               ••• [Ellipsis usage indicates nothing is close-ended a/o presciently unchangeable]

IMO:  IA requirements must address IS, IM, and P/S, while leaving IM and P/S security issues appropriately partitioned.  IS must contain and transfer IM created content and data security requirements, while P/S must securely transport content and data. 

 

Information Sharing Environments (ISE)

Information Services (IS) Harmony (ISH) W3C, ISO ... Activity Specifics and Standards compliance
               Human Usage Content specific (Documents, Pictures, Books, Music, Movies, Government, Engineering ...)
               Machine Usage Data specific (Bits, Bytes, Sensors, Measures, Variables, Algorithms, Manufacturing ...)
               •••
Information Management (IM) Harmony (IMH) W3C, ISO ... Object Specifics and Standards compliance
               Product Objects are "WhatIs" (Books, Applications, Documents ... discrete and explicit artifacts)
               Process Objects are "HowTo" (Organization, Operations, Maps ... discrete and implicit artifacts)
               •••
Platforms/Systems (P/S) Conventions (P/SC) W3C, ISO ... Infrastructure Specifics and Standards compliance
               Open Internet, Intranet, a/o Public systems have Default Access Allowed (DAA)
               Closed Enterprise, Internal a/o Private systems have Default Access Denied (DAD)
               •••
               NOTE:  P/SC Open or Closed is an IA consideration for DAA or DAD. 
                            P/SC does not relate/dictate IA hardware/software ... physical/virtual products selection.  
                            P/SC does require DAA or DAD configuration of products for IA and P/S functional purposes.

The Objective Purpose for Information Architecture (IA)

Information Sharing Environment (ISE), AKA: Information Collaboration Environment (ICE)
               NOTE:  IS, IM, P/S ... Informatics with W3C, ISO ... Standards compliance
                            does supports IA requirements for an ISE. 
               NOTE:  Ontology is Information Science Theory / Implicit.  
                             Informatics is Applied Information Science / Explicit. 
                             For Theory / Implicit there are always HoHa support (IOW: a Hypothetical Precursor). 
                             For Application / Explicit there are always supporting Facts (IOW: a Theoretical Precursor). 
               Why is this important?  Application of a theory with reproducible results is a fact, but
                                                          Application of a hypothesis is risky with no predictable results. 

The Objective Purpose for Information Sharing Environments (ISE)

               Information Derivatives Foundations (IDF) for Communities, Colleagues, Families ...
               NOTE:  Information leveraged post maker development ... sensor collection, analysis, metadata,
                            storage ... then requires structured discovery, suitable assessment, useful aggregation,
                            derivative packaging, distribution/delivery ... to create and edit derivative information in an ISE.
 

The Objective Purpose for Information Derivatives:  Mission, Information Use/Reuse/Recycle....