<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/marks/search/state">
<title>Public marks with search state</title>
<description>Public marks with search state</description>
<link>http://blogmarks.net/marks/search/state</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/gregg/mark/1058573155"/>
<rdf:li resource="http://blogmarks.net/api/user/mozkart/mark/1058571039"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058569740"/>
<rdf:li resource="http://blogmarks.net/api/user/mozkart/mark/1058563012"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058550434"/>
<rdf:li resource="http://blogmarks.net/api/user/kuroyagi/mark/1058549985"/>
<rdf:li resource="http://blogmarks.net/api/user/danijelzi/mark/1058542963"/>
<rdf:li resource="http://blogmarks.net/api/user/tadeufilippini/mark/1058501395"/>
<rdf:li resource="http://blogmarks.net/api/user/access2/mark/1058499727"/>
<rdf:li resource="http://blogmarks.net/api/user/newandforever/mark/1058490114"/>
<rdf:li resource="http://blogmarks.net/api/user/touristic/mark/1058486570"/>
<rdf:li resource="http://blogmarks.net/api/user/newandforever/mark/1058482897"/>
<rdf:li resource="http://blogmarks.net/api/user/Spone/mark/1058461149"/>
<rdf:li resource="http://blogmarks.net/api/user/CharlyBr/mark/1058447791"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058442031"/>
<rdf:li resource="http://blogmarks.net/api/user/br1o/mark/1058556670"/>
<rdf:li resource="http://blogmarks.net/api/user/gympie/mark/1058435213"/>
<rdf:li resource="http://blogmarks.net/api/user/ms_michel/mark/1058428675"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058428420"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058428366"/>
<rdf:li resource="http://blogmarks.net/api/user/Spone/mark/1058420215"/>
<rdf:li resource="http://blogmarks.net/api/user/fotopol/mark/1058419489"/>
<rdf:li resource="http://blogmarks.net/api/user/newandforever/mark/1058417949"/>
<rdf:li resource="http://blogmarks.net/api/user/newandforever/mark/1058398471"/>
<rdf:li resource="http://blogmarks.net/api/user/jey/mark/1058544848"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/gregg/mark/1058573155">
<title>Multimedia Standards (Beta) - A comprehensive resource for multimedia journalists</title>
<link>http://www.multimediastandards.org/</link>
<description>Our aim is to offer insights from top industry leaders on the state of multimedia journalism. We also provide guidelines based on their comments, information about conferences and awards, the ability to submit and critique projects and an in-depth list of resources</description>
<dc:date>2009-11-05T18:51:07Z</dc:date>
<dc:author>gregg</dc:author>
<dc:subject>multimédia, journalisme</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.multimediastandards.org/"><img border="0" src="http://blogmarks.net/screenshots/2009/11/05/e5fadaaa3bd2e2ecb0ec3e6bccbb27bc.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.multimediastandards.org/">Multimedia Standards (Beta) - A comprehensive resource for multimedia journalists</a></h4>
 
by <a href="http://blogmarks.net/user/gregg">gregg</a> 
<p class="description">Our aim is to offer insights from top industry leaders on the state of multimedia journalism. We also provide guidelines based on their comments, information about conferences and awards, the ability to submit and critique projects and an in-depth list of resources</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/multim%25C3%25A9dia">multimédia</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/journalisme">journalisme</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058573155">Copy</a> | 
<a href="http://blogmarks.net/link/3401439">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/mozkart/mark/1058571039">
<title>WordPress › Post Templates « WordPress Plugins</title>
<link>http://wordpress.org/extend/plugins/post-template/</link>
<description>It happens quite often that a blogger publishes posts or static pages on a regular basis which have the same structure. Think about for example a &quot;picture of the day&quot; daily post. With current wordpress state, we need to spend a lot of time doing copy/paste between posts instead of actually writing content.

All the instructions for installation, the support forums, etc. can be found on the plugin home page.

IMPORTANT: LICENSE CHANGE

Since version 4.0.0, the plugin has become a commercial plugin. It can be ordered (for cheap) on the plugin home page.

Version 3.4.x will remain available for download for free on the WordPress plugin repository. No further development will be made on this version.</description>
<dc:date>2009-11-03T09:23:53Z</dc:date>
<dc:author>mozkart</dc:author>
<dc:subject>wordpress</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://wordpress.org/extend/plugins/post-template/"><img border="0" src="http://blogmarks.net/screenshots/2009/11/03/c3e38ea368e3138c90601d83d892b550.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://wordpress.org/extend/plugins/post-template/">WordPress › Post Templates « WordPress Plugins</a></h4>
 
by <a href="http://blogmarks.net/user/mozkart">mozkart</a> 
<p class="description">It happens quite often that a blogger publishes posts or static pages on a regular basis which have the same structure. Think about for example a "picture of the day" daily post. With current wordpress state, we need to spend a lot of time doing copy/paste between posts instead of actually writing content.

All the instructions for installation, the support forums, etc. can be found on the plugin home page.

IMPORTANT: LICENSE CHANGE

Since version 4.0.0, the plugin has become a commercial plugin. It can be ordered (for cheap) on the plugin home page.

