|
From: <omd...@li...> - 2004-01-16 17:42:59
|
I'm not exactly sure what you mean by "sets". Based on looking around the OMD project webpage, it seems like OMD is also about developing applications for building deck files and what not. Did one of the applications contain a card database for deck building? I guess my impression for what to do with the XML standard once developed was slightly different. While I think the sorts of applications that are being written are useful, I think that the real kicker (pun kinda intended) here is the promise of interoperability between programs. That means that I should be able to download a deck file from brainburst.com, play with it in apprentice or magic workstation, tweak it in the java editor that you folks provide, print it out using a decklist printing tool to take to my tournament, and then post it on my own website by using XSLT along with my description of how the tournament went. I feel like the key to making this interoperability happen is having a standard that is independent from any single application (though certainly getting feedback from all the potential users of the standard). Then we go to application developers (as well as maybe developing our own projects, like a basic deck editor, a basic XSLT stylesheet, etc.) and convince them that XML will make their lives applications easier to write, and that interoperability will make their applications more powerful. I think this is where the real promise of OMD lies. It's interesting. I've been working on my own version of the DTD in the event that one didn't exist, and it's rather creepy how similar they turned out. I guess when one is taking inspiration from the same sources (like websites and deck editors), I guess that's bound to happen. My DTD is at: http://xenon.stanford.edu/~mdevine/dtd/magic-deck.dtd An example of a XML file implementing that dtd with a sample XSLT transform is at: http://xenon.stanford.edu/~mdevine/stompy.xml In many ways, I feel like my DTD is a superset of the OMD superset. My DTD includes all of the elements that the OMD DTD includes, with the exception of the card "Comment" element. In some of my elements have different names, for example, I use the name "edition" instead of Set. I prefer the name Set to edition. I personally like the element name "deck" instead of "OMDDeck". I realize that you may have named it OMDDeck so as not to interfere with other XML markup for things like Yu-Gi-Oh decks. There is a way to do this, and still use the name "deck". If you look in my stompy.xml file, you will see that I use the xmlns element in deck to define an XML Namespace. That means that "deck" and everything included within it, is really considered as "http://xenon.stanford.edu/~mdevine/mtg:deck" which is never going to conflict with anything. If you look in my XSLT file, I define a shorthand for that URL at the very beginning so I can match against "mtgml:deck". There are other elements and attributes that I have in my dtd that I think could be useful (though the OMD apps certainly wouldn't need to use them). The most bizarre ones are the "groups" and "group" elements. I added these so that an applcation could separate the cards in either the maindeck or the sideboard if they wanted to, in the way that apprentice files do it. This is also flexible enough to split things into other groupings. For example, I could group my sideboard by which cards are boarded in against each opponent ("Aggro-Hate", "Tog-Hate", and so on). I've added an event element for sites like brainburst who frequently have deck listings with information about how they did in a major tournament. I've added a date attribute to format because of the formats that change with time. "Extended" isn't sufficient to know the allowed card pool, but "Extended" on 1/16/03 is. Basically what I'm interested in is trying to make the XML that we're working with a standard for the online Magic community. I think in order to do this, we need to: 1.) broaden the dtd to include some of the features that other applications might want (I have an attempt at http://xenon.stanford.edu/~mdevine/dtd/magic-deck-omd.dtd) 2.) create an xml namespace URI for the standards. Nothing actually needs to be at that url, it's just a string that uniquely identifies the OMD namespace. I suggest "http://sourceforge.net/projects/omd" 3.) write documentation about the standard and make it available on the OMD page 4.) communicate with web site maintainers and application developers to convince them of the benefits of using this standard I'm willing to work on all of the above. I just need to know if this plan makes sense and fits in with the OMD project. Sorry if this was a lot of information to dump on you guys all at once. Let me know what you think. Thanks, SamuraiMike On Thu, 2004-01-15 at 23:18, omd...@li... wrote: > Sorry for the delay in replying... I've been working some [unpaid] OT at > work lately. > =^p > > Yes, there is a DTD for a deck file that I put together; you can find it at > http://www.coruscant.cc/OMD/MtGdeck.dtd > > There is not one for expansion sets, though you could likely use an editor > to extrapolate one from the >30 expansion files. Alas, I'm behind in > converting files as I've not had time to playtest or play constructed--thus > diminishing my efforts. =) You can find the sets that have been converted > at http://www.coruscant.cc/OMD/sets032002.zip -- only 2 years old... > =^p If someone wants to take "ownership" of the sets, you're more than > welcome to do so. > > --Sage Sam > > ----- Original Message ----- > From: <omd...@li...> > To: <omd...@li...> > Sent: Friday, January 09, 2004 10:03 AM > Subject: [sf_net] [Omd-dev] Is there an XML Namespace URI or DTD for OMD > yet? > > > > Hi guys, > > I'm a Magic player who is teaching himself about XML and XML-related > > technologies (XSLT/DTD/XPath/etc.). I noticed the OMD project and was > > wondering if OMD has defined the standard for XML magic decklists. If > > so, is there a DTD defining the standard? Is there an XML namespace? > > If so, I'd be happy to help develop them. My sourceforge username is > > SamuraiMike. > > > > Thanks, > > SamuraiMike > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Perforce Software. > > Perforce is the Fast Software Configuration Management System offering > > advanced branching capabilities and atomic changes on 50+ platforms. > > Free Eval! http://www.perforce.com/perforce/loadprog.html > > _______________________________________________ > > Omd-development mailing list > > Omd...@li... > > https://lists.sourceforge.net/lists/listinfo/omd-development > > > > > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > Omd-development mailing list > Omd...@li... > https://lists.sourceforge.net/lists/listinfo/omd-development |