Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
about:guidelines [2026/04/08 15:19] – vso_vsoabout:guidelines [2026/04/29 14:18] (current) – vso_vso
Line 2: Line 2:
  
 <WRAP meta> <WRAP meta>
-version: 8.2+version: 8.4
 updated: 8 April 2026 updated: 8 April 2026
 status: published status: published
Line 8: Line 8:
  
 <WRAP intro> <WRAP intro>
-This guide covers the principles, process, and standards that apply to every topic page. Read it before drafting. For markup syntax and formatting examples, see the [[about:markup|Wiki markup]] reference.+This guide covers the principles, process, and standards that apply to every topic page. Please read this carefully before making any contributions to the wiki.
 </WRAP> </WRAP>
  
  
-===== Wiki principles =====+===== Main ideas =====
  
-These principles apply to every topic page. They are the shared standards the whole wiki is built on.+==== Wiki principles ==== 
 + 
 +These principles apply to how the wiki is developed and maintained.
  
 <WRAP tablecap> <WRAP tablecap>
-**Table 1.** Wiki principles and what they mean in practice.+**Table 1.** Wiki principles
 </WRAP> </WRAP>
  
 ^ Principle ^ What it means in practice ^ ^ Principle ^ What it means in practice ^
 | **Transparency** | All contributions, including AI-assisted work, must be documented and attributed. | | **Transparency** | All contributions, including AI-assisted work, must be documented and attributed. |
-| **Credibility** | Every factual claim requires a source. Prefer primary sources: original papers, official documents, standards. | +| **Credibility** | Every factual claim requires a source. Prefer primary sources, such as original papers, official documents, standards. | 
-| **Triangulation** | Every topic is developed from three perspectives — actors, technology, institutions — because no single discipline captures smart grid transitions on its own. | +| **Triangulation** | Every topic is developed from three perspectives (actors, technology, institutions). | 
-| **Scope** | State clearly whether a definition or claim is global, regional, or discipline-specific. Where it originates matters. | +| **Scope** | State clearly whether a definition or claim used is applied universally or is distinct to a specific context or discipline. | 
-| **Accessibility** | Write for all three audiences. Define technical terms on first use. |+| **Accessibility** | Write for all Wiki audiences. Define technical terms on first use. |
 | **Knowledge integration** | Build on ISGAN tacit knowledge and publications as a shared baseline. Connect to broader literature where it expands the ISGAN framing. | | **Knowledge integration** | Build on ISGAN tacit knowledge and publications as a shared baseline. Connect to broader literature where it expands the ISGAN framing. |
-| **Critical reflexivity** | Where emerging literature challenges the current ISGAN framing, acknowledge it. The wiki's value depends on intellectual honesty. | +| **Critical reflexivity** | Mention many emerging literature that might challenge the current ISGAN framing. | 
-| **Feasible effort** | Quality matters more than completeness at first publication. A well-grounded page that grows over time is better than one delayed indefinitely. | +| **Feasible effort** | Quality is an utmost priority. It is better to have a short but relevant definition than a lengthy but rough draft. | 
-| **Referencing** | Use APA 7th edition. Include a DOI or stable URL where available. Verify all sources before submitting. | +| **Referencing** | The wiki combines the use of APA 7th edition for how references are formatted with inline endnotes. Include a DOI or stable URL where available. Verify all sources before submitting. Check markup guide for how to format references so that they appear as endnotes | 
-| **Copyright** | For any image, confirm the licence permits use and include attribution and a source link. | +| **Copyright** | For any image, confirm the license permits its use and include attribution and a source link. |
- +
-===== The three perspectives =====+
  
-Smart grid transitions cannot be fully understood from any one disciplinary perspective. Engineering analysis reveals what is technically feasible. Institutional analysis explains what rules and incentives make certain options viable. The study of actors and practices shows who acts and how. Each approach illuminates something the others miss, and each carries specific blind spots.+==== The three perspectives ====
  
-Triangulation is a method from the social sciences for understanding real-world phenomena by combining multiple theoretical perspectives and methods. The aim is to compensate for the limitations of any single method and to strengthen the credibility of findings through convergence across different approaches.+Smart grid transitions cannot be fully understood from any one disciplinary perspective. For instance, while engineering as a field allows to focus on what is technically feasible, institutional analysis highlights how rules and incentives make certain options viable. Further, exploring the perspectives of various actors underlines their distinct visions, needs and practices. Each approach illuminates something the others might miss, and each does not provide a complete outlook on any given topic. One can therefore use triangulation of different perspectives to gain a better outlook on the realities of energy transitions.
  
-Using multiple perspectives in combination makes it possible to understand phenomena in a more differentiated way: to identify priorities based on a fuller picture, to spot where different framings are compatible and where they conflict, and to develop options that are robust across more than one frame of analysis.+Triangulation is a method from the social sciences for understanding real-world phenomena by combining multiple theoretical perspectives and methods. The aim is to compensate for the limitations of any single method and to strengthen the credibility of findings through convergence across different approaches. Using multiple perspectives in combination makes it possible to understand phenomena in a more differentiated way: to identify priorities based on a fuller picture, to spot where different framings are compatible and where they conflict, and to develop options that are robust and relevant from different viewpoints.
  
 <WRAP callout> <WRAP callout>