Version 3.4.x will remain available for download for free on the WordPress plugin repository. No further development will be made on this version.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/wordpress">wordpress</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058571039">Copy</a> | 
<a href="http://blogmarks.net/link/3399751">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058569740">
<title>Traffic Server is finally here | Ogre.com</title>
<link>http://www.ogre.com/node/320</link>
<description>&lt;blockquote&gt;&lt;p&gt;# A scalable threaded   asynchronous state machine model. On a typical setup, 2 or 3 threads per core is enough to drive a large amount of traffic.&lt;/p&gt;&lt;p&gt;# Feature-rich HTTP/1.0 and HTTP/1.1 support. We fair well in various tests like CoAdvisor.&lt;/p&gt;&lt;p&gt;# Plugin architecture, making it easy (well, easier) to extend and customize your server.&lt;/p&gt;&lt;p&gt;# Well documented.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-11-02T01:35:24Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>apache, proxy, trafficserver</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ogre.com/node/320"><img border="0" src="http://blogmarks.net/screenshots/2009/11/02/b4f1783cbf64713ef00228de82432a30.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ogre.com/node/320">Traffic Server is finally here | Ogre.com</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p># A scalable threaded   asynchronous state machine model. On a typical setup, 2 or 3 threads per core is enough to drive a large amount of traffic.</p><p># Feature-rich HTTP/1.0 and HTTP/1.1 support. We fair well in various tests like CoAdvisor.</p><p># Plugin architecture, making it easy (well, easier) to extend and customize your server.</p><p># Well documented.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/apache">apache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/proxy">proxy</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/trafficserver">trafficserver</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058569740">Copy</a> | 
<a href="http://blogmarks.net/link/3398658">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/mozkart/mark/1058563012">
<title>CSS Tools: Reset CSS</title>
<link>http://meyerweb.com/eric/tools/css/reset/</link>
<description>The goal of a reset stylesheet is to reduce browser inconsistencies in things like default line heights, margins and font sizes of headings, and so on. The general reasoning behind this was discussed in a May 2007 post, if you're interested. Reset styles quite often appear in CSS frameworks, and the original &quot;meyerweb reset&quot; found its way into Blueprint, among others.

The reset styles given here are intentionally very generic. There isn't any default color or background set for the body element, for example. I don't particularly recommend that you just use this in its unaltered state in your own projects. It should be tweaked, edited, extended, and otherwise tuned to match your specific reset baseline. Fill in your preferred colors for the page, links, and so on.

In other words, this is a starting point, not a self-contained black box of no-touchiness.</description>
<dc:date>2009-10-25T10:27:50Z</dc:date>
<dc:author>mozkart</dc:author>
<dc:subject>css</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://meyerweb.com/eric/tools/css/reset/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/25/f1127eb1588ba86a4ccf6827eca211a7.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://meyerweb.com/eric/tools/css/reset/">CSS Tools: Reset CSS</a></h4>
 
by <a href="http://blogmarks.net/user/mozkart">mozkart</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2724527">1 other(s)</a> 
<p class="description">The goal of a reset stylesheet is to reduce browser inconsistencies in things like default line heights, margins and font sizes of headings, and so on. The general reasoning behind this was discussed in a May 2007 post, if you're interested. Reset styles quite often appear in CSS frameworks, and the original "meyerweb reset" found its way into Blueprint, among others.

The reset styles given here are intentionally very generic. There isn't any default color or background set for the body element, for example. I don't particularly recommend that you just use this in its unaltered state in your own projects. It should be tweaked, edited, extended, and otherwise tuned to match your specific reset baseline. Fill in your preferred colors for the page, links, and so on.

In other words, this is a starting point, not a self-contained black box of no-touchiness.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/css">css</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058563012">Copy</a> | 
<a href="http://blogmarks.net/link/2724527">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058550434">
<title>Applying the Web to Enterprise IT: Location Header Semantics</title>
<link>http://algermissen.blogspot.com/2009/09/location-header-semantics.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;Depending on the response's HTTP status the Location header has slightly different impact on the client's application state. The following table summarizes what I extracted from the HTTP spec.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-10-15T01:59:38Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>http</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://algermissen.blogspot.com/2009/09/location-header-semantics.html"><img border="0" src="http://blogmarks.net/screenshots/2009/10/15/e625f10fa9a7adb7312f466db44ce0f1.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://algermissen.blogspot.com/2009/09/location-header-semantics.html">Applying the Web to Enterprise IT: Location Header Semantics</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>Depending on the response's HTTP status the Location header has slightly different impact on the client's application state. The following table summarizes what I extracted from the HTTP spec.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/http">http</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058550434">Copy</a> | 
<a href="http://blogmarks.net/link/3383774">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/kuroyagi/mark/1058549985">
<title>The State Of Search: Q3 Data From Efficient Fronter And SearchIgnite</title>
<link>http://searchengineland.com/the-state-of-search-q3-data-from-efficient-fronter-and-searchignite-27657</link>
<description>&quot;The two data sets are based on client search campaigns managed by both firms.&quot;
... Google 75%, Yahoo! 20%, Microsoft 5%</description>
<dc:date>2009-10-14T10:58:29Z</dc:date>
<dc:author>kuroyagi</dc:author>
<dc:subject>search ads, google, yahoo!, microsoft</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://searchengineland.com/the-state-of-search-q3-data-from-efficient-fronter-and-searchignite-27657"><img border="0" src="http://blogmarks.net/screenshots/2009/10/14/55d78ace5c8bb375ae118bc29d5fa1c0.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://searchengineland.com/the-state-of-search-q3-data-from-efficient-fronter-and-searchignite-27657">The State Of Search: Q3 Data From Efficient Fronter And SearchIgnite</a></h4>
 
