This thread is the best resource for vlans…
http://forum.mikrotik.com/t/using-routeros-to-vlan-your-network/126489/1
Caveat the below is based upon my experience with ROUTER vlans on a bridge with bridge filtering (not switch based vlans).
Basically bridge ports are used to identify trunk ports and access ports when vlans are involved.
The pvid is entered for access ports as this controls the ingress functionality/rules for that port.
Typically we also besides the PVID add the following security additions. ingress-filtering enabled and allow-frames-only untagged and high priority.
This applies equally to etherports and WLANs.
The interface bridge vlans are used to dictate egress traffic rules.
In this case we identify tagged vlans (trunk ports) and untagged vlans (access ports) and of course the associated vlan-ids.
Some confusion comes into play when people use their bridge as their DHCP server and main lan. The problem is that the default PVID of the bridge and managed devices=1.
This leads to confusion and issues down the line. Much better to let the Bridge and managed devices keep their default pvid setting for bridge and trunk ports and put the homevlan on its own vlan (like 11).