search

Xalgorithms / rm-functions

https://rm-functions.netlify.app/
GNU Affero General Public License v3.0
1 stars 0 forks source link

Hierarchical naming structure for rules. #6

Open jpotvin opened 3 years ago

jpotvin commented 3 years ago

We're going to need a method to accommodate optional hierarchical naming to any rule. For example, the one I am working on presently is: TRADE AGREEMENT: Trans-Pacific Strategic Economic Partnership Agreement ARTICLE: Article 3.12: Price Band System SECTION: 1 The number of layers of a hierarchy will need to be flexible; as far as I can reckon less than a half-dozen, but possibly I've not thought of scenarios that would reasonably require many more. I would NOT name the layer fields per se, as what these fields would be called will depend on the domain.

Optimally the user working on a whole set of rules should be able to auto-fill the higher-level segments. For example, once I finish working on section 1, I should be able to start a new rule which is section 2 by calling up the first two parts.

RyanFleck commented 3 years ago

In the future, we can store this (like the address problem) in an array.