Do you which to work online with (Keith Ceramic Materials Ltd) withoutquitting
your previous job?Here is an opurtunity for you to work andearn more without
stress. Our company is offering you the chance to workunder his organization and
to earn good living. If you are interestedworking with us, kindly get back to us
for more informations. Thank

I tried integrating Magpie to display a member's latest blog post next
to their names in a vBulletin forum and it worked for the most part.
However, there appears to be some conflict with MagPie breaking
vBulletin's AJAX code.

See this thread: http://www.vbulletin.org/forum/showthread.php?t=156372

Post #21 says:

"From what I can see, the Quick Reply function and edit functions using
AJAX still work, but they don't clean up the page they way they should
when you click the submit/ok buttons. Looks like the problem lies in
the Magpie fetch_rss function. It's beyond my coding skills to
diagnose/fix this problem."

Any ideas?

At the request of some readers, I have fixed the links to the ICE
standard in the RSS 1.0 spec. I can't imagine anyone would object, but
I thought I'd let people know.

--
Keep an eye on politics: http://watchdog.net/

Hi

On line 28 of rss_utils, under the function parse_w3cdtf, there's this regular
expression
$pat =
"/(\d{4})-(\d{2})-(\d{2})T(\d{2}):(\d{2})(:(\d{2}))?(?:([-+])(\d{2}):?(\d{2})|(Z\
))?/";

It should match the ISO 8601 date format (ex: 2005-07-26T12:16:26+02:00)

However, the parenthesis are wrong for the matching seconds. This way it will
produce a
":26" instead of the desired "26"

This of course makes the next function gmmktime fail.

You should fix the regular expression and keep the : out. Should be an easy fix.

> That's why RSS 1.1 has had such great longevity.  It's very easy to
> create extensions that fit into the framework.  Now, if you want to
> create one that's fully RDF-savvy it can get a bit more complex.
>
RSS 1.1 ??  Is that regarded as a viable format (I have not followed
this list for very long so I was not even aware of RSS 1.1)? Is it
widely supported? (Perhaps this was intended to be ironic & flew past
me??)

-Peter Keane
daseproject.org

> So, care to discuss what sort of data you're planning to integrate?
> There might be folks here with some suggestions/experience to offer on
> how to effectively get it all working.
>
> -Bill Kearney
> Syndic8.com
>

> That's why RSS 1.1 has had such great longevity.

Heh, brain fart.  That would be version 1.0, the true RSS standard.

--- In rss-dev@yahoogroups.com, "Jairus Pryor" <jairus@...> wrote:
>
> --- In rss-dev@yahoogroups.com, "Bill Kearney" <ml2_yahoo@> wrote:
> >
> > > ...so if I were to create an RSS 1.0 fork and/or modification
> >
> > Fork?  Good Lord, why?
>
> Masochism, mostly.

Heh.

> That, and a need to syndicate fairly specialized statistical data to
> modified tools that already speak RSS. (Fork is a strong word,
> actually. Extension is much more accurate.)

That's why RSS 1.1 has had such great longevity.  It's very easy to
create extensions that fit into the framework.  Now, if you want to
create one that's fully RDF-savvy it can get a bit more complex.

So, care to discuss what sort of data you're planning to integrate?
There might be folks here with some suggestions/experience to offer on
how to effectively get it all working.

-Bill Kearney
Syndic8.com

--- In rss-dev@yahoogroups.com, "Bill Kearney" <ml2_yahoo@...> wrote:
>
> > ...so if I were to create an RSS 1.0 fork and/or modification
>
> Fork?  Good Lord, why?


Masochism, mostly.

That, and a need to syndicate fairly specialized statistical data to
modified tools that already speak RSS. (Fork is a strong word,
actually. Extension is much more accurate.)

Jairus

> ...so if I were to create an RSS 1.0 fork and/or modification

Fork?  Good Lord, why?

-Bill Kearney
Syndic8.com

A quick and easy question, I'm sure it's been answered before, but
searching didn't turn up anything.

The RSS rights statement says:

-
Copyright © 2000 by the Authors.

