<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Status words in ISO7816</title>
	<atom:link href="http://javacard.vetilles.com/2006/09/26/status-words-in-iso7816/feed/" rel="self" type="application/rss+xml" />
	<link>http://javacard.vetilles.com/2006/09/26/status-words-in-iso7816/</link>
	<description>A weblog on Java Card, security, and other things personal</description>
	<pubDate>Thu, 29 Jul 2010 11:50:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Eric Vétillard</title>
		<link>http://javacard.vetilles.com/2006/09/26/status-words-in-iso7816/#comment-303</link>
		<dc:creator>Eric Vétillard</dc:creator>
		<pubDate>Tue, 16 Jan 2007 10:02:46 +0000</pubDate>
		<guid isPermaLink="false">http://javacard.vetilles.com/2006/09/26/status-words-in-iso7816/#comment-303</guid>
		<description>Multos did things right in defining the content management and the application framework together, because it more or less guarantees their efficiency.

The '6999' thing is really one of the most stupid decisions in the Java Card spec, and it has led to numerous headaches, and I hope that we are better now.

About your last sentence, I just love it, but I am not quite sure how to achieve such a synchronization. The main issue is that all these work groups work at the same time, and that when they synchronize, it is often too late. But we're trying.</description>
		<content:encoded><![CDATA[<p>Multos did things right in defining the content management and the application framework together, because it more or less guarantees their efficiency.</p>
<p>The &#8216;6999&#8242; thing is really one of the most stupid decisions in the Java Card spec, and it has led to numerous headaches, and I hope that we are better now.</p>
<p>About your last sentence, I just love it, but I am not quite sure how to achieve such a synchronization. The main issue is that all these work groups work at the same time, and that when they synchronize, it is often too late. But we&#8217;re trying.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lexdabear</title>
		<link>http://javacard.vetilles.com/2006/09/26/status-words-in-iso7816/#comment-290</link>
		<dc:creator>lexdabear</dc:creator>
		<pubDate>Fri, 12 Jan 2007 07:40:25 +0000</pubDate>
		<guid isPermaLink="false">http://javacard.vetilles.com/2006/09/26/status-words-in-iso7816/#comment-290</guid>
		<description>First: Great blog about the smart card world.

SW1SW2 = '6999' is one of the incompatibilities between a pure Java Card and a GlobalPlatform card. MultOS gets rid of this problem by combining content management into the SC-OS. Still I think the Java Card / GP approach is the more flexible one. One just has to make sure that the specs are "in sync" with each other: JC, GP, VGP, MC and ISO.</description>
		<content:encoded><![CDATA[<p>First: Great blog about the smart card world.</p>
<p>SW1SW2 = &#8216;6999&#8242; is one of the incompatibilities between a pure Java Card and a GlobalPlatform card. MultOS gets rid of this problem by combining content management into the SC-OS. Still I think the Java Card / GP approach is the more flexible one. One just has to make sure that the specs are &#8220;in sync&#8221; with each other: JC, GP, VGP, MC and ISO.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
