XML Standard Format for HH
12-01-2008
, 11:25 AM
Quote:
12-12-2008
, 12:38 PM
[QUOTE=Eratosthenes;7378307]
I really don't know here.
If you only stick one hand history per file, it doesn't really matter - and sites would store hands one by one.
It's later, if one wants to do some processing. Does it help to have the "header" stuff outside, so that you can create a larger XML file of multiple hands without repeating the same header stuff (where appropriate?)
PS: Looks like I messed up my notifier
Quote:
Also I would make it so that each game contains general section (=table/tournament details) and the game itself so that each hand would be independent. Something like this:
<game id="123495900435"> in the poker_site element
<general>
<type>TOURNAMENT/CASH/SIT_GO/...</type> tournament element not in this hh
<tablename>My little table</tablename> in the poker_site element
<currency>USD/EUR</currency> in the poker_site element
<small_blind>20</small_blind>in the stakes element
<big_blind>40</big_blind>in the stakes element
<tournamentname></tournamentname>tournament element not in this hh
<tournament id="1239120">tournament element not in this hh
</general>
<game id="123495900435"> in the poker_site element
<general>
<type>TOURNAMENT/CASH/SIT_GO/...</type> tournament element not in this hh
<tablename>My little table</tablename> in the poker_site element
<currency>USD/EUR</currency> in the poker_site element
<small_blind>20</small_blind>in the stakes element
<big_blind>40</big_blind>in the stakes element
<tournamentname></tournamentname>tournament element not in this hh
<tournament id="1239120">tournament element not in this hh
</general>
If you only stick one hand history per file, it doesn't really matter - and sites would store hands one by one.
It's later, if one wants to do some processing. Does it help to have the "header" stuff outside, so that you can create a larger XML file of multiple hands without repeating the same header stuff (where appropriate?)
PS: Looks like I messed up my notifier
12-12-2008
, 01:08 PM
Quote:
I really don't know here.
If you only stick one hand history per file, it doesn't really matter - and sites would store hands one by one.
It's later, if one wants to do some processing. Does it help to have the "header" stuff outside, so that you can create a larger XML file of multiple hands without repeating the same header stuff (where appropriate?)
PS: Looks like I messed up my notifier
I really don't know here.
If you only stick one hand history per file, it doesn't really matter - and sites would store hands one by one.
It's later, if one wants to do some processing. Does it help to have the "header" stuff outside, so that you can create a larger XML file of multiple hands without repeating the same header stuff (where appropriate?)
PS: Looks like I messed up my notifier
12-15-2008
, 06:20 PM
Quote:
That quote looks like I was suggesting that some of the HH info be extracted out of the HH xml and put in a header that would apply to multiple hands in a file. I didn't look back at my post, but I'm sure I didn't suggest that because I think it would be a really bad idea. Each HH xml needs to have everything about that hand. People will be pasting these things into converters, mailing them to their mates, etc.
I think it is important if you later want to store in the hands in a DB for example.
I'm thinking of something along the lines of
<pokerxml>
<table table_stuff>
<holdem hand >
hand stuff
</holdem hand>
</table>
</pokerxml>
as opposed to
<pokerxml>
<holdem hand >
<table table_stuff>
</table>
hand stuff
</holdem hand>
</pokerxml>
The first one, if you want to combine hands together, say in a DB, would be a lot more efficient.
In fact, I don't see any drawbacks to the first one, but I may be particularly obtuse.
André
12-15-2008
, 09:39 PM
Quote:
Let me try again. Maybe it is a bad idea, but I want to make sure it was understood first
I think it is important if you later want to store in the hands in a DB for example.
I'm thinking of something along the lines of
<pokerxml>
<table table_stuff>
<holdem hand >
hand stuff
</holdem hand>
</table>
</pokerxml>
as opposed to
<pokerxml>
<holdem hand >
<table table_stuff>
</table>
hand stuff
</holdem hand>
</pokerxml>
The first one, if you want to combine hands together, say in a DB, would be a lot more efficient.
In fact, I don't see any drawbacks to the first one, but I may be particularly obtuse.
André
I think it is important if you later want to store in the hands in a DB for example.
I'm thinking of something along the lines of
<pokerxml>
<table table_stuff>
<holdem hand >
hand stuff
</holdem hand>
</table>
</pokerxml>
as opposed to
<pokerxml>
<holdem hand >
<table table_stuff>
</table>
hand stuff
</holdem hand>
</pokerxml>
The first one, if you want to combine hands together, say in a DB, would be a lot more efficient.
In fact, I don't see any drawbacks to the first one, but I may be particularly obtuse.
André
- If we are trying to produce an xml schema for a collection of related hand histories, then pulling all of the common stuff in to a header is fine. If you look at books on xml, one of their favorite examples is the purchase order, because it has header info and line item info. This would be similar to that example.
- OTOH, if we are trying to produce an xml schema for a hand history, then it should be a complete and self-contained description of a hand history.
I don't think there is much efficiency to be gained to factoring out the common info, because there isn't that much compared to the whole HH: table name (but not for tournaments), max seats, poker room, tournament no., game (but not for mixed games), stakes (but not for tournaments). What you give up for that flexibility is the ability to treat individual HHs without the rest of the collection.