Re: Magic Data
Yes, I agree with not nesting tags. Seems like the better solution of the two. May go with "no" instead of "number" also just to keep it shorter.
Not completely sure about type/kind though. I like type better as that is what it is; "type" is part of the domain we're modelling. You bring up a valid point with "type type" looking wierd though. Maybe supertype/type/subtype-elements are better as you originally proposed.
Typing out some other suggestions to see how they look:
Not completely sure about type/kind though. I like type better as that is what it is; "type" is part of the domain we're modelling. You bring up a valid point with "type type" looking wierd though. Maybe supertype/type/subtype-elements are better as you originally proposed.
Typing out some other suggestions to see how they look:
- Code: Select all
<typelist>
<item type="super">Legendary</item>
<item>Creature</item>
<item type="sub">Bunny</item>
<item type="sub">Ogre</item>
</typelist>
<typelist>
<supertype>Legendary</supertype>
<type>Creature</type>
<subtype>Bunny</subtype>
<subtype>Ogre</subtype>
</typelist>
{U}
: Draw a card, then discard a card. If a creature card is discarded this way, untap Civilized Scholar, then transform it.