|
From: Hogan L. <ho...@Ne...> - 2001-05-25 21:01:24
|
At 12:41 PM 5/25/01, you wrote: >here are some impulsive comments. as i come to understand >what you can do with schema, i will probably have more. > >1) i would gradually like to refactor this schema to support > other card games. So, there might be a very generic > base "Card", and the Card you presented could be > "MagicCard", or a Card, with a family element that > classifies it as MtG > (of course, this direction would probably end up forcing > a name change away from OMD, since it's not Mtg-specific) hmmm.... sounds like it might (sadly) be out of the scope of OMD but if you make a generic card schema send it to me and if I can change the OMD to make use of it I will (ie including it in the Card.xsd as a base that gets modified.) >2) typo, and possible corrections: > > <xsd:simpleType name="card-cost" base="xsd:string"> > <xsd:patern value="(0-9)*(W?U?B?R?G?)"/> > </xsd:simpleType> > > - "patern" should be "pattern" > - i don't think the pattern supports multiple letters, > like "1RR" > - should one or more "X"s be allowed, too? > > maybe something like this? > > <xsd:pattern value="X*(1-9)?(0-9)?W*U*B*R*G*"/> > > (in python, this pattern seems to work: > "^X*[1-9]?[0-9]?W*U*B*R*G*$" You are right about missing the X, multi color needed, and pattern but not about the digits. (0-9)* means any number of digits zero to nine so it works fine. [1-9]?[0-9]? would only match up to 99 so it is not quite right (not that any spell will cost more than 99 but you never know unglued etc.) so I am going to go with <xsd:pattern value="X?(0-9)*W*U*B*R*G*"/> This of course forces an ordering to the color letter - which I like. this seem right to all you regexp experts out there? Dave, can you hear me? >3) i've started noodling with behaviors and scripts (along the > lines of an omd-development conversation a long time ago. > i'm not ready to add this to the OMD spec, but i want to > make sure it fits (and again, i don't want it to be MtG-specific) I'd be interested to see what you got - when you are ready (you can send me non mailing info to ho...@ne...) >on another note, i've also been thinking about adding genealogy >support to deck markup, so that the full evolution of a deck might >be contained in a single file. > <add (cards) > <replace (cards) (other cards) > <remove (cards) > <merge (some other deck) > >i also want to add elements for annotating the changes: why was >a certain card replaced, ... Basically, capture the full dialog of >tuning a deck. > >the two reasons i'm interested in this are: 1) the current on-line deck >tuning sessions/tutorials/etc. don't result in a "consumable" product: >it's just html, and you still have to waste time capturing the deck in >some deck format. 2) i find the whole evolution thing fascinating, >and think it would be cool to draw a tree/graph linking all of the >decks and how they grow. really good idea - I've been pondering this a little too - I plan to address it when I get to the deck schema >any thoughts? i don't yet have a working prototype of a "delta-deck". >i'll post when i have one that i can actually load up. what is a delta-deck? >jeff Thanks for the feedback Jeff - looking forward to hearing more about your project, Hogan |