Remove "highly normalized" #424
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This shouldn't have been left in there, so I'm correcting the mistake. Rather than saying "typically denormalized", or "low normalization", I think it's best to remove altogether, as it's not an important basis of comparison against a relational data model. There are not specifications, per se, that dictate the level of normalization that should be applied to semantic models. While it's true that oftentimes some denormalization occurs when creating a semantic model, if the model is meant to be consumed by users who would not have knowledge of the underlying data structure and the importance of some relationships over others. But denormalization is not a prerequisite for a semantic model, because you can still express relationships. Though the goal is less about storing data efficiently (like through normalization) and more about expressing the logical model of the data. In either case, being highly normalized is certainly not an attribute of a semantic model.
|
Thanks @joelhulen |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This shouldn't have been left in there, so I'm correcting the mistake. Rather than saying "typically denormalized", or "low normalization", I think it's best to remove altogether, as it's not an important basis of comparison against a relational data model.
There are not specifications, per se, that dictate the level of normalization that should be applied to semantic models. While it's true that oftentimes some denormalization occurs when creating a semantic model, if the model is meant to be consumed by users who would not have knowledge of the underlying data structure and the importance of some relationships over others. But denormalization is not a prerequisite for a semantic model, because you can still express relationships. Though the goal is less about storing data efficiently (like through normalization) and more about expressing the logical model of the data. In either case, being highly normalized is certainly not an attribute of a semantic model.