Skip to content

Rework NamespaceProvider and NamespacedEntity in M3 #146

Closed

Description

@enikao

On 2023-07-07, we decided to remove NamespaceProvider from M3, and rename NamespacedEntity to IKeyed (#142).

Rationale: NamespaceProvider is not really needed. It was primarily meant to establish the semantic idea of a namespace. We still have the semantic idea, but don't need a manifestation in M3.
Calculating a qualified name can work by nested INamed elements. Once we have computed features (#6) we'll probably add a computed feature qualifiedName: String to INamed for this purpose.
Earlier, we thought about using fully qualified names to identify language entities. This is not relevant any more, as we have meta-pointers (#89).

Overall, this simplifies the M3 a lot.

Activity

  1. added a commit that references this issue on Jul 10, 2023
  2. gtothe7 commented on Oct 12, 2025

    @gtothe7

    On 2023-07-07, we decided to remove NamespaceProvider from M3, and rename NamespacedEntity to IKeyed (#142).

    Rationale: NamespaceProvider is not really needed. It was primarily meant to establish the semantic idea of a namespace. We still have the semantic idea, but don't need a manifestation in M3.

    Calculating a qualified name can work by nested INamed elements. Once we have computed features (#6) we'll probably add a computed feature qualifiedName: String to INamed for this purpose.

    Earlier, we thought about using fully qualified names to identify language entities. This is not relevant any more, as we have meta-pointers (#89).

    Overall, this simplifies the M3 a lot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions