I propose missed terminology

[a-x-]

Let's start to use a few new terms.

from: https://gist.github.com/a-x-/78933daf585d236f62831acf078a88d8#complete-formed-bem-blocks-literals

1. bemslug {String} e.g. 'block__elem_mod_val' slug is a short notation, //wiki/slug
2. extended-bemslug {String} e.g. 'block_mod_val__elem' it's used in the BH

from https://gist.github.com/a-x-/78933daf585d236f62831acf078a88d8#partial-bem-blocks-declarators-literals-tenorokи:

3. masked-bemslug {String} e.g. block_* (a mod of block, not elem) etc. (see more)

4. bemjson constrains:

   • bemjson-name {Object} {block: 'block', elem: 'elem', modName: 'mod', modVal: 'val'} — single block applicator/matcher declaration
   • bemjson-decl {Object} {block: 'block', elem: 'elem', elemMods: {mod:'val', mod2: 'val2'}} — multiple blocks applicator/matcher declaration
   • bemjson-def {Object} {block: 'block', elem: 'elem', elemMods: {mod:'val'}, content: [...],,,} — general bemjson block definition

[a-x-]

/cc @zxqfox @blond @tadatuta

[a-x-]

bemslug BNF like spec: https://gist.github.com/a-x-/78933daf585d236f62831acf078a88d8#bemslug-separators-schemes

[qfox]

[a-x-]

[qfox]

1. bemslug {String} e.g. 'block__elem_mod_val'
2. extended-bemslug {String} e.g. 'block_mod_val__elem'

Not sure who needs this and why you need to operate with string representations of BEM entities.

3. masked-bemslug {String} e.g. block_* (a mod of block, not elem) etc. (see more)

Even more confused why we need this in methodology.

4. bemjson constrains:
   • bemjson-name {Object} {block: 'block', elem: 'elem', modName: 'mod', modVal: 'val'} — single block applicator/matcher declaration

This is exactly the same what we call BEMEntityName.

• bemjson-decl {Object} {block: 'block', elem: 'elem', elemMods: {mod:'val', mod2: 'val2'}} — multiple blocks applicator/matcher declaration

This is Node for sure, absolutely not a decl.

• bemjson-def {Object} {block: 'block', elem: 'elem', elemMods: {mod:'val'}, content: [...],,,} — general bemjson block definition

What is the difference between 5 and 6? This is Node again.

[a-x-]

ok, let's keep BEMEntityName, and we not need bemjson-name so, BEMEntityName is for call one entity by name and BEMEntityNode is for call multiple entities finnaly, BEMEntityDef stands for definition entity, it's not for just call them.

[a-x-]

The string representations of BEM entities is too long and it's not ready for code term And yes, i see more cases, when we need term for

[a-x-]

I need a bemslug here for example. Help me. What are you think, guys?

[qfox]

BEMEntityNode, BEMEntityDef → BEMJSONNode ?

[tadatuta]

I don't think we should extend methodology with new terms if there's just so few cases for them.

[a-x-]

I have many cases. l'll gather them here in the future until the term will become obvious