Skip to content

name and hence id/fqn for Standard Definition Components #89

Open
@marksomething

Description

@marksomething

The specification defines name as "MUST be unique within components of the same type", and provides short examples. It's unclear how/why these components would have uniqueness between data products, and if not then fqn as defined would not be fully qualified. Have I misunderstood how this is intended to work.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions