Re: Updating the IceTV grabber for possible inclusion in the XMLTV project

Looks like I stuffed this one up originally and it didn't get sent to the
list.

I have finally had a chance to look over this again and while passing the
updated dtd-file to tv_validate_file works (we are still getting an error
on the channel_id for some reason "line 4 Invalid channel-id '62'"), so my
next question is whether these extra elements being added to the XMLTV DTD
in our feed would stop the grabber from being included in the XMLTV project?

I have included the changes that we have made below along with a link to
our updated DTD.

I have also attached the current version of the grabber to this post, if
someone could have a look at it and give me any feedback it would be
greatly appreciated. The grabber will create a free trial account during
configure to allow for a seamless setup, and I can convert any accounts
required to unlimited accounts for testing.

On Sun, Jul 2, 2017 at 3:32 PM, Robert Eden <[email protected]> wrote:

> On 6/26/2017 11:45 PM, Daniel Hall wrote:
>
>> In our feed we have included a custom DTD which is an extension of the
>> XMLTV DTD adding a couple of elements and defining a couple of new
>> episode-num schemes, however when attempting to run the tv_validate_grabber
>> script it comes back with validity errors on these new elements. Does the
>> grabber script only use the official XMLTV DTD? and if so is there a way
>> to extend that in any official way?
>>
>
> Can you be a bit more specific on what your DTD changes?  I wouldn't think
> a episode_num name would be validated.  Changing the *format* of a value
> would, because it could break apps.


No problem, we are definitely conscious of keeping the current DTD intact
and just extending it where appropriate, we have not changed the value of
any current elements and have defined the following new elements:

Under the channel element we have added an 'lcn' element that is the
logical channel number.

Under the programme element we have added both the 'airingID' and the
'mediaID' attributes, the 'airingID' is our internal showing ID that will
be unique for a showing and can be used for incremental updates, 'mediaID'
in a combination of our internal 'series_id' and 'episode_id' in the format
'series_id-episode_id'.

Within programme we have added the 'sport' and 'team' elements at the
request of Plex, the 'sport' element is literally the sport for sporting
events, and the 'team' elements are for the teams that are playing if
known, if included there will be a minimum of two teams listed.

In terms of episode-num elements, we have the the xmltv_ns included where
season and episode numbers are known, we have also added the following
episode-num systems:

   - SxxExx - This is in the format "SXXExx", where XX is the season number
   that is 1 based, and xx is the episod enumber within the season that is
   also 1 based. Some series instead of the season number it will list the
   year of the season where available.
   - original-air-date - This is the original air date of the showing in
   the format YEAR-MONTH-DAY, this field does not indicate a repeat (use the
   previously-shown element for this) if the air date is in the past.
   - thetvdb.com - This is the ID's for thetvdb.com, there can be two
   entries for each show, one for the series (in the format "series/ID")  and
   one for the episode (in the format "episode/ID")
   - imdb.com - This is the ID's for imdb.com, there can be two entries for
   each show, one for the series (in the format "series/ID") and one for the
   episode (in the format "episode/ID")
   - themoviedb.org - This is the ID for this movie from themoviedb.org

The DTD can be found at http://static.icetv.com.au/iceguide/icetv_xmltv.dtd


> My other concern is that IceTV is a paid service, so an email address and
>> password is required to setup the grabber (we have some explanation of this
>> in the configuration steps), but for ongoing validation without an account
>> it would not be able to be configured. Has this come up in the past with
>> other grabbers, and is there a possible way around this?
>>
>
> The Schedules Direct grabbers ( tv_grab_na_dd, tv_grab_zz_sdjon,
> tv_grab_zz_sdjson_sqlite)  solve this by creating a creating an account for
> the XMLTV validation app.  The config file is not part of the
> distribution and so the password is only known to the person who runs the
> tester.. (which is Chris Butler, but seems to be down. I think Nick was
> looking into taking it over)
>
> Robert
>
>
Excellent news, this is not an issue, just wanted to know what the process
was and if the testing account details could be left 'unpublished'.

*Daniel Hall*
*CTO *

* <http://www.icetv.com.au>*
*direct: +61 2 8424 7510mobile: +61 418 990 444visit me on: [image:
http://www.feng-gui.com/images/linkedin_logo_16x16.jpg]
<http://au.linkedin.com/pub/daniel-hall/1/440/7b/>*119 Willoughby
Road, Crows Nest, NSW, 2065.
PO Box 240, Wentworth Falls, NSW, 2782, Australia.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
xmltv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xmltv-devel