by <a href="http://blogmarks.net/user/kuroyagi">kuroyagi</a> 
<p class="description">"The two data sets are based on client search campaigns managed by both firms."
... Google 75%, Yahoo! 20%, Microsoft 5%</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/search%2Bads">search ads</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/yahoo%2521">yahoo!</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/microsoft">microsoft</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058549985">Copy</a> | 
<a href="http://blogmarks.net/link/3383419">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/danijelzi/mark/1058542963">
<title>Dell OptiPlex 780 Desktop</title>
<link>http://getitequipped.com/dell-optiplex-780.html</link>
<description>The Dell OptiPlex 780 is the company’s new business PC, featuring Intel technology.

The system is based on the Intel Q45 chipset and features an Intel Core 2 Quad, Core 2 Duo, Pentium Dual Core or Celeron CPU and up to 8GB of Non-ECC DDR3 1066MHz memory. The OptiPlex 780 is configurable with up to two 3.5- or 2.5-inch storage units, including standard hard drives and solid state drives. The drives can be configured without RAID or in RAID 0 and 1 modes. Optical drive options include a DVD ROM or a DVD burner, but the system can be also configured without optical device.</description>
<dc:date>2009-10-08T20:24:31Z</dc:date>
<dc:author>danijelzi</dc:author>
<dc:subject>dell, optiplex 780, desktop, pc, tower, intel, chipset, system, business</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://getitequipped.com/dell-optiplex-780.html"><img border="0" src="http://blogmarks.net/screenshots/2009/10/08/5fe870bae71708cb4a0f87c3f011d282.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://getitequipped.com/dell-optiplex-780.html">Dell OptiPlex 780 Desktop</a></h4>
 
by <a href="http://blogmarks.net/user/danijelzi">danijelzi</a> 
<p class="description">The Dell OptiPlex 780 is the company’s new business PC, featuring Intel technology.

The system is based on the Intel Q45 chipset and features an Intel Core 2 Quad, Core 2 Duo, Pentium Dual Core or Celeron CPU and up to 8GB of Non-ECC DDR3 1066MHz memory. The OptiPlex 780 is configurable with up to two 3.5- or 2.5-inch storage units, including standard hard drives and solid state drives. The drives can be configured without RAID or in RAID 0 and 1 modes. Optical drive options include a DVD ROM or a DVD burner, but the system can be also configured without optical device.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dell">dell</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/optiplex%2B780">optiplex 780</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/desktop">desktop</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/pc">pc</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tower">tower</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/intel">intel</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/chipset">chipset</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/system">system</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/business">business</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058542963">Copy</a> | 
<a href="http://blogmarks.net/link/3377528">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/tadeufilippini/mark/1058501395">
<title>Cambridge Grammar for First Certificate (book audio)</title>
<link>http://www.ingilizcepratik.net/cambridge-grammar-for-first-certificate-book-audio-t-18386.html</link>
<description>Cambridge Grammar for First Certificate (book audio)

Intermediate to Upper-intermediate

This book provides complete coverage of the grammar needed for the Cambridge FCE exam, and develops listening skills at the same time. It includes the full range of FCE exam tasks from the Reading, Writing, Listening, and Use of English papers, and contains helpful grammar explanations and a grammar glossary.

Contents
1. Present tenses: Present simple, present continuous, state verbs;
2. Past tenses: Past simple, past continuous, used to (and to be used to), would;
3. Present perfect simple and past simple: Present perfect and past simple, present perfect simple and continuous;
4. Past perfect: Past perfect simple and continuous;
5. Future 1: Present tenses, will, future continuous;
6. Future 2: Going to, future in the past, present after time adverbs, future perfect, to be about to;
7. Adjectives: Comparative and superlative adjectives, position, order, adjectives ending in -ing and -ed;
8. Adverbs: Formation, adverbs and adjectives easily confused, comparative and superlative adverbs, modifiers, position;
9. Questions: Yes / no questions, short answers, question words, question tags, agreeing;
10. Countable and uncountable nouns, articles: Countable and uncountable nouns, a, the and no article, special uses articles;
11. Pronouns and determiners: Possessives, reflexive pronouns, each other etc, there and it, someone etc, all, most and some, each and every, both, neither etc;
12. Modals 1: Use of modals, obligation, necessity;
13. Modals 2: Permission, requests, offers, suggestions, orders, advice;
14. Modals 3: Ability, deduction: certainty, probability and possibility;
15. Passive: Passive, to have something done;
16. Reported speech: Reporting about the past, reporting about the present, verbs used for reporting, questions;
17. Verbs followed by to-infinitive or -ing: Verb + to-infinitive, verb + infinitive without to, verb + -ing, verb + object + to-infinitive, verb + that, adjectives;
18. Phrasal verbs: Meaning and form, verb + preposition, verb + adverb, verb + preposition + adverb;
19. Conditionals 1: Zero, first, second and third conditionals, mixed conditionals;
20. Conditionals 2: Unless, in case, as / so long as, provided that, I wish / if only, it’s time, I’d rather, otherwise / or else; 21. Prepositions 1: Prepositions of place and time;
22. Prepositions 2: Prepositions which follow verbs and adjectives, prepositions to express who, how and why, expressions with prepositions;
23. Relative clauses: Defining and non-defining relative clauses, relative pronouns and prepositions;
24. Linking words 1: Because, as and since, so and therefore, in order to, to + infinitive and so (that), so and such, enough and too;
25. Linking words 2: In spite of and despite, but, although and though, even though and even if, participle clauses, before and after + -ing, when, while and since + -ing.
</description>
<dc:date>2009-09-13T00:45:37Z</dc:date>
<dc:author>tadeufilippini</dc:author>
<dc:subject>cambridge firstcertificate, cambridge grammar, grammar cambridge, ingilizcepratik english, ingilizcepratik, english ingilizcepratik, certificate, first certificate, certificate first, firstcertificate, firstcertificate cambridge</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ingilizcepratik.net/cambridge-grammar-for-first-certificate-book-audio-t-18386.html"><img border="0" src="http://blogmarks.net/screenshots/2009/09/13/ddeb5a6bef512650236b8b650352f038.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ingilizcepratik.net/cambridge-grammar-for-first-certificate-book-audio-t-18386.html">Cambridge Grammar for First Certificate (book audio)</a></h4>
 
