FRAGMOS - New Operator "string value" for drafting new kind of Condition

[JBZ-Fragmos]

Background

When an attribute is of type string, there is currently no way to force specific content for it.

Business Need is mostly situated in CDM spaces which relate to the modeling of

• Legal terms (screenshot A & B below)
• or Structured terms (screenshot C)

example A

example B the type Clause is actually made of string attributes nested within each other

example C quoted from Fragmos WS designed on behalf of Structured Product WG

Proposal

Create a new operator in Rosetta for specifying a condition according to which an attribute of type string must have a particular content. This means the value of the string is fixed by the condition.

• Proposed name for this new operator :
  • string =
• Proposed syntax for this new operator :
  • [attribute name] string = [expected value of the string]

Illustration

• say there is particular context for which type Multiplier below which include an attribute named bespokeName of type string

• say this Multiplier is used in a path, whatever it is, we may illustrate situation in generic manner e.g. "object -> multiplier -> [...] -> object"

• say we want bespokeName string value of Multiplier to be forced as [Bonus Lever] in this particular path

• then would attach the condition below to the parent object of which multiplier is an attribute :

[Oblongs]

A couple of points:

1. Not sure I understand why this syntax doesn't work?

2. This is probably a proposal to change the Rune DSL, rather than the CDM, and therefore should be in that project, ie https://github.com/finos/rune-dsl/issues. That project is also open source.

[JBZ-Fragmos]

thanks for the feedback @Oblongs

in regards of your two points :

1. the syntax is only a proposal, for illustration purposes, i do not know and i have no specific will for particular syntax or another one, my point is on the behavior i.e. expected effect... that is to force the value of a string... So in the above exemple, say there is an attribute which name is "bespoke" and that is of type "string", and i would like this "string" value to be "Bonus Lever" for instance...
2. do not understand the frontier between Rune // CDM... so far a "condition" and related syntax is an item that is part of CDM in Product Model (with a big "P" here... by opposition to Functional or Process Model) I mean that any "condition" is an item that belongs to a type object in CDM, so even if there is Rune-DSL behind the scene for checking whether condition is effectively applied in Process Model, all in all the "condition" is a CDM component and therefore do not understand why not referring any related Issue under current project scope