Why use API Sequences?

In the example in this section of the cookbook, “API sequences” are defined, which in this case map directly to a single read or write seq_item. I can understand that in some cases you might have a more complex bus operation such as a read-modify-write where this is useful, but for simple read/writes, what is the benefit of creating this additional layer, instead of just creating the corresponding seq_item directly in the higher level sequences?

In reply to miketrim:

I’d wager that the idea behind having API sequences is that it’s easier for newbies to start using them. If, for example, you want to have some of your design or software colleagues help out with verification, it’s easy for them to understand function calls. Starting sequence items/sequences is a concept some people have a hard time wrapping their head around. If you give them a C like API to write tests, then they can feel more comfortable.