poml 0.0.7 → 0.0.8

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2b093fb2077a5a12052a817a3b71038b81c97892bd8ba888165bbbed56cf21d4
-  data.tar.gz: 46cb25b278be930f116c97b46263dead78057289f200274daee79320045b8984
+  metadata.gz: 70dc9fc51326dadbeaf4ac370e2d336d8c84dd588c3fd8fa5dccc81b78c30dc6
+  data.tar.gz: 5bcee8ab87e81a98104cfb85cd44f55f6993c1c9d389e905c71442d9d1db806e
 SHA512:
-  metadata.gz: 66b01f839ae216447b86d45c8cb49d016e569e3d42fc91bd82e777abdb4fab466644d4610756f4cedb1bdd4e6171f6e2c177b3773afd2ad5a08c4b9328e9c44f
-  data.tar.gz: 2f107a45b2ee752c6303b6cc64d385bb3c77aa345c9697eeb0942a4221c1984054d4bd256658358b6732d37b44e0ff70112e6d9b84c8b39a6c4392bb93c80938
+  metadata.gz: 80a0bcb96bc46410dc54865ca8a36465c8776a58bb47732525c9630900229187f62ed926e64502058f679643532e677c267de2192e83eb36fb27d682dc1918e8
+  data.tar.gz: 0e8a9b993696d736ef5fec917661bc11e1b593f0c0723823ad10a3f753eeea3c31f18bfecb41ad4479a3b1ee5206b2e314d2e683f75f5193d7b5f99df11a3bae

data/docs/tutorial/advanced/tool-registration.md

@@ -650,16 +650,16 @@ class SafeToolProcessor
       valid_tools = tools.select { |tool| valid_tool?(tool) }
       
       {
-        success: true,
-        tools: valid_tools,
-        invalid_count: tools.length - valid_tools.length
+        'success' => true,
+        'tools' => valid_tools,
+        'invalid_count' => tools.length - valid_tools.length
       }
       
     rescue StandardError => e
       {
-        success: false,
-        error: e.message,
-        tools: []
+        'success' => false,
+        'error' => e.message,
+        'tools' => []
       }
     end
   end
@@ -676,10 +676,10 @@ end
 
 # Usage
 result = SafeToolProcessor.process_tools(markup, context)
-if result[:success]
-  puts "Processed #{result[:tools].length} valid tools"
+if result['success']
+  puts "Processed #{result['tools'].length} valid tools"
 else
-  puts "Error: #{result[:error]}"
+  puts "Error: #{result['error']}"
 end
 ```
 

data/docs/tutorial/components/formatting.md

@@ -33,9 +33,10 @@ Text with **bold** and *italic* formatting.
 ```ruby
 markup = <<~POML
   <poml>
-    <h1>Main Title</h1>
-    <p>Text with <b>bold</b> and <i>italic</i> formatting.</p>
-    <output format="html"/>
+    <output format="html">
+      <h1>Main Title</h1>
+      <p>Text with <b>bold</b> and <i>italic</i> formatting.</p>
+    </output>
   </poml>
 POML
 
@@ -55,9 +56,10 @@ puts result['output']
 ```ruby
 markup = <<~POML
   <poml>
-    <h1>Main Title</h1>
-    <p>Text with <b>bold</b> and <i>italic</i> formatting.</p>
-    <output format="text"/>
+    <output format="text">
+      <h1>Main Title</h1>
+      <p>Text with <b>bold</b> and <i>italic</i> formatting.</p>
+    </output>
   </poml>
 POML
 
@@ -68,9 +70,7 @@ puts result['output']
 **Output:**
 
 ```text
-Main Title
-
-Text with bold and italic formatting.
+# Main TitleText with **bold** and *italic* formatting.
 ```
 
 ## Text Formatting

data/docs/tutorial/index.md

@@ -13,9 +13,9 @@ POML is a markup language designed for creating structured, reusable AI prompts.
 The Ruby POML gem uses a **format-aware rendering system**:
 
 - **Default rendering**: Produces Markdown-like output optimized for readability
-- **HTML components**: Use `<output format="html"/>` for HTML output (`<h1>`, `<b>`, `<i>` tags)
-- **JSON/XML formats**: Use `<output format="json"/>` or `<output format="xml"/>` for structured data
-- **Text format**: Use `<output format="text"/>` for plain text output
+- **HTML components**: Use `<output format="html">content</output>` for HTML output (`<h1>`, `<b>`, `<i>` tags)
+- **JSON/XML formats**: Use `<output format="json">content</output>` or `<output format="xml">content</output>` for structured data
+- **Text format**: Use `<output format="text">content</output>` for plain text output
 
 **Example - Getting HTML Output:**
 
@@ -23,9 +23,10 @@ The Ruby POML gem uses a **format-aware rendering system**:
 markup = <<~POML
   <poml>
     <role>Documentation Writer</role>
-    <h1>Main Title</h1>
-    <p>Content with <b>bold</b> and <i>italic</i> text.</p>
-    <output format="html"/>
+    <output format="html">
+      <h1>Main Title</h1>
+      <p>Content with <b>bold</b> and <i>italic</i> text.</p>
+    </output>
   </poml>
 POML
 

data/docs/tutorial/output-formats.md

@@ -19,7 +19,7 @@ Control the **overall structure** of the result (API format):
 
 ### 2. Content Rendering Formats
 
-Control how **components render** within the content using `<output format="..."/>`:
+Control how **components render** within the content using `<output format="...">content</output>`:
 
 - `format="markdown"` - Markdown syntax (default): `# Header`, `**bold**`
 - `format="html"` - HTML tags: `<h1>Header</h1>`, `<b>bold</b>`
