In preparing the DCTAP as a document section for the SRAP documentation, I feared that having the ShapeID on the same row as the first property in that shape looked confusing. I therefore moved the shapeIDs to the row above.
We discussed having rows for shapes in the past but as a way to have constraints on the shapes. I'm wondering if we shouldn't include some examples in the Cookbook that show the shapeID on its own row for easier readability.
In preparing the DCTAP as a document section for the SRAP documentation, I feared that having the ShapeID on the same row as the first property in that shape looked confusing. I therefore moved the shapeIDs to the row above. We discussed having rows for shapes in the past but as a way to have constraints on the shapes. I'm wondering if we shouldn't include some examples in the Cookbook that show the shapeID on its own row for easier readability.