PLAST and IVAN should have a lot in common, see below the table.
Features
|
|
|
|
|
Purpose / Vision
|
Connecting professionals working on "socio-technological-economic-environmental systems"
|
Connecting People by Connecting Their Knowledge
|
Connecting people by connecting their practice and their thinking models. |
|
Mission
|
Development of framework and language for the building of an ecosystem of open source tools and methodologies that can help decode and encode patterns |
Right Information to Right Person at Right Time
|
The right information accessible to the right person at the right time;. |
|
Objectives
|
Develop a base infrastructure so that
- work can start with minimal set up / work / learning curve, and
- to get people / communities to engage, and
- a set of structuring principles so that things can be reconfigured and structured along the way, and so that
- the project can scale
|
Building of the unified virtual collective mental space
|
Connecting Practioners wherever they are So we can minimize "reinventing the wheel." |
|
| Implementation |
TBA
|
LikeInMind |
LikeInMind as a hub for Research and active changemakers. . Transmedia as the way to surface appropriate resources. |
|
| Taregeting |
Professional / occupational interest in developing their own projects and practice |
Anyone interested in
- expertise exchange, i.e., in
- finding expertise for his projects and
- being found for participating in projects of his interest
- finding particular information/ solution in the time frame close to theoretical limit (2-3 seconds)
|
Everyone engaged in change making. |
|
| Special requirements / education |
PLAST and fourth generation pattern languages |
No special requirements:
Basic knowledge of word processing and Internet browsing
|
The only requirement is fluent use of any platform on the Internet. |
|
| RDF |
Required?
|
IVAN is designed to be used by people with no special knowledge of any semantic tools and tricks. Knowledge of MS Word and a browser is sufficient to participate at full capacity.
As RDF was not captured at researchers' self-reflection of their cognition, it is thought of being "a foreign body" at human mental activities. Usage of RDF and metadata therefore is believed being counterproductive by "average participants": RDF and Metadata at LikeInMind
|
RDF is a platform dependent on the users choice. Specialization and integration is the approach. Tacit knowledge of diverse people to accessible explicit knowledge. |
|
| Fragmentation of Conceptual Space |
Fragmented between
- wiki,
- semantic database,
- discussion space (Facebook?)
- Kumu?
- Slack community
- Github community
- Debategraph map
|
Single environment: LikeInMind with integrated real-time collaboration tools |
A single LikeinMind extending it's unique value nested in Internet ecosystems. LM is a place of persistence so others can easily follow the thinking and progress. |
|
| Semantic meta-layers connecting fragmented resources |
|
Unified Conceptual Space
( Including a Layered approach of concepts - territories - actors ?) - Esteban
|
Using the nemetics code as a translation device, supporting and enriching native languages. |
|
| Mechanisms of detection of semantic match ("overlap") |
|
Tag Cloud around Sense Domains within a single Unified Conceptual Space |
Platform agnostic driven by user internet. |
|
https://en.wikipedia.org/wiki/Pattern_language
Aggregation in an associative network ("pattern language")
A pattern language, as thought by Alexander, contains links from one pattern to another, so when trying to apply one pattern in a project, a designer is pushed to other patterns that are considered helpful in its context.
In Alexander's book, such links are collected in the "references" part, and echoed in the linked pattern's "context" part - thus the overall structure is a directed graph. A pattern that is linked to in the "references" usually addresses a problem of lower scale, that is suggested as a part of the higher-scale problem. For instance, the "PUBLIC OUTDOOR ROOM" pattern has a reference to "STAIR SEATS".
Even without the pattern description, these links, along with meaningful names, carry a message: When building a place outside where people can spend time ("PUBLIC OUTDOOR ROOM"), consider to surround it by stairs where people can sit ("STAIR SEATS"). If you are planning an office ("WORKSHOPS AND OFFICES"), consider to arrange workspaces in small groups ("SMALL WORKING GROUPS"). Alexander argues that the connections in the network can be considered even more meaningful than the text of the patterns themselves.
The links in Alexander's book clearly result in a hierarchic network. Alexander draws a parallel to the hierarchy of a grammar - that is one argument for him to speak of a pattern language.
The idea of linking is generally accepted among pattern authors, though the semantic rationale behind the links may vary. Some authors, however, like Gamma et al. in Design Patterns, make only little use of pattern linking - possibly because it did not make that much sense for their collection of patterns. In such a case we would speak of a pattern catalogue rather than a pattern language.[3]
Usage
Alexander encouraged people who used his system to expand his language with patterns of their own. In order to enable this, his books do not focus strictly on architecture or civil engineering; he also explains the general method of pattern languages. The original concept for the book _A Pattern Language_ was that it would be published in the form of a 3-ring binder, so that pages could easily be added later; this proved impractical in publishing.[4] The pattern language approach has been used to document expertise in diverse fields. Some examples are architectural patterns, computer science patterns, human computer interaction patterns, educational patterns, social action patterns, and group facilitation patterns. The pattern language approach has also been recommended as a way to promote civic intelligence by helping to coordinate actions for diverse people and communities who are working together on significant shared problems (see [5] for additional discussion of motivation and rationale as well as examples and experiments). Alexander's specifications for using pattern languages as well as creating new ones remain influential, and his books are referenced for style by experts in unrelated fields.
It is important to note that notations such as UML or the flowchart symbol collection are not pattern languages. They could more closely be compared to an alphabet: their symbols could be used to document a pattern language, but they are not a language by themselves. A recipe or other sequential set of steps to be followed, with only one correct path from start to finish, is also not a pattern language. However, the process of designing a new recipe might benefit from the use of a pattern language.
Simple example of a pattern
Name: ChocolateChipRatio
Context: You are baking chocolate chip cookies in small batches for family and friends
Consider these patterns first: SugarRatio, FlourRatio, EggRatio
Problem: Determine the optimum ratio of chocolate chips to cookie dough
Solution: Observe that most people consider chocolate to be the best part of the chocolate chip cookie. Also observe that too much chocolate may prevent the cookie from holding together, decreasing its appeal. Since you are cooking in small batches, cost is not a consideration. Therefore, use the maximum amount of chocolate chips that results in a really sturdy cookie.
Consider next: NutRatio or CookingTime or FreezingMethod
Comments (0)
You don't have permission to comment on this page.