Part Suffixes

[Orion Pobursky]

Right now we have 6 different types of part number suffixes:
pXX(X)/pNNNN - Patterns
cXX - Shortcuts
dXX - Sticker Shortcuts
kNN - Flexible sections
-fN - Flexible states
s01 - Subpart
bNN - Sticker box subparts
Note: X = 0-9a-z, N = 0-9

b and s are easy, they're only for subparts.

By my reckoning, the rule is:
p/c in any order followed by optional one of d, k, or -f

Questions:
Is <part number>p01c01 a pattern, shortcut, or both?
What about <part number>c01p01?
If it's one or the other, what is the base part: <part number> or <part number>p/c01?

[Orion Pobursky]

I've reflected on this a bit. I think the possible combos are:

Pattern:
pXX
pXX-fN
cXXpXX
cXXpXX-fn

Composite:
cXX
cXX-fN
pXXcXX
pXXcXX-fn

Sticker Shortcut:
dXX
dXX-fN
pXXdXX
cXXdXX
pXXdXX-fn
cXXdXX-fn
pXXcXXdXX
cXXpXXdXX
pXXcXXdXX-fn
cXXpXXdXX-fn

Flexible Section
kXX
pXXkXX

[Peter Blomberg]

Questions:
Is <part number>p01c01 a pattern, shortcut, or both?
What about <part number>c01p01?
If it's one or the other, what is the base part: <part number> or <part number>p/c01?

Neither.

All patterned parts should have an unpatterned base version even if it never existed physically.
All assemblies should have an uncolored base version even if it never existed physically.
Some assemblies have an assembly number <> and some are suffixed onto the base part number <>cXX.

An assembly contains at least two parts; any of which can be patterned or colored. Whether they are or are not patterned/colored, should not affect the numbering.

<> is the base part
<>p01 is a patterned version of the base part --> PATTERN
<>c01 is an assembly containing the uncolored base part --> ASSEMBLY
<>c02 is an assembly containing colored part(s) --> ASSEMBLY
<>c03 is an assembly containing any number of patterned parts --> ASSEMBLY

<>p01c01 could be a shortcut(assembly) containing <>p01 as a member --> ASSEMBLY
<>p01c01 could be useful when there is already a corresponding c01 for an unpatterned part, but it is rare that a pattern would duplicate all existing assemblies. Therefore, I'd prefer not to have the p01 in the part number.

<>c01p01 is clearly a misnomer because the above suggests that any pattern or fixed part color is to affect a part and not an assembly.

[Hageta]

Neither.

All patterned parts should have an unpatterned base version even if it never existed physically.
All assemblies should have an uncolored base version even if it never existed physically.
Some assemblies have an assembly number <> and some are suffixed onto the base part number <>cXX.

An assembly contains at least two parts; any of which can be patterned or colored. Whether they are or are not patterned/colored, should not affect the numbering.

<> is the base part
<>p01 is a patterned version of the base part --> PATTERN
<>c01 is an assembly containing the uncolored base part --> ASSEMBLY
<>c02 is an assembly containing colored part(s) --> ASSEMBLY
<>c03 is an assembly containing any number of patterned parts --> ASSEMBLY

<>p01c01 could be a shortcut(assembly) containing <>p01 as a member --> ASSEMBLY
<>p01c01 could be useful when there is already a corresponding c01 for an unpatterned part, but it is rare that a pattern would duplicate all existing assemblies. Therefore, I'd prefer not to have the p01 in the part number.

<>c01p01 is clearly a misnomer because the above suggests that any pattern or fixed part color is to affect a part and not an assembly.

Do unpatterened parts, that do not have physical version, have the "~" name prefix?