<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:admin="http://webns.net/mvcb/"
	xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
	xmlns:content="http://purl.org/rss/1.0/modules/content/">

	<channel>

	<title>&#45; CircleID</title>
	<link>https://www.circleid.com/blogs/</link>
	<description>Postings from  on CircleID</description>
	<dc:language>en</dc:language>
	<dc:rights>Copyright 2026, unless where otherwise noted.</dc:rights>
	<dc:date>2026-04-30T19:14:00+00:00</dc:date>

	
	<item>
		<title> Suggestions on IDN Variant Management (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/postssuggestions_on_idn_variant_management</guid>
		<link>https://circleid.com/postssuggestions_on_idn_variant_management</link>
		<description><![CDATA[To some applicants, ICANN's variant management policy in DAG4 has become a big obstacle to the new generic Top-Level Domain (gTLD) application. The policy is to delegate the string while reserving the variants, and these variants will not be delegated until a sound mechanism is developed and the desired variants are evaluated. But for some languages, Chinese for example, the so called string and its variant, namely simplified Chinese and traditional Chinese, are equivalent and must be simultaneously delegated. <a href="https://circleid.com/postssuggestions_on_idn_variant_management">More...</a>]]></description>
		<dc:date>2026-04-30T12:14:00-07:00</dc:date>
	</item>
	

	</channel>
</rss>