[Xmltv-devel] New Grabber: tv_grab_na

[Matthew April]

Hello,

I would like to request that our grabber be included. I will be the active
maintainer. It is currently named tv_grab_na, but please let me know if I
should use something else.

Sourceforge account: matthewapril
Repo: https://sourceforge.net/p/xmltvlistingsgrabber/code/ci/master/tree/

Matthew April

[Robert Eden]

Post by Matthew April
Hello,
I would like to request that our grabber be included. I will be the active maintainer. It is currently named tv_grab_na, but please let me know if I
should use something else.
Sourceforge account: matthewapril
Repo: https://sourceforge.net/p/xmltvlistingsgrabber/code/ci/master/tree/
Matthew April

I haven't tried the grabber yet, but here are some comments after a quick scan.

1. I think tv_grab_na_tvmedia is a better name.
2. You should put the TVMedia.ca API signup URL in the POD docs. Maybe include signup instructions (It wasn't clear which product to get)
3. You should change the config file from tv_grab_cz to match the grabber name.
4. You should change other mentions of tv_grab_cz in the code/docs ( except attribution of course)
5. Since TVMedia asked you to develop the grabber, I assume you have their permission. If there are restrictions on who can get an API key, putting
that in the grabber docs isn't a bad idea. Is it only for development (leading to commercial) use? Personal use ok?

Granted I haven't read the contract or signed up for an API key, but those are some simple things to start.

Robert

[h***@gmail.com]

Post by Matthew April
Hello,
I would like to request that our grabber be included. I will be the active
maintainer. It is currently named tv_grab_na, but please let me know if I
should use something else.
Sourceforge account: matthewapril
Repo: https://sourceforge.net/p/xmltvlistingsgrabber/code/ci/master/tree/
Matthew April

Hi,

Thanks for the grabber. Just a couple of observations if I may: the "version" (L98) should be the grabber name (not "HowtoWriteAGrabber.txt" ;-) ), and the "description" (L99) would normally include the country (e.g. something like "North America (TVMedia.ca)" ).

Have you run it through tv_validate_grabber and tested the output files with tv_validate_file?

You may have already done these but a few basic tests would be:

1)
tv_validate_grabber tv_grab_na

2)
# grab --offset 1 --days 2
tv_grab_na --config-file test.conf --offset 1 --days 2 > t_1.xml --quiet 2>t_1.log

test = check that t_1.log is empty

# sort --offset 1 --days 2
tv_sort --duplicate-error t_1.xml > t_1.sorted.xml

3)
# grab --offset 1 --days 1 and --offset 2 --days 1
tv_grab_na --config-file test.conf --offset 1 --days 1 --output t_2.xml
tv_grab_na --config-file test.conf --offset 2 --days 1 > t_3.xml

# join them
tv_cat t_2.xml t_3.xml > t_2_3.xml

# and sort
tv_sort --duplicate-error t_2_3.xml > t_2_3.sorted.xml

# diff between sorted joined --offset 1 & --offset 2, with --offset 1 --days 2
# (should be identical)
diff t_1.sorted.xml t_2_3.sorted.xml

# validate the joined file
tv_validate_file t_2_3.xml


Rgds,
Geoff

[Karl Dietz]

Post by Matthew April
Repo: https://sourceforge.net/p/xmltvlistingsgrabber/code/ci/master/tree/

Hi Matthew,

I just tried your grabber with the provided test.conf and all I'm
getting is timeouts. It appears as if the URL is still pointing at your
personal development sandbox.

The URL when fetching the lineup tree is hardcoded instead of using the
$webroot variable.
http://sourceforge.net/p/xmltvlistingsgrabber/code/ci/master/tree/tv_grab_na.pl#l145

Seeing the test.conf I'm guessing that you already validated your
grabber, that's is very promising.
I'm hoping that you can provide/keep working a test key with a minimal
lineup for the nightly tester at
http://www.crustynet.org.uk/~xmltv-tester/sid/nightly/

