<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.9.1" -->
<rss version="0.92">
<channel>
	<title>Assertion.ru</title>
	<link>https://assertion.ru</link>
	<description>Talks about assertions, specifications and markup</description>
	<lastBuildDate>Sun, 21 Mar 2010 22:13:21 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Make it simple?</title>
		<description><![CDATA[Specification is important &#8211; this statement is clear to everyone. A widely used product, technology or language without a specification is useless. A specification without a testsuite is dangerous. A testsuite without markup and tests is impossible. This process is quite complex. However there are ways to simplify the markup stage.
As for Java Language Specification [...]]]></description>
		<link>https://assertion.ru/make-it-simple/</link>
			</item>
	<item>
		<title>Assertion coloring</title>
		<description><![CDATA[
Conformance test development involves identifying assertions in a specification, writing conformance tests that check the identified assertions and linking the test to the assertion that it tests.
Lets start from the following points:
- assertion is marked
- actual assertion is difficult to view in the spec (currently there are only small assertion gif&#8217;s at the end of [...]]]></description>
		<link>https://assertion.ru/assertion-coloring/</link>
			</item>
	<item>
		<title>Markup metadata</title>
		<description><![CDATA[The simplest definition of metadata is that it is data about data. Metadata might be very useful. As for the markup there was some metadata embedded: id, small description of assertion, link to test. During the markup transfer I realized that more metadata would be very helpful. In the new version of specification there were [...]]]></description>
		<link>https://assertion.ru/markup-metadata/</link>
			</item>
</channel>
</rss>
