Benchmark-Perl-Formance-Cargo

 view release on metacpan or  search on metacpan

share/SpamAssassin/easy_ham/01855.19acbc78b4bb1959ace6f1ec1d6329e8  view on Meta::CPAN

index.html[2]. 
- _Les Orchard_: Per-post comment RSS feed[3]. 
- _Phil Wainewright_: The bare necessities of RSS[4] and What to do about RDF
[5]. The beginning of an RSS 2.0 best practices document. 
- _Jonathon Delacour_: Trying to score a goal[6]. “As the best and the 
brightest focus on the possibilities of FOAF, I turned my attention to 
yesterday's news: RSS.” No, RSS will always be today's news. Get it? 
Today's newzzz... Never mind. 
- Comments on Ben Hammersley's Friend of a Friend[7]. Various ways to link to a 
FOAF file from an RSS feed. 
- _Nicholas Chase_: The Web's future: XHTML 2.0[8]. We're losing backward 
compatibility, isn't that great? Well, he seems to think so. 
- mod_cc[9], a module for including copyright information in RDF documents such 
as RSS 1.0 feeds, and, I hope, FOAF files. 
- _Shelley Powers_: Who is your audience, and what are you trying to 
accomplish?[10] Addressing the growing identity crisis on the RSS-DEV mailing 
list[11]. Also the comments on Shelley's article[12]. 
- _Ian Hickson_: Pingback 1.0[13]. “The best thing about this idea is 
that unlike similar schemes like TrackBack, it is totally transparent to both 
users.” 
- New software helps in building of accessible web sites[14]. A press release 

share/SpamAssassin/easy_ham/01867.bef318a5c37fc91ac6973482f70e50ce  view on Meta::CPAN

writing a schema-aware aggregator that can try to figure out what it should do 
with new elements that it hasn't seen before. That's actually an interesting 
project with some potential for success, but at this point I'm sick of the 
whole thing, so I'll leave that project for someone else.” 
- _Aaron Swartz_: TRAMP: Makes RDF look like Python data structures[2]. 
“RDF/XML got you down? Tired of having to go through contortions to deal 
with data? Want to write Python and be standards-compatible at the same time? 
Need a module to implement the psuedo-code you had on your slides? TRAMP may or 
may not be the answer to these problems!” Complete with an example of 
parsing FOAF files. 
- _Dan Connolly_: HyperRDF: Using XHTML Authoring Tools with XSLT to produce 
RDF schemas[3]. “XML syntax is a little tedious, but lots of people are 
evidently willing and able of editing it by hand. RDF adds another layer of 
tedium, but there are still a few folks willing to write it by hand. I make 
heavy use of reification/quoting in my representation of logical formulas in 
RDF. This adds another layer of tedium that I find unmanageable, and I have 
been writing XML/SGML/HTML by hand for 10 years.” Also includes a cogent 
explanation of the obscure profile attribute in HTML. 

share/SpamAssassin/easy_ham/02246.b353269018884d01ee252bca5bd419ef  view on Meta::CPAN

From: diveintomark <rssfeeds@spamassassin.taint.org>
Subject: Microsoft redesign
Date: Fri, 04 Oct 2002 08:00:05 -0000
Content-Type: text/plain; encoding=utf-8

URL: http://diveintomark.org/archives/2002/10/03.html#microsoft_redesign
Date: 2002-10-03T14:42:29-05:00

_Jeffrey Zeldman_: Party like it's 1997[1]. &#8220;Microsoft has redesigned. 
Its new layout uses font tags and other deprecated junk straight out of the 
mid-1990s. ... When a W3C member company that helped create XHTML and CSS 
ignores or misuses those web standards on its corporate site, you have to 
wonder who didn't get the memo.&#8221; 

The new design also fails even the most basic accessibility tests[2]; the home 
page contains 80 instances of images without ALT text. This is the same basic 
failing for which the Sydney Organizing Committee for the Olympic Games was 
successfully sued in 2000[3]. 

Here is what microsoft.com looks like in a text-only browser[4]. (To better 
understand the experience, take a piece of paper and cover your entire monitor 

share/SpamAssassin/easy_ham/02378.ff357ba03232ac47ae4cbdf1a770cfc4  view on Meta::CPAN

The problem with that list of RSS deficiencies is that it is also a list of 
necessities—RSS has flourished in a way that no other syndication format 
has, not despite many of these qualities but because of them. The very 
weaknesses that make RSS so infuriating to serious practitioners also make it 
possible in the first place. 

- Removing length limitations on description and making title optional opened 
up RSS to a whole new category of producer: the weblogger. 
- Allowing encoded HTML in description let publishers reuse both their existing 
content and the existing RSS infrastructure, without requiring them to produce 
valid XHTML (which could be embedded directly into an XML document). Social 
mores, rather than technical rules, prevent producers from intentionally 
introducing security risks through malicious script tags or unpredictable 
display through unclosed HTML elements. 
- Few publishing tools can produce real conforming GUIDs, and it doesn't 
matter, because virtually all RSS parsers are written in high level languages 
where handling strings is more efficient than converting strings to bytecodes 
and handling bytecodes. As for dates, by convention an RSS document is laid out 
in reverse chronological order, and no one seems to be clamoring for more 
flexibility. 

share/SpamAssassin/spam_2/00280.3432009813aa8a8683c72ad31ce7e0e0  view on Meta::CPAN

Hurry while supplies Last=2E Free Gift Offer at my expense=2E
http://home=2Eattbi=2Ecom/~johnsonhomestor1/YOUR_COMPLIMENTARY_GIFT=2Ehtx




------=_NextPart_84815C5ABAF209EF376268C8
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1=2E0 Transitional//EN"
"http://www=2Ew3=2Eorg/TR/xhtml1/DTD/xhtml1-transitional=2Edtd">
<title>welcome letter</title>
<style type=3D"text/css">
 div=2Ec6 {color: #000000; text-align: center}
 span=2Ec5 {color: #000000}
 span=2Ec4 {color: #000000}
 div=2Ec3 {text-align: center}
 span=2Ec2 {color: #000000}
 span=2Ec1 {color: #000000}
</style>