UML profile lacks clarity in use of "id" attribute and "isID" flag

[onthebreeze]

From Slack thread : Andreas Pelekies:

Importing: In section 2.4.3 you define that
An additional "id" attribute of type "identifier" shall be created for each class. I cannot see this in the StarUML result.
The isID Tag shall be checked for each attribute with name "id" or "name". I cannot find this either in the StarUML result. Example: TransportMovement contains several attributes containing "id" or "name". So setting "isID" to all of them probably is not what was intended. To my understanding only "identificationId" should get the isID checked. Or am I wrong? Wouldn't it be more meaningful to add the corresponding tag in the export first and then define a rule to import this tag and set isID to checked if the tag exists?

[onthebreeze]

Yes I think you are right. In my experience of using the tool for a bit, I think it should not create an "id" property because it's already in the vocabulary. also, as you say, I think it's best if the API designer sets the "isID" flag whenever they want the consequent behaviour and not have it forced by the importer.

So I think the tool is ok and spec is wrong - do you agree?