[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RSS for Everyone



To increase adoption, I think a few things need to happen. Users need to know about aggregators. The only print article I have seen was in some linux magazine. How about "the economist" or some maintream business magazine? Most people who are not computer scientists take some form of computer training at university or college. Convincing universities to include rss aggregation and syndication in these courses and in marketing business courses would help.

I think a big win for RSS will be for organizations to communicate to the world in a useful way, small to huge companies. I think tutorials on marking up RSS with RDF for these applications would be valuable. Something your typical webmaster/webprogrammer can figure out. I think the blog applications have enough momentum that blog tools will advance just fine. But most of the web I wan't to read isn't comprised of web logs, and most of the people who need to generate RSS or aggregate it don't have a clue. They need boilerplate templates.

Tutorials - howto cut and past articles - on marking up channels and items for: category (job, press release, propaganda, financial release, new item on a particular page, etc).
  geographic location if applicable
  membership in a trade organization or other organization
  type of business or organization (univirsity, etc)


Basically, text XML examples web programmers can copy and paste and tweak Maybe includes an example CSS as well to display RSS. This might be a good article for xml.com?

I have been thinking about writing some form of microsoft .net control, which takes in a data fufu (adapter, dataset, whatever the right fufu is for this application -- I don't know .net all that well) and builds the RSS up from a properties page for the channel and all info about the items comes from the dataset.


And maybe guidlines for designing URIs. I have been thinking about this a bit lately -- should the URI path define the channel?

http://host/press/rss
http://host/jobs/rss

or should the query define the channel?
http://host/rss?category=jobs&category=press

or should we reinterpret the URL path after "rss" in this example to be unordered?
http://hosts/rss/category/jobs/category/press/operator-postfix-or/location/victoria/operator-postifix-and

Paths in a file system may dissappear as metadata based file systems emerge (Microsoft is working on one) in preference of queries with predicates, and asking for items which match a query instead of being on a certain "channel" seems like an analagous idea (daypop does this as a simple example).




keyword "microsoft dotnet"

Danny Ayers wrote:

Some real applications would help too -- good metadata for indicating
wether a channel or item is:
- a job (for what firm, in what classification, based on what location
(and not based on a US address))
- a press release
- corporate propaganda about specific topics
- financial release (for public companies)
- event
- etc.

+1

The FOAF vocabulary looks like its going to be the first that will be in
widespread use outside of the RSS core and modules (inc. DC etc), perhaps
partly because it's acting as a catch-all, and already has many of the
features you list. The applications still have a long way to go, but it was
nice to see FOAF in use with NewsMonster.

What would be really useful would be a list of languages that although not
'attached' to RSS would be very appropriate for use with RSS to avoid
duplication of work (e.g. I've got one in progress for project issue
management).
// hmm... actually I'd be happy to compile it if people send me the info...

When one can look for softare jobs located within 50 miles of victoria
bc with RSS, that will be a big step.

This can already be expressed in at least one way (there's been discussion
elsewhere about a jobs vocabulary, and there's a few ways of doing
location - e.g. foaf:Geo), so I suppose what's need is the app to
demonstrate it - shouldn't be too difficult, a filter for extracting
job-related data from feeds, a store to accumulate it, a filter to select on
location (or whatever) and a front end to access it.  (I'll put this down
for a use case for JemBlog!).

Cheers,
Danny.


To unsubscribe from this group, send an email to:
rss-dev-unsubscribe@egroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/