Learn about Webel's comprehensive SysMLv2 Workshop Seminar course!
Webel now has a SysMLv2 Online Self-Study course with self-test Quizzes!
Learn about the Webel Q&A     online self-testing system for SysML v2/v1

In general, declaring an element within the body of a namespace denotes that the element is an owned member of the namespace—that is, that there is an owning membership relationship between the namespace and the member element.

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
Source
OMG Systems Modeling Language TM (SysML®) Version 2.0 formal/2025-09-03 (Sep 2025)
Copyright information
About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes
Snippet kind
INFO
Full quote
In general, declaring an element within the body of a namespace denotes that the element is an owned member of the namespace—that is, that there is an owning membership relationship between the namespace and the member element.
Next snippet
The visibility of the membership can be specified by placing one of the keywords public, protected or private before the public element declaration.
Related snippets
An Expose is an Import of Memberships into a ViewUsage that provide the Elements to be included in a view. Visibility is always ignored for an Expose (i.e., isImportAll = true).
An Expose always imports all Elements, regardless of visibility (isImportAll = true).
An Expose always has protected visibility.
Related snippets (backlinks)
If the membership is public (the default), then it is visible outside of the namespace. If it is private, then it is not visible. For namespaces other than definitions and usages, protected visibility is equivalent to private.
For definitions and usages, protected visibility has a special meaning relating to member inheritance ...
The visibility of an import is always shown explicitly by placing the keyword private, protected, or public before the import declaration.
If the import is private (which is the default in the abstract syntax), then the imported memberships become private relative to the importing namespace.
A visibility of protected is the same as private, unless the importing namespace is a definition or usage, in which case the imported memberships are also visible in all specializations of the definition or usage ...
If the import is public, then all the imported memberships become public for the importing namespace.
Visit also
Visit also (backlinks)