OPML Inclusion - did I miss the boat?
When including, it’s also not necessary to take an entire outline, starting with its root. The way OPML works, you can take a branch, a twig, or even just one leaf.
From Winer on wikis: Just add OPML; Between the Lines, ZDNet.com
Unless I’m missing something essential (and it wouldn’t be the first time), I think the above statement is completely inaccurate. My understanding of inclusion[1] is that there’s no way to include a sub-node within an outline (unless, of course, that sub-node is itself an inclusion, at which point you’d be including the original source file in your new outline, not the sub-node from the intermediate outline).
In other words, from my standpoint, deep-linking to a point within an outline is not supported by OPML - one of the biggest drawbacks of OPML from my standpoint, but an acceptable weakness rather than a structural flaw.
Am I missing something?
1 Yes, I know that this draft of the spec is not released for deployment, but this point seems to be the description of inclusion that’s closest to the source, and is acceptably cogent for this purpose.
RSS 2