@@ -33,9 +33,10 @@ Control how **components render** within the content using `<output format="..."
 markup = <<~POML
   <poml>
     <role>Writer</role>
-    <h1>Article Title</h1>
-    <p>Content with <b>emphasis</b></p>
-    <output format="html"/>  <!-- Content format -->
+    <output format="html">
+      <h1>Article Title</h1>
+      <p>Content with <b>emphasis</b></p>
+    </output>
   </poml>
 POML
 

data/readme.md

@@ -23,87 +23,6 @@ For comprehensive documentation, tutorials, and examples, please refer to the **
 
 The original documentation is an excellent resource for learning POML concepts, syntax, and best practices that apply to this Ruby implementation as well.
 
-## Recent Development Findings
-
-### XML Parsing and Component Rendering
-
-During test-driven development, several critical insights were discovered about POML's dual-mode architecture:
-
-#### Code Component Behavior in XML Mode
-
-**Key Discovery**: The original POML TypeScript implementation uses `SimpleMarkupComponent` with `tagName='code'` which preserves XML attributes when `syntax="xml"` is specified. This means:
-
-- **Tutorial formatting tests** expect plain HTML: `<code>content</code>`
-- **Markup component tests** expect XML with attributes: `<code inline="true">content</code>`
-- Both behaviors are correct depending on context - the `syntax="xml"` mode should preserve XML structure with attributes
-
-#### XML Parsing Boundary Issues
-
-**Critical Fix**: The regex pattern `/<code\b[^>]*>/` was incorrectly matching `<code-block>` tags, causing XML parsing failures. Fixed with negative lookahead: `/<code(?!-)[^>]*>/`
-
-- Word boundaries (`\b`) don't prevent hyphenated extensions
-- Negative lookahead (`(?!-)`) provides precise disambiguation
-- This fix resolved multiple XML parsing test failures
-
-#### Dual Output Modes
-
-The Ruby implementation now correctly handles:
-
-1. **Markdown Mode**: Components render to Markdown syntax (`` `code` ``, `**bold**`, etc.)
-2. **XML Mode**: Components preserve HTML/XML structure for `syntax="xml"` contexts
-3. **Attribute Preservation**: XML mode maintains component attributes like `inline="true"`
-
-### Test-Driven Architecture Validation
-
-The comprehensive test suite revealed the importance of:
-
-- **Boundary condition testing** for regex patterns
-- **Context-aware rendering** based on `syntax` attributes  
-- **Dual compatibility** between chat and XML syntax modes
-- **Progressive complexity** in template and component interactions
-
-### Implementation status
-
-Please refer to [ROADMAP.md](https://github.com/GhennadiiMir/poml/blob/main/ROADMAP.md) for understanding which features are already implemented.
-
-## Key Differences from Original Implementation
-
-### Presentation Modes and Output Formats
-
-The **original POML library** uses a sophisticated presentation system with multiple rendering modes:
-
-- **`markup`** - Renders to markup languages (Markdown by default, configurable)
-- **`serialize`** - Renders to serialized data formats (JSON, XML, etc.)
-- **`free`** - Flexible rendering mode
-- **`multimedia`** - Media-focused rendering
-
-The **Ruby implementation** currently uses a simplified approach:
-
-- **Default rendering** - Produces Markdown-like output for readability
-- **Output format components** - Use `<output format="html|json|xml|text|markdown"/>` for specific formats
-- **XML mode** - Components can render HTML when in XML context
-
-### Header Components
-
-**Original Implementation:**
-
-- Uses generic `<h>` tags with `level` attributes
-- Presentation mode determines output format (HTML vs Markdown)
-
-**Ruby Implementation:**
-
-- Supports both `<h>` and `<h1>`-`<h6>` tag syntax
-- Defaults to Markdown output (`# text`) unless in XML mode
-- Use `<output format="html"/>` for HTML output (`<h1>text</h1>`)
-
-### Migration Notes
-
-If migrating from the original TypeScript/JavaScript implementation:
-
-1. **Output Formats**: Explicitly specify output format for HTML rendering
-2. **Presentation Context**: Ruby gem uses output format components instead of presentation context
-3. **Component Mapping**: Most components work identically, but output format may differ
-
 ## Installation
 
 ```bash
@@ -207,6 +126,87 @@ poml markup.poml --format raw
 
 > **Note**: While this Ruby implementation aims for compatibility with the original POML library, the output format structures may differ slightly from the original TypeScript/Python implementations. The format names are kept consistent for API compatibility, but the Ruby gem provides its own implementation of each format suitable for Ruby applications.
 
+## Recent Development Findings
+
+### XML Parsing and Component Rendering
+
+During test-driven development, several critical insights were discovered about POML's dual-mode architecture:
+
+#### Code Component Behavior in XML Mode
+
+**Key Discovery**: The original POML TypeScript implementation uses `SimpleMarkupComponent` with `tagName='code'` which preserves XML attributes when `syntax="xml"` is specified. This means:
+
+- **Tutorial formatting tests** expect plain HTML: `<code>content</code>`
+- **Markup component tests** expect XML with attributes: `<code inline="true">content</code>`
+- Both behaviors are correct depending on context - the `syntax="xml"` mode should preserve XML structure with attributes
+
+#### XML Parsing Boundary Issues
+
+**Critical Fix**: The regex pattern `/<code\b[^>]*>/` was incorrectly matching `<code-block>` tags, causing XML parsing failures. Fixed with negative lookahead: `/<code(?!-)[^>]*>/`
+
+- Word boundaries (`\b`) don't prevent hyphenated extensions
+- Negative lookahead (`(?!-)`) provides precise disambiguation
+- This fix resolved multiple XML parsing test failures
+
+#### Dual Output Modes
+
+The Ruby implementation now correctly handles:
+
+1. **Markdown Mode**: Components render to Markdown syntax (`` `code` ``, `**bold**`, etc.)
+2. **XML Mode**: Components preserve HTML/XML structure for `syntax="xml"` contexts
+3. **Attribute Preservation**: XML mode maintains component attributes like `inline="true"`
+
+### Test-Driven Architecture Validation
+
+The comprehensive test suite revealed the importance of:
+
+- **Boundary condition testing** for regex patterns
+- **Context-aware rendering** based on `syntax` attributes  
+- **Dual compatibility** between chat and XML syntax modes
+- **Progressive complexity** in template and component interactions
+
+### Implementation status
+
+Please refer to [ROADMAP.md](https://github.com/GhennadiiMir/poml/blob/main/ROADMAP.md) for understanding which features are already implemented.
+
+## Key Differences from Original Implementation
+
+### Presentation Modes and Output Formats
+
+The **original POML library** uses a sophisticated presentation system with multiple rendering modes:
+
+- **`markup`** - Renders to markup languages (Markdown by default, configurable)
+- **`serialize`** - Renders to serialized data formats (JSON, XML, etc.)
+- **`free`** - Flexible rendering mode
+- **`multimedia`** - Media-focused rendering
+
+The **Ruby implementation** currently uses a simplified approach:
+
+- **Default rendering** - Produces Markdown-like output for readability
+- **Output format components** - Use `<output format="html|json|xml|text|markdown"/>` for specific formats
+- **XML mode** - Components can render HTML when in XML context
+
+### Header Components
+
+**Original Implementation:**
+
+- Uses generic `<h>` tags with `level` attributes
+- Presentation mode determines output format (HTML vs Markdown)
+
+**Ruby Implementation:**
+
+- Supports both `<h>` and `<h1>`-`<h6>` tag syntax
+- Defaults to Markdown output (`# text`) unless in XML mode
+- Use `<output format="html"/>` for HTML output (`<h1>text</h1>`)
+
+### Migration Notes
+
+If migrating from the original TypeScript/JavaScript implementation:
+
+1. **Output Formats**: Explicitly specify output format for HTML rendering
+2. **Presentation Context**: Ruby gem uses output format components instead of presentation context
+3. **Component Mapping**: Most components work identically, but output format may differ
+
 ## 🔄 Migration Guide (Breaking Change)
 
 ### Tools Structure Change

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: poml
 version: !ruby/object:Gem::Version
-  version: 0.0.7
+  version: 0.0.8
 platform: ruby
 authors:
 - Ghennadii Mirosnicenco
 bindir: bin
 cert_chain: []
-date: 2025-08-29 00:00:00.000000000 Z
+date: 2025-08-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rexml
@@ -51,6 +51,62 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '2.1'
+- !ruby/object:Gem::Dependency
+  name: csv
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+- !ruby/object:Gem::Dependency
+  name: base64
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.1'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.1'
+- !ruby/object:Gem::Dependency
+  name: net-http
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.3'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.3'
+- !ruby/object:Gem::Dependency
+  name: uri
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.12'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.12'
 description: "POML is a Ruby gem that implements POML (Prompt Oriented Markup Language),
   \na markup language for structured prompt engineering. This is a Ruby port of \nthe
   original Microsoft POML library, providing comprehensive tools for creating, \nprocessing,