Regards,
Karl

[Matthew April]

Thanks to everyone for the suggestions.

I will be changing the name to something else. I have also reviewed the
docs and will update them again in the near future.

I have run it through several validation tests and passed. Although I'm
still working out some encoding issues so I will re-do them once I figure
it out.

The actual website XMLTVListings.com associated with this grabber has not
been launched yet (should be up by end of week), so the development URL's
will be replaced ASAP. And I have already setup a test account/key for the
nightly validation.

Thanks,
Matthew

Post by Matthew April
https://sourceforge.net/p/xmltvlistingsgrabber/code/ci/master/tree/
Hi Matthew,
I just tried your grabber with the provided test.conf and all I'm
getting is timeouts. It appears as if the URL is still pointing at your
personal development sandbox.
The URL when fetching the lineup tree is hardcoded instead of using the
$webroot variable.
http://sourceforge.net/p/xmltvlistingsgrabber/code/ci/master/tree/tv_grab_na.pl#l145
Seeing the test.conf I'm guessing that you already validated your
grabber, that's is very promising.
I'm hoping that you can provide/keep working a test key with a minimal
lineup for the nightly tester at
http://www.crustynet.org.uk/~xmltv-tester/sid/nightly/
Regards,
Karl
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
xmltv-devel mailing list
https://lists.sourceforge.net/lists/listinfo/xmltv-devel

[Robert Eden]

Hmmm that website name (XMLTVlistings.com) bothers me a bit, as TV media
isn't associated with the XMLTV project.

Of course we haven't filled for a trademark, and any confusion could be
fixed with a note and link in the web page.

What do others think?

Robert

Post by Matthew April
Thanks to everyone for the suggestions.
I will be changing the name to something else. I have also reviewed the
docs and will update them again in the near future.
I have run it through several validation tests and passed. Although I'm
still working out some encoding issues so I will re-do them once I figure
it out.
The actual website XMLTVListings.com associated with this grabber has not
been launched yet (should be up by end of week), so the development URL's
will be replaced ASAP. And I have already setup a test account/key for the
nightly validation.
Thanks,
Matthew

Post by Matthew April
https://sourceforge.net/p/xmltvlistingsgrabber/code/ci/master/tree/
Hi Matthew,
I just tried your grabber with the provided test.conf and all I'm
getting is timeouts. It appears as if the URL is still pointing at your
personal development sandbox.
The URL when fetching the lineup tree is hardcoded instead of using the
$webroot variable.
http://sourceforge.net/p/xmltvlistingsgrabber/code/ci/master/tree/tv_grab_na.pl#l145
Seeing the test.conf I'm guessing that you already validated your
grabber, that's is very promising.
I'm hoping that you can provide/keep working a test key with a minimal
lineup for the nightly tester at
http://www.crustynet.org.uk/~xmltv-tester/sid/nightly/
Regards,
Karl
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
xmltv-devel mailing list
https://lists.sourceforge.net/lists/listinfo/xmltv-devel

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
xmltv-devel mailing list
https://lists.sourceforge.net/lists/listinfo/xmltv-devel

[h***@gmail.com]

Post by Robert Eden
Hmmm that website name (XMLTVlistings.com) bothers me a bit, as TV media
isn't associated with the XMLTV project.
Of course we haven't filled for a trademark, and any confusion could be
fixed with a note and link in the web page.
What do others think?
Robert

Good point Robert. Especially as it will be a paid-for service I think.

Perhaps a disclaimer on the website along the lines of:

"This website is not affiliated with the XMLTV Project ( http://wiki.xmltv.org/index.php/XMLTVProject ), and provides a commercial service for TV listings for North America only."

We would also need to see the Terms & Conditions of data usage (i.e. the license) before we could add the grabber to the project.

Geoff

[Matthew April]

Sorry for the lack of response, adding the disclaimer is not an issue and
has already been done. Once the website launches I will let everyone know
so you can review the terms and conditions.