by <a href="http://blogmarks.net/user/tadeufilippini">tadeufilippini</a> 
<p class="description">Cambridge Grammar for First Certificate (book audio)

Intermediate to Upper-intermediate

This book provides complete coverage of the grammar needed for the Cambridge FCE exam, and develops listening skills at the same time. It includes the full range of FCE exam tasks from the Reading, Writing, Listening, and Use of English papers, and contains helpful grammar explanations and a grammar glossary.

Contents
1. Present tenses: Present simple, present continuous, state verbs;
2. Past tenses: Past simple, past continuous, used to (and to be used to), would;
3. Present perfect simple and past simple: Present perfect and past simple, present perfect simple and continuous;
4. Past perfect: Past perfect simple and continuous;
5. Future 1: Present tenses, will, future continuous;
6. Future 2: Going to, future in the past, present after time adverbs, future perfect, to be about to;
7. Adjectives: Comparative and superlative adjectives, position, order, adjectives ending in -ing and -ed;
8. Adverbs: Formation, adverbs and adjectives easily confused, comparative and superlative adverbs, modifiers, position;
9. Questions: Yes / no questions, short answers, question words, question tags, agreeing;
10. Countable and uncountable nouns, articles: Countable and uncountable nouns, a, the and no article, special uses articles;
11. Pronouns and determiners: Possessives, reflexive pronouns, each other etc, there and it, someone etc, all, most and some, each and every, both, neither etc;
12. Modals 1: Use of modals, obligation, necessity;
13. Modals 2: Permission, requests, offers, suggestions, orders, advice;
14. Modals 3: Ability, deduction: certainty, probability and possibility;
15. Passive: Passive, to have something done;
16. Reported speech: Reporting about the past, reporting about the present, verbs used for reporting, questions;
17. Verbs followed by to-infinitive or -ing: Verb + to-infinitive, verb + infinitive without to, verb + -ing, verb + object + to-infinitive, verb + that, adjectives;
18. Phrasal verbs: Meaning and form, verb + preposition, verb + adverb, verb + preposition + adverb;
19. Conditionals 1: Zero, first, second and third conditionals, mixed conditionals;
20. Conditionals 2: Unless, in case, as / so long as, provided that, I wish / if only, it’s time, I’d rather, otherwise / or else; 21. Prepositions 1: Prepositions of place and time;
22. Prepositions 2: Prepositions which follow verbs and adjectives, prepositions to express who, how and why, expressions with prepositions;
23. Relative clauses: Defining and non-defining relative clauses, relative pronouns and prepositions;
24. Linking words 1: Because, as and since, so and therefore, in order to, to + infinitive and so (that), so and such, enough and too;
25. Linking words 2: In spite of and despite, but, although and though, even though and even if, participle clauses, before and after + -ing, when, while and since + -ing.
</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cambridge%2Bfirstcertificate">cambridge firstcertificate</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cambridge%2Bgrammar">cambridge grammar</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/grammar%2Bcambridge">grammar cambridge</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ingilizcepratik%2Benglish">ingilizcepratik english</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ingilizcepratik">ingilizcepratik</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/english%2Bingilizcepratik">english ingilizcepratik</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/certificate">certificate</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/first%2Bcertificate">first certificate</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/certificate%2Bfirst">certificate first</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/firstcertificate">firstcertificate</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/firstcertificate%2Bcambridge">firstcertificate cambridge</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058501395">Copy</a> | 
<a href="http://blogmarks.net/link/3341046">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/access2/mark/1058499727">
<title>Tennessee Valley Old Time Fiddler's Convention</title>
<link>http://www.squidoo.com/TVOTFC</link>
<description>The Tennessee Valley Old Time Fiddler's Convention is held at Athens State University in Athens, Alabama on the first full weekend in October.  Contestants compete for prize money in 15 categories, including several fiddle categories, guitar, harmonica, mandolin, old-time singing, banjo, old-time string band, blugrass band, and buck dancing.  Proceeds from the event support various Athens State student organizations and a scholarship fund.</description>
<dc:date>2009-09-11T08:46:53Z</dc:date>
<dc:author>access2</dc:author>
<dc:subject>fiddler's conventions, Bluegrass, fiddle contests, folk music, country music, Athens State College</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.squidoo.com/TVOTFC"><img border="0" src="http://blogmarks.net/screenshots/2009/09/11/507b1c22b2530436ca1cdc3f38ea10c7.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.squidoo.com/TVOTFC">Tennessee Valley Old Time Fiddler's Convention</a></h4>
 