-A finding that holds across independent perspectives is more credible than one that depends on a single method or theory.+A finding that holds across different perspectives is more credible than one that depends on a single method or theory.
 </WRAP> </WRAP>
-{{:actor_institutions_technology_triangulation.jpg?600|Triangulation diagram}}+{{:0:oscardamen_perspective_overlay_traingulation.png?600|Triangulation diagram}}
  
-Every topic is explored from three perspectives. These are not separate sections to fill in independently; they are lenses that together give a fuller picture of how a smart grid concept operates in the real world. Where the perspectives interact, or where one uniquely exposes something the others miss, this should be made explicit in the text.+Every topic is explored from three perspectives. These are not separate sections to fill in independently; they are lenses that together give a fuller picture of how a smart grid concept operates in the real world. Where the perspectives interact, or where one uniquely exposes something the others miss, this should be made explicit in the text. The three perspectives also have some resemblance to how the wiki is structured, but this structuring works somewhat differently. While a topic might belong in the "Technologies & Infrastructure" category because of how it is commonly used, it still benefits from having three different perspectives filled out as other disciplines might have other interpretations.
  
 <WRAP perspectives> <WRAP perspectives>
 **Actors and stakeholders** **Actors and stakeholders**
  
-This perspective addresses the activities and practices of the multiple groups whose actions shape smart grid transitions.+This perspective addresses the activities, views, interests and practices of the multiple groups whose actions shape smart grid transitions.
  
-Market actors — energy suppliers, producers, aggregators, storage providers, and consumers at the grid edge — participate in markets for energy and capacity. Transmission and distribution grid operators, balancing parties, and the institutions that regulate them carry mandates to operate and invest in specific parts of the electricity system. National and local policy makers, regulatory bodies, civil society organisations, and citizens shape framework conditions through law-making and political decisions. Technology providers and research organisations are part of the innovation ecosystem and play an active role in transitions even when they are not direct market participants.+Actors such as energy suppliers, producers, aggregators, storage providers, and consumers at the grid edge participate in (regulated and or unregulated) markets for energy and capacity. Transmission and distribution grid operators, balancing parties, and the institutions that regulate them carry mandates to operate and invest in specific parts of the electricity system. National and local policy makers, regulatory bodies, civil society organisations, and citizens shape framework conditions through law-making and political decision making processes. Technology providers and research organisations are part of the innovation ecosystem and play an active role in transitions even when they are not direct market participants.
  
-Key disciplines: Microeconomics, behavioural economics, organisational studies, business administration.+Key disciplines: Energy economics, behavioural economics, organisational studies, business administration.
  
 **Technologies and infrastructure** **Technologies and infrastructure**
  
-This perspective addresses the technical components, systems, and infrastructures that make up the electricity system, and the ways they can be configured to fulfil system functions. It covers generation, transmission, distribution, and storage as functionalities of a cyber-physical system, including both physical infrastructure and the digital layer of data exchange, control systems, and communication protocols.+This perspective addresses the technical components, systems, and infrastructures that make up the electricity system, and the ways they can be configured to fulfil system functions. It covers generation, transmission, distribution, and storage as functionalities of a cyber-physical system, i.e. physical infrastructure and the digital layer of data exchange, control systems, and communication protocols.
  
-The technology perspective extends beyond hardware. Interoperability standards, data exchange interfaces, metering systems, and control architectures are all within scope, and often where the most consequential transitions are taking place.+Interoperability standards, data exchange interfaces, metering systems, and control architectures are all within scope of the technology perspective. In smart grid the most consequential transitions are taking place in the cyber-physical realm, beyond hardware.
  
 Key disciplines: Electrical engineering, informatics, systems engineering. Key disciplines: Electrical engineering, informatics, systems engineering.
Line 66: Line 66:
 **Institutional structures** **Institutional structures**
  
-This perspective addresses the rules, regulations, norms, and cognitive frameworks that govern the electricity system. Markets for power and energy, grid codes, regulatory frameworks for grid operation and balancing, and rules for energy communities and aggregation are all institutional arrangements that define what is possible and what is incentivised.+This perspective addresses what governs the electricity system. It includes rules, regulations, norms, and cognitive frameworks that are common to the actors and stakeholders in its operation as well as in its transformation. Markets for power and energy, grid codes, regulatory frameworks for grid operation and balancing, and rules for energy communities and aggregation are all institutional arrangements that define what is possible and what is incentivised.
  
-Understanding how open or resistant an institutional structure is to change is often as important as understanding the technical options available.+Understanding how open or resistant an institutional structure is to change is as important as understanding the technical options available.
  
-Key disciplines: Institutional and evolutionary economics, political science, sociology.+Key disciplines: Institutional and evolutionary economics, political science, sociology, law.
  
 </WRAP> </WRAP>
  
-===== Tone and voice ===== 
  
-Topics should read as though written by a knowledgeable colleague explaining something clearly. It should be direct and precise, with focus on building shared understanding.+===== Process =====
  
