docs: remove export feature from documentation

Author: MathiasVDA

README.md

@@ -213,17 +213,18 @@ Contributions welcome! Please follow the project constitution (`.specify/memory/
 ## 🐛 Troubleshooting
 
 ### Plugin tab not showing
-- Ensure query type is **CONSTRUCT** (not SELECT/ASK/DESCRIBE)
+- Verify plugin is registered correctly
 - Check browser console for errors
 - Verify YASGUI version is ^4.0.0
 
 ### Empty visualization
-- Confirm CONSTRUCT query returns triples (check "Table" or "Response" tab)
-- Verify results have subject/predicate/object structure
+- Ensure query type is **CONSTRUCT** or **DESCRIBE**
+- Confirm query returns triples (check "Table" or "Response" tab)
+- Verify results have RDF structure
 
 ### Performance issues
 - Limit results to <1000 nodes for best performance
-- Disable physics after initial layout (automatic)
+- Disable physics after initial layout
 - Consider using LIMIT clause in SPARQL query
 
 For more help, see [Quickstart Guide - Troubleshooting](./specs/001-construct-graph-viz/quickstart.md#troubleshooting).

demo/index.html

@@ -116,7 +116,6 @@ <h2 onclick="toggleInstructions()">
         <li><strong>Navigate</strong>: Mouse wheel to zoom, drag background to pan, click "Zoom to Fit" button</li>
         <li><strong>Reorganize</strong>: Drag individual nodes to rearrange the layout</li>
         <li><strong>Inspect</strong>: Hover over nodes/edges to see full details (300ms delay)</li>
-        <li><strong>Export</strong>: Click "Export PNG" to save the current viewport as an image</li>
         <li><strong>Color coding</strong>: <span style="color: #c5c5c5ff">⬤ Grey</span> = literals, 
             <span style="color: #e15b13ff">⬤ Orange</span> = blank nodes, 
             <span style="color: #a6c8a6ff">⬤ Green</span> = rdf:type objects, 

specs/001-construct-graph-viz/checklists/requirements.md

@@ -35,14 +35,13 @@
 
 **Clarity Assessment**:
 - 5 user stories prioritized (P1-P5) with clear dependencies
-- 31 functional requirements organized by category (parsing, rendering, interaction, export, edge cases)
+- 31 functional requirements organized by category (parsing, rendering, interaction, edge cases)
 - 11 edge cases explicitly handled with defined behaviors
 - 8 success criteria all measurable and technology-agnostic
 - 8 assumptions documented for context
 
 **No Clarifications Needed**: Specification is complete with informed defaults applied:
 - Layout algorithm: Force-directed or hierarchical (standard graph viz approach)
-- Export format: PNG/SVG (industry standard image formats)
 - Performance target: 2 seconds for 1,000 nodes (aligned with constitution)
 - Color scheme: Grey/green/blue with semantic meaning (clear visual hierarchy)
 - Label truncation: ~50 chars for literals (reasonable reading length)

specs/001-construct-graph-viz/contracts/vis-network-integration.md

@@ -374,27 +374,6 @@ network.once('stabilizationIterationsDone', () => {
   network.setOptions({physics: {enabled: false}});
 });
 ```
-
-## Export Functionality
-
-```javascript
-// Get canvas element
-const canvas = network.canvas.frame.canvas;
-
-// Export as PNG
-canvas.toBlob(blob => {
-  const url = URL.createObjectURL(blob);
-  const link = document.createElement('a');
-  link.href = url;
-  link.download = 'graph.png';
-  link.click();
-  URL.revokeObjectURL(url);
-}, 'image/png');
-
-// Or get data URL
-const dataURL = canvas.toDataURL('image/png');
-```
-
 ## Performance Optimization
 
 ### Disable Physics After Layout

specs/001-construct-graph-viz/contracts/yasr-plugin-interface.md

@@ -233,50 +233,6 @@ getIcon() {
 
 **Side Effects**: None (creates new element each call)
 
-## Optional Methods
-
-### `download(filename)`
-
-**Signature**:
-```typescript
-download(filename: string): void
-```
-
-**Purpose**: Export visualization to file (triggered by YASR download button)
-
-**Contract**:
-- Should export visualization in suitable format (PNG, SVG)
-- `filename` is suggested name (may need extension)
-- Must handle case where visualization not yet rendered
-- Optional: YASR shows download button only if method exists
-
-**Example**:
-```javascript
-download(filename) {
-  if (!this.network) {
-    console.warn('No visualization to download');
-    return;
-  }
-  
-  // Export as PNG
-  const canvas = this.container.querySelector('canvas');
-  if (canvas) {
-    canvas.toBlob(blob => {
-      const url = URL.createObjectURL(blob);
-      const a = document.createElement('a');
-      a.href = url;
-      a.download = `${filename}.png`;
-      a.click();
-      URL.revokeObjectURL(url);
-    });
-  }
-}
-```
-
-**Return**: void
-
-**Side Effects**: Triggers browser download
-
 ## Data Access Patterns
 
 ### Accessing Query Results
@@ -362,14 +318,7 @@ try {
 │ - Create visualization              │
 │ - Append to resultsEl               │
 └─────────────────────────────────────┘
-          │
-          │ User clicks download button
-          ↓
-┌─────────────────────────────────────┐
-│ download(filename)                  │
-│ - Export visualization              │
-│ - Trigger browser download          │
-└─────────────────────────────────────┘
+
 ```
 
 ## Testing Contract Compliance

specs/001-construct-graph-viz/plan.md

@@ -7,9 +7,9 @@
 
 ## Summary
 
-**Primary Requirement**: Create a YASGUI plugin that visualizes SPARQL CONSTRUCT query results as interactive graphs with nodes (subjects/objects) and edges (predicates), supporting zoom, drag, tooltips, color coding by node type, and PNG image export.
+**Primary Requirement**: Create a YASGUI plugin that visualizes SPARQL CONSTRUCT query results as interactive graphs with nodes (subjects/objects) and edges (predicates), supporting zoom, drag, tooltips and color coding by node type.
 
-**Technical Approach**: Implement a YASR plugin class following the yasgui-geo pattern (constructor, canHandleResults, draw, getIcon methods) using vis-network v9.x for graph rendering. Parse RDF triples from bindings format, transform to vis-network DataSets with color-coded nodes (grey literals, green rdf:type objects, blue other URIs), apply prefix abbreviation, and leverage vis-network's built-in force-directed layout, interaction, and export capabilities. Build with esbuild to UMD format for `Yasgui.Yasr.registerPlugin()` registration.
+**Technical Approach**: Implement a YASR plugin class following the yasgui-geo pattern (constructor, canHandleResults, draw, getIcon methods) using vis-network v9.x for graph rendering. Parse RDF triples from bindings format, transform to vis-network DataSets with color-coded nodes (grey literals, green rdf:type objects, blue other URIs), apply prefix abbreviation, and leverage vis-network's built-in force-directed layout and interaction. Build with esbuild to UMD format for `Yasgui.Yasr.registerPlugin()` registration.
 
 ## Technical Context
 

specs/001-construct-graph-viz/quickstart.md

@@ -97,10 +97,6 @@ LIMIT 100
    - **Drag nodes**: Click and drag individual nodes
    - **Inspect**: Hover over nodes/edges to see tooltips
 
-### 3. Export Graph
-
-Click the download button (💾) in the YASR toolbar to export the graph as a PNG image.
-
 ## Example Queries
 
 ### Basic Graph (Entities and Relationships)
@@ -231,7 +227,7 @@ console.log(yasgui.getTab().yasr.results.getBindings());
 
 **Solution**:
 1. Limit query results (use `LIMIT 100` or `LIMIT 1000`)
-2. Wait for layout stabilization (physics disables automatically)
+2. Wait for layout stabilization
 3. If still slow, manually disable physics:
    ```javascript
    // In browser console
@@ -309,7 +305,6 @@ See detailed contracts:
 
 - **Issues**: https://github.com/Matdata-eu/yasgui-graph-plugin/issues
 - **Discussions**: https://github.com/Matdata-eu/yasgui-graph-plugin/discussions
-- **Email**: [email protected]
 
 ## License
 

specs/001-construct-graph-viz/research.md

@@ -9,7 +9,7 @@
 **Decision**: Use **vis-network** for graph visualization with YASR plugin architecture pattern from yasgui-geo example.
 
 **Key Findings**:
-- vis-network provides built-in force-directed layout, zoom/pan, drag nodes, and export capabilities
+- vis-network provides built-in force-directed layout, zoom/pan and drag nodes capabilities
 - YASR plugin pattern requires: constructor, canHandleResults(), draw(), getIcon(), priority, label
 - No additional layout libraries needed - vis-network handles all requirements
 - Browser compatibility excellent (ES2018+ with Canvas rendering)
@@ -32,7 +32,6 @@
 - **Built-in physics engine**: Force-directed and hierarchical layouts out of the box, no additional configuration
 - **Interaction model**: Native support for zoom (mouse wheel), pan (drag background), node dragging, tooltips (hover events)
 - **Performance**: Handles 1000+ nodes smoothly with physics stabilization optimization
-- **Export**: Built-in methods for canvas-to-image conversion (PNG/SVG via canvas API)
 - **API simplicity**: `Network(container, data, options)` - single constructor with straightforward data model
 - **Browser compatibility**: Canvas-based rendering, works on all modern browsers (Chrome, Firefox, Safari, Edge)
 - **Size**: ~500KB minified (~150KB gzipped) - reasonable for functionality provided
@@ -313,34 +312,7 @@ function applyPrefix(uri, prefixes) {
 
 **Decision**: Extract prefixes from YASR query context, apply to all URIs. Include common RDF/RDFS/XSD defaults. Truncate unprefixed URIs with ellipsis.
 
-### 6. Export Image Functionality
-
-**Question**: How to implement "save as image" for current viewport?
-
-**vis-network approach**:
-```javascript
-// Get canvas element from network
-const canvas = network.canvas.frame.canvas;
-
-// Export as PNG
-function exportPNG() {
-  canvas.toBlob(blob => {
-    const url = URL.createObjectURL(blob);
-    const a = document.createElement('a');
-    a.href = url;
-    a.download = 'graph-visualization.png';
-    a.click();
-    URL.revokeObjectURL(url);
-  });
-}
-
-// Export as SVG (requires dom-to-image library or manual SVG creation)
-// vis-network doesn't directly support SVG export, PNG is primary format
-```
-
-**Decision**: Implement PNG export using canvas.toBlob(). SVG export would require additional library (dom-to-image) - defer to future enhancement, PNG sufficient for success criteria.
-
-### 7. Performance Optimization
+### 6. Performance Optimization
 
 **Question**: How to meet <2s rendering target for 1000 nodes?
 
@@ -373,7 +345,7 @@ const options = {
 
 **Decision**: Use default physics settings with 200 iteration limit. Disable physics after stabilization to improve interaction performance. Monitor performance in testing phase.
 
-### 8. Responsive Layout
+### 7. Responsive Layout
 
 **Question**: How to ensure graph fills 100% of YASR container space?
 
@@ -461,11 +433,7 @@ setTimeout(() => network.fit(), 100);
 - Hover tooltips (vis-network hover events + custom overlay)
 - Show full URI/literal/datatype
 
-### Phase 5: Export (P5)
-- PNG export from canvas
-- Download trigger
-
-### Phase 6: Edge Cases & Polish
+### Phase 5: Edge Cases & Polish
 - Empty state handling
 - Self-loop rendering (vis-network supports)
 - Label truncation
@@ -477,7 +445,6 @@ setTimeout(() => network.fit(), 100);
 None - all critical technical unknowns resolved. Remaining questions are implementation details:
 - Exact hex color values (resolved: #808080, #00FF00, #0000FF)
 - Tooltip styling (CSS, standard approach)
-- Export button placement (within plugin container, consistent with YASR patterns)
 - Error messaging for unsupported results (empty state div with message)
 
 ## References

specs/001-construct-graph-viz/spec.md

@@ -3,13 +3,12 @@
 **Feature Branch**: `001-construct-graph-viz`  
 **Created**: 2025-12-05  
 **Status**: Draft  
-**Input**: User description: "Visualize SPARQL CONSTRUCT query results as interactive graphs with nodes (subjects/objects) and edges (predicates), supporting zoom, drag, tooltips, color coding, and image export"
+**Input**: User description: "Visualize SPARQL CONSTRUCT query results as interactive graphs with nodes (subjects/objects) and edges (predicates), supporting zoom, drag, tooltips and color coding"
 
 ## Clarifications
 
 ### Session 2025-12-06
 
-- Q: When a user exports the graph visualization as an image, what should be the exact scope of the export? → A: Export only the visible viewport content at current zoom/pan level (what user currently sees)
 - Q: What visual styling should be used for graph nodes to distinguish between different node types and content lengths? → A: All nodes use uniform shape (circle/ellipse) with fixed size, regardless of label length or type
 - Q: How should tooltips be triggered and displayed to balance information access with usability? → A: Hover only with 300ms delay before showing, auto-hide on mouse leave
 - Q: How should the plugin handle blank nodes (anonymous RDF nodes with no URI) that appear in CONSTRUCT results? → A: Display with generated label but use unique color (e.g., yellow) to distinguish from literals
@@ -84,22 +83,6 @@ While exploring the graph, the user wants to see detailed information about node
 
 ---
 
-### User Story 5 - Export Visualization (Priority: P5)
-
-After exploring and potentially adjusting the graph, the user wants to save the current view as an image for documentation, presentations, or reports. They should be able to export exactly what they see in the viewport.
-
-**Why this priority**: Essential for knowledge sharing and documentation, but only valuable after graph is rendered and explored (depends on P1, P2). Lowest priority as core functionality works without it.
-
-**Independent Test**: Render and navigate to a specific view, click export, and verify the downloaded image matches the current viewport appearance.
-
-**Acceptance Scenarios**:
-
-1. **Given** a rendered graph at any zoom/pan level, **When** the user clicks "save as image" control, **Then** the browser downloads a PNG/SVG file showing only the visible viewport content at current zoom/pan (not the entire graph)
-2. **Given** a graph with manually repositioned nodes, **When** the user exports the image, **Then** the exported image reflects the current node positions and zoom level exactly as displayed in viewport
-3. **Given** a graph is exported, **When** the user opens the image file, **Then** the image has sufficient resolution for readable labels and maintains aspect ratio of the viewport
-
----
-
 ### Edge Cases
 
 - **Empty results**: What happens when a CONSTRUCT query returns zero triples? → Display empty state message "No graph data to visualize"
@@ -163,20 +146,15 @@ After exploring and potentially adjusting the graph, the user wants to save the
 - **FR-025**: Plugin MUST display tooltip after 300ms hover delay over edges showing the full prefixed predicate URI
 - **FR-026**: Plugin MUST hide tooltips when cursor leaves element boundary (auto-hide on mouse leave)
 
-#### Export
-
-- **FR-027**: Plugin MUST provide "save as image" control that exports only the visible viewport content at current zoom/pan level as a downloadable image file
-- **FR-028**: Plugin MUST export image in PNG or SVG format with sufficient resolution for readable labels
-
 #### Edge Case Handling
 
-- **FR-029**: Plugin MUST display empty state message when CONSTRUCT query returns zero triples
-- **FR-030**: Plugin MUST handle self-referencing triples (subject equals object) by rendering loop edges
-- **FR-031**: Plugin MUST handle blank nodes by creating nodes with generated labels and yellow color
-- **FR-032**: Plugin MUST render multiple predicates between the same node pair as separate parallel edges with curved/offset paths
-- **FR-033**: Plugin MUST truncate very long URI labels with ellipsis while preserving full URI in tooltips
-- **FR-034**: Plugin MUST truncate literal labels exceeding ~50 characters while preserving full value in tooltips
-- **FR-035**: Plugin MUST de-duplicate identical triples (same subject, predicate, object) to avoid rendering duplicate edges
+- **FR-028**: Plugin MUST display empty state message when CONSTRUCT query returns zero triples
+- **FR-029**: Plugin MUST handle self-referencing triples (subject equals object) by rendering loop edges
+- **FR-030**: Plugin MUST handle blank nodes by creating nodes with generated labels and yellow color
+- **FR-031**: Plugin MUST render multiple predicates between the same node pair as separate parallel edges with curved/offset paths
+- **FR-032**: Plugin MUST truncate very long URI labels with ellipsis while preserving full URI in tooltips
+- **FR-033**: Plugin MUST truncate literal labels exceeding ~50 characters while preserving full value in tooltips
+- **FR-034**: Plugin MUST de-duplicate identical triples (same subject, predicate, object) to avoid rendering duplicate edges
 
 ### Key Entities
 
@@ -203,11 +181,10 @@ After exploring and potentially adjusting the graph, the user wants to save the
 - **SC-001**: Users can visualize CONSTRUCT query results as graphs within 2 seconds of receiving results (for graphs up to 1,000 nodes)
 - **SC-002**: Users can identify node types (literal vs. blank node vs. URI vs. type instance) through color coding without reading labels (grey/yellow/blue/green)
 - **SC-003**: Users can navigate graphs of any size by zooming and panning without performance degradation
-- **SC-004**: Users can export publication-ready images of graph visualizations with readable labels
-- **SC-005**: Users can reorganize graph layouts manually to improve understanding of relationships
-- **SC-006**: Users can access full URI details for any node or edge via hover tooltips
-- **SC-007**: Plugin maintains responsive layout across all YASR container sizes (from 320px mobile to 4K desktop)
-- **SC-008**: Graph rendering completes successfully for 95% of valid CONSTRUCT query results without errors or empty states (excluding intentionally empty results)
+- **SC-004**: Users can reorganize graph layouts manually to improve understanding of relationships
+- **SC-005**: Users can access full URI details for any node or edge via hover tooltips
+- **SC-006**: Plugin maintains responsive layout across all YASR container sizes (from 320px mobile to 4K desktop)
+- **SC-007**: Graph rendering completes successfully for 95% of valid CONSTRUCT query results without errors or empty states (excluding intentionally empty results)
 
 ## Assumptions
 
@@ -218,4 +195,3 @@ After exploring and potentially adjusting the graph, the user wants to save the
 - Modern browsers support Canvas or SVG rendering for graph visualization (covered by constitution's browser compatibility requirements)
 - Force-directed layout algorithms are acceptable for automatic node positioning (no specific layout algorithm mandated)
 - Graph visualizations do not require persistence - each query execution produces a fresh visualization
-- Export image resolution is suitable for screen viewing and standard print (no poster-size export required)