[drupal-docs] OPML for documentation import/export

[Vladimir Zlatanov]

+1 OPML sounds like a great way to advertise what is available
on-site.

 
> Please add your notes directly to the wiki. I'm not sure exactly how
> we would handle links. I suspect we would need support for path
> aliases, since we couldn't rely on node ids. 
path aliases will work, but might provide path clashes, similar 
situation will arise from taxonomy paths. Basically we can't or
shouldn't enforce but at most just suggest documentation structure,
since different sites will have different focus hence different
needs and ways to provide or classify documentation to users. Blind
mapping and replication might work at first, but will most probably
result in very unorganised(hard to understand/navigate) documentation.
It's actually related to the discussions about folksonomy vs
taxonomy ...

I don't want to promise too much, since my time at the moment is
extremely limited, but I'm trying to work on a simple partial path 
mapping between independent sites. It's a kind of automagic aligning of
different documents based on some form of paths. It's to be used with I
scheme I intend to propose to exchange pieces of information between
sites, the scheme should be independent of underlying transport RSS,
RDF, whatever.

If somebody is interested, please contact me off list, since it can 
get too technical and is not worthy at the moment to waste everyones'
time on that.

> ENT is great, and it would be fantastic if Drupal supported it (it's a
> bit like an open distributed version of Technorati tags). I don't
> think it applies in this case necessarily.
I concur, ENT is great way for tagging or hinting what is this thing about,
can be very helpful in doing your own mapping, where should something go
in your documentation tree, but won't solve the problem of where is it 
logical or best to place an article.

The problem can be split into two major parts:
* how do we exchange docs
* how do we integrate the imported or related docs

OPML will help solving the first bit by announcing what is where.
Regardless whether you want to actually import the documentation or just
refer to it (similar to interwiki)

ENT and related will provide hints on how to integrate the docs into
your own strictures as any other taxonomy or tag exchange, but still
there will be a need to provide mapping between the different sites
vocabularies, unless of course a strict control vocabulary is introduced
- I'm not sure that it is the best idea though.

Cheers,
Vlado