I also sorted out the encoding issues I was having, and the grabber passes
all tests provided by Geoff (thank you). We will also be renaming the
grabber to something more appropriate, but have not come to a final
decision yet.

Regards,
Matt

Post by h***@gmail.com

Post by Robert Eden
Hmmm that website name (XMLTVlistings.com) bothers me a bit, as TV media
isn't associated with the XMLTV project.
Of course we haven't filled for a trademark, and any confusion could be
fixed with a note and link in the web page.
What do others think?
Robert

Good point Robert. Especially as it will be a paid-for service I think.
"This website is not affiliated with the XMLTV Project (
http://wiki.xmltv.org/index.php/XMLTVProject ), and provides a commercial
service for TV listings for North America only."
We would also need to see the Terms & Conditions of data usage (i.e. the
license) before we could add the grabber to the project.
Geoff
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
xmltv-devel mailing list
https://lists.sourceforge.net/lists/listinfo/xmltv-devel

[Matthew April]

Hello again everyone,

I am back, this time with our newly launched website:
https://www.xmltvlistings.com/
(xmltv disclaimer can be found at bottom of main page)

The grabber has been named tv_grab_na_tvmedia as suggested previously, and
can be found here:
https://sourceforge.net/projects/xmltvlistings/

If it could be included in the next release that would be great!

Thanks,
Matthew

Post by Matthew April
Sorry for the lack of response, adding the disclaimer is not an issue and
has already been done. Once the website launches I will let everyone know
so you can review the terms and conditions.
I also sorted out the encoding issues I was having, and the grabber passes
all tests provided by Geoff (thank you). We will also be renaming the
grabber to something more appropriate, but have not come to a final
decision yet.
Regards,
Matt

Post by h***@gmail.com

Post by Robert Eden
Hmmm that website name (XMLTVlistings.com) bothers me a bit, as TV

media

Post by Robert Eden
isn't associated with the XMLTV project.
Of course we haven't filled for a trademark, and any confusion could be
fixed with a note and link in the web page.
What do others think?
Robert

Good point Robert. Especially as it will be a paid-for service I think.
"This website is not affiliated with the XMLTV Project (
http://wiki.xmltv.org/index.php/XMLTVProject ), and provides a
commercial service for TV listings for North America only."
We would also need to see the Terms & Conditions of data usage (i.e. the
license) before we could add the grabber to the project.
Geoff
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
xmltv-devel mailing list
https://lists.sourceforge.net/lists/listinfo/xmltv-devel

[Robert Eden]

[h***@gmail.com]

Post by Matthew April
Hello again everyone,
https://www.xmltvlistings.com/
(xmltv disclaimer can be found at bottom of main page)
The grabber has been named tv_grab_na_tvmedia as suggested previously, and
https://sourceforge.net/projects/xmltvlistings/
If it could be included in the next release that would be great!
Thanks,
Matthew

Hi,

You need to check your encoding process as you are created mis-encoded characters:

./tv_grab_na_tvmedia --config-file test.conf --days 1 --offset 1 --output z1.xml

tv_validate_file z1.xml
file contains unexpected control characters, misencoded windows-1252?
look here "sc lang="fr">àla découver"
^^
1 error found.


You probably don't want to "encode" on line 110 since it looks like your incoming data are already UTF8.

Rgds,
Geoff

p.s. also note the encoding in the opening xml tag should be "UTF-8" (capitals) not "utf-8" ;-)

[Matthew April]

Yes I can maintain in your repo, not a problem. Our SF ID is 'tvmedia'.

Good catch Geoff. When I originally wrote it the input was not utf-8 which
is why I added the encode on line 110. But we made some changes since then,
just forgot to remove it. Funny that none of the validations I ran
yesterday caught that though.

Post by h***@gmail.com

Post by Matthew April
Hello again everyone,
https://www.xmltvlistings.com/
(xmltv disclaimer can be found at bottom of main page)
The grabber has been named tv_grab_na_tvmedia as suggested previously,