Permission to use, copy, modify and distribute the RDF Site Summary
1.0 Specification and its accompanying documentation for any purpose
and without fee is hereby granted in perpetuity, provided that the
above copyright notice and this paragraph appear in all copies. The
copyright holders make no representation about the suitability of the
specification for any purpose. It is provided "as is" without
expressed or implied warranty.

This copyright applies to the RDF Site Summary 1.0 Specification and
accompanying documentation and does not extend to the RSS format itself.
-

...so if I were to create an RSS 1.0 fork and/or modification, I'm
have to display the rights statement and the copyright notice, where
the copyright notice of "the Authors" is (presumably) referring to the
authors of RSS, and not referring to me, even though it would be
posted on the new fork.

Second, what are the licensing implications of a fork? If I create
RSS-FOO 8.1, the rights statement is explicit that it's referring to
RSS 1.0. Can I then license RSS-FOO 8.1 under the LGPL or some such,
or (hypothetically) choose not to license it and sue anyone but me who
uses it? Or is the spirit of the notice that it's a share-alike
statement that all derivatives are bound by (even if that's not what
it says)?

As I said, I'm sure these questions have come up before, but I
couldn't find any answers to them.

Jairus

BlogTalk 2008
The 5th International Conference on Social Software
Cork, Ireland - 3-4 March 2008

http://blogtalk.net/

= Overview =

Following the international success of previous BlogTalk events in 2003,
2004, 2005 and 2006, the next BlogTalk - to be held in Cork, Ireland on
3-4 March 2008 - is continuing with its focus on social software, while
remaining committed to the diverse cultures, practices and tools of our
emerging networked society. The conference is designed to maintain a
sustainable dialog between developers, innovative academics and scholars
who study social software, practitioners and administrators in corporate
and educational settings, and other general members of the social
software community.

We invite you to submit a proposal for presentation at the BlogTalk 2008
conference. Possible areas include, but are not limited to:

     * Forms and consequences of emerging social software practices
     * Social software in enterprise and educational environments
     * The political impact of social software
     * Applications, prototypes, concepts and standards

= Participants and proposal categories =

Due to the interdisciplinary nature of the conference, audiences will
come from different fields of practice and will have different
professional backgrounds. We strongly encourage proposals to bridge
these cultural differences and to be understandable for all groups
alike. Along those lines, we will offer three different submission
categories:

     * Academic
     * Developer
     * Practitioner

For academics, BlogTalk is an ideal conference for presenting and
exchanging research work from current and future social software
projects at an international level. For developers, the conference is a
great opportunity to fly ideas, visions and prototypes in front of a
distinguished audience of peers, to discuss, to link-up and to learn
(developers may choose to give a practical demonstration rather than a
formal presentation if they so wish). For practitioners, this is a venue
to discuss use cases for social software and to report on any results
you may have with like-minded individuals.

= Submitting your proposals =

Please upload your submission along with some personal information at
the http://www.easychair.org/blogtalk2008/ site. You will receive a
confirmation of the arrival of your submission within three working
days. The submission deadline is November 16th, 2007. The length of the
proposal should be between two and four pages. BlogTalk is a
peer-reviewed conference.

= Timeline and important dates =

Proposal submission deadline: November 16th, 2007

Notification of acceptance or rejection: December 7th, 2007

Paper version due: January 7th, 2008

Presentations and abstracts on website due: February 7th, 2008

(We will work hard to endow a fund for supporting travel costs. As soon
as we review all of the papers we will be able to announce more details.)

= Chairs =

     * John Breslin
     * Thomas N. Burg
     * Tom Raftery
     * Jan Schmidt

= Programme Committee =

     * Stowe Boyd
     * Dan Brickley
     * Jyri Engeström
     * Jen Golbeck
     * Eugene Eric Kim
     * Kevin Marks
     * Peter Mika
     * José Luis Orihuela
     * Jeremy Ruston
     * Paolo Valdemarin
     * David Weinberger

Please visit our website at http://blogtalk.net for more information.

--
Dr. John Breslin
DERI, NUI Galway
http://sw.deri.org/~jbreslin/
john.breslin@...