-**Language rules:** +==== Roles ====
-  * Use plain language. If a technical term is necessary, define it on first use. +
-  * Prefer active constructions: "Several countries have introduced regulatory sandboxes" rather than "Regulatory sandboxes have been established." +
-  * Prefer //can// and //could// over //should// when describing possibilities. The wiki describes what institutions do and what options exist. It does not prescribe what countries ought to do. +
-  * Avoid hollow evaluative phrases: "a fundamental shift", "a critical enabler", "plays an increasingly important role." State what changed and why it matters. +
-  * Avoid generic prose markers: "It is important to note that", "This section explores", "Moreover", "Furthermore." +
-  * Avoid unnecessary introductions: "In an era of increasing complexity", "Given the rapidly evolving landscape." +
-  * Vary sentence length for readability and flow; avoid overly long sentences. +
- +
-**Headings:** All section headings use sentence case. Write "Why this matters", not "Why This Matters". +
- +
-===== Roles =====+
  
 Wiki development is a co-creative process. Every topic has a small team. Wiki development is a co-creative process. Every topic has a small team.
Line 102: Line 90:
 | **Reviewer** | Provides at least one round of structured feedback. Critical comments must be addressed before the topic advances. | | **Reviewer** | Provides at least one round of structured feedback. Critical comments must be addressed before the topic advances. |
 | **WG7 Task Lead** | Coordinates the overall editorial process, the Quality Review Panel, and publication logistics. | | **WG7 Task Lead** | Coordinates the overall editorial process, the Quality Review Panel, and publication logistics. |
-| **Communications Working Group** | Handles upload, promotional activities, and coordinates publication logistics. | +| **Communications Working Group** | Promotional activities and fostering wiki uptake, creating a link to wiki on ISGAN website | 
-| **Quality Review Panel** | Expert reviewers from at least three countries, with at least one outside the EU. Provides structured feedback during Stage 2. |+| **Quality Review Panel** | Expert reviewers from different countries, with at least one outside the EU. Provides structured feedback during Stage 2. |
 | **Inter-working group meeting** | Endorses the shared definition. Endorsement is required before a topic is published and again if the shared definition is subsequently changed. | | **Inter-working group meeting** | Endorses the shared definition. Endorsement is required before a topic is published and again if the shared definition is subsequently changed. |
  
-===== Becoming a lead author =====+==== Becoming a lead author ====
  
 Lead authors are the core of the wiki and every topic needs one. Lead authors take responsibility for a topic from first draft to publication: organising input from co-authors, coordinating the review process, addressing comments, and keeping the topic current after it is published. Lead authors are the core of the wiki and every topic needs one. Lead authors take responsibility for a topic from first draft to publication: organising input from co-authors, coordinating the review process, addressing comments, and keeping the topic current after it is published.
Line 122: Line 110:
 **To propose a new topic:** See the [[about:newtopic|New topic]] guide. **To propose a new topic:** See the [[about:newtopic|New topic]] guide.
  
-===== Editorial process =====+==== Editorial process ====
  
 The process has three stages and three decision gates. Gate 1 is a lead author self-check before external review begins. Gate 2 is the substantive quality threshold before endorsement. The process has three stages and three decision gates. Gate 1 is a lead author self-check before external review begins. Gate 2 is the substantive quality threshold before endorsement.
  
 <WRAP callout> <WRAP callout>