and

Post by Matthew April
https://sourceforge.net/projects/xmltvlistings/
If it could be included in the next release that would be great!
Thanks,
Matthew

Hi,
./tv_grab_na_tvmedia --config-file test.conf --days 1 --offset 1 --output z1.xml
tv_validate_file z1.xml
file contains unexpected control characters, misencoded windows-1252?
look here "sc lang="fr">àla découver"
^^
1 error found.
You probably don't want to "encode" on line 110 since it looks like your
incoming data are already UTF8.
Rgds,
Geoff
p.s. also note the encoding in the opening xml tag should be "UTF-8"
(capitals) not "utf-8" ;-)
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
xmltv-devel mailing list
https://lists.sourceforge.net/lists/listinfo/xmltv-devel

[h***@gmail.com]

Looks good; runs tests ok.

I don't know if you know, but we have a nightly test suite which checks all the grabbers (looking for broken ones). This runs a sample config file to download some listings and validates them. Are you happy for the api key and lineup used in your sample test.conf file to be public and non-expiring, so it can be used for this automated testing?

[Matthew April]

Yes not a problem. The key and lineup in test.conf were setup with that in
mind (no rate limits & limited stations).

Post by h***@gmail.com
Looks good; runs tests ok.
I don't know if you know, but we have a nightly test suite which checks
all the grabbers (looking for broken ones). This runs a sample config file
to download some listings and validates them. Are you happy for the api key
and lineup used in your sample test.conf file to be public and
non-expiring, so it can be used for this automated testing?
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
xmltv-devel mailing list
https://lists.sourceforge.net/lists/listinfo/xmltv-devel

[Robert Eden]

[Robert Eden]

[h***@gmail.com]

Post by Matthew April
Yes I can maintain in your repo, not a problem. Our SF ID is 'tvmedia'.
Good catch Geoff. When I originally wrote it the input was not utf-8 which
is why I added the encode on line 110. But we made some changes since then,
just forgot to remove it. Funny that none of the validations I ran
yesterday caught that though.

Hi Matthew,

The nightly test suite has barfed with :

+++++++++++++++++++
The file is not well-formed xml:
t_na_tvmedia_1_2.xml:23: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xE9 0x73 0x65 0x61
<display-name>RDS (Réseau des sports)</display-name>
^
+++++++++++++++++++

Looks like you have iso-8859-1 (or similar) data rather than actual UTF-8 ? (0xE9 = %C3 %A9 in UTF-8)

Rgds,
Geoff

[Matthew April]

Well that's upsetting. At one point I too was getting these errors, and I
thought I had fixed them long ago, as I no longer get them when running
validation tests (any ideas why that would be?), but its obviously still
there. I'm almost certain the problem is mixed encoding, unfortunately I
won't be able to sort this out until Tuesday.

Post by Karl Dietz

Post by Matthew April
Yes I can maintain in your repo, not a problem. Our SF ID is 'tvmedia'.
Good catch Geoff. When I originally wrote it the input was not utf-8

which

Post by Matthew April
is why I added the encode on line 110. But we made some changes since

then,

Post by Matthew April
just forgot to remove it. Funny that none of the validations I ran
yesterday caught that though.

Hi Matthew,
+++++++++++++++++++
t_na_tvmedia_1_2.xml:23: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xE9 0x73 0x65 0x61
<display-name>RDS (Réseau des sports)</display-name>
^
+++++++++++++++++++
Looks like you have iso-8859-1 (or similar) data rather than actual UTF-8
? (0xE9 = %C3 %A9 in UTF-8)
Rgds,
Geoff
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
xmltv-devel mailing list
https://lists.sourceforge.net/lists/listinfo/xmltv-devel

[h***@gmail.com]

Post by Matthew April
Well that's upsetting. At one point I too was getting these errors, and I
thought I had fixed them long ago, as I no longer get them when running
validation tests (any ideas why that would be?), but its obviously still
there. I'm almost certain the problem is mixed encoding, unfortunately I
won't be able to sort this out until Tuesday.

