Hi all,
Anyone know what happened to the group for RSS-0.93 here on YahooGroups? It
appears to have been deleted and all it's archives are lost. It was active
as of this morning.
http://groups.yahoo.com/group/reallysimplesyndication/
"Oops...
There is no group called reallysimplesyndication."
If anyone's got a copy of the messages, let me know.
-Bill Kearney
HTML offers a simple format:
<HTML
<HEAD
<BODY
That is one of it's key advantages. With the advent of XML -> RSS
I'm noticing that dtd's especially, are extremely redundant (much
like constructing complex tables for Netscape).
<!ELEMENT
repeated 20 times
for example.
This redundancy times a million (pages on the web) is undesirable. I
think language developers should consider a more compact way of
writing (or generating) the code. One suggestion would be to get with
the 'compaction' experts to help define an abbreviated method. I
would think that even a reduction to 5 characters would be an
improvement (<!ele). Better yet, eliminate that type of redundant
syntax from the declarations altogether, whereas repeated <!ELEMENT
tags could be something shorter, and multiple instances character
delimited (;). Also, why the need for verbose symmetry (</ELEMENT>)?
Couldn't </> be made to do the same function? I don't think you would
have any problem convincing the browser people (both of them) that
more compact code is better when bandwidth is one of the major hot
spots of both browser and website development. Changes should be made
now while the technology is young.
Dennis.
http://www.dennisys.com/
I'm trying to get a feel for the current adoption level of RSS and the
demand for it's usage. I stubled across RSS, and I've become very
interested with it's potential for sharing content. Can anyone point me to
a location that has some more info on the adoption of this technology,
including companies that currently make sure of it etc.
Regards,
Eric M.
/n software, inc.
http://www.nsoftware.com/
Hi Eric,
Check out http://www.syndic8.com and http://www.moreover.com.
Greets,
Laurens
----- Original Message -----
From: "Eric M." <ericm@...>
To: <rss-dev@yahoogroups.com>
Sent: Wednesday, November 28, 2001 02:07
Subject: [RSS-DEV] Market potential/adoption RSS
>
> I'm trying to get a feel for the current adoption level of RSS and the
> demand for it's usage. I stubled across RSS, and I've become very
> interested with it's potential for sharing content. Can anyone point me
to
> a location that has some more info on the adoption of this technology,
> including companies that currently make sure of it etc.
>
> Regards,
>
> Eric M.
> /n software, inc.
> http://www.nsoftware.com/
>
>
>
>
>
>
>
> 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/
>
>
>
On 27-Nov-2001 16:15:20 Laurens Pit laurens@... wrote:
> Hi Eric,
>
> Check out http://www.syndic8.com and http://www.moreover.com.
>
Hi Laurens,
Thanks for the links, they were a big help. The reason that I
ask is that the company that I work for builds components. We build
these components for all platforms and technologies, Java, ASP, Delphi,
JSP, etc. We are trying to weigh the interest in the addition of
another component to our package (an RSS component). Basically the
components would provide a simple interface to both read and write
RSS files, locally or over http. This would also allow users to
dynamically generate RSS files on their sites with little extra
code. Hopefully by simplifying the process further it could help
drive additional adoption.
The only problem is that we do not like to create components
without a defined RFC or absolute protocol. If there is significant
demand, however, we may just impliment it anyway. What do you think
about the idea?
Regards,
Eric M.
/n software, inc.
http://www.nsoftware.com/
Hi all,
Is there someplace that discusses what's appropriate for the contents of
various Dublic Core elements?
I'm specfically interested in dc:publisher and dc:creator but other fields
are also of concern.
What's really supposed to be in these? The specs are ambiguous at best.
http://dublincore.org/documents/dces/http://www.ietf.org/rfc/rfc2413.txt
My specific question is where should an e-mail address of the publisher,
creator, contributor and like persons be placed and using what format?
-Bill Kearney
2001-11-29 23:56:41, "wkearney99" <wkearney99@...>:
> Is there someplace that discusses what's appropriate for
> the contents of various Dublic Core elements?
See the usuage guide <URL:
http://dublincore.org/documents/usageguide/ > and related
(linked) documents.
See also the qualifiers document <URL:
http://dublincore.org/documents/dcmes-qualifiers/ >.
--
Karl Ove Hufthammer
Looking at the published book or document context
gives some insight esp. keeping in mind the process
role the field is related to.
The role of the creator is document content creation.
The role of the publisher is to facilitate delivery or
presentation of the created content. For E-mail, I'd
say the "from:" would usually be the creator and the
organization or department might be the publisher (if
the message is an official communication). For an
individual both fields would probably be the same: the
person who created is also the facilitator of
presentation and sending infrastructure.
The contributor probably only makes sense in E-mails
sent by teams within organizations or by virtual
teams, and then perhaps only internal messages. The
role of contributor is performed by someone who
contributes to the content of the message like a team
member - the creator might be the project manager
(i.e. mouthpiece for the team) or the project sponsor
(political supporter of the team). For an individual
E-mail, contributor would likely be null/omitted.
Other cases could be akin to the sender/secretary
initial system in business letters (since E-mail and
PCs you don't see this as much - you see it in junk
mail sometimes).
You could also come up with machine-generated E-mail
cases. Naming specific apps is a possibility but it
might be better to label functional roles instead -
will saying the creator was siebel002@...
going to be useful. Instead a process role mailbox
would be better: marketing@... because it
was created as part of the marketing campaign module
as opposed to activities in the sales or tech support
modules.
If you are looking for hard and fast rules, I don't
think you find them because RDF is a very general
purpose format and the possible processes by which
E-mails might be created varies so much. Think
"process roles"! It usually helps.
Hope this helps!
>
> Is there someplace that discusses what's appropriate
> for the contents of
> various Dublic Core elements?
>
> I'm specfically interested in dc:publisher and
> dc:creator but other fields
> are also of concern.
>
> What's really supposed to be in these? The specs
> are ambiguous at best.
>
> http://dublincore.org/documents/dces/
> http://www.ietf.org/rfc/rfc2413.txt
>
> My specific question is where should an e-mail
> address of the publisher,
> creator, contributor and like persons be placed and
> using what format?
__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1
How does one express DC qualifiers in RSS 1.0? Is it just the
equivalent RDF/XML encoding (which could get ugly)?
Cheers,
On Fri, Nov 30, 2001 at 11:50:53AM +0100, Karl Ove Hufthammer wrote:
> 2001-11-29 23:56:41, "wkearney99" <wkearney99@...>:
>
> > Is there someplace that discusses what's appropriate for
> > the contents of various Dublic Core elements?
>
> See the usuage guide <URL:
> http://dublincore.org/documents/usageguide/ > and related
> (linked) documents.
>
> See also the qualifiers document <URL:
> http://dublincore.org/documents/dcmes-qualifiers/ >.
>
> --
> Karl Ove Hufthammer
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
--
Mark Nottingham
http://www.mnot.net/
2001-11-30 19:59:11, Mark Nottingham <mnot@...>:
> How does one express DC qualifiers in RSS 1.0?
Using the 'Dublin Core' module:
<URL: http://www.purl.org/rss/1.0/modules/dc/ >
--
Karl Ove Hufthammer
Right. dcmes-qualifiers covers the semantics, but I don't see any
specific syntax there. the dc module doesn't make and reference to,
or give examples of, qualified dc elements.
There seems to be a gap here. There are obvious/proper ways to do
this in RDF, but IMHO it's asking a bit much for RSS
developers/producers/users to have a knowledge of RDF at that level,
considering its current state.
--- In rss-dev@y..., "Laurens Pit" <laurens@o...> wrote:
> To be more precise:
>
> http://dublincore.org/documents/dcmes-qualifiers/
>
>
> Greets,
> Laurens
>
> > 2001-11-30 19:59:11, Mark Nottingham <mnot@m...>:
> >
> > > How does one express DC qualifiers in RSS 1.0?
> >
> > Using the 'Dublin Core' module:
> > <URL: http://www.purl.org/rss/1.0/modules/dc/ >
Yes, there seems to be a gap. The RDF specs give examples of dc elements and
dc qualifiers (see paragraph 7.4). The reason no specific syntax is given at
the dublin core website is probably because the dc elements can be expressed
in many ways/formats, one of which is in RDF format.
----- Original Message -----
From: "Mark Nottingham" <mnot@...>
To: <rss-dev@yahoogroups.com>
Sent: Saturday, December 01, 2001 04:05
Subject: [RSS-DEV] Re: [syndication] Authoritative examples of DC element
usage?
> Right. dcmes-qualifiers covers the semantics, but I don't see any
> specific syntax there. the dc module doesn't make and reference to,
> or give examples of, qualified dc elements.
>
> There seems to be a gap here. There are obvious/proper ways to do
> this in RDF, but IMHO it's asking a bit much for RSS
> developers/producers/users to have a knowledge of RDF at that level,
> considering its current state.
>
>
>
> --- In rss-dev@y..., "Laurens Pit" <laurens@o...> wrote:
> > To be more precise:
> >
> > http://dublincore.org/documents/dcmes-qualifiers/
> >
> >
> > Greets,
> > Laurens
> >
> > > 2001-11-30 19:59:11, Mark Nottingham <mnot@m...>:
> > >
> > > > How does one express DC qualifiers in RSS 1.0?
> > >
> > > Using the 'Dublin Core' module:
> > > <URL: http://www.purl.org/rss/1.0/modules/dc/ >
>
>
> 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/
>
>
>
Hi
> > > > 2001-11-30 19:59:11, Mark Nottingham <mnot@m...>:
> > > >
> > > > > How does one express DC qualifiers in RSS 1.0?
I didn't think one could, I thought RSS 1.0 only supported unqualified
DC, but perhaps I'm wrong.
Aaron, or someone should be able to answer this?
Chris
--
Chris Croome <chris@...>
web design http://www.webarchitects.co.uk/
web content management http://mkdoc.com/
everything else http://chris.croome.net/
On Sat, 1 Dec 2001, Chris Croome wrote:
> Hi
>
> > > > > 2001-11-30 19:59:11, Mark Nottingham <mnot@m...>:
> > > > >
> > > > > > How does one express DC qualifiers in RSS 1.0?
>
> I didn't think one could, I thought RSS 1.0 only supported unqualified
> DC, but perhaps I'm wrong.
>
> Aaron, or someone should be able to answer this?
One common form of qualifying DC is to declare properties as
sub-properties of the 15 DC properties. If I remember right, I think we
declared rss:title and rss:description as sub-properties of dc:title,
description...
You can mix all sorts of stuff into RSS 1.0; there are no restrictions on
the extension vocabularies you can mix in. My favourite example (albeit
inadequately written up) was the experiment Libby and I did using job
descriptions:
http://ilrt.org/discovery/2000/11/rss-query/
the way we do it is to associate RSS items more explicitly with the things
they describe; in our scenario, jobs. The sample data we give has a little
redundancy, but shows that we can use RSS 1.0 as a generic data transport,
with non-RSS vocabs (DC, jobs, whatever) used to decorate the basic RSS
structure with all sorts of (independently developed) richness. I'm off at
a slight tangent here, but just wanted to make the point that RSS 1.0
doesn't exclude anything, especially DC qualifiers.
cheers,
Dan
--
mailto:danbri@...
http://www.w3.org/People/DanBri/
I'm writing a small cms that will be generating an RSS 1.0 feed, but
have a question that I'd like to put to the group. If I were RSS-ifying
a magazine (i'm not, but this analogy fits my situation) that had
several types of content - e.g. book reviews, film reviews, articles,
letters to the editor, etc ... and I would like to group the items for
the different types of content together, would my only option be to
generate separate rss feeds (like bookreviews.rss, filmreviews.rss,
features.rss, letterstoed.rss, etc.) or is there some means of grouping
items with a feed into collections of some sort ? I've read the rss 1.0
spec at http://groups.yahoo.com/group/rss-dev/files/specification.html
and don't see any alternative to multiple feeds, but was hoping that I
had missed something.
thanks,
brian donovan
--- In rss-dev@y..., lophty lists <lists@l...> wrote:
> I'm writing a small cms that will be generating an RSS 1.0 feed,
but
> have a question that I'd like to put to the group. If I were RSS-
ifying
> a magazine (i'm not, but this analogy fits my situation) that had
> several types of content - e.g. book reviews, film reviews,
articles,
> letters to the editor, etc ... and I would like to group the items
for
> the different types of content together, would my only option be to
> generate separate rss feeds (like bookreviews.rss, filmreviews.rss,
> features.rss, letterstoed.rss, etc.) or is there some means of
grouping
> items with a feed into collections of some sort ? I've read the
rss 1.0
> spec at http://groups.yahoo.com/group/rss-
dev/files/specification.html
> and don't see any alternative to multiple feeds, but was hoping
that I
> had missed something.
The RSS-1.0 format supports putting categories on items. The RSS-
0.92 also supports one category per item. This is a topic being
discussed on the syndi8 list: http://groups.yahoo.com/group/syndic8
Right now many folks do what you're talking about with different
feeds for each topic/category/department. Hopefully this will start
changing.
-Bill Kearney
I'm looking to evaluate some scraping software out there. Currently
I have a perl script that checks some defined pages once a day to
find the latest tv-critic reviews (similar to the critics link at
www.tvbarn.com). The desired output is an RSS file.
So far, I have found sitescooper (jmason.org). It doesn't generate
an RSS file, but I figure I can get it to do that. I really like the
configuration of the .site files.
Are there any other organized packages out there that can do this?
Curious,
Thanks,
Doug
Hi all,
Can anyone offer some examples of 'authoritative' use of the dc:coverage
element from Dublin Core?
http://dublincore.org/documents/dces/
Element: Coverage
Name: Coverage
Identifier: Coverage
Definition: The extent or scope of the content of the resource.
Comment: Coverage will typically include spatial location (a place
name
or geographic coordinates), temporal period (a period label,
date, or date range) or jurisdiction (such as a named
administrative entity).
Recommended best practice is to select a value from a
controlled vocabulary (for example, the Thesaurus of
Geographic
Names [TGN]) and that, where appropriate, named places or
time
periods be used in preference to numeric identifiers such as
sets of coordinates or date ranges.
I'm most curious as to what you're supposed to be putting here as the value
and how you're supposed to indicate the 'controlled vocabulary'.
Why am I asking this? Because I'm wondering what format a feed might use if
it wanted to indicate it's geographic location. Using city names is one way
but likely to be fairly inaccurate. Using latitude/longitide is more
accurate. One doesn't have to use a precise lat/lon coordinate if there's
some concerns about privacy, security or whatever. The coordinates of one's
local post office might be just as useful. The point being to be able to
find feeds based on more than just content. I'd like to know who's 'near' a
given location. Perhaps for travel or just to get to know my neighbors.
Thanks,
Bill Kearney
This looked interesting:
http://andrew.triumf.ca/coverage/
<meta name="DC.coverage.y" scheme="UTM10N" content="5454818">
<meta name="DC.coverage.placeName" content="British Columbia">
<meta name="DC.coverage.placeName" scheme="ISO3166-A3" content="GBR">
Is this used with any regularity?
Thanks,
Bill Kearney
Use of dc qualifiers in HTML:
http://dublincore.org/documents/2000/08/15/dcq-html/
<meta name="DC.Coverage.spatial"
scheme="DCMIPoint"
content="
east=76.59882;
north=39.33327;
elevation=135" >
Or wrapped/mangled:
<meta name="DC.Coverage.spatial" scheme="DCMIPoint "content="
east=76.59882; north=39.33327; elevation=135" >
Does this look more correct?
-Bill Kearney
--- In rss-dev@y..., "wkearney99" <wkearney99@h...> wrote:
>
> Bill Kearney
The USPS has defined something labeled 'the address standardization
database'. It seems to codify destination points such as home
addresses for use with their automated systems. It is something
relatively new. I saw an example of it associated with 'web
services'. http://web03.primordial.com/pcmagdemo/
The USPS system may contain more location and logistical information
than is apparent in this small demo, so you may want to contact them
directly. They have a website.
I stumbled across this thread via Google today - did anything ever
come of the Usenet as RDF exchange idea ? Was the proposal rejected ?
I apologize for dredging the archives, but the idea seems very
interesting.
:D
-brian donovan
http://www.lophty.com/kumo/
--- In rss-dev@y..., Dan Brickley <daniel.brickley@b...> wrote:
> Let's start a Usenet newsgroup.
>
> I started to draft a request for news:alt.rdf.* group(s). Idea was
> that a simple good old fashioned usenet group would be a great way
for XML/RDF
> apps to publish and discover services and data. We already have global
> infrastructure in place to support this, Perl, Java etc client libraries
> and lots more. Unlike Web-based aggregation and 'e-market' sites, the
> lack of central management depoliticises things rather helpfully. No one
> WWW site gets to be the central whiteboard on which RDF/XML apps
> scribble messages to one another. Contrast: if I'd just suggested that
> everyone uses www.danbri.org as a central service for sharing RSS files,
> that'd be rather different.
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 : /Modules/Proposed/mod_company.html
Uploaded by : Indus Khaitan
Description : RSS 1.0 Module: mod_company
You can access this file at the URL
http://groups.yahoo.com/group/rss-
dev/files/Modules/Proposed/mod_company.html
To learn more about file sharing for your group, please visit
http://help.yahoo.com/help/us/groups/files
Regards,
Indus Khaitan
> File : /Modules/Proposed/mod_company.html
> Uploaded by : Indus Khaitan
> Description : RSS 1.0 Module: mod_company
Is calling this "company" as definitive as necessary? Since this
seems like it's intended to provide stock market info shouldn't it's
name refect that? And couldn't something else in the DC namespace be
used to for the name element?
Otherwise it sounds like a reasonable idea.
There is an RSS feed that's including ticker info. It's from the
Motley Fool:
http://www.syndic8.com/feedinfo.php?FeedID=2235http://www.fool.com/xml/foolnews_rss091fn.xml
They're using:
<ticker exchange="NYSE" symbol="SGP" />
I have no idea if/where it's documented.
-Bill Kearney
> Is calling this "company" as definitive as necessary? Since this
> seems like it's intended to provide stock market info shouldn't
it's
> name refect that? And couldn't something else in the DC namespace
be
> used to for the name element?
>
The use of "company" resulted from the original imagination of the
RSS 1.0 Authors, as illustrated in the RSS 1.0 spec.
The module gives some information about the company(s) mentioned in
the text, and also their taxonomic realm.
Best Regards,
Indus Khaitan
maybe it's a temporary thing but I can't access
http://purl.org/rss/1.0/schema.rdf - maybe something to do with
yahoogroups mucking around? it just hangs....
cheers
Libby
Send Email