-The inter-working group meeting endorses the shared definition only. All other content — perspectives, case studies, examples, references, distinctions — can be edited after publication without a new endorsement. A new inter-WG meeting is required only if the topic definition or specific shared definitions are altered. +The inter-working group meeting endorses the shared definition only. All other content (perspectives, case studies, examples, references, distinctions) can be edited after publication without a new endorsement. A new inter-WG meeting is required only if the topic definition or specific shared definitions are altered.
-</WRAP> +
- +
-<html> +
-<div style="margin: 1.4em 0;"> +
-<svg viewBox="0 0 780 160" xmlns="http://www.w3.org/2000/svg" style="width:100%;max-width:780px;display:block;font-family:inherit;"> +
-  <defs> +
-    <marker id="arr" markerWidth="7" markerHeight="7" refX="6" refY="3.5" orient="auto"> +
-      <polygon points="0 0, 7 3.5, 0 7" fill="#888"/> +
-    </marker> +
-  </defs> +
-  <rect x="10" y="30" width="108" height="44" rx="5" fill="#dbeafe" stroke="#93c5fd" stroke-width="1.5"/> +
-  <text x="64" y="49" text-anchor="middle" font-size="11" font-weight="600" fill="#1e40af">Stage 1</text> +
-  <text x="64" y="64" text-anchor="middle" font-size="9.5" fill="#1e40af">Content creation</text> +
-  <text x="64" y="90" text-anchor="middle" font-size="8.5" fill="#64748b">2–6 weeks · draft</text> +
-  <line x1="118" y1="52" x2="136" y2="52" stroke="#888" stroke-width="1.5" marker-end="url(#arr)"/> +
-  <polygon points="160,30 192,52 160,74 128,52" fill="#fef9c3" stroke="#fbbf24" stroke-width="1.5"/> +
-  <text x="160" y="49" text-anchor="middle" font-size="10" font-weight="600" fill="#92400e">Gate</text> +
-  <text x="160" y="62" text-anchor="middle" font-size="10" font-weight="600" fill="#92400e">1</text> +
-  <text x="160" y="90" text-anchor="middle" font-size="8.5" fill="#64748b">Lead author check</text> +
-  <line x1="192" y1="52" x2="210" y2="52" stroke="#888" stroke-width="1.5" marker-end="url(#arr)"/> +
-  <rect x="210" y="30" width="108" height="44" rx="5" fill="#dbeafe" stroke="#93c5fd" stroke-width="1.5"/> +
-  <text x="264" y="49" text-anchor="middle" font-size="11" font-weight="600" fill="#1e40af">Stage 2</text> +
-  <text x="264" y="64" text-anchor="middle" font-size="9.5" fill="#1e40af">Review</text> +
-  <text x="264" y="90" text-anchor="middle" font-size="8.5" fill="#64748b">4–8 weeks · in-review</text> +
-  <line x1="318" y1="52" x2="336" y2="52" stroke="#888" stroke-width="1.5" marker-end="url(#arr)"/> +
-  <polygon points="360,30 392,52 360,74 328,52" fill="#fef9c3" stroke="#fbbf24" stroke-width="1.5"/> +
-  <text x="360" y="49" text-anchor="middle" font-size="10" font-weight="600" fill="#92400e">Gate</text> +
-  <text x="360" y="62" text-anchor="middle" font-size="10" font-weight="600" fill="#92400e">2</text> +
-  <text x="360" y="90" text-anchor="middle" font-size="8.5" fill="#64748b">Quality review</text> +
-  <line x1="392" y1="52" x2="410" y2="52" stroke="#888" stroke-width="1.5" marker-end="url(#arr)"/> +
-  <rect x="410" y="30" width="108" height="44" rx="5" fill="#dbeafe" stroke="#93c5fd" stroke-width="1.5"/> +
-  <text x="464" y="49" text-anchor="middle" font-size="11" font-weight="600" fill="#1e40af">Stage 3</text> +
-  <text x="464" y="64" text-anchor="middle" font-size="9.5" fill="#1e40af">Awaiting endorsement</text> +
-  <text x="464" y="90" text-anchor="middle" font-size="8.5" fill="#64748b">WG schedule · under-approval</text> +
-  <line x1="518" y1="52" x2="536" y2="52" stroke="#888" stroke-width="1.5" marker-end="url(#arr)"/> +
-  <polygon points="560,30 592,52 560,74 528,52" fill="#fef9c3" stroke="#fbbf24" stroke-width="1.5"/> +
-  <text x="560" y="49" text-anchor="middle" font-size="10" font-weight="600" fill="#92400e">Gate</text> +
-  <text x="560" y="62" text-anchor="middle" font-size="10" font-weight="600" fill="#92400e">3</text> +
-  <text x="560" y="90" text-anchor="middle" font-size="8.5" fill="#64748b">Inter-WG endorsement</text> +
-  <line x1="592" y1="52" x2="610" y2="52" stroke="#888" stroke-width="1.5" marker-end="url(#arr)"/> +
-  <rect x="610" y="30" width="108" height="44" rx="5" fill="#dcfce7" stroke="#86efac" stroke-width="1.5"/> +
-  <text x="664" y="49" text-anchor="middle" font-size="11" font-weight="600" fill="#166534">Published</text> +
-  <text x="664" y="64" text-anchor="middle" font-size="9.5" fill="#166534">Live on wiki</text> +
-  <text x="664" y="90" text-anchor="middle" font-size="8.5" fill="#64748b">2–3 weeks · published</text> +
-  <path d="M 664,74 L 664,130 L 64,130 L 64,74" fill="none" stroke="#cbd5e1" stroke-width="1.2" stroke-dasharray="5,3" marker-end="url(#arr)"/> +
-  <text x="364" y="148" text-anchor="middle" font-size="8.5" fill="#94a3b8">Major revision returns to Stage 1</text> +
-</svg> +
-</div> +
-</html> +
- +
-<WRAP tablecap> +
-**Table 3.** Editorial process stages, gates, indicative durations, and status values.+
 </WRAP> </WRAP>
  
Line 196: Line 132:
  
 <WRAP checklist> <WRAP checklist>
-  * ☐ The topic template is used, including the shared definition, three perspective subsections, and section word limits.+  * ☐ The topic template is used, including the shared definition, three perspective subsections, and compliance with the word limits.
   * ☐ Every factual claim has a source. Geographical scope is stated. Technical terms are defined on first use.   * ☐ Every factual claim has a source. Geographical scope is stated. Technical terms are defined on first use.
   * ☐ Lead author and all co-authors are attributed in the metadata block.   * ☐ Lead author and all co-authors are attributed in the metadata block.
Line 230: Line 166:
 Milestone 3: Topic is ready for publication. Milestone 3: Topic is ready for publication.
  
-===== Sensitivity rating =====+==== Topic status ====
  
-Topics may be assigned sensitivity ratings, however how they should function is still to be decided. At the moment no sensitivity ratings are assigned.+Each topic carries a status visible on the start page and on the topic page. The lead author is responsible for keeping it current. Only topics with status ''published'', ''under-approval'', ''in-review'', or ''draft'' are counted as active topics.
  
