mortenjacobsen2000 wrote:
> I've seen in the RSS 2.0 specification that referring to other
> namespaces my allow to extend RSS 2.0. I wonder if I can use this
> feature to include OPML.
> Since I'm quite inexperienced in RSS, I also will ask if it could be
> possible the other way round, include RSS in OPML.
Because neither RSS nor OPML specify namespaces for themselves, the
clean XML answer is not available, i.e. (simplified)
<rss>
<channel />
<item>
<description>
<opml xmlns="http://www.opml.org/some_non-existant_namespace">
<head/>
<body>
<outline text="insert your opml here"/>
</body>
</opml>
</description>
</item>
</rss>
So it is not possible to embed RSS 2.0 in OPML or vice-versa.
In both specifications, the correct thing to do is to point at the other
relevant file, in OPML with an "rss" nodetype and in RSS either with the
<link> element of <item> or your own custom namespace, depending on
the application. In general, if an HTML rendering of the OPML file
exists I would point <link> at that and have a custom namespace of your
own for pointing at the OPML file.
If you are willing to control the readers which are consuming your RSS,
you *could* define your own namespace like
"http://cdeaandrss.blogspot.com/almost-opml-in-rss", and declare that
the tags inside of that namespace are *just like* the ones in the
official OPML spec... but that would be a derivative specification, and
you should not call that OPML as no current OPML reader is likely to be
able to read it. The most standards-compliant thing to do is probably
just to provide a link to the relevant OPML file, which current OPML
consumers will be able to read.
I'm looking on if it is possible to use OPML and RSS to display
accounting information.
At http://www.summasummarium.com/morten/accountopml/ you can see an
4 year old prototype using OPML for accounting purposes. Regretably
its still in Norwegian.
I've seen in the RSS 2.0 specification that referring to other
namespaces my allow to extend RSS 2.0. I wonder if I can use this
feature to include OPML.
Since I'm quite inexperienced in RSS, I also will ask if it could be
possible the other way round, include RSS in OPML.
I have recently started a blog (actually my first) noting my
thoughts and observartions at http://cdeaandrss.blogspot.com where
you find more background on my private research.
Sincerly,
Morten Jacobsen
On Wednesday, February 18, 2004, at 03:29PM, Lawrence Lee <tomalak@...>
wrote:
>Would this work for you Steve? Create a new discussion group message in your
>browser. Then edit the new message in Radio's outliner. And then use the
>OPML version of the discussion group message in your macro.
Yes, I think it would. This is simpler than the version I had in my mind. I
have a reason to publish the same information in three places (1 Manila site, 1
private Manila site, 1 public Radio weblog) and I want to only write the
information once and have it update everywhere.
With this background and your suggestion, my plan is this:
Rewrite the content once as a Manila discussion group message or Manila story on
the public Manila site. Next, use the viewOpml macro to publish it on the
private Manila site, but that leaves the Radio weblog out in the cold. Is there
a Radio equivalent to the viewOpml macro from Manila?
Steve Kirks
http://houseofwarwick.com/
Manila/Radio/OPML Dev Listers:
I know that Radio can edit OPML easily. I know that Radio can pull an OPML from
a URL for editing. Can Radio pull an OPML file stored as a 'gem' on a Manila
server?
Why?
I'm keeping a Radio Feature Wish List in OPML to editing and version control
easier. I want to store it on a Manila server as a gem, then call it in a story
using the Manila viewOpml macro. For simplicity (and to avoid multiple FTP
sessions), I want to store the OPML file on the server, then use whatever copy
of Radio I'm at to edit it.
By the way, the macro works like a champ, but when I edit the OPML file, the
changes are not reflected when the page is regenerated. It does change if I
change the name of the file in the macro and the 'gem'.
Summary:
Q: remote editing and saving OPML via Radio?
Q: viewOpml macro behavior right?
Q: is there a smarter way to do this?
Q: is there a viewOpml macro equivalent for Radio?
Steve Kirks
http://houseofwarwick.com/
Hi Dave
> http://feeds.scripting.com/
Very cool.
> http://www.scripting.com/feeds/top100.opml
That OPML file uses an attribute, count,
which I didn't have an entry for in
OPML_Elements_and_Attributes.
Is it new ? Or been used before by others ?
Any other data on it ?
Thanks
stan
A new OPML-based Web application.
http://feeds.scripting.com/
"The purpose of this site is to gather a community of subscription
lists, in OPML format, and aggregate them in interesting ways."
Its top 100 list is itself an OPML resource.
http://www.scripting.com/feeds/top100.opml
Dave
Howdy
I've incorporated the OPML usage info noted
in this thread by:
Rogers Cadenhead, Morbus Iff, Brent Simmons,
Mark Fletcher, and Øyvind Kolås
... into OPML_Elements_and_Attributes.opml
(which lives here:
http://JavaOutlineEditor.org/OPML/OPML_Elements_and_Attributes.opml )
Those folks might want to
take a look to see if I've got things
straight.
Other folks who work on OPML tools: please
post away to this thread RE your OPML usage.
I'll continue to incorporate data posted
to this Yahoo group into the file.
( I have NOT yet added all the new tools,
e.g. agregators et al, that do some OPMLing.
It'll take some time ... )
Plus: expanding the process a bit:
I've opened up a Groove workspace wherein
folks can add to or modify
OPML_Elements_and_Attributes.opml directly
as regards their products' OPMLation.
I'me sending invites to this Groove workspace to
folks who've posted to this Yahoo group about tools
they work on and OPML. If
you don't get an invite, and want to join the
workspace, just drop me a personal email off-group
(Stan@...)and I'll send you an invite.
I'll also be sending invites to other folks who
seem involved in OPML tooldom.
[ If you don't have Groove,
there's a [free for personal use/free for 60 days
of business use] Groove Workspace Preview Edition
downloadable here: http://www.groove.net/downloads/groove/ ]
The Groove workspace can be particularly useful
for indicating your tools' support of the various
elements, attributes, and types. Takes a load of
detail work off me.
Homage and regards to all OPMLers ....
Stan
hnb is a unix ncurses based outline editor, for plain outlines, it
adheres to the old standard, with it's current feature set, which is
probably a quite common feature set amongst todolist/outliner combo
apps.
At the moment hnb development is frozen, but this might change in
the future, if something resemblign the extra attributes I use are included
in the standard I'll probably put out a new release.
/Øyvind K.
<?xml version="1.0" encoding="ISO-8859-1"?><?pos="1"?>
<!-- generated by hnb 1.9.18pre6 (http://hnb.sourceforge.net/) -->
<opml version="1.0">
<head>
<title>outline exported from hnb</title>
<dateCreated></dateCreated>
<dateModified></dateModified>
<ownerName></ownerName>
<ownerEmail></ownerEmail>
<expansionState></expansionState>
<vertScrollState></vertScrollState>
<windowTop>20</windowTop>
<windowLeft>20</windowLeft>
<windowBottom>200</windowBottom>
<windowRight>200</windowRight>
</head>
<body>
<outline text="main item">
<outline text="sub item" />
<outline text="sub item">
<outline text="sub sub item,. with a lot more text, but no
linebreaks,. that is one
of the few things hnb doesn't allow at the moment, when writing a longer
text, I simple treat e
ach node as a paragraph,. and up down arrows move between the lines of the
paragraph" />
</outline>
<outline text="todo" type="todo" done="no">
<outline text="an item" type="todo" done="no" />
<outline text="another item" type="todo" done="yes">
<outline text="a sub item" type="todo" done="yes" />
</outline>
</outline>
</outline>
</body>
</opml>
--
.^.
/V\ Øyvind Kolås, Gjøvik University College, Norway
/(_)\ <oeyvindk@...>,<pippin@...>
^ ^
It's true that examples aren't specs, but beggars can't be choosers.
I'll take whatever information I can get in whatever form. Let's be detectives.
I don't recall Columbo or Sherlock Holmes refusing a clue because it wasn't a
spec. ;->
Dave
----- Original Message -----
From: Jeremy Bowers
To: opml-dev@yahoogroups.com
Sent: Tuesday, December 02, 2003 4:35 PM
Subject: Re: [opml-dev] OPML 1.1
Jeremy Bowers wrote:
> I think it would be worth having authors catalog what their software
> *outputs* as well. It's (somewhat) fine to accept any case tags, but
> OPML is specified as XML, so the case should be honored and programs
> outputting wrong cases should be considered broken according to the
> current spec.
Clarification: By "catalog what their software outputs" I mean actual
specifications and promises, not just example OPML files their system
outputs. Examples aren't specs.
Yahoo! Groups Sponsor
ADVERTISEMENT
To unsubscribe from this group, send an email to:
opml-dev-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]
A couple of things..
1. I moved the OPML website from UserLand's server to a server of my own
here in Boston. At this point anyone who says it's a UserLand spec will have
very little basis. It's true I authored it while I was at UserLand, but the
copyright was always very liberal and the site isn't hosted there and it
will soon move to Creative Commons and hosting at Harvard.
2. If you were a member of the original OPML site, you still are, but your
password has been deleted. I'm honestly not sure how this works, try signing
up, and see what happens. If you need help, send me a private email.
3. I posted a plan for OPML 1.1.
http://opml.scripting.com/stories/storyReader$23
After a bit of discussion, I'll start working on specifying it. One of the
things I hope to do is to enhance the <cloud> element so it can connect up
through Instant Messaging. Maybe there are other ideas.
4. I'm going to turn the home page of the site into a weblog of some
fashion.
5. I'm looking for other people who wish to be editors of the site. Only one
or two, and I only want to work with people I've worked with before.
6. There's lots of places people could flame here. I'm being relaxed as I
work on this. Don't flame, if you do, I'll boot you from the list. I'm tired
of people who get in the way of progress using emotional tricks. This time
there will be zero tolerance for personal stuff, or efforts to stop the work
or talk about RDF or why Danny Ayers doesn't like this, or whatever. Not
interested. Thanks.
Dave
On Tue, 02 Dec 2003 15:10:11 -0500, Morbus Iff wrote:
> * I believe you had "text=" as the title of the RSS feed. I
> use "title=", but the code converts "text" to "title".
It appears that Radio creates both text and title attributes for RSS
feed titles.
--
Rogers Cadenhead, rogers@... on 12/3/2003
Weblog: http://www.cadenhead.org/workbench
Jeremy Bowers wrote:
> I think it would be worth having authors catalog what their software
> *outputs* as well. It's (somewhat) fine to accept any case tags, but
> OPML is specified as XML, so the case should be honored and programs
> outputting wrong cases should be considered broken according to the
> current spec.
Clarification: By "catalog what their software outputs" I mean actual
specifications and promises, not just example OPML files their system
outputs. Examples aren't specs.
Mark Fletcher wrote:
> We consider all attributes case insensitive.
I think it would be worth having authors catalog what their software
*outputs* as well. It's (somewhat) fine to accept any case tags, but
OPML is specified as XML, so the case should be honored and programs
outputting wrong cases should be considered broken according to the
current spec.
As a soon-to-be producer and consumer of OPML, I have to say this case
insensitivity is disturbing to me; it's not XML. I won't throw a
hissy-fit ;-) but I do think we need to make extra certain that at least
all generators meet the spec.
Hi Dave
> Could you add Morbus's info to that.
Yes.
> I think people should post their reports to the list,
> as long as it isn't overwhelming, and you should merge
> them into the outline as they become available.
Sounds fine. Info on elements and attributes that
are supported or not supported, and elements and attributes
that a particular tool has introduced, are of interest.
> Also, how about a list of apps you reviewed. Looks like
> you have "UserLand" and "JOE." There are now many
> others, basically all the aggregators do something with
> OPML.
As folks supply info on support/non-support, I'll add that
data to particular elements/attributes.
I'll also add new OPML tools to the list at the node
"further info : OPML tools". In that regard, I've
just added a sub-node for RSS feed readers/news aggregators, and will
add info for starters digested from here:
http://www.hebig.org/blogs/archives/main/000877.php
Stan
Dave Winer wrote:
>Another area that needs attention is to sort out the common uses of attributes
in different tools. Since this is XML, names are case-sensitive. And there is
even some variability beyond that. The first step should be to survey all the
existing tools, see what they produce and then collate the results. Then, once
that's done, it may be possible to have a simple set of recommendations that
enables more interop between tools. But first we have to see how far apart all
the tools actually are. I'll get the ball rolling on this, unless someone else
wants to take the lead. It's not a glamorous job, it requires that one be
thorough and be good at tabulating information.
>
>
>
When importing OPML files, here's what Bloglines does:
For every 'outline' tag after the opening tag, we do:
We look for the 'xmlurl' attribute. If we find it, we add that as a
subscription. If we also find a 'title' attribute, we use that for the
name of the subscription.
If we don't find the 'xmlurl' attribute, we look for 'text'. If we don't
find 'text', we look for 'title'. If we find one of those, and we do not
find 'url', we add a new folder. All subscriptions found after this tag
and before the closing </outline> are then inserted in that folder. We
only support one level of folders, so nested folders are ignored (but
the subscriptions within them are not ignored).
We consider all attributes case insensitive.
Here's an example of what we output when exporting subscriptions. This
example has 2 subscriptions in the 'Press/Journalists' folder, and two
subscriptions at the top level:
<?xml version="1.0" encoding="utf-8"?>
<opml version="1.0">
<head>
<title>Bloglines Subscriptions</title>
<dateCreated>Tue, 2 Dec 2003 21:04:44 GMT</dateCreated>
<ownerEmail>markf@...</ownerEmail>
</head>
<body>
<outline title="Subscriptions">
<outline title="Press/Journalists">
<outline title="Wired News" htmlUrl="http://www.wired.com/" type="rss"
xmlUrl="http://www.wired.com/news_drop/netcenter/netcenter.rdf" />
<outline title="Dan Gillmor's eJournal"
htmlUrl="http://weblog.siliconvalley.com/column/dangillmor/" type="rss"
xmlUrl="http://weblog.siliconvalley.com/column/dangillmor/index.xml" />
</outline>
<outline title="Weblogg-ed News" htmlUrl="http://www.weblogg-ed.com/"
type="rss" xmlUrl="http://www.weblogg-ed.com/xml/rss.xml" />
<outline title="wingedpig.com" htmlUrl="http://www.wingedpig.com/"
type="rss" xmlUrl="http://www.wingedpig.com/index.rdf" />
</outline>
</body>
</opml>
Mark
--
Mark Fletcher
Bloglines
http://www.bloglines.com
NetNewsWire imports and exports OPML subscriptions lists.
It doesn't currently understand nested subscriptions lists, but that
will change. (It will both import and export nested lists.)
***Importing
It tries to be as forgiving as possible in what it accepts. It ignores
case. For the name of a feed it first looks at the text attribute, then
at the title attribute. For the home URL of a feed it looks at htmlUrl
then at url.
If an RSS URL doesn't exist, it does RSS auto-discovery to try to find
the feed. (This makes it possible to import blogrolling.com OPML files,
for instance.)
***Exporting
It exports using ISO-8859 encoding, since that's most likely to be
compatible (with Radio and with Windows aggregators).
It sets the following attributes:
text -- name of feed
title -- name of feed (redundancy for compatibility sake)
description -- description of feed
type -- rss
version -- RSS (more redundancy for compatibility sake)
htmlUrl -- URL of home page
xmlUrl -- URL of feed
***Sample OPML file
http://ranchero.com/downloads/MySubscriptions.opml
-Brent
Stan that looks very useful. Could you add Morbus's info to that.
I think people should post their reports to the list, as long as it isn't
overwhelming, and you should merge them into the outline as they become
available.
Also, how about a list of apps you reviewed. Looks like you have "UserLand" and
"JOE." There are now many others, basically all the aggregators do something
with OPML.
Dave
----- Original Message -----
From: Stan Krute
To: opml-dev@yahoogroups.com
Sent: Tuesday, December 02, 2003 3:42 PM
Subject: [opml-dev] Re: OPML 1.1
Hi Dave
> Another area that needs attention is to sort out the
> common uses of attributes in different tools. Since
> this is XML, names are case-sensitive. And there is
> even some variability beyond that. The first step
> should be to survey all the existing tools, see what
> they produce and then collate the results. Then, once
> that's done, it may be possible to have a simple set of
> recommendations that enables more interop between
> tools. But first we have to see how far apart all the
> tools actually are. I'll get the ball rolling on this,
> unless someone else wants to take the lead. It's not a
> glamorous job, it requires that one be
> thorough and be good at tabulating information.
Per an old thread on this list, I started and posted
an OPML document that contains this sort of info. It
still lives at :
http://JavaOutlineEditor.org/OPML/OPML_Elements_and_Attributes.opml
Last revisions to that document
are almost two years old, January of 2002.
I'd be happy to make revisions to that document based on folks
postings here on the list or notes sent to me via email,
whichever is easiest.
Stan
Yahoo! Groups Sponsor
To unsubscribe from this group, send an email to:
opml-dev-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]
Hi Dave
> Another area that needs attention is to sort out the
> common uses of attributes in different tools. Since
> this is XML, names are case-sensitive. And there is
> even some variability beyond that. The first step
> should be to survey all the existing tools, see what
> they produce and then collate the results. Then, once
> that's done, it may be possible to have a simple set of
> recommendations that enables more interop between
> tools. But first we have to see how far apart all the
> tools actually are. I'll get the ball rolling on this,
> unless someone else wants to take the lead. It's not a
> glamorous job, it requires that one be
> thorough and be good at tabulating information.
Per an old thread on this list, I started and posted
an OPML document that contains this sort of info. It
still lives at :
http://JavaOutlineEditor.org/OPML/OPML_Elements_and_Attributes.opml
Last revisions to that document
are almost two years old, January of 2002.
I'd be happy to make revisions to that document based on folks
postings here on the list or notes sent to me via email,
whichever is easiest.
Stan
Excellent. That's exactly the kind of report we need. Since Brent went next,
maybe he could explain how he uses OPML, in a style similar to this explanation.
Since he's not subscribed to OPML-DEV, I've cc'd him. Dave
----- Original Message -----
From: Morbus Iff
To: opml-dev@yahoogroups.com ; opml-dev@yahoogroups.com
Cc: berkman-thursday@yahoogroups.com
Sent: Tuesday, December 02, 2003 3:10 PM
Subject: Re: [opml-dev] OPML 1.1
>Another area that needs attention is to sort out the common uses of
>attributes in different tools. Since this is XML, names are case-sensitive.
>And there is even some variability beyond that. The first step should be to
>survey all the existing tools, see what they produce and then collate the
>results. Then, once that's done, it may be possible to have a simple set of
Dave: AmphetaDesk was the first application to take the
mySubscriptions.opml of Radio Userland and adopt it for it's own
channel list. NetNewsWire followed thereafter. I haven't been
near AmphetaDesk for a while, but off the top of my head:
* I hate innerCaps, so I write attributes lowercase. I read both.
* I believe you had "text=" as the title of the RSS feed. I
use "title=", but the code converts "text" to "title".
* Any attributes that AmphetaDesk doesn't explicitly use
are read and written as if I did. Likewise, I provide
an API to get at that "unused" data.
More info, including sample OPML output is here:
http://disobey.com/amphetadesk/pod_amphetadesk_mychannels.html
I believe I've added two or three attributes not part
of the original mySubscriptions.opml files I've seen:
* filename: internal use for AmphetaDesk.
* date_downloaded and _added. self explanatatory.
* email: the nearest approximation to the
channel's email address, if any.
--
Morbus Iff ( i put the demon back in codemonkey )
Culture: http://www.disobey.com/ and http://www.gamegrene.com/
My book, Spidering Hacks: http://amazon.com/exec/obidos/ASIN/0596005776/
icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus
Yahoo! Groups Sponsor
ADVERTISEMENT
To unsubscribe from this group, send an email to:
opml-dev-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]
>Another area that needs attention is to sort out the common uses of
>attributes in different tools. Since this is XML, names are case-sensitive.
>And there is even some variability beyond that. The first step should be to
>survey all the existing tools, see what they produce and then collate the
>results. Then, once that's done, it may be possible to have a simple set of
Dave: AmphetaDesk was the first application to take the
mySubscriptions.opml of Radio Userland and adopt it for it's own
channel list. NetNewsWire followed thereafter. I haven't been
near AmphetaDesk for a while, but off the top of my head:
* I hate innerCaps, so I write attributes lowercase. I read both.
* I believe you had "text=" as the title of the RSS feed. I
use "title=", but the code converts "text" to "title".
* Any attributes that AmphetaDesk doesn't explicitly use
are read and written as if I did. Likewise, I provide
an API to get at that "unused" data.
More info, including sample OPML output is here:
http://disobey.com/amphetadesk/pod_amphetadesk_mychannels.html
I believe I've added two or three attributes not part
of the original mySubscriptions.opml files I've seen:
* filename: internal use for AmphetaDesk.
* date_downloaded and _added. self explanatatory.
* email: the nearest approximation to the
channel's email address, if any.
--
Morbus Iff ( i put the demon back in codemonkey )
Culture: http://www.disobey.com/ and http://www.gamegrene.com/
My book, Spidering Hacks: http://amazon.com/exec/obidos/ASIN/0596005776/
icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus
Rogers, thanks for kicking off the restart of this list. And thanks to everyone
else for not objecting to the newly stated charter. I'm optimistic about our
being able to get work done this time around. I'm willing to use the tools that
Yahoo provides to keep the list on-topic. There are over 170 subscribers [1],
which is quite a lot, so it's potentially a very powerful community. My hope is
that we can have something like the Berkman-Thursdays group at Harvard Law
School, where we have a high standard of achievement and cooperation and we get
things done. That group organized a conference and hosted over 200 people on two
days. That's what can be done if people have a will to work together.
Anyway, Rogers, I will take your notes on OPML 1.1 and turn them into a document
on the opml.org website. I'm also going to move that site off the UserLand host
and put it on one of the new servers I have running here in the Boston area.
Also once the OPML 1.1 spec is adequately reviewed, I will transfer it to
Berkman Center, as I did with the RSS 2.0 spec, and redistribute it under the
Creative Commons license.
Another area that needs attention is to sort out the common uses of attributes
in different tools. Since this is XML, names are case-sensitive. And there is
even some variability beyond that. The first step should be to survey all the
existing tools, see what they produce and then collate the results. Then, once
that's done, it may be possible to have a simple set of recommendations that
enables more interop between tools. But first we have to see how far apart all
the tools actually are. I'll get the ball rolling on this, unless someone else
wants to take the lead. It's not a glamorous job, it requires that one be
thorough and be good at tabulating information.
Dave
PS: I've cc'd this to the Berkman-Thursday list, in case any of you want to
participate in the restart of the OPML developers list.
[1] http://groups.yahoo.com/group/opml-dev/
[Non-text portions of this message have been removed]
Glad to see the list firing up again.
One of the first things we should address is the spec, which hasn't
been updated to OPML 1.1, the current version in Radio UserLand.
OPML 1.1 was announced here:
http://www.opml.org/stories/storyReader$11
It adds an optional CLOUD element to the HEAD element of an OPML
file, supporting publish-subscribe notification. The syntax is
borrowed from the same element in RSS:
Publish-Subscribe Notification
<cloud> is a new optional sub-element of <head>. It specifies a Web
service that supports the rssCloud interface which can be implemented
in HTTP-POST, XML-RPC or SOAP 1.1.
Its purpose is to allow processes to register with a cloud to be
notified of updates to the channel. For example:
<cloud domain="data.ourfavoritesongs.com" port="80" path="/RPC2"
registerProcedure="ourFavoriteSongs.rssPleaseNotify"
protocol="xml-rpc"/>
A full explanation of this element and the rssCloud interface is here
[1].
1: http://www.thetwowayweb.com/soapmeetsrss
--
Rogers Cadenhead, rogers@... on 12/01/2003
Weblog: http://www.cadenhead.org/workbench
I'm doing a lot of work with OPML and want to start discussing it with other
developers.
So this is a heads-up, if you don't want to talk about applications, now is
the time to unsubscribe.
Read more about the charter of this list here.
http://groups.yahoo.com/group/opml-dev/message/197
Please stay on-topic -- applications of OPML only, no debates whether you
like it or not, because that's off-topic.
We're going to try to address as many practical issues as we can in the
coming weeks and months.
Dave
OPML is a great simple format for heirarchical data. It was quite
easy to adapt another link viewer to read OPML (originally by Mark
Davis, http://drdreff.blogspot.com). It's now posted to allow
anyone to embed a set of links from an opml file in their pages:
http://www.mylaszlo.com/cgi-bin/blogbox
Someone recently asked me about adapting this to display a slideshow
with an OPML file like this:
<outline text="Southeast Asia">
<outline text="Hmong girl" type="link"
url="/default_album/img01.jpg" target="" />
<outline text="Lisu infant" type="link"
url="/default_album/img02.jpg" target="" />
<outline text="Lisu mother" type="link"
url="/default_album/img03.jpg" target="" />
<outline text="Torajan farmer" type="link"
url="/default_album/img04.jpg" target="" />
</outline>
I didn't see other examples of specifying and displaying non-text
data in OPML, but it conforms to the spec and it seems like a nice
feature of an OPML viewer to display linked graphics in-line... or
is there a different XML format that would be better for this
application?
Sarah Allen
http://www.laszlosystems.com (work)
http://www.ultrasaurus.com (personal)
I took Daniel Naber's tree perl script (tree.pl)* and by changing ten
lines converted it from output of XHTML to OPML instead. This
provides input to Danny Goodman's OPML navigation javascript widget.**
Works great for me. Let me know if this is something of interest.
* Daniel Naber, General Public License, <http://www.danielnaber.de/tree/>.
** "Collapsable XML Menus" recipe 10.11 on page 307 of his "JS&DHTML
COOKBOOK (O'Reilly & Associates, Paperback, Published April 2003, 520
pages, isbn:0596004672, for sale $40 list $25 bookpool
<http://www.oreilly.com/catalog/jvdhtmlckbk/>.
Cheers
:Monty