An example of this is a WellFormedEntry being rendered in HTML, RSS, OPML, or whatever other formats may exist. It is conceivable that the WellFormedEntry would be required to keep track of all of it's various physical representations and know how to direct folks to each.
Prior art from other domains:
[MarkNottingham] I'm beginning to suspect that we'll end up with a format that serializes multiple alternate representations as content modules; it would be nice if the content modules could optionally replace the content with a URI if you don't want to include it locally.
[TimothyAppnel] +1 James.
[BillKearney] I'd favor some sort of mechanism that allowed for programmatic resolving of available alternatives. As in, make it possible to use a common querying mechanism to ask what other formats of an item are available.
[JasonGorman] I would find that very useful, too.
[TimBray] Mu explained: This is not something that needs to be defined at the current time; we do not have sufficent consensus, experience, or running code. I suggest amputating this branch of the tree or sticking it in FutureWork.