-===== Versioning =====+<WRAP tablecap> 
 +**Table 6.** Topic status values, transitions, and gate anchors. 
 +</WRAP> 
 + 
 +^ Status ^ Meaning ^ Enters when ^ Exits when ^ 
 +| **Published** | Live and publicly visible. | Stage 4 upload is complete. | A major revision begins, returning the topic to ''draft''. | 
 +| **Under approval** | Quality review is complete; the topic is awaiting endorsement at an inter-WG meeting. | Gate 2 is passed. | The shared definition is endorsed at an inter-WG meeting. | 
 +| **In review** | Under editorial revision and quality panel review. Expert input is especially valuable at this stage. | Gate 1 is passed. | Gate 2 is passed. | 
 +| **Draft** | Actively being written or undergoing major revision. | Work begins, or a major version bump is made. | Gate 1 is passed. | 
 +| **Planned** | Content exists from an earlier wiki version but has not been updated to the current template and standards. | Old content is confirmed to exist. | Restructuring begins, moving the topic to ''draft''. | 
 +| **Backlog** | Topic identified; nothing written yet. | The topic is added to the registry. | Work begins, moving the topic to ''draft''. | 
 + 
 +==== Versioning ====
  
 Every topic page carries a version number. The version and status move together at defined triggers. Every topic page carries a version number. The version and status move together at defined triggers.
Line 254: Line 202:
 Start at version 1.0 on first publication. Update the version number and the updated date in the page metadata on every change. Use the optional topic notes section to record what changed between versions. Start at version 1.0 on first publication. Update the version number and the updated date in the page metadata on every change. Use the optional topic notes section to record what changed between versions.
  
-===== Topic page structure =====+==== Sensitivity rating ====
  
-Every topic page follows the same structure. Sections must appear in this order.+Topics may be assigned sensitivity ratings, however how they should function is still to be decided. At the moment no sensitivity ratings are assigned.
  
-<WRAP tablecap> +==== Comment system ====
-**Table 5.** Required sections for every topic page, in order. +
-</WRAP> +
- +
-^ # ^ Section ^ Purpose ^ +
-| 1 | Category badge | Identifies which of the five categories this topic belongs to. | +
-| 2 | Title | The topic name. | +
-| 3 | Metadata block | Records lead authors, contributors, reviewers, version, date, sensitivity, status, and AI use. Drives the status display and author attribution on the start page. | +
-| 4 | Intro panel | One paragraph defining the topic and situating it in smart grid transitions. Every sentence must be specific to this topic. | +
-| 4b | Insight block | A single plain-text sentence, 120–160 characters, no links or markup. Not visible on the topic page; feeds the topic card on the start page. | +
-| 5 | Why this matters | One to two paragraphs and one callout box explaining why the topic matters for smart grid transitions. | +
-| 6 | Shared definitions | The working definition, with an optional table for multi-dimensional concepts. | +
-| 7 | Perspectives | Three subsections (Actors and stakeholders, Technologies and infrastructure, Institutional structures), each with one paragraph and one to three case examples. | +
-| 8 | Distinctions and overlaps | Two to five entries clarifying what this topic is not, and where it borders adjacent concepts. | +
-| 9 | Related topics | Direct links to other topic pages using ''%%[[topics:slug|Title]]%%'' format. Not tags. | +
-| 10 | References | Full APA 7th edition, auto-generated from inline footnotes. | +
-| 11 | Topic notes | Editorial working notes, gap log, AI attribution, and verification record. Not published on the live wiki. | +
- +
-For markup syntax and code examples for each section, see the [[about:markup|Wiki markup]] reference. +
- +
-===== Topic status ===== +
- +
-Each topic carries a status visible on the start page and on the topic page. The lead author is responsible for keeping it current. Only topics with status ''published'', ''under-approval'', ''in-review'', or ''draft'' are counted as active topics. +
- +
-<WRAP tablecap> +
-**Table 6.** Topic status values, transitions, and gate anchors. +
-</WRAP> +
- +
-^ Status ^ Meaning ^ Enters when ^ Exits when ^ +
-| **Published** | Live and publicly visible. | Stage 4 upload is complete. | A major revision begins, returning the topic to ''draft''. | +
-| **Under approval** | Quality review is complete; the topic is awaiting endorsement at an inter-WG meeting. | Gate 2 is passed. | The shared definition is endorsed at an inter-WG meeting. | +
-| **In review** | Under editorial revision and quality panel review. Expert input is especially valuable at this stage. | Gate 1 is passed. | Gate 2 is passed. | +
-| **Draft** | Actively being written or undergoing major revision. | Work begins, or a major version bump is made. | Gate 1 is passed. | +
-| **Planned** | Content exists from an earlier wiki version but has not been updated to the current template and standards. | Old content is confirmed to exist. | Restructuring begins, moving the topic to ''draft''. | +
-| **Backlog** | Topic identified; nothing written yet. | The topic is added to the registry. | Work begins, moving the topic to ''draft''. | +
- +
-===== Comment system =====+
  
 Every topic page allows for comments from lead authors, contributors and reviewers within the main body of the text. Every topic page allows for comments from lead authors, contributors and reviewers within the main body of the text.
Line 313: Line 225:
   * Mark a passage for follow-up after a meeting   * Mark a passage for follow-up after a meeting
  
