All PIMs should. . .
Posted by srdiamond15
on 1/5/2005
srdiamond15
1/5/2005 8:14 pm
I'm generally not too enthusiastic about such proclamations, because pims are almost inherently niche products. But here's one such statement I would endorse:
All pims should import and export to cv files.
This would limit the users losses if he decides to switch pims. Cutting and pasting document after document is no fun, even with a top of the line clip manager.
This would also make it much easier to compare one pim to another.
Stephen R. Diamond
All pims should import and export to cv files.
This would limit the users losses if he decides to switch pims. Cutting and pasting document after document is no fun, even with a top of the line clip manager.
This would also make it much easier to compare one pim to another.
Stephen R. Diamond
sub
1/6/2005 2:37 am
[Stephen D: All pims should import and export to cv files]
I'd alter that to "all pims should import and export to XML, preferably OPML". XML has been created from the ground up to represent hierarchies. It's now the undisputed standard behind content management systems like Radio Userland's. It's fast becoming the underlying structure for Office Suites and all kinds of large scale knowledge databases. I don't think there's any reason to go back to older standards.
alx
I'd alter that to "all pims should import and export to XML, preferably OPML". XML has been created from the ground up to represent hierarchies. It's now the undisputed standard behind content management systems like Radio Userland's. It's fast becoming the underlying structure for Office Suites and all kinds of large scale knowledge databases. I don't think there's any reason to go back to older standards.
alx