poml 0.0.1

data/examples/ruby_expects/107_read_report_pdf.txt

@@ -0,0 +1,403 @@
+===== human =====
+
+Provide a concise executive summary of the following text, highlighting key points, objectives, and outcomes. Keep the summary under 150 words and ensure it is suitable for a professional audience.
+
+Esc
+
+F1
+
+F2
+
+F3
+
+§
+
+!
+
+"
+
+#
+
+¤
+
+½
+
+1
+
+2 @
+
+3 £
+
+4
+
+W
+
+Q
+
+F4
+
+$
+
+E
+
+E-Mail
+
+F6
+
+F7
+
+F5
+
+%
+
+&
+
+/
+
+5
+
+6
+
+7
+
+R
+
+Web
+
+T
+
+Tuner
+
+(
+{
+
+Y
+
+8
+
+Menu
+
+F8
+
+)
+[
+
+U
+
+Previous
+
+=
+]
+
+9
+
+I
+
+}
+
+0
+
+O
+
+Next
+
+F9
+
+F10
+
+?
+
+`
+
++
+
+'
+
+P
+
+Å
+
+A
+
+S
+
+D
+
+F
+
+G
+
+H
+
+J
+
+K
+
+L
+
+Æ
+
+-Volume
+
++Volume
+
+F11
+
+F12
+
+|
+
+^
+" ~
+
+€
+
+Caps Lock
+
+Mute
+
+Ø
+
+*
+
+Power
+
+Sleep
+
+Wake
+Up
+
+Print
+Scrn
+SysRq
+
+Scroll
+Lock
+
+Pause
+Break
+
+Insert
+
+Home
+
+Page
+Up
+
+Delete
+
+End
+
+Page
+Down
+
+'
+>
+< \
+
+Z
+
+X
+
+C
+
+V
+
+B
+
+N
+
+M
+
+;
+,
+
+:
+.
+
+_
+-
+
+Num Lock
+
+Caps Lock
+
+Num
+Lock
+
+/
+
+7
+
+8
+
+Home
+
+*
+
+Scroll Lock
+
+_
+
+9
+PgUp
+
+4
+
+5
+
+1
+
+2
+
+6
+
++
+
+3
+
+End
+
+PgDn
+
+0
+
+,
+
+Ins
+
+Del
+
+Enter
+Ctrl
+
+Alt
+
+Alt Gr
+
+Ctrl
+
+Figure 2: This figure floats to the top of the page, spanning both columns.
+
+3.1 HTML5
+This template uses HTML5 elements to aid in representing the document structure. The section
+element is used to split the text into sections, and
+the header element holds the headlines. The
+figure element is used to include figures and
+their corrensponding captions live inside the figcaption element. The cite element holds all references.
+A small microformat, based on a convention of
+class names, is used to encode the name and affiliation of the authors.
+
+3.2 CSS
+A CSS style sheet describes how to format the
+HTML document into a PDF file. CSS is a declarative language which attaches property values to
+HTML elements and documents. Many aspects of
+CSS is used to achieve the presentation of USENIX
+papers, including:
+•
+•
+•
+•
+
+multi-column layout
+footnotes
+page and column floats
+multi-level counters
+
+Some commonly used features are absent from
+the above list: page numbers and running headers
+should not be specifed by USENIX authors, these
+are added by those who compile the Proceedings.
+
+references to the end of the paper, leaving behind
+a numeric marker.
+
+3.4 PDF
+(This section has been added by Håkon Wium Lie)
+In order to convert the document to PDF, a formatter is needed. Common browsers support
+HTML and CSS, but they do not support all the CSS
+functionality for page-based formatting. For example, browsers do not support footnotes or page
+floats. This paper has been formatted with
+[a]
+Prince, a purpose-built program for converting
+HTML and XML documents into PDF by way of
+CSS. Prince is a commercial product, but can be
+downloaded and used for free for non-commercial
+purposes.
+In order for Prince to process the script included in this template, a command line option must
+be specified:
+$ prince --javascript example.html
+
+4 Tables
+The table below lists recipients of the USENIX Lifetime Achievement Award in the 1900s. Notice how
+notes inside the table are moved to the end of the
+table.
+Year
+
+Recipient
+
+1999
+
+X Window System*
+
+3.3 JavaScript
+
+1998
+
+Tim Berners-Lee
+
+This template uses JavaScript to process references. References are added at the point where
+they appear, and a script is later used to move the
+
+1997
+
+Brian W. Kernighan
+
+[a] www.princexml.com
+
+1996
+
+The Software Tools Project
+
+work.
+
+1995
+
+The Creation of USENET **
+
+1994
+
+Networking Technologies
+
+Availability
+
+1993
+
+Berkeley UNIX
+
+* Given to the Community at Large
+** Given to Jim Ellis and Tom Truscott
+
+5 Conclusions
+Each good paper concludes the most significant
+findings in the end.
+
+Acknowledgments
+A polite author always includes acknowledgments.
+Thank everyone, especially those who funded the
+
+Please include a section at the end of your paper
+providing availability information. If the system
+you describe is available to others, and if more information (reports, etc.) may be obtained, indicate
+terms and contact information.
+
+References
+[1] STRUNK, W. JR., AND WHITE, E.B. The Elements
+of Style, 4th Ed, Allyn and Bacon, August, 1999,
+ISBN 020530902X
+[2] ZOBEL, J. Writing for Computer Science,
+Springer-Verlag,
+December
+1997,
+ISBN
+9813083220

data/examples/ruby_expects/201_orders_qa.txt

@@ -0,0 +1,41 @@
+===== system =====
+
+# Role
+
+You are a chatbot agent answering customer's questions in a chat.
+
+# Task
+
+Your task is to answer the customer's question using the data provided in the data section.
+
+1. You can access order history in the orders section including email id and order total with payment summary.
+
+2. Refer to orderlines for item level details within each order in orders.
+
+# Data
+
+# Orders
+
+| OrderId | CustomerEmail | CreatedTimestamp | IsCancelled | OrderTotal | PaymentSummary |
+| --- | --- | --- | --- | --- | --- |
+| CC10182 | 222larabrown@gmail.com | 2024-01-19 | true | 0.0 | Not available |
+| CC10183 | baklavainthebalkans@gmail.com | 2024-01-19 | true | 0.0 | Not available |
+
+# Orderlines
+
+OrderId	OrderLineId	CreatedTimestamp	ItemDescription	Quantity	FulfillmentStatus	ExpectedDeliveryDate	ActualDeliveryDate	ActualShipDate	ExpectedShipDate	TrackingInformation	ShipToAddress	CarrierCode	DeliveryMethod	UnitPrice	OrderLineSubTotal	LineShippingCharge	TotalTaxes	Payments
+CC10182	1		Shorts	0.0	unshipped	2024-01-31	2024-02-01	2024-01-30	2024-01-29				ShipToAddress	115.99	0.0	0.0	0.0	
+
+
+
+# Stepwise Instructions
+
+Instruction 1: If there is no data that can help answer the question, respond with "I do not have this information. Please contact customer service".
+Instruction 2: You are allowed to ask a follow up question if it will help narrow down the data row customer may be referring to.
+Instruction 3: You can only answer questions related to order history and amount charged for it. Include OrderId in the response, when applicable.
+Instruction 4: For everything else, please redirect to the customer service agent.
+Instruction 5: Answer in plain English and no sources are required.
+
+**QUESTION:** How much did I pay for my last order?
+
+**Answer:**

data/examples/ruby_expects/202_arc_agi.txt

@@ -0,0 +1,17 @@
+Be brief and clear in your responses{
+  "table": {
+    "syntax": "csv",
+    "writerOptions": {
+        "csvHeader": false,
+        "csvSeparator": " "
+    }
+  },
+  "input": {
+    "captionEnding": "colon-newline",
+    "captionStyle": "plain"
+  },
+  "output": {
+    "captionEnding": "colon-newline",
+    "captionStyle": "plain"
+  }
+}

data/examples/ruby_expects/301_generate_poml.txt

@@ -0,0 +1,17 @@
+// PromptLibrary.jsx
+
+/* Create a blog post. The prompt contains very specific instructions around output format, styles, and what to include in the content. */
+
+
+/* Conduct in-depth research with AI, such as tackling academic papers, business analyses, or large investigative projects. */
+
+
+/* Test the ability of an LLM to perform a complex reasoning task -- ARC-AGI. The data is in `arc_agi_data.json`.
+ */
+
+
+/* Summarize a report, such as a research paper or a business report. */
+
+
+/* Write a entertaining story that is engaging, imaginative and captivating for the audience. */
+

data/lib/poml/components/base.rb

@@ -0,0 +1,132 @@
+module Poml
+  # Base class for all POML components
+  class Component
+    attr_reader :element, :context
+
+    def initialize(element, context)
+      @element = element
+      @context = context
+    end
+
+    def render
+      raise NotImplementedError, "Components must implement render method"
+    end
+
+    protected
+
+    def apply_stylesheet
+      # Apply stylesheet rules to the element
+      style_rules = @context.stylesheet[@element.tag_name.to_s] || {}
+      style_rules.each do |attr, value|
+        @element.attributes[attr] ||= value
+      end
+
+      # Apply class-based styles
+      class_name = @element.attributes['classname'] || @element.attributes['className']
+      if class_name
+        class_rules = @context.stylesheet[".#{class_name}"] || {}
+        class_rules.each do |attr, value|
+          @element.attributes[attr] ||= value
+        end
+      end
+    end
+
+    def xml_mode?
+      @context.determine_syntax(@element) == 'xml'
+    end
+
+    def render_as_xml(tag_name, content = nil, attributes = {})
+      # Render as XML element with proper formatting
+      content ||= render_children
+      attrs_str = attributes.map { |k, v| " #{k}=\"#{v}\"" }.join('')
+      
+      if content.strip.empty?
+        "<#{tag_name}#{attrs_str}/>\n"
+      else
+        # Add line breaks for nice formatting
+        if content.include?('<item>')
+          # Multi-line content with nested items - add indentation
+          indented_content = content.split("\n").map { |line| 
+            line.strip.empty? ? "" : "  #{line}" 
+          }.join("\n").strip
+          "<#{tag_name}#{attrs_str}>\n  #{indented_content}\n</#{tag_name}>\n"
+        else
+          # Simple content
+          "<#{tag_name}#{attrs_str}>#{content}</#{tag_name}>\n"
+        end
+      end
+    end
+
+    def get_attribute(name, default = nil)
+      value = @element.attributes[name.to_s.downcase]
+      case value
+      when REXML::Attribute
+        value.value
+      when String
+        value
+      else
+        default
+      end
+    end
+
+    def render_children
+      return '' if @element.children.empty?
+      
+      rendered_children = @element.children.map do |child_element|
+        Components.render_element(child_element, @context)
+      end
+      
+      # Add proper spacing between elements - specifically between text and components
+      result = []
+      rendered_children.each_with_index do |child_content, index|
+        result << child_content
+        
+        # Add spacing if current element is text and next element is a component  
+        if index < rendered_children.length - 1
+          current_element = @element.children[index]
+          next_element = @element.children[index + 1]
+          
+          if current_element.text? && next_element.component?
+            result << "\n\n"
+          end
+        end
+      end
+      
+      result.join('')
+    end
+    
+    def apply_text_transform(text)
+      return text if text.nil? || text.empty?
+      
+      # Get text transformation from stylesheet
+      component_name = self.class.name.split('::').last.gsub('Component', '').downcase
+      
+      # Check for text transformation in stylesheet - first try component-specific, then "cp" (for captioned paragraph inheritance)
+      transform = @context.stylesheet.dig(component_name, 'captionTextTransform') ||
+                  @context.stylesheet.dig('cp', 'captionTextTransform')
+      
+      case transform
+      when 'upper'
+        text.upcase
+      when 'lower'
+        text.downcase
+      when 'capitalize'
+        text.split(' ').map(&:capitalize).join(' ')
+      else
+        text
+      end
+    end
+  end
+
+  # Component registry and factory
+  module Components
+    # Component mapping will be defined in main components.rb after all components are loaded
+    COMPONENT_MAPPING = {}
+
+    def self.render_element(element, context)
+      component_class = COMPONENT_MAPPING[element.tag_name] || TextComponent
+      component = component_class.new(element, context)
+      component.render
+    end
+  end
+end