-===== AI use =====+ 
 +===== Writing guidelines ===== 
 + 
 +==== Language, tone and voice ==== 
 + 
 +Topics should read as though written by a knowledgeable colleague explaining 
 +something clearly. It should be direct and precise, with focus on building 
 +shared understanding. 
 + 
 +**Language rules:** 
 +  * Use UK English spelling throughout. 
 +  * Use plain language. If a technical term is necessary, define it on first use. 
 +  * Prefer active constructions: "Several countries have introduced regulatory sandboxes" rather than "Regulatory sandboxes have been established." 
 +  * Prefer can and could over should when describing possibilities. The wiki describes what is done and what options exist. It does not prescribe what countries ought to do. 
 +  * Avoid hollow evaluative phrases: "a fundamental shift", "a critical enabler", "plays an increasingly important role." State what changed and why it matters. 
 +  * Avoid generic prose markers: "It is important to note that", "This section explores", "Moreover", "Furthermore." 
 +  * Avoid unnecessary introductions: "In an era of increasing complexity", "Given the rapidly evolving landscape." 
 +  * Vary sentence length for readability and flow; avoid overly long sentences. 
 +  * All section headings use sentence case. Write "Why this matters", not "Why This Matters". 
 + 
 +==== Topic page structure ==== 
 + 
 +Every topic page follows the same structure. Sections must appear in this order. 
 + 
 +<WRAP tablecap> 
 +**Table 5.** Required sections for every topic page, in order. 
 +</WRAP> 
 + 
 +^ # ^ Section ^ Purpose ^ Word count ^ 
 +| 1 | Category badge | Identifies which of the five categories this topic belongs to. | — | 
 +| 2 | Title | The topic name. | — | 
 +| 3 | Metadata block | Records lead authors, contributors, reviewers, version, date, sensitivity, status, and AI use. Drives the status display and author attribution on the start page. | — | 
 +| 4 | Intro panel | One paragraph defining the topic and situating it in smart grid transitions. Every sentence must be specific to this topic. | 80–120 words | 
 +| 4b | Insight block | A single plain-text sentence, 120–160 characters, no links or markup. Not visible on the topic page; feeds the topic card on the start page. For backlog and planned topics, leave the block structurally present but empty. | 120–160 characters | 
 +| 5 | Why this matters | One to two paragraphs and one callout box explaining why the topic matters for smart grid transitions. | 150–250 words | 
 +| 6 | Shared definitions | The working definition, with an optional table for multi-dimensional concepts. | 80–150 words | 
 +| 7 | Perspectives | Three subsections (Actors and stakeholders, Technologies and infrastructure, Institutional structures), each with one paragraph and one to three case examples. | 120–200 words per subsection | 
 +| 8 | Distinctions and overlaps | Two to five entries clarifying what this topic is not, and where it borders adjacent concepts. | 30–60 words per entry | 
 +| 9 | Related topics | Direct links to other topic pages using ''%%[[topics:slug|Title]]%%'' format. 3–7 links, substantive connections only. Not tags. | — | 
 +| 10 | References | Auto-generated from inline DokuWiki footnotes placed throughout body text. No section heading required. | — | 
 +| 11 | Topic notes | Editorial working notes, gap log, AI attribution, and verification record. Not published on the live wiki. | — | 
 + 
 +For markup syntax and code examples for each section, see the [[about:markup|Wiki markup]] reference. 
 + 
 +==== AI use ====
  
 AI tools may be used in wiki development when helpful, but their use is not required or expected. Where AI is used, it can help reorganise source material into the template structure, improve sentence flow, reformat references, or convert approved documents into DokuWiki markup. AI tools may be used in wiki development when helpful, but their use is not required or expected. Where AI is used, it can help reorganise source material into the template structure, improve sentence flow, reformat references, or convert approved documents into DokuWiki markup.