by <a href="http://blogmarks.net/user/access2">access2</a> 
<p class="description">The Tennessee Valley Old Time Fiddler's Convention is held at Athens State University in Athens, Alabama on the first full weekend in October.  Contestants compete for prize money in 15 categories, including several fiddle categories, guitar, harmonica, mandolin, old-time singing, banjo, old-time string band, blugrass band, and buck dancing.  Proceeds from the event support various Athens State student organizations and a scholarship fund.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/fiddler%2527s%2Bconventions">fiddler's conventions</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Bluegrass">Bluegrass</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/fiddle%2Bcontests">fiddle contests</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/folk%2Bmusic">folk music</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/country%2Bmusic">country music</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Athens%2BState%2BCollege">Athens State College</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058499727">Copy</a> | 
<a href="http://blogmarks.net/link/3339708">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/newandforever/mark/1058490114">
<title>Georgia State Federal Credit Union</title>
<link>http://dir.artmam.com/Credit_Union-4.htm</link>
<description>Georgia State Federal Credit Union</description>
<dc:date>2009-09-02T17:35:27Z</dc:date>
<dc:author>newandforever</dc:author>
<dc:subject>technology, software, sports, videos, web, video, tv, компании, imported, ildarakbulat, bookmarks, credit, union, колыма, social, site</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://dir.artmam.com/Credit_Union-4.htm"><img border="0" src="http://blogmarks.net/screenshots/2009/09/02/91b27b79028099317f8b4f72e2cde199.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://dir.artmam.com/Credit_Union-4.htm">Georgia State Federal Credit Union</a></h4>
 
by <a href="http://blogmarks.net/user/newandforever">newandforever</a> 
<p class="description">Georgia State Federal Credit Union</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/technology">technology</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/software">software</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sports">sports</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/videos">videos</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/video">video</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tv">tv</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/%25D0%25BA%25D0%25BE%25D0%25BC%25D0%25BF%25D0%25B0%25D0%25BD%25D0%25B8%25D0%25B8">компании</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/imported">imported</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ildarakbulat">ildarakbulat</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bookmarks">bookmarks</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/credit">credit</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/union">union</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/%25D0%25BA%25D0%25BE%25D0%25BB%25D1%258B%25D0%25BC%25D0%25B0">колыма</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/social">social</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/site">site</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058490114">Copy</a> | 
<a href="http://blogmarks.net/link/3331929">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/touristic/mark/1058486570">
<title>Official State of Montana Vacation, Recreation, Accommodations and Travel Information Website</title>
<link>http://www.visitmt.com/</link>
<description></description>
<dc:date>2009-08-31T04:16:19Z</dc:date>
<dc:author>touristic</dc:author>
<dc:subject>cdt64, graphisme</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.visitmt.com/"><img border="0" src="http://blogmarks.net/screenshots/2009/08/31/ed840090e8b89e6a6387d706866004bc.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.visitmt.com/">Official State of Montana Vacation, Recreation, Accommodations and Travel Information Website</a></h4>
 
by <a href="http://blogmarks.net/user/touristic">touristic</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/637001">1 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cdt64">cdt64</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/graphisme">graphisme</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058486570">Copy</a> | 
<a href="http://blogmarks.net/link/637001">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/newandforever/mark/1058482897">
<title>Homes for sale near chico state</title>
<link>http://viselka.com/Chico_Homes.htm</link>
<description>Homes for sale near chico state</description>
<dc:date>2009-08-27T15:57:35Z</dc:date>
<dc:author>newandforever</dc:author>
<dc:subject>Homes for sale near chico state, state, Chico, categorycat, bookmarks, homes, for, sale, near</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://viselka.com/Chico_Homes.htm"><img border="0" src="http://blogmarks.net/screenshots/2009/08/27/0fffb174d473150deaf1fcb1436cc16f.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://viselka.com/Chico_Homes.htm">Homes for sale near chico state</a></h4>
 
by <a href="http://blogmarks.net/user/newandforever">newandforever</a> 
<p class="description">Homes for sale near chico state</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Homes%2Bfor%2Bsale%2Bnear%2Bchico%2Bstate">Homes for sale near chico state</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/state">state</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Chico">Chico</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/categorycat">categorycat</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bookmarks">bookmarks</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/homes">homes</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/for">for</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sale">sale</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/near">near</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058482897">Copy</a> | 
<a href="http://blogmarks.net/link/3325812">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Spone/mark/1058461149">
<title>a textile editor - built over html5 canvas</title>
<link>http://guillaume.bort.fr/textile-editor/</link>
<description> I'm pretty sure that textile is the right way to produce content for the web, and that WYSIWYG editors are bad for your website.  But editing a large chunk of textile using a textarea is not fun. I usually use Textmate to edit textile content, and wanted to reproduce the same feeling inside a browser.

The best online text editor is currently Bespin and I gave it a try. Unfortunately, the current state of bespin make it pretty difficult to embed the editor itself in a standalone way. Moreover I needed specifics features like 'soft wrap' that is totally required to edit some textile content.

So I took the Bespin way, and started to hack using javascript and HTML5 canvas to create a simple, standalone and totally embeddable textile editor for the web. </description>
<dc:date>2009-08-10T08:12:05Z</dc:date>
<dc:author>Spone</dc:author>
<dc:subject>canvas, éditeur de texte, html5, javascript, script</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://guillaume.bort.fr/textile-editor/"><img border="0" src="http://blogmarks.net/screenshots/2009/08/10/1ebb2099f70ade4f300daf8c62f7bcc5.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://guillaume.bort.fr/textile-editor/">a textile editor - built over html5 canvas</a></h4>
 