Steven Clift wrote:

> Is there a standard that defines how news aggregators should request
> access to web feeds behind a login/password?

You can just use the standard HTTP authentication described in RFC2617.

http://www.ietf.org/rfc/rfc2617.txt

Regards
James

Is there a standard that defines how news aggregators should request
access to web feeds behind a login/password?

Our few private groups - http://forums.e-democracy.org - generate web
feeds which may be read by default browser-based feed readers and
there is no problem display them if someone stays logged in via the
browser.

However, I'd like to have the developer of the open source GroupServer
- http://groupserver.org - tool explore giving authenticated access to
Bloglines and other users of aggregators that supposedly support this
kind of access.

Steven Clift
E-Democracy.Org

<snip />

> The W3C validator at http://validator.w3.org/  handles HTML
> and XHTML but not RSS.
>
> As the validator homepage states, there are other services
> for validating content syndication formats, including one
> provided by the W3C at http://validator.w3.org/feed/ and
> http://www.feedvalidator.org/ (which look surprisingly similar :-))
>
> --
> Klaus Johannes Rusch
> KlausRusch@...
> http://www.atmedia.net/KlausRusch/
>

That explains that Klaus thanks. Two more quick questions persist: Is there
an XML validator on the web that shows the source that was validated? -- and
-- Would you know why the HTML generated by the validators we've just
discussed wrap HTML alt attribute text in brackets, e.g. alt="[Valid RSS]"?

<%= Clinton

Clinton Gallagher wrote:

>Could somebody submit the test cases to the W3 validator?
>
>* http://metromilwaukee.com/testRSS-1.xml
>* http://metromilwaukee.com/testRSS-2.xml
>
>And then explain what the validator is attempting to tell me so I can get
>valid results?
>
>
The W3C validator at http://validator.w3.org/  handles HTML and XHTML
but not RSS.

As the validator homepage states, there are other services for
validating content syndication formats, including one provided by the
W3C at http://validator.w3.org/feed/ and http://www.feedvalidator.org/
(which look surprisingly similar :-))

--
Klaus Johannes Rusch
KlausRusch@...
http://www.atmedia.net/KlausRusch/

I'm getting results from the W3 validator [1] I don't understand. I
understand what the error message says as it infers the Dublin Core
namespace is incorrect but I get the same results when that namespace is
removed.

Could somebody submit the test cases to the W3 validator?

* http://metromilwaukee.com/testRSS-1.xml
* http://metromilwaukee.com/testRSS-2.xml

And then explain what the validator is attempting to tell me so I can get
valid results?

<%= Clinton

[1] http://validator.w3.org/

> > Clinton Gallagher wrote:
> > So it seems to be a general consensus that CDATA within
> > the title and the description is widely supported at this
> > point in time...

> Jon's 1st reply:
> Personally, I tend to find it just as handy to escape & and <
> to &amp; and &lt; (and > to &gt; though in most cases that
> should be safe ...

Well Jon, I was thinking of using Regular Expressions to escape
the characters but a couple of test cases with the latest IE,
FF and OP browsers showed they do not parse the entities back
to their respective text characters. What a dilemma!

At the moment I'm considering doing nothing in the Title, using
CDATA in the Description and disallow XML in all other elements.

Clinton Gallagher wrote:
> So it seems to be a general consensus that CDATA within the title and the
> description is widely supported at this point in time as a means to allow
> users to submit data such as the word AT&T in a title or description? What
> are the generally accepted pitfalls of using CDATA?

It's pretty depressing that "widely supported" can even be talked about
in this case. It's 9 years since XML became a recommendation. There are
kids out there younger than XML that understand CDATA, and some of the
parsers don't. :(

Anyway the biggest pitfall I can see with CDATA at the authors side is
the belief that you can pass anything through without having to worry
about escaping anything - there is the exception of the string "]]>".
Now granted the string ]]> doesn't come up very much in normal
conversation, but it certainly can come up in technical posts, etc. and
of course Murphy's law applies - if there's a set of inputs that will
cause failure someone will give you that set of inputs.

