Originally Posted by
IAN-UK
EF's map is simply the result of its attempt to interpret data used (internally) by QR. It is the manifestation of a mismatch between systems which were not built to interact in any functional sense.
The interface between QR and its passengers retains its functionality regardless of EF practices.
ExpertFlyer's seat maps are what the airline is publishing into the global reservation systems. We are not "interpreting" the data, we are presenting it just as the airlines publish it. In this case, QR is publishing those seats as Blocked, likely because they don't want travel agencies requesting/assigning those seats.