by <a href="http://blogmarks.net/user/Spone">Spone</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3308235">2 other(s)</a> 
<p class="description"> I'm pretty sure that textile is the right way to produce content for the web, and that WYSIWYG editors are bad for your website.  But editing a large chunk of textile using a textarea is not fun. I usually use Textmate to edit textile content, and wanted to reproduce the same feeling inside a browser.

The best online text editor is currently Bespin and I gave it a try. Unfortunately, the current state of bespin make it pretty difficult to embed the editor itself in a standalone way. Moreover I needed specifics features like 'soft wrap' that is totally required to edit some textile content.

So I took the Bespin way, and started to hack using javascript and HTML5 canvas to create a simple, standalone and totally embeddable textile editor for the web. </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/canvas">canvas</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/%25C3%25A9diteur%2Bde%2Btexte">éditeur de texte</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html5">html5</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/javascript">javascript</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/script">script</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058461149">Copy</a> | 
<a href="http://blogmarks.net/link/3308235">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/CharlyBr/mark/1058447791">
<title>RethinkDB - The database for solid state drives.</title>
<link>http://www.rethinkdb.com/</link>
<description></description>
<dc:date>2009-07-29T08:28:56Z</dc:date>
<dc:author>CharlyBr</dc:author>
<dc:subject>database, mysql, RethinkDB, storage engine</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.rethinkdb.com/"><img border="0" src="http://blogmarks.net/screenshots/2009/07/29/30566cbc3197f7a9b189bfba03ce61c0.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.rethinkdb.com/">RethinkDB - The database for solid state drives.</a></h4>
 
by <a href="http://blogmarks.net/user/CharlyBr">CharlyBr</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3300530">2 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/database">database</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mysql">mysql</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/RethinkDB">RethinkDB</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/storage%2Bengine">storage engine</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058447791">Copy</a> | 
<a href="http://blogmarks.net/link/3300530">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058442031">
<title>Semantosoph - The Semantic Web Landscape 2009</title>
<link>http://semantosoph.net/2009/7/19/the-semantic-web-landscape-2009</link>
<description>&lt;blockquote&gt;&lt;p&gt;survey of the technologies, tools, and state of the world with respect to the Semantic Web as of the first half of 2009&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-07-26T16:10:46Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>websemantique</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://semantosoph.net/2009/7/19/the-semantic-web-landscape-2009"><img border="0" src="http://blogmarks.net/screenshots/2009/07/26/1890842c71e9a914c5cef326568f0d97.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://semantosoph.net/2009/7/19/the-semantic-web-landscape-2009">Semantosoph - The Semantic Web Landscape 2009</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>survey of the technologies, tools, and state of the world with respect to the Semantic Web as of the first half of 2009</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/websemantique">websemantique</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058442031">Copy</a> | 
<a href="http://blogmarks.net/link/3295673">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/br1o/mark/1058556670">
<title>Feature Detection: State of the Art Browser Scripting</title>
<link>http://peter.michaux.ca/articles/feature-detection-state-of-the-art-browser-scripting</link>
<description></description>
<dc:date>2009-07-21T01:06:08Z</dc:date>
<dc:author>br1o</dc:author>
<dc:subject>dev, code, programming, feature, feature-detection, webdevelopment, debugging, detection, scripting, compatible, coding, browsers, browser, script, javascript</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://peter.michaux.ca/articles/feature-detection-state-of-the-art-browser-scripting"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://peter.michaux.ca/articles/feature-detection-state-of-the-art-browser-scripting">Feature Detection: State of the Art Browser Scripting</a></h4>
 
by <a href="http://blogmarks.net/user/br1o">br1o</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dev">dev</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/code">code</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/programming">programming</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/feature">feature</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/feature-detection">feature-detection</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webdevelopment">webdevelopment</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/debugging">debugging</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/detection">detection</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/scripting">scripting</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/compatible">compatible</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/coding">coding</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/browsers">browsers</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/browser">browser</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/script">script</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/javascript">javascript</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058556670">Copy</a> | 
<a href="http://blogmarks.net/link/3389071">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/gympie/mark/1058435213">
<title>Remarks by The Honourable Neil J.Turner, Speaker of the Queensland Parliament</title>
<link>http://www.owenguns.com/important-firearm-information/remarks-by-the-honourable-neil-jturner-speaker-of-the-queensland-parliament/</link>
<description>Remarks by The Honourable Neil J.Turner, Speaker of the Queensland Parliament, on the Bill that would implement Australia&amp;#8217;s gun-control measures in the State of Queensland

Hon. N. J. Turner (Nicklin) (3.51 p.m.): In answer to the honourable memb...</description>
<dc:date>2009-07-19T21:28:17Z</dc:date>
<dc:author>gympie</dc:author>
<dc:subject>Riflescope Sale, Black Powder Guns, ammo, binoculars, Target Shooting, telescopic sights, .22 rimfire Rifles, Air Rifles, bullets, Gun books</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.owenguns.com/important-firearm-information/remarks-by-the-honourable-neil-jturner-speaker-of-the-queensland-parliament/"><img border="0" src="http://blogmarks.net/screenshots/2009/07/19/f7180ef55bf30c6a9afc8210a7ba90d4.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.owenguns.com/important-firearm-information/remarks-by-the-honourable-neil-jturner-speaker-of-the-queensland-parliament/">Remarks by The Honourable Neil J.Turner, Speaker of the Queensland Parliament</a></h4>
 
by <a href="http://blogmarks.net/user/gympie">gympie</a> 
<p class="description">Remarks by The Honourable Neil J.Turner, Speaker of the Queensland Parliament, on the Bill that would implement Australia&#8217;s gun-control measures in the State of Queensland

Hon. N. J. Turner (Nicklin) (3.51 p.m.): In answer to the honourable memb...</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Riflescope%2BSale">Riflescope Sale</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Black%2BPowder%2BGuns">Black Powder Guns</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ammo">ammo</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/binoculars">binoculars</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Target%2BShooting">Target Shooting</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/telescopic%2Bsights">telescopic sights</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/.22%2Brimfire%2BRifles">.22 rimfire Rifles</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Air%2BRifles">Air Rifles</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bullets">bullets</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Gun%2Bbooks">Gun books</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058435213">Copy</a> | 
<a href="http://blogmarks.net/link/3290001">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ms_michel/mark/1058428675">
<title>Wean Yourselves off View State From the Start</title>
<link>http://aspnetresources.com/blog/wean_yourselves_off_view_state.aspx</link>
<description>enableViewState=&quot;false&quot; : un point de départ indispensable quand on veut bien faire les choses
</description>
<dc:date>2009-07-15T09:32:24Z</dc:date>
<dc:author>ms_michel</dc:author>
<dc:subject>.net</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://aspnetresources.com/blog/wean_yourselves_off_view_state.aspx"><img border="0" src="http://blogmarks.net/screenshots/2009/07/15/484c911998e51eb587151ab5259b3a59.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://aspnetresources.com/blog/wean_yourselves_off_view_state.aspx">Wean Yourselves off View State From the Start</a></h4>
 
by <a href="http://blogmarks.net/user/ms_michel">ms_michel</a> 
<p class="description">enableViewState="false" : un point de départ indispensable quand on veut bien faire les choses
</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/.net">.net</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058428675">Copy</a> | 
<a href="http://blogmarks.net/link/3285824">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058428420">
<title>Joe Gregorio | BitWorking | Wave Protocol Thoughts</title>
<link>http://bitworking.org/news/431/wave-first-thoughts#X5</link>
<description>&lt;blockquote&gt;&lt;p&gt;What makes portions of the Wave API opaque is the parts where the developers gave into temptation and serialized internal state (inside-out) vs designing an API (outside-in).&lt;/p&gt;&lt;/blockquote&gt;

interieur-exterieur comme approche d'une API</description>
<dc:date>2009-07-15T03:50:57Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>api, bestpractices, googlewave, http, rest</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://bitworking.org/news/431/wave-first-thoughts#X5"><img border="0" src="http://blogmarks.net/screenshots/2009/07/15/bc4864a93be16b6e6a0520c651012445.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://bitworking.org/news/431/wave-first-thoughts#X5">Joe Gregorio | BitWorking | Wave Protocol Thoughts</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>What makes portions of the Wave API opaque is the parts where the developers gave into temptation and serialized internal state (inside-out) vs designing an API (outside-in).</p></blockquote>

interieur-exterieur comme approche d'une API</div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/api">api</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bestpractices">bestpractices</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/googlewave">googlewave</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/http">http</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/rest">rest</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058428420">Copy</a> | 
<a href="http://blogmarks.net/link/3285615">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058428366">
<title>Good design: Dieter Rams' ten commandments</title>
<link>http://www.vitsoe.com/en/gb/about/gooddesign</link>
<description>&lt;blockquote&gt;&lt;p&gt;Back in the early 1980s, Dieter Rams was becoming increasingly concerned by the state of the world around him – “an impenetrable confusion of forms, colours and noises.” Aware that he was a significant contributor to that world, he asked himself an important question: is my design good design?&lt;/p&gt;&lt;p&gt;As good design cannot be measured in a finite way he set about expressing the ten most important criteria for what he considered was good design. Subsequently they have become known as the ‘Ten commandments’.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-07-15T01:55:11Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>design</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.vitsoe.com/en/gb/about/gooddesign"><img border="0" src="http://blogmarks.net/screenshots/2009/07/15/17db3fc31c8cb9f5285e14b5438c28ba.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.vitsoe.com/en/gb/about/gooddesign">Good design: Dieter Rams' ten commandments</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>Back in the early 1980s, Dieter Rams was becoming increasingly concerned by the state of the world around him – “an impenetrable confusion of forms, colours and noises.” Aware that he was a significant contributor to that world, he asked himself an important question: is my design good design?</p><p>As good design cannot be measured in a finite way he set about expressing the ten most important criteria for what he considered was good design. Subsequently they have become known as the ‘Ten commandments’.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/design">design</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058428366">Copy</a> | 
<a href="http://blogmarks.net/link/3285567">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Spone/mark/1058420215">
<title>Bugs Everywhere</title>
<link>http://bugseverywhere.org/be/show/HomePage</link>
<description>Bugs Everywhere is a “distributed bugtracker”, designed to complement distributed revision control systems. By using distributed revision control as a backend for bug state, we gain several convenient features:

    * Bugs and code that live on branches are tracked together—when a branch is merged, both the code changes and bug changes that the branch contains are merged alongside each other. We no longer have to be confused about whether a fix that is applied to the development branch but not yet present in the production branch means that our bug is “fixed”.
    * Users can fully modify bug state while offline, unlike with many centralized bugtrackers.
    * When a user checks out your source code, she gets the current bug state for free.
    * We can still provide access to a friendly web interface for users—in this model, a web interface becomes just another client that merges with the main repository.</description>
