Contribution and Organization of Custom Rules

Custom rule writing comrades,
I have a proposition. The folks at Notion provided a bit of information around the future of custom rules. Although we cannot integrate libraries as neatly as those already supported by Notion, it appears that Notion 4 will allow us greater flexibility in writing rules for other libraries.
Instead of assigning rules to a VSTi, it appears we will soon have the ability to write rules to a "group ID" which can be assigned to any staff at any time. More specifically, the group ID will be a unique four character string. I suggest that we establish a naming convention for group IDs so that we can more easily share and use custom rules without creating unintended coding conflicts. This would be completely unofficial, but I think it would make integrating each others' rules much easier in the long run.
My recommendation is to use the first two characters of the group ID string to establish the library or producer for the given rule. For example, we could use "la" for the first two characters of LA Scoring Strings, "ch" for Chris Hein libraries, and so forth.
The third character would be used to identify the instrument family the rule belongs to. "b" for brass, "w" for woodwind, "f" for fretted strings, etc.
Finally the last character could be used sequentially to separate one rule set from another within the same library and instrument family.
Some examples:
"lasa" would stand for LA Scoring Strings, strings, first group ID
"lasb" would stand for LA Scoring Strings, strings, second group ID
"chfa" would stand for Chris Hein, fretted instrument, first group ID
Thoughts?
I have a proposition. The folks at Notion provided a bit of information around the future of custom rules. Although we cannot integrate libraries as neatly as those already supported by Notion, it appears that Notion 4 will allow us greater flexibility in writing rules for other libraries.
Instead of assigning rules to a VSTi, it appears we will soon have the ability to write rules to a "group ID" which can be assigned to any staff at any time. More specifically, the group ID will be a unique four character string. I suggest that we establish a naming convention for group IDs so that we can more easily share and use custom rules without creating unintended coding conflicts. This would be completely unofficial, but I think it would make integrating each others' rules much easier in the long run.
My recommendation is to use the first two characters of the group ID string to establish the library or producer for the given rule. For example, we could use "la" for the first two characters of LA Scoring Strings, "ch" for Chris Hein libraries, and so forth.
The third character would be used to identify the instrument family the rule belongs to. "b" for brass, "w" for woodwind, "f" for fretted strings, etc.
Finally the last character could be used sequentially to separate one rule set from another within the same library and instrument family.
Some examples:
"lasa" would stand for LA Scoring Strings, strings, first group ID
"lasb" would stand for LA Scoring Strings, strings, second group ID
"chfa" would stand for Chris Hein, fretted instrument, first group ID
Thoughts?