-
Notifications
You must be signed in to change notification settings - Fork 0
Meeting #7, 2021 05 20
Zoom meeting 2021-05-20 13:00-15:00 CEST
Attendees: |
---|
Knut Jetlund, Norway, HMMG Convenor |
Evert Bleys, Standards Australia |
Heidi Vanparys, Danish Standards |
Peter Parslow, UK |
Magnus Karge, Standards Norway |
Ronald Tse, CalConnect / Ribose ISOGR |
Chuck Heazel NGA U.S. |
Tobias Spears, Canada |
David Stolarz, US ANSI |
Reese Plews, Japan, TMG |
Minor modifications based om tests for implementation:
- Added attribute
standardizationTarget
toConformanceClass
- Tagged values can only contain 255 characters, which proved to be an issue for requirement texts from ISO 19131. Sparx has a workaround (https://www.sparxsystems.com/enterprise_architect_user_guide/15.2/automation/taggedvalue.html). Another possibility is to use the
Notes
field instead for thetext
attribute. Ref https://github.com/ISO-TC211/AutomatedDocumentation/issues/4
Example based on an existing standard: Tested with 19131 (Magnus Karge and Knut Jetlund). Ref https://github.com/ISO-TC211/AutomatedDocumentation/issues/3.
Magnus Karge had tested the UML Profile. Issues:
- The limitation of 255 characters. Ref https://github.com/ISO-TC211/AutomatedDocumentation/issues/4
- The content of IdentifiedObject-attributes:
URI=complete URI
.name= local name
, for example the last part of the URI for 19131 requirements. - Example:
URI=https://standards.isotc211.org/19131/-/2/req/content/specification-language
,name = specification-language
Knut Jetlund presented an OWL representation of the conceptual model and an RDF representation of the ISO 19131 modular specification.
A challenge for the implementation of the conceptual model may be how to get the Project Teams to develop modular specifications according to the model. EA and the UML profile has a user thershold, and so do tools for writing RDF. The suggested approach from this group is to follow the UML approach, and rather export to RDF for further use. A template of a modular specification in EA may be useful. Besides, export and import to and from spreadsheets etc may be useful for the project teams, for maintaining content.
Updating the documentation on https://github.com/ISO-TC211/UML-Best-Practices/wiki/DocumentationOfUmlModels
- Tobias Spears and Heidi Vanparys volunteered in the previous meeting to review the content and start the work on updated documentation. This is still left to be done, after we have finalized the model and implementation approach for modular specifications.
- ref https://github.com/ISO-TC211/AutomatedDocumentation/issues/1
Ronald Tse presented the latest version of the tools for deriving documentation, with ISO 19170-1 and CityGML as examples. Some issues:
- Some challenges with file formats for diagrams. NOTE: ISO CS prefer separate EMF files, for translation. They accept PNG for UML diagrams, as we do not want them to be able to perform changes that may break the model. We have a good relation to ISO CS on this issue.
- Should the model-derived content in standards documents be purely machine-written, or can some content in between be manually written? This group suggest that manually written content should be avoided for the clauses in question.
- Structure of the tables for representing classes, attributes and associations: ISO/TC 211 standard have used many different layouts for those tables. We suggest to have only one layout, which can be derived from the UML model.
- For ISO 19170-1, each subpackage becomes a main clause in the document (6, 7, 8). For other standards, it may be better with only one main clause for the model documentation, with subclauses (6.1, 6.2, 6.3 ...). This can be configured.
The presentation has been uploaded here.
The work from the AHG will be presented at the HMMG meeting on June 9th (https://sd.iso.org/meetings/77107)
- Recommend the use of MDD for ISO/TC 211 standards
- Present the draft extended conceptual model for modular specifications, with implementation examples
- Future NWIP for the conceptual model for modular specifications, extended with normative statements
- Update the existing documentation (https://github.com/ISO-TC211/UML-Best-Practices/wiki/DocumentationOfUmlModels) & https://github.com/ISO-TC211/UML-Best-Practices/blob/master/DocumentationOfUMLModels/Automatic%20generation%20of%20documentation%20from%20UML%20models.docx based on findings from this group. Will be on Github only, not as a Word document.