(Sorry if you guys have already thought of this; I saw no indication
of it in the design doc)
One addition that I think would be useful is file-type tagging that's
more rich than text vs. binary. How about specifications similar to
HTTP, including MIME types? They have their flaws, but overall they
work pretty well. Here's what using them would add:
- Lots of tough decisions have already been made, and there's an
existing standards body maintaining the MIME-type namespace
- You can could use existing mailcap files to associate certain
actions with file types. I know that viewing, editing, and printing
are standard. Subversion could potentially support extensions to
add diffing, conflict resolution, and pre-commit filtering as well.
- Can use existing mime.types files to make much smarter decisions
about how to handle a file on the client side, but using the file's
extension won't be a requirement
- Nice fit with web servers. Subversion could provide MIME types to
Apache.
These could just be implemented as some of the live properties (to use
WebDAV lingo) of each file.
Not something that should necessarily be in 1.0, though it might be
cool, and just having the infrastructure in place might be a good
thing.
Received on Sat Oct 21 14:36:05 2006