Both of you make good points. I do tend to assume that people should know what they are doing when they start to be professionals, but as you note, that isn't always the case.
I have no objection to the warning -- I love warnings -- but I'm not sure it would help the situation beyond alerting that something is awry. The user MUST understand what the warning means and make the right decision, no? If you answer one way, your spot will be converted to process as defined by the document, if the other way, your process will get redefined as spot.
Gerald said the warning was eliminated in CS2 and the color is replaced with the document definition automatically. I took that to mean a defined process color could be converted to spot as well as the other way around. But now I'm really confused because I just did a little experiment.
Here's what I did. I made a simple rectangle in AI and colored it Reflex Blue C using the book definition, so it is spot. I made another file the same way, but redefined the color to be process in Illustrator, so now I have two files with swatches named Reflex Blue C.
Next I made 2 new files ea in ID 3 & 4 with Reflex Blue C swatches. I defined one of each to be spot and one to be process.
Here's what I found:
In all cases, the file that had the process definition of the swatch imported without warning into the ID file, and retained it's process definition. If, however, I tried to import a spot definition into a file with a process definition I got a warning in CS and it either converted the color to to process or to spot, depending on the answer, as mentioned above, so there was uniform color defined. In CS2 it was converted as Gerald said into process without warning.
This is not exactly the same as converting everything to the document definition. Also, both of the imported files can co-exist in the same file happily. I suspect all of this is because ID does not import the swatch with the process definition when you place the file, it simply imports the color, whereas it does import swatches defined as spots in order to create the plates.
I can see where this could be a problem for a collaborative situation where someone mistakenly redefines a spot to process in ID. Assembling the files into a book and synching colors could mess up the entire book if the process file were chosen as the reference. On the other hand, it requires a real effort to make this happen -- you must deliberately re-define the spot to process in ID, so it is rarely likely to be an accident.
I think the opposite situation would crop up more frequently, i.e. the color is redefined outside ID and what you presume is a spot color comes in as process without any warning at all. I guess this just reinforces the necessity to understand what the spot/process difference is, and to learn to use the separations preview before going to press, just to double check.
Peter