On 9/5/07, <b class="gmail_sendername">Robert Current</b> <<a href="mailto:robert.current@gmail.com">robert.current@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> Rather than re-inventing a standard schema for importing and<br>> exporting this data, I suggest using XMLTV's well-established schema.<br>> That means getting all the data into XMLTV format. That means the
<br>> XMLTV people would be the most reliable source of information on<br>> doing this.<br><br>I could be wrong, but I think the standard is set by XMLTV already. I<br>think the Import for MythTV is already done by mythfilldatabase I
<br>don't know what they could do to contribute.</blockquote><div><br>They can assist with the proper data formatting of the grabber. Nothing about the grabber development really has anything to do with MythTV directly since MythTV only requires that the data be XMLTV compliant. All the hard work from the import side is done already.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The parts that aren't done are the EXPORT from a filled database to an<br>
.xml file, which could be used by others. Again, people overseas<br>might want to share, I might want to do it to an un-networked system<br>with a cable capture card down the hall from me… there are legitimate<br>uses. But that's part of MythTV code, not XMLTV.
</blockquote><div><br>Honestly, I don't see why most people would care at all about exporting and peer sharing of data. The process of downloading the data is easy enough for most people to do directly so why bother adding the complexity? And you just might be opening up a grabber for violating terms by redistributing the data.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Honestly, I think the solution (creation of alternatives) for MythTV<br>has to be done inside MythTV existing structure. 1) export .xmltv
<br>data scripts. 2) solution for .xmltv data file distribution. 3) a<br>GUI interface to do both of those from within MythTV. But, that's my<br>opinion… one I'm researching and willing to work on.</blockquote>
<div><br>None of that is necessary. You need:<br><br>1. Directly download guide data either already in XMLTV or in another format (doesn't matter to Myth how you download it)<br>2. (optionally) Parse data into XMLTV format (again, doesn't matter to Myth)
<br>3. Run mythfilldatabase to import file (already existing for you to use)<br><br>Done.<br><br>Kevin<br></div></div><br>