I do not like the side-file idea, in both of its incarnations
- 1 sidefile per part
or
- 1 sidefile for the whole library.
My reasoning is that the connection information is a genuine information coupled tightly to an individual part.
There is no better place to put that information as directly into the part's DAT implementation.
I can not imagine a more canonical place to put that.
This especially becomes important when that connection information at one day in the future will have become
an official standard. Then it needs to be reviewed / checked the same way as the rest of a part's implementation.
Not putting the information into the part's DAT file will mean evading that strategy.
- 1 sidefile per part
or
- 1 sidefile for the whole library.
My reasoning is that the connection information is a genuine information coupled tightly to an individual part.
There is no better place to put that information as directly into the part's DAT implementation.
I can not imagine a more canonical place to put that.
This especially becomes important when that connection information at one day in the future will have become
an official standard. Then it needs to be reviewed / checked the same way as the rest of a part's implementation.
Not putting the information into the part's DAT file will mean evading that strategy.