SysMLv1: When using model queries (such as tables) for compliance with some older systems engineering docs you may not always be able to use anonymous Property names and anonymous instance level element names. Or try the owner context or the ID!

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
Policy level
Keywords

Often in query view reports including a column with the owner context is completely adequate, and in MagicDraw/Cameo you can even include the generated Element ID.

Dr Darren says:
The documentation requirements of some older "obligatory" pre-MBSE systems engineering methodologies address problems that simply don't exist anymore with modern SysML for MBSE and Single Source of Truth (SSOT) systems!

Names like longTypeName for a Property typed by LongTypeName are not useful; use short role indicators names when there is more than one Property of the same Type in the one owner context, otherwise, unless you have very special report extraction requirements, anonymous Properties are your modelling friend:

In SysMLv1, whenever and wherever you can, always "Trust The Type" to do the talking for the Property!

Visit also some cross-linked examples here:

And a full discussion here:

Relates to
Related notes
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)