Line 337: Line 293:
 <style> <style>
 .vh-entry { margin-bottom: 0.5em; border: 1px solid #ddd; border-radius: 4px; overflow: hidden; } .vh-entry { margin-bottom: 0.5em; border: 1px solid #ddd; border-radius: 4px; overflow: hidden; }
-.vh-entry summary { display: flex; justify-content: space-between; align-items: baseline; padding: 0.55em 1em; cursor: pointer; font-weight: bold; background: #f8f8f8; list-style: none; }+.vh-entry summary { display: flex; justify-content: space-between; align-items: baseline; padding: 0.55em 1em; cursor: pointer; background: #f8f8f8; list-style: none; font-weight: normal; }
 .vh-entry summary::-webkit-details-marker { display: none; } .vh-entry summary::-webkit-details-marker { display: none; }
-.vh-entry .vh-tag { font-weight: normal; color: #666; font-size: 0.9em; }+.vh-entry .vh-tag { color: #666; font-size: 0.9em; }
 .vh-entry .vh-body { padding: 0.8em 1em 0.9em; line-height: 1.65; } .vh-entry .vh-body { padding: 0.8em 1em 0.9em; line-height: 1.65; }
 .vh-entry .vh-body p { margin: 0 0 0.6em; } .vh-entry .vh-body p { margin: 0 0 0.6em; }
 .vh-entry .vh-body p:last-child { margin-bottom: 0; } .vh-entry .vh-body p:last-child { margin-bottom: 0; }
 </style> </style>
- 
 <details class="vh-entry"> <details class="vh-entry">
-  <summary>Version 8.2 &mdash; 8 April 2026 <span class="vh-tag">Table prose, TOC cleanup, stage-gate diagram, version history</span></summary> +<summary>Version 8.3 — 20 April 2026 <span class="vh-tag">Restructured into four parts; topic structure table updated</span></summary> 
-  <div class="vh-body"> +<div class="vh-body"> 
-    <p>Rewrote all table cells that previously used clipped, semicolon-separated fragments. The "What happens" column in Table 3 was the main case: each stage and gate now reads as a sentence. The same treatment was applied to Table 4 ("Process" column), Table 5 (metadata block, insight block, and topic notes entries), and Table 6 ("Enters when" and "Exits when" columns). The three perspectives subsections and gate checklists were demoted from level-3 headings to bold paragraph leads so they no longer appear in the table of contents. An SVG stage-gate diagram was added above Table 3. Version history section added with entries for all prior versions. Minor wording updates to tone and voice intro and becoming a lead author section carried forward from the author's edits.</p> +<p>Guide restructured into four parts: Main ideas, Process, Writing guidelines, and Version history. Wiki principles and The three perspectives moved to lead the document. Language, tone and voice, Topic page structure, and AI use consolidated into Writing guidelines. Topic page structure table updated: word counts added for all substantive sections, References description corrected to reflect inline footnote behaviour, Insight block note added for backlog and planned topics, Related topics link-count constraint (3–7) added. Markup reference link relocated from intro to end of Topic page structure section.</p> 
-  </div>+</div>
 </details> </details>
- 
 <details class="vh-entry"> <details class="vh-entry">
-  <summary>Version 8.1 &mdash; early April 2026 <span class="vh-tag">Details not recorded</span></summary> +<summary>Version 8.2 — 8 April 2026 <span class="vh-tag">Approval distinctions and version record added</span></summary> 
-  <div class="vh-body"> +<div class="vh-body"> 
-    <p>Revision notes for this version were not transferred to this record. See the editorial Teams folder for working notes from this period.</p> +<p>Distinctions between topic approval and further updates were added. Complete version history section now appears at the end of the document. Minor refinements were also made in tone and style</p> 
-  </div>+</div>
 </details> </details>
- 
 <details class="vh-entry"> <details class="vh-entry">
-  <summary>Version 7 &mdash; 17 March 2026 <span class="vh-tag">Alignment with Master Writing Guide; restored principles; terminology</span></summary> +<summary>Version 7 — 17 March 2026 <span class="vh-tag">Expanded tone and voice and clarified terminology</span></summary> 
-  <div class="vh-body"> +<div class="vh-body"> 
-    <p>A consolidation and alignment update produced on the same date as Version 6. Critical reflexivity was restored as a named Wiki Principle after being dropped in an earlier draft. The Knowledge integration principle was expanded to explicitly include tacit knowledge held across working groups. The major/minor revision distinction and the recommended Stage 1 duration (2–6 weeks) were reintroduced after having been removed. The Tone and voice section was added as a standalone section with guidance on register, sentence rhythm, and heading capitalisation. The high-level roles table was restored. The Gate 2 procedure for critical comments was clarified: disputes must be documented in writing and the reviewer informed before the topic can proceed. The content waves framing ("content will be delivered in successive waves") was added to the introduction. The knowledge valorisation benefit was restored to the community benefits list. Perspective order was aligned with Master Writing Guide 18.9 (Actors / Technologies / Institutional). Lead author terminology was aligned with Master Writing Guide 18.8. The AI attribution record format was aligned with Master Writing Guide 18.9.</p> +<p>Critical reflexivity returned as a listed principle, and the idea of knowledge integration was broadened to include tacit knowledge shared across teams. Sections on tone and voice were expanded, giving more detail on writing style. The procedure for addressing reviewer comments at Gate 2 was clarified. Updated terminology from "page owner" to "lead author"</p> 
-  </div>+</div>
 </details> </details>
- 
 <details class="vh-entry"> <details class="vh-entry">
-  <summary>Version 6 &mdash; 17 March 2026 <span class="vh-tag">Triangulation perspectives; AI use guidance; sensitivity rating; target groups</span></summary> +<summary>Version 6 — 17 March 2026 <span class="vh-tag">Expanded content, AI guidance, sensitivity, audience details</span></summary> 
-  <div class="vh-body"> +<div class="vh-body"> 
-    <p>A substantial expansion that added several major sections. The three triangulation perspectives were given full standalone descriptions covering scope, actor types, and key disciplines, replacing the earlier brief list. AI use guidance was formalised with a structured record format distinguishing stage, type, tool, and reviewer. A three-level sensitivity rating system was introduced as a working proposal pending formal confirmation. Detailed target group descriptions were added for ISGAN experts, policy makers, and researchers. A two-week post-publication review window was introduced as a standing feature of Stage 4. Gate 1 and Gate 2 checklists were expanded, with Gate 2 adding a substitution test for the intro panel and an explicit URL-verification requirement for all sources.</p> +<p>This version introduced several new sections. The three perspectives gained fuller descriptions, now covering their scope and main disciplines. Guidance on the appropriate use of AI tools was added with a consistent record format. A draft sensitivity rating system (three levels) appeared for the first time but was put to the side for further consideration. Audience descriptions were expanded to include policy makers, ISGAN experts, and researchers. The publication review period was also established here, along with updated Gate 1 and Gate 2 checklists with more clear review requirements and source verification steps.</p> 
-  </div>+</div>
 </details> </details>
- 
 <details class="vh-entry"> <details class="vh-entry">
-  <summary>Version 5 &mdash; 17 May 2025 <span class="vh-tag">Principles lightly edited; Gate 2 criteria updated</span></summary> +<summary>Version 5 — 17 May 2025 <span class="vh-tag">Minor edits to principles and review rules</span></summary> 
-  <div class="vh-body"> +<div class="vh-body"> 
-    <p>Minor update. Wiki principles were lightly edited for clarity and consistency. The Gate 2 quality review criteria were updated to require feedback from at least two ISGAN national experts beyond the ExCo panel, in addition to the existing ExCo delegate requirement. Stage descriptions were cleaned up editorially. No structural changes.</p> +<p>The update clarified the principles and refined quality review requirements. Gate 2 now explicitly calls for feedback from at least two national experts, in addition to the ExCo panel. Stage descriptions were also revised for consistency.</p> 
-  </div>+</div>
 </details> </details>
- 
 <details class="vh-entry"> <details class="vh-entry">
-  <summary>Version 4 &mdash; August 2024 <span class="vh-tag">Named principles; roles table; Stage 4; major/minor revision distinction</span></summary> +<summary>Version 4 — August 2024 <span class="vh-tag">Named principles, role table, publication stage, revision levels</span></summary> 
-  <div class="vh-body"> +<div class="vh-body"> 
-    <p>A substantial restructuring. The numbered rules format was replaced by ten named Wiki Principles, including new entries for Critical reflexivity, Knowledge integration, and Feasible effort. A roles section was introduced with an overview table distinguishing high-level wiki-wide roles from topic-level roles. Stage checklists were formalised at the end of each gate. Stage 4 (Publication and promotion) was added explicitly. The major/minor revision distinction was introduced with guidance on when each triggers a return to Stage 1. Stage 1 duration guidance (2–6 weeks) was added.</p> +<p>A major structural overhaul replaced the older numbered rules with ten named principles, such as Critical reflexivity and Feasible effort. A clear roles table was introduced, showing how wiki-wide responsibilities differ from topic-level tasks. Stage 4, covering publication and outreach, was added. This version also introduced the concept of major versus minor revisions, with guidance on how each affects the review stages.</p> 
-  </div>+</div>
 </details> </details>
- 
 <details class="vh-entry"> <details class="vh-entry">
-  <summary>Version 3 &mdash; August 2024 <span class="vh-tag">Purpose section; rules reorganised; tone and voice; AI reference note</span></summary> +<summary>Version 3 — August 2024 <span class="vh-tag">Purpose and audience, reorganized rules, tone section, AI note</span></summary> 
-  <div class="vh-body"> +<div class="vh-body"> 
-    <p>Added a purpose and target audience section at the front of the document. The nine numbered rules were reorganised into ten named categories without yet becoming the full named-principles format that arrived in Version 4. A brief AI reference note was added under Referencing. Tone and voice was introduced as a heading for the first time. A screenshot showing Teams-based registration was added to the technical access section.</p> +<p>The guide opened with a new purpose and audience section. The nine rules were reorganized under ten thematic headings, setting the stage for the later named-principles format. A short note was added on AI references, and a section on tone and voice appeared for the first time. A screenshot showing Teams registration was also included.</p> 
-  </div>+</div>
 </details> </details>
- 
 <details class="vh-entry"> <details class="vh-entry">
-  <summary>Version 2 &mdash; July 2024 <span class="vh-tag">Textual refinements; title updated</span></summary> +<summary>Version 2 — July 2024 <span class="vh-tag">Refined text and updated title</span></summary> 
-  <div class="vh-body"> +<div class="vh-body"> 
-    <p>Textual refinements to the rules and stage descriptions. The document was renamed from "Editorial Guide for the ISGAN online Wiki" to "ISGAN Smart Grids Transitions Wiki — Editorial Guide." The background framing was lightly revised. Structure, nine rules, technical access guide, and stage-gate process were otherwise unchanged from Version 1.</p> +<p>The text was lightly refined throughout, and the document's title was updated to "ISGAN Smart Grids Transitions Wiki — Editorial Guide."</p> 
-  </div>+</div>
 </details> </details>
- 
 <details class="vh-entry"> <details class="vh-entry">
-  <summary>Version 1 &mdash; February 2024 <span class="vh-tag">First draft</span></summary> +<summary>Version 1 — February 2024 <span class="vh-tag">Initial draft</span></summary> 
-  <div class="vh-body"> +<div class="vh-body"> 
-    <p>First complete draft, produced within WG7 during the initial wiki setup phase by Klaus Kubeczko and Max Gasser. The guide covered nine numbered rules (transparency and attribution, triangulation of perspectives, geographical scope, contentious terms and footnotes, cross-checking with IEEE and IEC glossaries, word limits, referencing in APA 7th edition, copyright for images, and page ownership), a technical access section with step-by-step instructions for logging in, adding pages, and subscribing to changes, and a stage-gate process with two stages and two gates. The three perspectives were present from the start as Institutions, Actors and Stakeholders, and Technology. DokuWiki technical instructions were included in the same document.</p> +<p>This first full draft, prepared during the initial wiki setup, introduced the stage-gate workflow and the original nine rules. It also offered technical guidance for logging in, adding pages, and managing changes. The three core perspectives on Institutions, Actors and Stakeholders, and Technology were taken up.</p> 
-  </div>+</div>
 </details> </details>
 </html> </html>