As such you still have to do escaping with anything you are putting into
a CDATA section so that ]]> gets replaced with ]]>]<![CDATA[]> (there
are a couple of other workable equivalents).

Personally, I tend to find it just as handy to escape & and < to &amp;
and &lt; (and > to &gt; though in most cases that should be safe - but
again there are parsers that may think differently) especially since I
got into the habit of looking for those a long time ago when dealing
with HTML (not to say I never ever overlook that those characters could
be coming into a given piece of code, but I'm still well used to looking
out for them and not for ]]>

On 5/25/07, Clinton Gallagher <csgallagher@...> wrote:
>
> So it seems to be a general consensus that CDATA within the title and the
>  description is widely supported at this point in time as a means to allow
>  users to submit data such as the word AT&T in a title or description? What
>  are the generally accepted pitfalls of using CDATA?

This may be useful for you:

http://www.therssweblog.com/?guid=20070522124846

Regards,
Alan Dean
http://thoughtpad.net/alan-dean

So it seems to be a general consensus that CDATA within the title and the
description is widely supported at this point in time as a means to allow
users to submit data such as the word AT&T in a title or description? What
are the generally accepted pitfalls of using CDATA?

<%= Clinton

The replies to the question regarding the display of the channel's image has
been good news thank you.

Now, from a developer's perspective is using the channel image a good way to
record usage or are other tactics a better metric? When customers use a
service which generates a webfeed the customer's feed is served from their
servers so then what? I've considered hosting the channel's image would be a
reasonable method to record usage.

<%= Clinton

itunes does as does magpie parser if wanted when showing a feed on a website.

Bruce Prochnau

   ----- Original Message -----
   From: James Holderness
   To: rss-dev@yahoogroups.com
   Sent: Saturday, May 12, 2007 4:08 PM
   Subject: Re: [RSS-DEV] Using the channel image


   Clinton Gallagher wrote:
   > What's been learned when using the channel image? The browser
   > style sheets will not display it. Do any of the feed readers
   > done so?

   FWIW, I know there is some support for the channel image element in RSS 2.0
   feeds. I don't know whether the readers that support the RSS 2.0 element
   also support the 1.0 version, but I would think it's fairly likely.

   In my tests, Firefox displayed the image in its feed preview (but obviously
   not in LiveBookmarks); IE7 didn't display the image in its feed preview, but
   did show it when you subscribed to a feed; other readers I know of that
   support the image in some way include Abilon, Awasu, Bloglines, RssReader,
   RSS Bandit, SharpReader and YeahReader.

   Regards
   James





[Non-text portions of this message have been removed]

Clinton Gallagher wrote:
> What's been learned when using the channel image? The browser
> style sheets will not display it. Do any of the feed readers
> done so?

FWIW, I know there is some support for the channel image element in RSS 2.0
feeds. I don't know whether the readers that support the RSS 2.0 element
also support the 1.0 version, but I would think it's fairly likely.

In my tests, Firefox displayed the image in its feed preview (but obviously
not in LiveBookmarks); IE7 didn't display the image in its feed preview, but
did show it when you subscribed to a feed; other readers I know of that
support the image in some way include Abilon, Awasu, Bloglines, RssReader,
RSS Bandit, SharpReader and YeahReader.

Regards
James

What's been learned when using the channel image? The browser style sheets
will not display it. Do any of the feed readers done so?

I've been thinking of how a channel image may be used as a "web bug" to log
the usage of the web feed. I assume others have thought of this and have
tried doing so. What if anything is known of this usage?

<%= Clinton Gallagher

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the rss-dev
group.

   File        : /specification.pt.pdf
   Uploaded by : aaronswartz <aswartz@...>
   Description : partial portugeuese translation of spec

You can access this file at the URL:
http://groups.yahoo.com/group/rss-dev/files/specification.pt.pdf

To learn more about file sharing for your group, please visit:
http://help.yahoo.com/help/us/groups/files

Regards,

aaronswartz <aswartz@...>

[passing along per request]

---------- Forwarded message ----------
From: Teresa <tpereira@...>
Date: May 3, 2007 7:06 AM
Subject: RE: RSS 1.0 spec
To: Aaron Swartz <me@...>


