<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="https://www.taxtmi.com/rss_sitemap/rss_feed_blog.xsl?v=1750492856"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>2002 (11) TMI 680 - HIGH COURT OF DELHI</title>
    <link>https://www.taxtmi.com/caselaws?id=108592</link>
    <description>Notifications governing high security registration plates required the hologram design to conform strictly to the notified Chakra specification. The approved type design could not be expanded to include the Ashok Chakra, and the authorities were directed to recheck the sample and drawings used for type approval to ensure compliance. The operative effect was that no company hologram on such plates could contain the Ashok Chakra, and the approval process had to be verified against the notified design.</description>
    <language>en-us</language>
    <pubDate>Fri, 22 Nov 2002 00:00:00 +0530</pubDate>
    <lastBuildDate>Mon, 02 Apr 2012 18:15:24 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=145609" rel="self" type="application/rss+xml"/>
    <item>
      <title>2002 (11) TMI 680 - HIGH COURT OF DELHI</title>
      <link>https://www.taxtmi.com/caselaws?id=108592</link>
      <description>Notifications governing high security registration plates required the hologram design to conform strictly to the notified Chakra specification. The approved type design could not be expanded to include the Ashok Chakra, and the authorities were directed to recheck the sample and drawings used for type approval to ensure compliance. The operative effect was that no company hologram on such plates could contain the Ashok Chakra, and the approval process had to be verified against the notified design.</description>
      <category>Case-Laws</category>
      <law>Companies Law</law>
      <pubDate>Fri, 22 Nov 2002 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=108592</guid>
    </item>
  </channel>
</rss>