Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Expand
title20180125

ATTENDEES: Wendy, Dan S., Jeremy, Larry, Jon, Oliver, Kelly, Guillaume
Johan - unavailable

Update on DNS filing / DDI URN resolution
Achim will be filing issues - we need to track it and nudge as needed
Should CV one be revised to fit into the DDI structure (for example agency name DDI-CV)

DDILIFE-3585
see issue

DDILIFE-3524
NEW revision - Guillaume will review and comment - if OK then this is what we go with

3.3 documentation
Wendy needs to do a brain dump - ASAP
System is up and running after working with Jeremy
Moving examples to COGS
Will put up on Bitbucket to get it available for contributions
Make sure people have access - they aren't beating down the doors at the moment

DID not get to.
3.3 work plan for review release
2018 priorities



Expand
title20180118

ATTENDING: Wendy, Oliver, Jon, Guillaume, Jeremy, Dan S.

DDILIFE-3524 need examples see issue
DDILIFE-3583 closed
DDILIFE-3584 closed

Documentation: Jon needs and hour with Jeremy next week to sort out final issues. Wendy needs to do a content dump for Jon.

Short Sprint prior to NADDI. This is at the pass-off point between documentation and TC review. This is being looked at as a chance to do the following:

Wrap up any documentation issues
Organize and plan work of TC review
Layout DDI4 project work for the remainder of year (this would include Drupal to COGS conversion of work platform)
[space has been arranged]

Oliver - remotely
Jon - remotely
Jeremy - maybe (Sunday is easter) focus is 3.3 almost certainly no

Announcement of sprints and ask people to participate

Should this be a TC meeting? in which case we have 3.3 work that could be done even if it is out for review. Implementation issues, software development issues.

We used to have annual face-to-face meeting and these have always been very productive we need to reinstitute support for this. If we want a TC meeting do we do this as part of a review of 4 or do we want more 3.3 line.



Expand
title20180111

ATTENDEES: Wendy, Dan S., Jeremy, Oliver, Guillaume, Larry

DDILIFE-3524
Original idea was that the conditional text was interleafed with the static text. By using the current conditional text is compute text or identify text using the source parameter. But people want an IF condition that if something is true then insert this text. It's supposed to be generating the text but there is nothing there that does this. If we want both computing text and an IF statement that results in a literal text.

The conditional text type inserts a block of text
How can we a conditional for literal text choices - Using the control construct within the text is overkill so we could probably make something more streamlined for this situation.

IfStatement condition and text if true - should probably go through Else to provide a default insert at minimum

Resolve to add an IfThenElse to choice in ConditionalText.

WT will draft IfElse for dynamic text.

How to indicate the position. Write documentation and examples of usage.
Still want allow source parameter
Want to be able to insert a combination of a text and source parameter as a result of an IF - Limit to a combination of literal text and source parameter


Reviewed DDI_L_3 entries and pulled into Master



Expand
title20180104

ATTENDEES: Wendy, Oliver, Johan, Jeremy, Larry


DDILIFE 3581 - OK to remove

DDILIFE 3582 all approved with following not#4. Make sure it stays in the same order as previous when it was in in AbstraceVersionable. If not just add to each (non Abstract) to retain order

#7-9 move to reusable

DDILIFE 3524 - Check with Guilaume and others about using computation and logical expression, separating "true" and "false" responses into separate conditinal texts. How to specify which text. Definately good to be able to express specific text insert in a consistent way.


Agenda Topic Index Key

2016-1017 Minutes Page

Pre-2016 Minutes Page

AGENDA TOPICDATE
DDI 3.3

20180125

20180118

20180111

20180104

DDI 4 Prototype20180118