Let’s put our money where our mouth is. Last week, we wrote about the need to favor protocols over APIs. This obviously also applies to schemas.
Recently a customer of ours asked about the iTunes Store feeds. As we normalize (mostly to ATOM and a couple other namespaces), some of the data that this user needed was missing, as this data was part of the
We could certainly start supporting this protocol, but we quickly found out that some of the data would be redundant with the ActivityStreams schema that we already implement. This iTunes feed, for example is a list of albums, and albums are objects, so this feed could certainly be mapped in some kind of ActivityStreams schema. Obviously it is not ‘complete’ AS, as there is no activity, but at least one can use the same code to identify the objects, whether they’re albums, pictures, or places!