[drupal-docs] OPML for documentation import/export

[Charlie Lowe]

Boris Mann wrote:
> 
> Please add your notes directly to the wiki. 

added a note about internal links.

> 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. 

nid's are easier than path aliases. for node id's, the opml module would 
need to map the existing nid to new nid's into an array when importing, 
then do a search and replace on the text of all the nid's.

IMHO, to allow for effective integration of documentation from multiple 
sources, path aliases are not going to work; they are assigned based on 
the context of the documentation. how would the import module deal with 
reassigning path aliases to another unique context specific 
representation when a path alias is already in use on a site?

> Your other stuff is
> guidelines for writing documentation...I'm just focusing my
> technologist skills on building a better mousetrap for import/export
> of documentation at this point.

those were just examples :)

> 
> 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.
> 
> Sheldon (I think?) over on CS has a taxonomy_xml module that is almost
> complete, and probably simpler for Drupal-to-Drupal. Documentation
> doesn't usually taxo terms, so it's likely an "advanced" feature for
> future representation.

taxonomy could very useful for

- providing necessary metadata for the documentation. could be tagged 
with a distribution/distributor field (drupal, bryght, civicspace, 
notify.module, ecommerce.module) and version number (drupal 4.6, 
civicspace .8x, etc.) i could forsee a lot of uses for this, including 
solving some of the document versioning issues.
- master indices. assuming that drupal doc people could agree on a 
master taxonomy for indexing drupal documentation (start by building off 
the project list on drupal.org), tagging documentation with keywords 
would allow for autogeneration of a master index across all 
documentation imported into a site.