Hi,

I attached a document with part of the RSS specification 1.0 translated to
Portuguese and therefore become this document available to the RSS 1.0
community.

In the head of the document I am just telling that "This document is the
translation in Portuguese of part of the specification of RDF Site Summary

(RSS) 1.0. This translation was concluded in December of 2006. The possible
detected mistakes in this document are of translator's responsibility and
they cannot be attributed in way to the work group RSS-DEV. The comments
concerning this translation should be addressed to Teresa Pereira
(tpereira[at]esce.ipvc.pt). The official version of part of this document is
the original version (in English) available in the following URL:"


Kindly regards,
Teresa Pereira


[Non-text portions of this message have been removed]

In the spec, these pages are linked:

Where to go for more...

     * RSS Info -- News and information on the RSS format
     * xmlhack
     * XMLfr

but there is absolutely no content...

Hi All,

I have tried parsing the example structure of the RDF files from dmoz
(rdf.dmoz.org) but it says : Fail to parse RDF and XML parsing failed.

I plan to parse the whole content but since the file is large, i am using so far
the example (http://rdf.dmoz.org/rdf/structure.example.txt) provided in the
website.
Has anyone managed to successfully parse the structure example? Care to share it
please...???
I have made some changes to the code but still failed..:((

hope to get some feedback soon.
thanks !


---------------------------------
All new Yahoo! Mail
---------------------------------
Get news delivered. Enjoy RSS feeds right on your Mail page.

[Non-text portions of this message have been removed]

To be a little clearer, and certainly not insulting, some years back several
modules were being discussed and proposed, some from within your own group. The
work this group has accomplished since that time apparently took the focus from
modules and development/approving them to Atom.  There are only so many hours in
a day...however, the modules which can be beneficial( and would have perhaps
proven timely for adoption) are needing an approval by this group to cultivate
wider gain and acceptance for RDF and Web 2.0.

It goes without saying how important this is.  So whether I achieve something
more useful to the greater RDF deployments or not, at this date and time there
is no active practice of submitting a module to this group for review and
gaining approval. There is no recent evidence of such work in progress.

Does this keep me from writing something useful for myself?  Not really. But
would it not be better if developers had a voice with this commitee for their
needs and then that in itself was beneficial for RDF and Atom cultivations?

I have been hoping for several years to see RSS 1.0 plus modules become a focus
for extending semantic web interoperations and simplifying web services. Now we
have SOA developments in full swing and what are the planned developments for
RSS 1.0 for SOAs?

Could the RSS-DEV group at least state a position on their intentions for
approving proposed modules? Or perhaps shed some light on planned or considered
future work for RSS 1.0? Is the work better split off in two groups?(of course
all work under the same roof).

Jon Hanna <jon@...> wrote:                                  Cecelia
Hickel wrote:
   > I would interested to know, will my hard work pay off for others if
   > I write a good module for instance.

  Frankly, and while I have every psychological motivation to believe
  otherwise, I would be pessimistic in this regard.

  However. Would your module be useful in either other RDF efforts or ATOM
  as well?

  Would it be useful for you at least?

  I'm pretty pessimistic about things, but I certainly don't want to
  dissuade a fellow hacker from doing good work.






Cecelia Hickel
cjhickel@...

---------------------------------
8:00? 8:25? 8:40?  Find a flick in no time
  with theYahoo! Search movie showtime shortcut.

[Non-text portions of this message have been removed]

On 3/23/07, john.breslin@... <john.breslin@...> wrote:
>
> Alan - you can add SIOC to your list:
>
> Semantically-Interlinked Online Communities
> http://www.sioc-project.org/

Yes, I already had the SIOC frontpage under

http://del.icio.us/alan.dean/sioc

and the SIOC spec is under

http://del.icio.us/alan.dean/rdf+specification

but you're right, I didn't have the schema. A quick google and
http://rdfs.org/sioc/ns is now added to
http://del.icio.us/alan.dean/rdf+schema

:-)

Thanks,
Alan Dean
http://thoughtpad.net/who/alan.dean/