maybe he should simply stick to # as seperator. As you said, / is used for "x per y". But ; is used to seperate a list where order doesn't matter. In this case however, order does matter (although it's implied by ascending numbers).
Also I vote for not sticking it into PT-3.1-Tradeskill but into a spereate file. This will allow addons to only load that part of data.
iirc the numbers in Tradeskill.Crafted.* are the skill level required to learn/craft the item. This has nothing to do with the data he wants although it may seems so at first look. But there are some recipes that start at yellow or worse at the time you can learn them.
It's you since I added them myself (and I think even before your post, at least I only noticed it after adding the info). Maybe you are having an outdated version of PT3.1 or the change hasn't been 'released', yet.
@saltorio: I jsut noticed that you most likely mind the data you provided by hand from wowhead. But you made a bit mistake:
Instead of the item ids you provided spell ids in many cases (eg most of the ids >50000).
Mind rechecking that data to have it use only item ids? (in many cases on wowhead, the icon links to the item and the name links to the spell creating the item)
I'm going to add sets for stuff money can't buy but other currency can (eg heroic/raid tockens or lots of stuff in Dalaran) but I haven't settled on a name yet and if I should put it in a seperate file. Any comments on that?
Would it be possible to add code to the dataminer to have the data of the sets sorted by the 'key'-id of the values so that a diff shows which ids have been added/removed.
Currently, it seems like the data can shuffle between to dataminer runs so you get a bunch of changes that are none.
we could change it to use @file-date-integer@ instead of $Revision: x $ though that would mean we would have to add special treatment if a svn checkout is used since then that keyword wouldn't be replaced. though a svn cehckout can theoretically be assumed as the latest version I think.
(see: http://www.wowace.com/knowledge-base/repository-keyword-substitutions/ )