2016-07-20 - SLPG Meeting

Welcome, introductions and apologies

@Former user (Deleted)

Agenda review

@Former user (Deleted)

Review agenda for today's meeting

Finalize syntax for cardinality

@Former user (Deleted)

What syntax should we use to define cardinality constraints?

• [[@Procedure]]: [[ {} [1..2] @boris]] { ..... }

• [[@Procedure]]: [[ {} [1..2] ]] { ..... }

• [[@Procedure]]: [1..2 [ @boris]]  { [1..2 [ .....  ]]  ..... }

• [[@Procedure]]: [1..2 [ ]]  { [1..2 [ .....  ]]  ..... }

• [[@Procedure]]: {{1..2 @boris }} { ..... } - ECH, JLO, MLA, RHA, LBI

• [[@Procedure]]: {{1..2 }} { ..... }

• [[@Procedure]]: ~[1..2] @boris { ..... }

• [[@Procedure]]: ~[1..2] { ..... }

• 
  
  

• [[@Procedure]]: #[1..2] @boris { ..... }

• [[@Procedure]]: #[1..2]  { ..... }

• [[@Procedure]]: %[1..2] @boris { ..... }

• [[@Procedure]]: %[1..2]  { ..... }

1. On a focus concept, an attribute or an attribute value - e.g. in the relevant slot [[ [1..*] < 123456 @slotName ]]

2. On a relationship group - e.g. 123456 |concept|: ~[1..*] { .......}

   • Note: The syntax must clearly indicate that the cardinality on a relationship group does not appear in the concrete expression that is generated when the expression template is populated. This is needed to distinguish an Expression Template (with relationship group cardinalities) from an Expression Constraint Template (for which the relationship group cardinalities do appear in the populated version of the template).

   • In this example syntax, the "~" is being used to say "The following constraint needs to be removed when the template is populated."

   • For example, an expression template such as:

     • [[ @Procedure ]] : ~[1..2] @group1 { 405813007 |Procedure site - direct| = [[ [1..1] @bodySite ]], 260686004 |Method| = [[ [1..1] @method ]] }

   • may be populated to generate the following expression:

     • 71388002 |Procedure site - direct|:  { 405813007 |Procedure site - direct| = 66754008 |Appendix structure|, 260686004 |Method| = 129304002 |Excision - action| }

   • Note that the cardinality "[1..2]" is removed when generating the final expression.

Template syntax requirements

@Former user (Deleted)

Are there any other template requirements that we haven't yet considered (e.g. additional concept authoring requirements)?

• Currently being discussed internally within IHTSDO

• Please send me any other functional requirements for templates that you know of - with examples of where and why it is needed.

Finalize draft template syntax

@Former user (Deleted)

•  Goal is to start drafting the template syntax for wider review, and input from IHTSDO Tooling and Content teams.

Confirm next meeting date/time

@Former user (Deleted)

Next meeting to be held in 4 weeks on Wednesday 17th August