Plan Spec-Up-T and Spec-Up integration

[henkvancann]

Hi all,

@kordwarshuis and I are honored to be admins of spec-up.

Our approach to integrate Spec-Up-T and Spec-Up:

1. synchronize / update bundles
2. NPM install instead of the old way
3. Make it optional to take the terminology engine
4. Address the open issues

[henkvancann]

In relation to point 3

What: The regular current def-ref for terminology is the minimal solution. We suggest enjoying the Spec-Up-T Terminology engine.

Why: To offer a choice

|Who: anyone used to DIF Spec-Up

When: Available after the integration

Which way: One-way system, you can upgrade Spec-Up to Spec-Up-T, downgrading (T to old one) will be hand work, content is involved. The directory structure and functionality is different, etc.

[henkvancann]

Topics related to point 1

It is an arbitrary categorization.

1. Client-side
2. NodeJS
3. Specs.json simplification

[bumblefudge]

Hey there, joining in late: what's the status on this stuff? are there meetings on NL time? i'd love to join if so. I just got a feature request from a DIF member and came here to open an issue and saw this, so I'm glad to see work is happening on it!

[henkvancann]

Hi Juan, welcome. The status is that we're making a solid version of spec-up-t at LF-ToIP/Blockchainbird and thereafter integrating it with spec-up.

See more here:

https://github.com/blockchainbird/spec-up-t

https://github.com/blockchainbird/spec-up-t-website (documentation in Docusaurus) generating https://blockchainbird.github.io/spec-up-t-website/

An example of how spec-up-t looks like:
glossary.trustoverip.org (old design)
https://henkvancann.github.io/ctwg-main-glossary/ (new)