[rules-dev] quick design questions to mull over - regarding the repo

BUT this also applies to the file structure for "packages" in a file system/IDE (forget monolothic DRL for a moment - but instead imagine a folder which is a rule package containing lots of rules). (in no particular order); Q1: Should DSL "language configurations" be stored as an "asset" inside a package (ie a file, perhaps multiple ones of them?) - or are they an attribute of a package? Q2: The object model: should this be stored as an attribute of a package - or just another asset of which there can be muliple ones uploaded (as a jar, for instance). This is needed for validation/tooling. Obviously in the IDE the classes will be on the classpath, but in the repo they have to be stored somewhere. Note versioning works well in all scenarios (subtle differences between a package attribute and asset for versioning, but ignore them for now). I have opinions, but wanted some discussion (attachment screenshot shows the package managment screen).