<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Relx Pods</title>
    <description>The latest articles on DEV Community by Relx Pods (@relxpods).</description>
    <link>https://dev.to/relxpods</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4204100%2F37fe972f-f7e1-41ae-92f1-88ecb3e86ac7.jpg</url>
      <title>DEV Community: Relx Pods</title>
      <link>https://dev.to/relxpods</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/relxpods"/>
    <language>en</language>
    <item>
      <title>How to Model Ecommerce Product Compatibility in JSON</title>
      <dc:creator>Relx Pods</dc:creator>
      <pubDate>Fri, 20 Nov 2026 05:45:50 +0000</pubDate>
      <link>https://dev.to/relxpods/how-to-model-ecommerce-product-compatibility-in-json-20ng</link>
      <guid>https://dev.to/relxpods/how-to-model-ecommerce-product-compatibility-in-json-20ng</guid>
      <description>&lt;p&gt;Every store that sells accessories or consumables gets the same support question: "will this fit my device?" On the RELX store I work on, the answer used to live in prose spread across dozens of product pages, and the pages didn't always agree. One said a pod line didn't fit a device that it does fit.&lt;/p&gt;

&lt;p&gt;This post walks through the data model we moved to, how to handle compatibility that comes with conditions, how to render it on product pages, and how to describe it with schema.org markup. The examples use real RELX devices and pods, but the pattern works for any product with "fits" relationships: phone cases, printer ink, filters, chargers.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is a product compatibility matrix?
&lt;/h2&gt;

&lt;p&gt;A compatibility matrix is a table of pairs: one device, one accessory line, and the fit answer for that pair. For RELX it looks like this:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Device&lt;/th&gt;
&lt;th&gt;Pod line&lt;/th&gt;
&lt;th&gt;Fits&lt;/th&gt;
&lt;th&gt;Note&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://relxpod.ae/category/relx-infinity-2" rel="noopener noreferrer"&gt;RELX Infinity 2&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="https://relxpod.ae/category/relx-pod-pro" rel="noopener noreferrer"&gt;RELX Pod Pro&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Smooth mode only&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;RELX Infinity 2&lt;/td&gt;
&lt;td&gt;&lt;a href="https://relxpod.ae/category/relx-pod-pro-2" rel="noopener noreferrer"&gt;RELX Pod Pro 2&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Eco, Smooth and Boost modes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://relxpod.ae/category/relx-artisan" rel="noopener noreferrer"&gt;RELX Artisan&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Pod Pro and Pod Pro 2&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;One fixed output&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;RELX Essential&lt;/td&gt;
&lt;td&gt;Pod Pro 2&lt;/td&gt;
&lt;td&gt;Check&lt;/td&gt;
&lt;td&gt;Usually fits, check the pack&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;RELX Classic&lt;/td&gt;
&lt;td&gt;Pod Pro and Pod Pro 2&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Takes Classic pods only&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;That table is easy for people to read. The trouble starts when the same facts are typed into 50 product descriptions by hand.&lt;/p&gt;

&lt;h2&gt;
  
  
  A JSON model for device and accessory compatibility
&lt;/h2&gt;

&lt;p&gt;Each pair becomes one record with four fields:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"device"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Infinity 2"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"accessory"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Pod Pro"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"fits"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"note"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Smooth mode only"&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Three design choices made this work:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;fits&lt;/code&gt; has three values, not two.&lt;/strong&gt; &lt;code&gt;true&lt;/code&gt;, &lt;code&gt;false&lt;/code&gt; and &lt;code&gt;"check"&lt;/code&gt;. The third exists for one real case: a pod line that usually fits a device, where buyers should check the pack first. A boolean would force you to lie in one direction.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The exception is a row, not a sentence.&lt;/strong&gt; The RELX Classic fits neither current pod line. Writing that as two &lt;code&gt;false&lt;/code&gt; rows means no page can forget it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Notes are written for customers.&lt;/strong&gt; "Smooth mode only" can be shown as-is. An internal code like &lt;code&gt;PM_LIMIT_2&lt;/code&gt; would need translating on every page.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The full dataset (18 records covering 9 devices and 2 pod lines) is public in this &lt;a href="https://gitlab.com/relx-pods/relx-compatibility-guide" rel="noopener noreferrer"&gt;compatibility guide repo on GitLab&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Handling conditional compatibility
&lt;/h2&gt;

&lt;p&gt;The interesting cases are the ones where a product fits but behaves differently. The RELX Infinity 2 has three power modes: Eco at 5.5 W, Smooth at 6.5 W and Boost at 8 W. Both pod lines fit it, but only Pod Pro 2 unlocks all three modes. The older pod keeps the device in Smooth.&lt;/p&gt;

