This StyleSheet defines how tags (datapack), tags (/tag), nbts, scoreboards, functions, advancements, loot tables, structures, world generation settings, recipes, data storage are formated.
This convention aims to prevent conflict when deciding the name for your scoreboards, functions, storages, etc. by using a "namespace prefix".

Reference: https://mc-datapacks.github.io/en/conventions/namespace.html

#>Scoreboards: use . to seperate namespace from the name

    xxxx.yyyyyyyyyyy
    
    with xxxx being the short form of the datapack name and yyyyyyyyyyy being the name

    e.g.:
    scoreboard objectives add holo.time dummy

#>Tags: no character limit -> make it detailed / use . to seperate different parts

    xxxxxxxx.yyyyyyyy.zzzzzzz

    with xxxxxxxx being the datapack name, yyyyyyyy being the the subsection where this is used and zzzzzzzz being the name

    e.g.:
    tag @s add holopack.gui.table

#>Data storage: has already support for namespacing -> don't need to use a prefix

    xxxxxxxx:yyyyyyyy/zzzzzzzz

    with xxxxxxxx being the datapack name, yyyyyyyy being the the subsection where this is used and zzzzzzzz being the name
    
    e.g.:
    data merge storage holopack:gui/table {}

#>Custome Data: wrap the custom_data nbt inside another tag

    xxxxxxxx:{yyyyyyyy:zzzzzzzz}

    e.g.:
    give @s diamond{boomber: {custom_data: 123}}


    
    
    
    
Possible other variants: namespace_foo, NAMESPACEfoo, namespace.foo, namespace:foo and namespace/foo