[ENHANCEMENT] Support multiple table generation and embedding in IEC documents via AsciiDoc

[jarthurgrey]

Is your feature request related to a problem? Please describe:

We want to make use of CIMTool table generation in IEC documents. Depending on whether one is dealing with an IEC 61968-45x series standard for RDFS profiles or an IEC 61968-3 through -9 (Part) standard for XSD profiles (or JSON), the tables generated are different. We would like to be able to generate them and reference them consistently even within the same .adoc file.

Describe the solution you'd like:

I would like to open the UCAiug-CIM repo up on my desktop CIMTool, go to my IEC 61968-3 master, or 61968-452 master, or some custom master document that references tables and parts of each of these, and then generate downstream HTML and PDF documents.

Describe alternatives you've considered:

N/A

Additional context:

N/A or To be added examples of existing generated tables and their code.

[tviegut]

@jarthurgrey : Thanks for identifying this as it's an important consideration. Could you gather as many examples of variations of tables to be generated as you can identify? This can be as simple as screenshots in comments for this GitHub issue that include which standard you have taken them from (and the edition). For sure each of IEC 61970-301, IEC 61968-11, IEC 62325-301. Then I think from a couple of the IEC 61968 Part standards. IEC 61850 table will be fairly different so we'd need to evaluate if they vary across the different 61850 part publications. Thanks in advance for gathering this as requirements.

One other thing. Table structures have changed over the years as better ways to express them have been identified. You'll notice this for example in the IRC 61970-452 across editions. So we'll want to confirm latest expectations.

• Todd

[jarthurgrey]

I will focus on CIM17 and CIM18 as a priority.

IEC 61970-301
(Ed. 8, CIM18 Non-generated)

(Ed. 7 CIM17 Generated)
Starting from section 6 with the jCleanCIM variable:
startUmlPackage.Base.endUml
replaced to show:

And more specifically we get tables like:

And a little further down for some slight variety:

and

IEC 619670-452
(Ed. 5 v03, CIM18 Non-generated)

(Ed. 4 Generated)

IEC 61970-600-2
(Ed 1, CIM18 Generated)

More to come...

[jarthurgrey]

IEC 61968-11 Ed. 2

IEC 61968-1 Ed. 3

IEC 61968-6 v14

IEC 61968-100 (for reference)

More to come...

[jarthurgrey]

IEC 62325-301
(rev 4)

IEC 62325-451-3 Ed 1

[jarthurgrey]

I will pause for now to see if this satisfies most of the base cases...

I did mostly stick to the latest published versions or latest draft versions I could find. Of course I mostly stuck to showing tables as well because that's what we called out in the issue/discussion we had. However each part team and WG has a variety of images from XMLSpy, EA, or other sources and other code components. Let me know if it will make sense to have another issue to cover those. I think largely that should be covered by SVG and puml handled already, along with individual image references.

You mentioned IEC 61850 "will be fairly different so we'd need to evaluate if they vary across the different 61850 part publications." I will talk to some members this week and review the documentation we have and get back to you @tviegut .

Thanks!
Jesse