&lt;p&gt;If that condition lives in a footnote on one page, the other pages drift. If it lives in the &lt;code&gt;note&lt;/code&gt; field, every page that renders the pair shows the same caveat. A good test: could a customer get a wrong answer from any single page? If yes, the condition belongs in the data.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rendering compatibility on product pages
&lt;/h2&gt;

&lt;p&gt;With one dataset, each product page can generate its own "fits these devices" block. A minimal version:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;fitsFor&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;accessory&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;data&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;filter&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;r&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;accessory&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="n"&gt;accessory&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;fits&lt;/span&gt; &lt;span class="o"&gt;!==&lt;/span&gt; &lt;span class="kc"&gt;false&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;map&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;r&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;fits&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="s2"&gt;"check"&lt;/span&gt;
      &lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="sb"&gt;`${r.device} (check the pack)`&lt;/span&gt;
      &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;note&lt;/span&gt; &lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="sb"&gt;`${r.device} (${r.note})`&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;device&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="c1"&gt;// fitsFor("Pod Pro 2", data)&lt;/span&gt;
&lt;span class="c1"&gt;// ["Infinity", "Infinity Plus", "Infinity 2 (Eco, Smooth and Boost modes)", ...]&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On a pod page such as &lt;a href="https://relxpod.ae/product/relx-pod-pro-2-green-melon-15-mg" rel="noopener noreferrer"&gt;RELX Pod Pro 2 Green Melon 15mg&lt;/a&gt;, this produces the device list. On a device page such as &lt;a href="https://relxpod.ae/product/relx-artisan-indigo-denim" rel="noopener noreferrer"&gt;RELX Artisan Indigo Denim&lt;/a&gt;, you run the same filter the other way round, by device instead of accessory. When a fact changes, you edit one record and every page updates.&lt;/p&gt;

&lt;h2&gt;
  
  
  Describing compatibility with schema.org markup
&lt;/h2&gt;

&lt;p&gt;Search engines can read compatibility too. schema.org's &lt;code&gt;Product&lt;/code&gt; type has two properties built for this:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;isConsumableFor&lt;/code&gt;: a product used up with another product, such as pods for a device or ink for a printer&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;isAccessoryOrSparePartFor&lt;/code&gt;: an add-on or replacement part, such as a case or a charger&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For a pod, the markup looks like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"@context"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://schema.org"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Product"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"RELX Pod Pro 2 Menthol Xtra 5%"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"isConsumableFor"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Product"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"RELX Infinity 2"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Product"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"RELX Artisan"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You can build that list from the same dataset, so the markup can't disagree with the page. The &lt;a href="https://relxpod.ae/product/relx-pod-pro-2-menthol-xtra" rel="noopener noreferrer"&gt;RELX Menthol Xtra&lt;/a&gt; page is a good candidate: same flavor name as an older pod, a different strength, and nearly the same device list.&lt;/p&gt;

&lt;h2&gt;
  
  
  Answering the question directly: a compatibility hub
&lt;/h2&gt;

&lt;p&gt;Product pages answer "does this fit?" one product at a time. A single hub page answers it for every model at once, and it's where the dataset is easiest to check. Ours is the &lt;a href="https://relxpod.ae/relx-pod-compatibility" rel="noopener noreferrer"&gt;RELX pod compatibility checker&lt;/a&gt;, which shows every device against both pod lines.&lt;/p&gt;

&lt;p&gt;When two product lines are close enough to confuse people, a comparison page helps as well. For RELX that's the &lt;a href="https://relxpod.ae/blog/relx-pod-pro-vs-pod-pro-2" rel="noopener noreferrer"&gt;Pod Pro vs Pod Pro 2 comparison&lt;/a&gt;, which covers strength, pack size and power modes alongside fit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lessons
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Store compatibility as records, not prose. Prose drifts.&lt;/li&gt;
&lt;li&gt;Allow a third value for "usually fits". Real products have edge cases.&lt;/li&gt;
&lt;li&gt;Put conditions in the data so every page shows them.&lt;/li&gt;
&lt;li&gt;Generate product-page text and schema.org markup from the same source.&lt;/li&gt;
&lt;li&gt;Keep the dataset in a public repo. You get version history, and anyone can spot a mistake.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;How do you handle compatibility data in your store or app? I'd like to hear other approaches in the comments.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I work on the &lt;a href="//relxpod.ae"&gt;RELX Dubai store&lt;/a&gt;. RELX products contain nicotine and are for adults 18+ only.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>ecommerce</category>
      <category>json</category>
      <category>seo</category>
    </item>
    <item>
      <title>RELX Pod Pro 2: Flavor Profiles, Compatibility, and What to Check</title>
      <dc:creator>Relx Pods</dc:creator>
      <pubDate>Sat, 24 Oct 2026 07:29:08 +0000</pubDate>
      <link>https://dev.to/relxpods/relx-pod-pro-2-flavor-profiles-compatibility-and-what-to-check-165e</link>
      <guid>https://dev.to/relxpods/relx-pod-pro-2-flavor-profiles-compatibility-and-what-to-check-165e</guid>
      <description>&lt;p&gt;Choosing a pod involves more than comparing flavor names. Understanding flavor profiles, device compatibility, and product specifications can help readers make better-informed decisions.&lt;/p&gt;

