[
Lists Home |
Date Index |
Thread Index
]
> -----Original Message-----
> From: Bill Humphries [mailto:bill@whump.com]
...
> You have to have an editor in the process, otherwise your writers find
> clever ways around your schema and drift sets in. It isn't much work if
> it's done regularly.
If you are referring to a meatspace editor, expecting an editor to enforce
schemas will simply not work. They are too busy and focused on other
things.
If you are referring to a schema-directed text editor, there are many issues
one must solve such as:
1. Acquisition and training cost might be prohibitive
2. Frustration caused by inflexibility can affect productivity
3. Slow and akward schema evolution
I think a web-based solution with policy-directed schema editor that allows
only certain types of schema changes might be more effective. If harmful
schema changes are prevented, it shouldn't be too hard to just walk the
history of schema changes and generate appropriate migration scripts. This
approach also allows one to integrate business process.
Best,
Don Park
Docuverse
|