<dc:date>2009-07-07T13:47:51Z</dc:date>
<dc:author>Spone</dc:author>
<dc:subject>bugtracker, mercurial, git, python, versioncontrol</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://bugseverywhere.org/be/show/HomePage"><img border="0" src="http://blogmarks.net/screenshots/2009/07/15/6ece6b82efc97e77a278dbec4a1c4b62.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://bugseverywhere.org/be/show/HomePage">Bugs Everywhere</a></h4>
 
by <a href="http://blogmarks.net/user/Spone">Spone</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3278848">1 other(s)</a> 
<p class="description">Bugs Everywhere is a “distributed bugtracker”, designed to complement distributed revision control systems. By using distributed revision control as a backend for bug state, we gain several convenient features:

    * Bugs and code that live on branches are tracked together—when a branch is merged, both the code changes and bug changes that the branch contains are merged alongside each other. We no longer have to be confused about whether a fix that is applied to the development branch but not yet present in the production branch means that our bug is “fixed”.
    * Users can fully modify bug state while offline, unlike with many centralized bugtrackers.
    * When a user checks out your source code, she gets the current bug state for free.
    * We can still provide access to a friendly web interface for users—in this model, a web interface becomes just another client that merges with the main repository.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bugtracker">bugtracker</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mercurial">mercurial</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/git">git</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/python">python</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/versioncontrol">versioncontrol</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058420215">Copy</a> | 
<a href="http://blogmarks.net/link/3278848">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/fotopol/mark/1058419489">
<title>BioLinks - Web Links for Biology Students</title>
<link>http://www.mnstate.edu/weibust/internetresbiostu.htm</link>
<description>| Biosciences Home | Minnesota State University Moorhead Home | </description>
<dc:date>2009-07-06T19:22:47Z</dc:date>
<dc:author>fotopol</dc:author>
<dc:subject>10, web, ressources, biologie, insectes, Botanique, MEB, sem</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.mnstate.edu/weibust/internetresbiostu.htm"><img border="0" src="http://blogmarks.net/screenshots/2009/07/06/a7cbd91264bbd43abece369bfd286879.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.mnstate.edu/weibust/internetresbiostu.htm">BioLinks - Web Links for Biology Students</a></h4>
 
by <a href="http://blogmarks.net/user/fotopol">fotopol</a> 
<p class="description">| Biosciences Home | Minnesota State University Moorhead Home | </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/10">10</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ressources">ressources</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/biologie">biologie</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/insectes">insectes</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Botanique">Botanique</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/MEB">MEB</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sem">sem</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058419489">Copy</a> | 
<a href="http://blogmarks.net/link/3278296">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/newandforever/mark/1058417949">
<title>tiaa cref ohio state university</title>
<link>http://viselka.com/University_Faculty.htm</link>
<description>tiaa cref ohio state university</description>
<dc:date>2009-07-09T15:51:12Z</dc:date>
<dc:author>newandforever</dc:author>
<dc:subject>tubaravara, cref, Ohio, state, university, tiaa, tiaa cref ohio state university</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://viselka.com/University_Faculty.htm"><img border="0" src="http://blogmarks.net/screenshots/2009/07/09/f2aea6bfea4cfea9e76a31f853ee9308.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://viselka.com/University_Faculty.htm">tiaa cref ohio state university</a></h4>
 
by <a href="http://blogmarks.net/user/newandforever">newandforever</a> 
<p class="description">tiaa cref ohio state university</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tubaravara">tubaravara</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cref">cref</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Ohio">Ohio</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/state">state</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/university">university</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tiaa">tiaa</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tiaa%2Bcref%2Bohio%2Bstate%2Buniversity">tiaa cref ohio state university</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058417949">Copy</a> | 
<a href="http://blogmarks.net/link/3277067">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/newandforever/mark/1058398471">
<title>apartments near cal state east bay</title>
<link>http://viselka.com/Cal_State_East_Bay.htm</link>
<description>apartments near cal state east bay</description>
<dc:date>2009-07-01T18:08:02Z</dc:date>
<dc:author>newandforever</dc:author>
<dc:subject>state, apartments, East, bay, sashatornadova, apartments near cal state east bay, Cal</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://viselka.com/Cal_State_East_Bay.htm"><img border="0" src="http://blogmarks.net/screenshots/2009/07/01/9e967c58be34f5b422782cd23cae028e.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://viselka.com/Cal_State_East_Bay.htm">apartments near cal state east bay</a></h4>
 
by <a href="http://blogmarks.net/user/newandforever">newandforever</a> 
<p class="description">apartments near cal state east bay</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/state">state</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/apartments">apartments</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/East">East</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bay">bay</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sashatornadova">sashatornadova</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/apartments%2Bnear%2Bcal%2Bstate%2Beast%2Bbay">apartments near cal state east bay</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Cal">Cal</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058398471">Copy</a> | 
<a href="http://blogmarks.net/link/3259749">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/jey/mark/1058544848">
<title>nothingmuch's perl blog: App::Prove::State rocks</title>
<link>http://blog.woobling.org/2009/06/appprovestate-rocks.html</link>
<description></description>
<dc:date>2009-06-27T16:00:42Z</dc:date>
<dc:author>jey</dc:author>
<dc:subject>perl, testing</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://blog.woobling.org/2009/06/appprovestate-rocks.html"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://blog.woobling.org/2009/06/appprovestate-rocks.html">nothingmuch's perl blog: App::Prove::State rocks</a></h4>
 
by <a href="http://blogmarks.net/user/jey">jey</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/perl">perl</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/testing">testing</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058544848">Copy</a> | 
<a href="http://blogmarks.net/link/3379082">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>