&lt;p&gt;At &lt;a href="https://relxpod.ae/" rel="noopener noreferrer"&gt;RELX Dubai&lt;/a&gt;, we focus on product information and flavor comparisons for the UAE market. This guide explains what to consider when researching RELX Pod Pro 2 variants.&lt;/p&gt;

&lt;h2&gt;
  
  
  Understanding RELX Pod Pro 2 Flavor Profiles
&lt;/h2&gt;

&lt;p&gt;Flavor names often provide an initial indication of a pod's intended taste profile, but the actual descriptions can vary between variants.&lt;/p&gt;

&lt;p&gt;Here are four characteristics to consider when comparing flavors:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Fruit notes:&lt;/strong&gt; Fruit-inspired variants may emphasize profiles such as grape, apple, peach, or guava.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cooling sensation:&lt;/strong&gt; Ice or menthol terminology generally indicates a cooling element in the described flavor profile.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tea-inspired notes:&lt;/strong&gt; Tea-inspired variants combine a different aromatic direction with their other listed flavor characteristics.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sweetness and tartness:&lt;/strong&gt; These characteristics help explain why two fruit-based variants may have different flavor descriptions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Flavor perception is subjective. The same description may not produce identical experiences for every person, so use product descriptions as guidance rather than a guarantee.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Device Compatibility Matters
&lt;/h2&gt;

&lt;p&gt;One of the most important checks when researching replacement pods is whether they are designed for your specific device.&lt;/p&gt;

&lt;p&gt;Product names can be similar across different generations, but that does not mean their pods are interchangeable.&lt;/p&gt;

&lt;p&gt;Before relying on a compatibility claim, check:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The exact name and generation of your device.&lt;/li&gt;
&lt;li&gt;The manufacturer's compatibility information.&lt;/li&gt;
&lt;li&gt;The pod model specified in the product listing.&lt;/li&gt;
&lt;li&gt;Any relevant instructions supplied with the device.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For example, compatibility information for RELX Pod Pro 2 should be checked against the exact device requirements rather than inferred from the RELX brand name alone.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to Compare Before Choosing a Variant
&lt;/h2&gt;

&lt;p&gt;When reviewing product listings, focus on information that helps you distinguish one variant from another.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Product Identification
&lt;/h3&gt;

&lt;p&gt;Confirm the full product name and variant. This helps prevent confusion between similar names and different product generations.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Flavor Description
&lt;/h3&gt;

&lt;p&gt;Read the listed flavor notes carefully. Descriptions such as fruity, tea-inspired, or menthol indicate different flavor directions, although personal perceptions can vary.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Verified Specifications
&lt;/h3&gt;

&lt;p&gt;Check the published product details rather than relying on assumptions. If a specification is missing or unclear, consult the manufacturer or an authorized source instead of treating an unverified claim as fact.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Compatibility Information
&lt;/h3&gt;

&lt;p&gt;Verify that the specific pod is intended for your device before making a decision. This is more reliable than assuming compatibility based on appearance or product naming.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where to Find RELX Pod Pro 2 Information
&lt;/h2&gt;

&lt;p&gt;For readers researching this product range, the &lt;a href="https://relxpod.ae/category/relx-pod-pro-2" rel="noopener noreferrer"&gt;RELX Pod Pro 2&lt;/a&gt; category on RELX Dubai provides a starting point for exploring relevant product listings.&lt;/p&gt;

&lt;p&gt;Review each listing individually and compare its stated flavor description, product identification, and compatibility information. Product details should always be checked against the exact variant rather than generalized across an entire range.&lt;/p&gt;

&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;Researching RELX Pod Pro 2 products is easier when you separate flavor descriptions from verified specifications and device compatibility.&lt;/p&gt;

&lt;p&gt;Start with the exact product name, compare the published flavor notes, and confirm compatibility using reliable product information. These simple checks help reduce confusion and make product research more useful.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Which detail do you check first when comparing product listings: flavor descriptions, specifications, or device compatibility?&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>relx</category>
      <category>uae</category>
      <category>productreviews</category>
      <category>ai</category>
    </item>
  </channel>
</rss>
