This is a fundamental construct of your Information Supply Chains.
In today's version of LINQ, LINQsets represent nodes that share the same value and are called Value LINQsets.
Information Assets (outputs) at the end of the supply chain can hold an Output Value. As value cascades through the supply chain, elements which have the same value are grouped into Value LINQsets. When a new information output node appears as part of the Information Supply Chain, a new Value LINQset is created.
The LINQset boundary is defined by the Input and Output information nodes. These interface nodes join LINQsets together. The Output Information Node is always contained in the supplying LINQset.
LINQsets may be minimised, in which case the interface nodes "pop out" of the LINQset to ensure that the LINQ Information Supply Chain construct is maintained correctly.
Collapsing Value LINQsets is an important way to manage the level of detail shown by your LINQ sketch when sharing with people who may not have need to understand all of the detail of your sketch. Value LINQsets can contain a lot of information so minimising them ensures that diagrams remain understood by everyone:
An expanded LINQset showing information flow for financial management:
The same Value LINQset collapsed, hiding all of the detail:
The capability of the LINQset will develop over time. Value will not be the only "container" that you can use, you will eventually be able to group your own nodes into special sets that are important to you. With that will come better management tools which will allow you to create entire new sketches from LINQsets.
Neil Calvert
What is a LINQset?
This is a fundamental construct of your Information Supply Chains.
In today's version of LINQ, LINQsets represent nodes that share the same value and are called Value LINQsets.
Information Assets (outputs) at the end of the supply chain can hold an Output Value. As value cascades through the supply chain, elements which have the same value are grouped into Value LINQsets. When a new information output node appears as part of the Information Supply Chain, a new Value LINQset is created.
The LINQset boundary is defined by the Input and Output information nodes. These interface nodes join LINQsets together. The Output Information Node is always contained in the supplying LINQset.LINQsets may be minimised, in which case the interface nodes "pop out" of the LINQset to ensure that the LINQ Information Supply Chain construct is maintained correctly.
Collapsing Value LINQsets is an important way to manage the level of detail shown by your LINQ sketch when sharing with people who may not have need to understand all of the detail of your sketch. Value LINQsets can contain a lot of information so minimising them ensures that diagrams remain understood by everyone:An expanded LINQset showing information flow for financial management:
The same Value LINQset collapsed, hiding all of the detail:
The capability of the LINQset will develop over time. Value will not be the only "container" that you can use, you will eventually be able to group your own nodes into special sets that are important to you. With that will come better management tools which will allow you to create entire new sketches from LINQsets.