It's not. Let's take an example, AMS-IX: https://www.peeringdb.com/private/exchange_view.php?id=26
That record doesn't say AS1200 anywhere. You'll have to search for "Amsterdam Internet Exchange" to find AS1200; a search for "AMS-IX" will lead you only to its route server ASN. There is no way to filter participants by IXP as "Network Type" doesn't offer that option.
I studied all the AS-Path in the routing table (from routeviews and RIPE), and found that some ASN of IXPs were included in some AS-Path. I think that under normal circumstances they should not appear in the AS-Path, hence i want to filter out them.
* nick@foobar.org (Nick Hilliard) [Mon 22 Dec 2014, 15:28 CET]:
Not sure how useful the mgmt ASN is, although most IXPs will paradoxically include this on their list of members.
As long as they don't count it for their total connected parties
statistics, I'm good with it being included in the list, to help
people find missing or since-disconnected peers at the IXP in an
automated fashion.
it is inappropriate to include it in the number of connected parties, but
there's no problem including the IXP ASN in the list of connected parties
so long as it's made clear that they're not standard IXP participants.