FluxPoint

From PatternSmithingAlliance

A FluxPoint provides a way for an individual or group to secure an authorative identifier for a static pattern (or aggregation of static patterns) [1] and:

• represent the evolving structure on the world wide web in multiple rendered formats depending on consumer [data]
• provide a common set of framework operations against the static pattern [behaviors]

This initial concept was nothing more than morphing together a few existing ideas that have developed over the last two decades. The endpoints idea was intended to take the web service endpoint concept and apply it toward static patterns at the service layer with all types of interesting convolutions of the usual infrastructure surrounding web services [2]. This first phase of thinking, which encompasses ‘releasing’ or publishing a static pattern, is still going to be part of the process (with some as yet undisclosed modifications to the way it is represented) — this notion of allowing a pattern’s representation to become static is enforced by the criteria that it:

• has an authorative and established identifier that gives it an identity
• has a physical location that hosts it [3]
• has a structure and set of behaviors that define it, otherwise it is neither active nor static

This last criterion, which defines whether the pattern [virtual] representation (not necessarily the underlying pattern itself) is static also defines whether it can be active introduces the notion of active pattern. In consciousness (the cognitive domain), a static pattern becomes active when cognition is actively operating with that pattern to produce transformations in the pattern itself or other patterns. If the sole purpose of the endpoints project was simply to reflect the products of consciousness as virtual representations, then endpoints would be a proper name; however, the purpose of static pattern engineering is to operate on and transform these patterns — in the transition states they are active patterns. With the tremendous potential of a global network, if the endpoint were designed to release the pattern in a way that allowed it to be activated by bidirectional information flow according to its orientation and exposure then there would be many opportunities for the pattern to become an active pattern (not just for consumer but for creator and aggregators). Thus, we are most interested in the flux through the endpoint — and the sole purpose of the endpoint is to serve as a FluxPoint.

[1] analogous to a domain name in concept but not at all in syntax

[2] for instance, web services are usually unique type definitions that usually delegate to a well-known data source while an endpoint represents a unique manifestation using a standard type definition with variable data sources (often other endpoints)

[3] in the first implementation, this will be a hosting location I will provide; however, the infrastructure will be designed from the bottom up that this location can vary for each endpoint