They were probably being hidden by your extra "encode" pass which you just took out :-(

Rgds,
Geoff

[Matthew April]

OK, sorry this took so long.. thanksgiving long weekend here. Should be all
fixed now.

Post by h***@gmail.com

Post by Matthew April
Well that's upsetting. At one point I too was getting these errors, and I
thought I had fixed them long ago, as I no longer get them when running
validation tests (any ideas why that would be?), but its obviously still
there. I'm almost certain the problem is mixed encoding, unfortunately I
won't be able to sort this out until Tuesday.

They were probably being hidden by your extra "encode" pass which you just took out :-(
Rgds,
Geoff
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
xmltv-devel mailing list
https://lists.sourceforge.net/lists/listinfo/xmltv-devel

[unknown]

This is a multi-part message in MIME format.
--------------030700070307030005030404
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I ran a quick test and it seems to work for me. Thanks for the website
note about affiliation.

Are you willing to maintain the grabber in our SF repository? (looks
like you set up your own). What's your SF id?

Anyone else have any comments?

BTW, your timing is good.. we'll be releasing soon! :)

Robert

Post by Matthew April
Hello again everyone,
https://www.xmltvlistings.com/
(xmltv disclaimer can be found at bottom of main page)
The grabber has been named tv_grab_na_tvmedia as suggested previously,
https://sourceforge.net/projects/xmltvlistings/
If it could be included in the next release that would be great!
Thanks,
Matthew
Sorry for the lack of response, adding the disclaimer is not an
issue and has already been done. Once the website launches I will
let everyone know so you can review the terms and conditions.
I also sorted out the encoding issues I was having, and the
grabber passes all tests provided by Geoff (thank you). We will
also be renaming the grabber to something more appropriate, but
have not come to a final decision yet.
Regards,
Matt

Post by Robert Eden
Hmmm that website name (XMLTVlistings.com) bothers me a bit,

as TV media

Post by Robert Eden
isn't associated with the XMLTV project.
Of course we haven't filled for a trademark, and any

confusion could be

Post by Robert Eden
fixed with a note and link in the web page.
What do others think?
Robert

Good point Robert. Especially as it will be a paid-for
service I think.
"This website is not affiliated with the XMLTV Project (
http://wiki.xmltv.org/index.php/XMLTVProject ), and provides a
commercial service for TV listings for North America only."
We would also need to see the Terms & Conditions of data usage
(i.e. the license) before we could add the grabber to the project.
Geoff
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise?
Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest
code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
xmltv-devel mailing list
https://lists.sourceforge.net/lists/listinfo/xmltv-devel
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
xmltv-devel mailing list
https://lists.sourceforge.net/lists/listinfo/xmltv-devel

--------------030700070307030005030404
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">I ran a quick test and it seems to work
for me.&nbsp; Thanks for the website note about affiliation.<br>
<br>
Are you willing to maintain the grabber in our SF repository?
(looks like you set up your own).&nbsp; What's your SF id?<br>
<br>
Anyone else have any comments?<br>
<br>
BTW, your timing is good.. we'll be releasing soon! :)<br>
<br>
Robert<br>
<br>
On 10/9/2014 10:34 AM, Matthew April wrote:<br>
</div>
<blockquote
cite="mid:CAFSk1X8X6Cn0cpWjfU+bJ6W=***@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>Hello again everyone,<br>
<br>
</div>
I am back, this time with our newly launched website: <a
moz-do-not-send="true" href="https://www.xmltvlistings.com/">https://www.xmltvlistings.com/</a><br>
</div>
<div>(xmltv disclaimer can be found at bottom of main page)<br>
</div>
<div><br>
</div>
The grabber has been named tv_grab_na_tvmedia as suggested
previously, and can be found here:<br>
<div><a moz-do-not-send="true"
href="https://sourceforge.net/projects/xmltvlistings/">https://sourceforge.net/projects/xmltvlistings/</a><br>
<br>
</div>
<div>If it could be included in the next release that would be
great!<br>
<br>
</div>
<div>Thanks,<br>
</div>
<div>Matthew<br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Aug 5, 2014 at 12:14 PM,
Matthew April <span dir="ltr">&lt;<a moz-do-not-send="true"
href="mailto:***@tvmedia.ca" target="_blank">***@tvmedia.ca</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>Sorry for the lack of response, adding the
disclaimer is not an issue and has already been done.
Once the website launches I will let everyone know so
you can review the terms and conditions.<br>
<br>
I also sorted out the encoding issues I was having,
and the grabber passes all tests provided by Geoff
(thank you). We will also be renaming the grabber to
something more appropriate, but have not come to a
final decision yet.<br>
<br>
</div>
Regards,<br>
</div>
Matt<br>
</div>
<div class="HOEnZb">
<div class="h5">
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Fri, Jul 25, 2014 at 5:08
AM, <span dir="ltr">&lt;<a moz-do-not-send="true"
href="mailto:***@gmail.com" target="_blank">***@gmail.com</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Thu, 24 Jul 2014 13:10:50 -0500, Robert
Eden wrote:<br>
<br>
&gt; Hmmm that website name (XMLTVlistings.com)
bothers me a bit, &nbsp;as TV media<br>
&gt; isn't associated with the XMLTV project.<br>
&gt;<br>
&gt; Of course we haven't filled for a
trademark, &nbsp;and any confusion could be<br>
&gt; fixed with a note and link in the web page.<br>
&gt;<br>
&gt; What do others think?<br>
&gt;<br>
&gt; Robert<br>
<br>
<br>
</div>
Good point Robert.&nbsp; Especially as it will be a
paid-for service I think.<br>
<br>
Perhaps a disclaimer on the website along the
lines of:<br>
<br>
"This website is not affiliated with the XMLTV
Project ( <a moz-do-not-send="true"
href="http://wiki.xmltv.org/index.php/XMLTVProject"
target="_blank">http://wiki.xmltv.org/index.php/XMLTVProject</a>
), and provides a commercial service for TV
listings for North America only."<br>
<br>
We would also need to see the Terms &amp;
Conditions of data usage (i.e. the license) before
we could add the grabber to the project.<br>
<br>
Geoff<br>
<div>
<div><br>
------------------------------------------------------------------------------<br>
Want fast and easy access to all the code in
your enterprise? Index and<br>
search up to 200,000 lines of code with a free
copy of Black Duck<br>
Code Sight - the same software that powers the
world's largest code<br>
search on Ohloh, the Black Duck Open Hub! Try
it now.<br>
<a moz-do-not-send="true"
href="http://p.sf.net/sfu/bds"
target="_blank">http://p.sf.net/sfu/bds</a><br>
_______________________________________________<br>
xmltv-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:xmltv-***@lists.sourceforge.net"
target="_blank">xmltv-***@lists.sourceforge.net</a><br>
<a moz-do-not-send="true"
href="https://lists.sourceforge.net/lists/listinfo/xmltv-devel"
target="_blank">https://lists.sourceforge.net/lists/listinfo/xmltv-devel</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
<a class="moz-txt-link-freetext" href="http://pubads.g.doubleclick.net/gampad/clk?id=154622311&amp;iu=/4140/ostg.clktrk">http://pubads.g.doubleclick.net/gampad/clk?id=154622311&amp;iu=/4140/ostg.clktrk</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
xmltv-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:xmltv-***@lists.sourceforge.net">xmltv-***@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/xmltv-devel">https://lists.sourceforge.net/lists/listinfo/xmltv-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>

--------------030700070307030005030404--

[unknown]

This is a multi-part message in MIME format.
--------------090406040507060202010601
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sounds good.. welcome abort Matthew! I'll add things to CVS.

(yes, CVS... it works, and it's effort to change! :) )

(I find git annoying, but use svn for most of my stuff)

Post by Matthew April
Yes not a problem. The key and lineup in test.conf were setup with
that in mind (no rate limits & limited stations).
Looks good; runs tests ok.
I don't know if you know, but we have a nightly test suite which
checks all the grabbers (looking for broken ones). This runs a
sample config file to download some listings and validates them.
Are you happy for the api key and lineup used in your sample
test.conf file to be public and non-expiring, so it can be used
for this automated testing?
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
xmltv-devel mailing list
https://lists.sourceforge.net/lists/listinfo/xmltv-devel
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
xmltv-devel mailing list
https://lists.sourceforge.net/lists/listinfo/xmltv-devel

--------------090406040507060202010601
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Sounds good.. welcome abort Matthew!&nbsp;
I'll add things to CVS.<br>
<br>
(yes, CVS... it works, and it's effort to change! :) )<br>
<br>
(I find git annoying, but use svn for most of my stuff) <br>
<br>
On 10/10/2014 10:07 AM, Matthew April wrote:<br>
</div>
<blockquote
cite="mid:CAFSk1X-Ejk_ktvdyzBq5wL4wAWJhgQV4-***@mail.gmail.com"
type="cite">
<div dir="ltr">Yes not a problem. The key and lineup in test.conf
were setup with that in mind (no rate limits &amp; limited
stations).<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Oct 10, 2014 at 10:49 AM, <span
dir="ltr">&lt;<a moz-do-not-send="true"
href="mailto:***@gmail.com" target="_blank">***@gmail.com</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Looks
good; runs tests ok.<br>
<br>
I don't know if you know, but we have a nightly test suite
which checks all the grabbers (looking for broken ones).
This runs a sample config file to download some listings and
validates them. Are you happy for the api key and lineup
used in your sample test.conf file to be public and
non-expiring, so it can be used for this automated testing?<br>
<div class="HOEnZb">
<div class="h5"><br>
------------------------------------------------------------------------------<br>
Meet PCI DSS 3.0 Compliance Requirements with EventLog
Analyzer<br>
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box
PCI DSS Reports<br>
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download
White paper<br>
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with
EventLog Analyzer<br>
<a moz-do-not-send="true"
href="http://pubads.g.doubleclick.net/gampad/clk?id=154622311&amp;iu=/4140/ostg.clktrk"
target="_blank">http://pubads.g.doubleclick.net/gampad/clk?id=154622311&amp;iu=/4140/ostg.clktrk</a><br>
_______________________________________________<br>
xmltv-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:xmltv-***@lists.sourceforge.net">xmltv-***@lists.sourceforge.net</a><br>
<a moz-do-not-send="true"
href="https://lists.sourceforge.net/lists/listinfo/xmltv-devel"
target="_blank">https://lists.sourceforge.net/lists/listinfo/xmltv-devel</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
<a class="moz-txt-link-freetext" href="http://pubads.g.doubleclick.net/gampad/clk?id=154622311&amp;iu=/4140/ostg.clktrk">http://pubads.g.doubleclick.net/gampad/clk?id=154622311&amp;iu=/4140/ostg.clktrk</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
xmltv-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:xmltv-***@lists.sourceforge.net">xmltv-***@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/xmltv-devel">https://lists.sourceforge.net/lists/listinfo/xmltv-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>

--------------090406040507060202010601--

[unknown]

This is a multi-part message in MIME format.
--------------030007020802060601000309
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Looks like Geoff beat me to CVS. :) It's added.

I've updated the Makefile.PL
I've updated the alpha xmltv.exe (and it's in there)
I've added Mathew as a SF dev.

Tomorrow we can see the automated test results.

Robert

Post by unknown
Sounds good.. welcome abort Matthew! I'll add things to CVS.
(yes, CVS... it works, and it's effort to change! :) )
(I find git annoying, but use svn for most of my stuff)

Post by Matthew April
Yes not a problem. The key and lineup in test.conf were setup with
that in mind (no rate limits & limited stations).
Looks good; runs tests ok.
I don't know if you know, but we have a nightly test suite which
checks all the grabbers (looking for broken ones). This runs a
sample config file to download some listings and validates them.
Are you happy for the api key and lineup used in your sample
test.conf file to be public and non-expiring, so it can be used
for this automated testing?
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
xmltv-devel mailing list
https://lists.sourceforge.net/lists/listinfo/xmltv-devel
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
xmltv-devel mailing list
https://lists.sourceforge.net/lists/listinfo/xmltv-devel

--------------030007020802060601000309
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Looks like Geoff beat me to CVS. :)&nbsp;
It's added.<br>
<br>
I've updated the Makefile.PL&nbsp; <br>
I've updated the alpha xmltv.exe&nbsp; (and it's in there)<br>
I've added Mathew as a SF dev.<br>
<br>
Tomorrow we can see the automated test results.<br>
<br>
Robert<br>
<br>
On 10/10/2014 4:16 PM, Robert Eden wrote:<br>
</div>
<blockquote cite="mid:***@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Sounds good.. welcome abort Matthew!&nbsp;
I'll add things to CVS.<br>
<br>
(yes, CVS... it works, and it's effort to change! :) )<br>
<br>
(I find git annoying, but use svn for most of my stuff) <br>
<br>
On 10/10/2014 10:07 AM, Matthew April wrote:<br>
</div>
<blockquote
cite="mid:CAFSk1X-Ejk_ktvdyzBq5wL4wAWJhgQV4-***@mail.gmail.com"
type="cite">
<div dir="ltr">Yes not a problem. The key and lineup in
test.conf were setup with that in mind (no rate limits &amp;
limited stations).<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Oct 10, 2014 at 10:49 AM, <span
dir="ltr">&lt;<a moz-do-not-send="true"
href="mailto:***@gmail.com" target="_blank">***@gmail.com</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Looks
good; runs tests ok.<br>
<br>
I don't know if you know, but we have a nightly test suite
which checks all the grabbers (looking for broken ones).
This runs a sample config file to download some listings
and validates them. Are you happy for the api key and
lineup used in your sample test.conf file to be public and
non-expiring, so it can be used for this automated
testing?<br>
<div class="HOEnZb">
<div class="h5"><br>
------------------------------------------------------------------------------<br>
Meet PCI DSS 3.0 Compliance Requirements with EventLog
Analyzer<br>
Achieve PCI DSS 3.0 Compliant Status with
Out-of-the-box PCI DSS Reports<br>
Are you Audit-Ready for PCI DSS 3.0 Compliance?
Download White paper<br>
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with
EventLog Analyzer<br>
<a moz-do-not-send="true"
href="http://pubads.g.doubleclick.net/gampad/clk?id=154622311&amp;iu=/4140/ostg.clktrk"
target="_blank">http://pubads.g.doubleclick.net/gampad/clk?id=154622311&amp;iu=/4140/ostg.clktrk</a><br>
_______________________________________________<br>
xmltv-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:xmltv-***@lists.sourceforge.net">xmltv-***@lists.sourceforge.net</a><br>
<a moz-do-not-send="true"
href="https://lists.sourceforge.net/lists/listinfo/xmltv-devel"
target="_blank">https://lists.sourceforge.net/lists/listinfo/xmltv-devel</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://pubads.g.doubleclick.net/gampad/clk?id=154622311&amp;iu=/4140/ostg.clktrk">http://pubads.g.doubleclick.net/gampad/clk?id=154622311&amp;iu=/4140/ostg.clktrk</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
xmltv-devel mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:xmltv-***@lists.sourceforge.net">xmltv-***@lists.sourceforge.net</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/xmltv-devel">https://lists.sourceforge.net/lists/listinfo/xmltv-devel</a>
</pre>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>

--------------030007020802060601000309--