Under the section 'MPD File Structure' it says:
Unofficial parts are allowed to be used. The filename of the unofficial part is subject to the following naming rules:
<Set Number>[-<Optional Qualifier>] - <Unofficial Part Number>.dat
And then under 'File Headers' we have:
Each individual model file in the MPD that represents an unofficial part must use the standard header format of unofficial parts on the parts tracker. Its 0 FILE entry will reflect the modified MPD version of the part's filename, but the rest of the header will reflect the original filename.
This is saying that if I import the part '12345.dat' into a model called '8888-1.mpd' then the part's header should be:
0 FILE 8888-1 - 12345.dat
0 Part Title
0 Name: 12345.dat
This is inconsistent with the MPD spec, which expects both 'FILE' and 'Name:' to have the same value.
The OMR spec also makes no mention of what you should do if you import a part and its subpart. For example, suppose I have the unofficial part '12345.dat' which references the unofficial subpart 's\12345s01.dat'. Presumably the subpart's 'FILE' line will have to read 's\8888-1 - 12345.dat' (although the spec doesn't state anything about this), and so the part will have to have its type-1 lines fixed-up to point to the new name.
I strongly disagree with the renaming given in the current spec, not least because no editing tool currently available will handle it correctly. I also cannot see why it was even considered necessary or desirable.
Unofficial parts are allowed to be used. The filename of the unofficial part is subject to the following naming rules:
<Set Number>[-<Optional Qualifier>] - <Unofficial Part Number>.dat
And then under 'File Headers' we have:
Each individual model file in the MPD that represents an unofficial part must use the standard header format of unofficial parts on the parts tracker. Its 0 FILE entry will reflect the modified MPD version of the part's filename, but the rest of the header will reflect the original filename.
This is saying that if I import the part '12345.dat' into a model called '8888-1.mpd' then the part's header should be:
0 FILE 8888-1 - 12345.dat
0 Part Title
0 Name: 12345.dat
This is inconsistent with the MPD spec, which expects both 'FILE' and 'Name:' to have the same value.
The OMR spec also makes no mention of what you should do if you import a part and its subpart. For example, suppose I have the unofficial part '12345.dat' which references the unofficial subpart 's\12345s01.dat'. Presumably the subpart's 'FILE' line will have to read 's\8888-1 - 12345.dat' (although the spec doesn't state anything about this), and so the part will have to have its type-1 lines fixed-up to point to the new name.
I strongly disagree with the renaming given in the current spec, not least because no editing tool currently available will handle it correctly. I also cannot see why it was even considered necessary or desirable.