For the marketplace ("Distributed E-Commerce") feature down the line, how does metadata like pictures and such descriptive info get stored?
Well, with Class B we're limited to a touch over 7KB per transaction so technically we could fit in a thumbnail or small image, but personally (just my view) I come firmly down on the side of keeping things as light as possible. At first thought I'd posit if we need images we store them externally (eg link to a http resource or secondary blockchain that's fit for purpose as a storage provider).
From my suggested amendment EDIT: Sorry old habits, this is actually part of the spec now

The size of a Mastercoin packet in a compressed public key is thus 31 bytes (33 bytes minus the first and last bytes for the key identifier (02) and ECDSA manipulation byte). The Mastercoin packet reserves the first byte for the sequence number, providing a total of 30 bytes per packet for Mastercoin transaction data. The range of sequence numbers in a Class B transaction is 1 to 255, providing for a total 7,650 bytes maximum actual transaction data storage per Mastercoin Class B transaction.
What about an API fed exchange on a website? The API data would come from the raw blockchain data, but could be nicely designed like any other web based exchange. Is that even possible? I'm think something similar to blockchain.info's redesign of the raw blockchain...