Re: [Omd-dev] tuning of Card schema

[Jeff T. <sjt...@ya...>]

(to keep this relatively short, i cut out some stuff, noted by "...")

> ...
> When something is a creature then the card needs to have
> an additional field "sub-type" that states what "type of creature it
> is"

isn't this covered by CreatureCard?

<xsd:complexType name="CreatureCard"/>
  <xsd:complexContent>

  <extension base="Card">
    <xsd:element name="subtype"   type="xsd:string"/>
    <xsd:element name="power"     type="positiveInteger"/>
    <xsd:element name="toughness" type="positiveInteger"/>
  </extension>  
  </xsd:complexContent>
</xsd:complexType>


> When something is an enchantment then the card needs to have
> an additional field "sub-type" that states what it enchants.

ok.  i'll add that.  i'll also remove "Enchant Land",
"Enchant Creature", from CardTypes, since the new
extension covers that.

<xsd:simpleType name="CardType" base="xsd:string">
    <xsd:enumeration value="Artifact"/>
    <xsd:enumeration value="Creature"/>
    <xsd:enumeration value="Artifact Creature"/>
    <xsd:enumeration value="Instant"/>
    <xsd:enumeration value="Sorcery"/>
    <xsd:enumeration value="Land"/>
    <xsd:enumeration value="Enchantment"/>
  </xsd:simpleType>


  <xsd:complexType name="EnchantmentCard"/>
    <xsd:complexContent>
      <extension base="Card">
        <xsd element name="subtype"   type="EnchantmentTargetType"/>
      </extension>
    </xsd:complexContent>
  </xsd:complexType>

  <xsd:simpleType name="EnchantmentTargetType" base="xsd:string">
    <xsd:enumeration value="Artifact"/>
    <xsd:enumeration value="Creature"/>
    <xsd:enumeration value="Land"/>
    <xsd:enumeration value="Permanent"/>
  </xsd:simpleType>

 
> When something is an artifact it can also be a creature (with
> creature
> attributes) - how do we do this... any ideas?

i'll have to think about that.  since there's currently no
Artifact "subclass", we can get away with another CardType.

> ...
> >#    - minor changes, to line schema up with current xml set files
> >#        - added single-letter rarity codes
>
> how would this work? seems a program would have to check for both
> - makes more work for the end programmer... any ideas?

this was mostly pragmatic: all of my <set>.xml files (mostly dated
Jan 2001) use the single-letter code.

i agree that aliasing tends to cause headaches, but if you want
to stick with "Uncommon", we'll have to update all of the existing
xml.

> >#        - replaced "Colorless" with "None"
> 
> why is none better?

it's not - just lining up with the existing xml: all "colorless"
examples i could find in the xml used None.

> >#        - upper-cased colors and types
> >#            - is xml case-sensitive?
> 
> XML IS CASE SENSITIVE - please be careful!
> my plan was to just have "high" level defines be uppercase
> (eg Card, Expansion, Deck etc.)

again, just lining up with the current xml, which uses "White",
"Blue", ...

> >#
> ># Notes:
> >#    - i would like to add a <state> element, for arbitrary stuff, 
> >#      so that i can store the full state of a game/table
> >#
> >#        <state key="tapped"   value="true"/>
> >#        <state key="location" value="500@300"/>
> >#        <state key="z-order"  value="5"/>
> >#
> >#     any objections?  (note: this might be a way to "try" things
> >#     before schema-izing them, too)
> 
> The way to do this is to create a NEW top level data item...
> called 
> <StateCard>
> This would include all the stuff from the card schema (see schema
> doc on how to do this) and the new stuff you need for state
> information.
> 
> If you want to start creating a schema for functional information
> (eg when this comes into play destroy target non-black creature)
> please call this schema <FunctionalCard>
> (Note for any type of simulator to work you need to have the concept
> of a FunctionalCard being an effect that goes on the stack.  If this
> is not clear email me.)
> 
> If you want to create a schema for collection information
> call this schema <CollectionCard>  (eg condition, value, location
> purchased etc)
> 
> Can you think of any other card schemas needed besides
> Card
> StateCard
> FunctionalCard
> CollectionCard

i see where you're going with this, but i wonder if schemas support
multiple inheritance
("mixins" is really what i want): i want all of these
things to "be" Cards, but i can see scenarios where
i will need a single Card, with state, functionality, 
collection info, and possibly other stuff 

i'll think about this some more



__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/