Glossary - sgml/signature GitHub Wiki

Values are raw data. Times, dates, money, tuples, tags, URLs, files, email addresses, strings, arrays, numbers, coordinate pairs, and base64 encoded strings are values.

Values and words are grouped together in blocks.

A variable can be used to hold any type of value. Variables only have meaning within the context where they are defined. A context can span the entire program or be restricted to a particular block, object, or function.

An object is a group of variables which have values in a specific context. Objects are used for managing data structures which have more complex behavior. For instance, a bank account can benefit from using an object to specify its attributes and functions

A function is a block which has local variables that are given new values each time the block is evaluated. The local variables are the arguments of the function. Functions can be created in several ways.

A message is simply a file of text that is sent from one place to another.

A bridge is a way to connect two Ethernet segments together in a protocol independent way. Packets are forwarded based on Ethernet address, rather than IP address (like a router). Since forwarding is done at Layer 2, all protocols can go transparently through a bridge

Big O is an estimate of the worst case performance of a function assuming the algorithm will perform the maximum number of iterations.

Dialects are blocks that carry condensed meaning through the use of a different grammar (ordering) of values and words. Dialect require a parser to translate them into words and values. Dialects are usually unique and well-suited to the problems they are designed to solve. For instance, the list of arguments to a function is a dialect.

Photogrammetry is also commonly employed in collision engineering, especially with automobiles. When litigation for accidents occurs and engineers need to determine the exact deformation present in the vehicle, it is common for several years to have passed and the only evidence that remains is accident scene photographs taken by the police. Photogrammetry is used to determine how much the car in question was deformed, which relates to the amount of energy required to produce that deformation. The energy can then be used to determine important information about the crash (such as the velocity at time of impact).

Two-way data bindings led to cascading updates, where changing one object led to another object changing, which could also trigger more updates. As applications grew, these cascading updates made it very difficult to predict what would change as the result of one user interaction. When updates can only change data within a single round, the system as a whole becomes more predictable.

The state tree is a living tree. The tree consists of mutable, but strictly protected objects enriched with runtime type information. In other words, each tree has a shape (type information) and state (data). From this living tree, immutable, structurally shared, snapshots are automatically generated. By using the type information available, snapshots can be converted to living trees, and vice versa, with zero effort. Because of this, time travelling is supported out of the box, and tools like HMR are trivial to support

The store contains all of the data for records loaded from the server. The only way to change the state inside it is to dispatch an action on it. A dispatch is forbidden while stores are handling the action and emitting updates. Stores accept updates and reconcile them as appropriate, rather than depending on something external (like custom events) to update its data in a consistent way. Nothing outside the store has any insight into how it manages the data for its domain, helping to keep a clear separation of concerns.

An action commits mutations to the store. By committing mutations, a plugin can be used to sync a data source to the store. For example, to sync a websocket data source to the store, commit a mutation from the plugin to the store

Subscribe adds a change listener. You can subscribe to store mutations to know when the state tree has been changed, or store actions to know when an action is dispatched.

A computed property is a cached, trackable value outside of the store. By default the getter will only be called once and the result will be cached. You can specify various properties that your computed property depends on. This will force the cached result to be cleared if the dependencies are modified, and lazily recomputed the next time something asks for it. If a computed property is not in use by some reaction, computed expressions will be evaluated lazily; each time their value is requested (so they just act as normal property). Computed values will only track their dependencies if they are observed. It is possible to provide a setter for a computed property as well. A setter should always invoke an action.

Actions are anything that modify the state. An action is required to modify observables and can run asynchronously and have side effects.

Watchers are useful when you want to perform asynchronous or expensive operations in response to changing data. A watch allows us to perform an asynchronous operation (accessing an API), limit how often we perform that operation, and set intermediary states until we get a final answer. None of that would be possible with a computed property.

Getters are cached, computed properties that can be shared. You can also pass arguments to getters by returning a function. This is particularly useful when you want to query an array in the store.

While it may seem as though the companies in the "leaders" category are always the best bet, Gartner advises users to examine all quadrants, since businesses in every category have their own unique strengths and weaknesses that should be taken into consideration.

Magic Quadrants can be a useful instrument for companies who wish to analyze their competition. Magic Quadrants gives a synopses of a market's top businesses, displaying their strengths and weaknesses. Competing companies can then use that information to improve their own business in areas where others are vulnerable, giving them a unique advantage in the market.

Ability to Execute

Product or Service:

Goods and services offered by the company that compete in the defined market. This includes current product or service capabilities, quality, feature sets, skills, and others.

Overall Viability:

Viability includes an assessment of the overall financial health of the organization, the likelihood of the individual business to continue investing resources in product development, and the financial means to advance the portfolio of products.

Sales Execution & Pricing:

The company’s capabilities in pre-sales activities and the structures that supports them. This includes deal management, pricing and negotiation, pre-sales support and the overall effectiveness of the sales channel(s).

Market Responsiveness and Track Record:

Ability to respond, change direction, be flexible and achieve competitive success as opportunities develop, competitors change, customer needs evolve and market & economic dynamics change.

Marketing Execution:

Often difficult to quantify, marketing execution is the clarity, quality, creativity and efficacy of programs designed to deliver the organization's message. It’s the ability to influence the market, promote the brand and business, increase awareness of the products, and establish a positive identification with the product, brand and organization in the minds of buyers, analysts, stake/shareholders and competitors. This mind share is driven by a combination of publicity, advertising, promotional efforts, thought leadership, word-of-mouth and sales activities.

Customer Experience:

Relationships, products and service programs that enable clients to be successful with the products evaluated. Specifically, this includes the ways customers receive technical support or account support. This can also include ancillary tools, customer support programs, availability of user groups, service-level agreements, and others.

Operations:

The ability of the organization to meet its goals and commitments. Factors include the quality of the organizational structure including skills, experiences, programs, systems and other vehicles that enable the organization to operate effectively and efficiently on a long-term basis.

Completeness of Vision

Market Understanding:

Ability of the company to understand buyers' wants and needs and to translate those into highly-desired products and services. Companies that show the highest degree of vision, listen and seek to fully understand buyers' wants and needs, and as a result, shape and add value to their products and services.

Marketing Strategy:

A clear, differentiated set of messages that are consistently communicated throughout the organization and externalized through the web site, advertising, PR, customer programs, promotional efforts and positioning statements.

Sales Strategy:

A unique strategy for selling products that uses the appropriate network of direct and indirect sales, marketing, service and communication affiliates that extend the scope and depth of market reach, skills, expertise, technologies, services.

Product Strategy:

The company's approach to product development and delivery that emphasizes differentiation, functionality, methodology and feature set as they map to current and future requirements.

Business Model:

The soundness and logic of the company's fundamental, underlying business proposition.

Keywords

• Hulu: Teen

• Amazon: Included

• Netflix: 1999

• Max: Classic

• Kanopy: Rhyme

• Hoopla: Zero