Cooking with SWF, and the understanding of copyright
There seems to be a lot of angst over the fact that the SWF specification is only covered by copyright. So lets take a moment to discuss this.
I'm not a lawyer, though I get to spend a lot of time around them in relation to standards and open source work. So here goes.
First, the specification is a document. It describes the SWF file format. It's like a book (albeit a short one). You, the reader don't need a license to read a book.
Open nearly any book and you'll see a copyright notice basically saying you can't copy the book. Same thing here
In fact, let's think of this as a cookbook. There are some pretty interesting recipes (SWF, FLV/F4V, AMF) that are there. You can certainly bake a SWF "cake" based on the recipe, and you don't need our permission to do so. You might have to buy some exotic ingredients that the recipe calls for to get it exactly like the lovely illustrative pictures, but you don't expect the cookbook to contain all your ingredients. And while some places provide ingredients for free (such as Tamarin or Flex SDK), not all ingredients are equally free (just as codecs aren't free even to us).
You buy your ingredients (or grow them, if you wish), you use the SWF recipe to bake it, and voila, a SWF-powered application.
Now, as with nearly every product, specification, etc around, there's other interesting text. Trademarks, references to other links, no offer of warranty on the contents. Again, absolutely normal. If you build it, you can't call it by our trademark names. If you use someone else's materials, we aren't responsible for the contents. (Here, think of using a oven to bake that cake. We aren't responsible for bad eggs someone else sells you, nor if you mislabeled salt as sugar). And it's absolutely standard for no warranty to be extended. Your "cake" is completely under your control, and we aren't responsible for how it turns out.
SO, no copyright traps. Feel free to write your own software that implements the specification. Since the specification does not include source code, you can't infringe our source code.
So, we'll look into ways to clarify the issues, but bottom line is that the specification is open and ready for you to cook up a storm.