Reply to thread

Message

<blockquote data-quote="doskabouter" data-source="post: 1037625" data-attributes="member: 98267">First draft of the JSON stuff:[SPOILER]OverviewParse WebEPG data from json sourcesDescription of ChangeBesides Html, Xml, and generic data, JSON is now supported as wellFor that I have created a JSON parser, and a JSON Xpath evaluatorChanged to be made in the <a href="http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/18_Contribute/5_Localization/EPG_Grabbers_and_Tuning_details/WebEPG/WebEPG_Grabber" target="_blank">http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/18_Contribute/5_Localization/EPG_Grabbers_and_Tuning_details/WebEPG/WebEPG_Grabber</a> page:Add a 2.3.7. &lt;JSON&gt;At #.3CListing_type.3D.22.22.3E add JSONThe &quot;JSON&quot; element may containg the following content:Attributes:&nbsp; &quot;xpath&quot;: Xpath expression which returns the EPG-elements. Note that this is a custom implementation of Xpath, and not all possibilities are supported (yet)&nbsp; &quot;channel&quot;: Filter to apply to the list of EPG-elementsChildNodes:&nbsp; &quot;Fields&quot;: Mapping from JSON-attributes to EPG-fields&nbsp; This contains a number of &quot;Field&quot; nodes, with these attributes:&nbsp; &quot;name&quot;: EPG-Field&nbsp; &quot;jsonname&quot;: JSON-attributeExample:&nbsp; &nbsp;&nbsp; &lt;JSON channel=&quot;channel/id=28&quot; xpath=&quot;airing&quot;&gt;&nbsp; &nbsp; &nbsp;&nbsp; &lt;Fields&gt;&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &lt;Field name=&quot;#START&quot; jsonname=&quot;air_time&quot; /&gt;&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &lt;Field name=&quot;#TITLE&quot; jsonname=&quot;title&quot; /&gt;&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &lt;Field name=&quot;#DESCRIPTION&quot; jsonname=&quot;episode/original_title&quot; /&gt;&nbsp; &nbsp; &nbsp;&nbsp; &lt;/Fields&gt;&nbsp; &nbsp;&nbsp; &lt;/JSON&gt;Additional Information and ReferencesIssue #:&nbsp; &nbsp;&nbsp; <a href="https://issues.team-mediaportal.com/browse/MP1-4215" target="_blank">4215</a>Issue Component:&nbsp; &nbsp; WebEPGType of Change:&nbsp; &nbsp; FeatureRelated Wiki page(s):&nbsp; &nbsp;&nbsp; <a href="http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/18_Contribute/5_Localization/EPG_Grabbers_and_Tuning_details/WebEPG/WebEPG_Grabber" target="_blank">http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/18_Contribute/5_Localization/EPG_Grabbers_and_Tuning_details/WebEPG/WebEPG_Grabber</a>Author:&nbsp; &nbsp; doskabouterDate added:&nbsp; &nbsp; Fri, 01 Nov 2013[/SPOILER]Is this along the lines you want it, or should I try to make it more user-friendly?And an explanation which can already be added to the Xml section:[SPOILER]The &quot;Xml&quot; element may containg the following content:Attributes:&nbsp; &quot;xpath&quot;: Xpath expression which returns the EPG-elements&nbsp; &quot;channel&quot;: Filter to apply to the list of EPG-elementsChildNodes:&nbsp; &quot;Fields&quot;: Mapping from xml-attributes to EPG-fields&nbsp; This contains a number of &quot;Field&quot; nodes, with these attributes:&nbsp; &quot;name&quot;: EPG-Field&nbsp; &quot;xmlname&quot;: xml-attribute&nbsp;&nbsp; Example:&nbsp; &nbsp;&nbsp; &lt;Xml channel=&quot;id=28&quot; xpath=&quot;airing&quot;&gt;&nbsp; &nbsp; &nbsp;&nbsp; &lt;Fields&gt;&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &lt;Field name=&quot;#START&quot; xmlname=&quot;air_time&quot; /&gt;&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &lt;Field name=&quot;#TITLE&quot; xmlname=&quot;title&quot; /&gt;&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &lt;Field name=&quot;#DESCRIPTION&quot; xmlname=&quot;description&quot; /&gt;&nbsp; &nbsp; &nbsp;&nbsp; &lt;/Fields&gt;&nbsp; &nbsp;&nbsp; &lt;/Xml&gt;[/SPOILER]</blockquote>

[QUOTE="doskabouter, post: 1037625, member: 98267"] First draft of the JSON stuff: [SPOILER] Overview Parse WebEPG data from json sources Description of Change Besides Html, Xml, and generic data, JSON is now supported as well For that I have created a JSON parser, and a JSON Xpath evaluator Changed to be made in the [url]http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/18_Contribute/5_Localization/EPG_Grabbers_and_Tuning_details/WebEPG/WebEPG_Grabber[/url] page: Add a 2.3.7. <JSON> At #.3CListing_type.3D.22.22.3E add JSON The "JSON" element may containg the following content: Attributes: "xpath": Xpath expression which returns the EPG-elements. Note that this is a custom implementation of Xpath, and not all possibilities are supported (yet) "channel": Filter to apply to the list of EPG-elements ChildNodes: "Fields": Mapping from JSON-attributes to EPG-fields This contains a number of "Field" nodes, with these attributes: "name": EPG-Field "jsonname": JSON-attribute Example: <JSON channel="channel/id=28" xpath="airing"> <Fields> <Field name="#START" jsonname="air_time" /> <Field name="#TITLE" jsonname="title" /> <Field name="#DESCRIPTION" jsonname="episode/original_title" /> </Fields> </JSON> Additional Information and References Issue #: [URL=https://issues.team-mediaportal.com/browse/MP1-4215]4215[/URL] Issue Component: WebEPG Type of Change: Feature Related Wiki page(s): [url]http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/18_Contribute/5_Localization/EPG_Grabbers_and_Tuning_details/WebEPG/WebEPG_Grabber[/url] Author: doskabouter Date added: Fri, 01 Nov 2013 [/SPOILER] Is this along the lines you want it, or should I try to make it more user-friendly? And an explanation which can already be added to the Xml section: [SPOILER] The "Xml" element may containg the following content: Attributes: "xpath": Xpath expression which returns the EPG-elements "channel": Filter to apply to the list of EPG-elements ChildNodes: "Fields": Mapping from xml-attributes to EPG-fields This contains a number of "Field" nodes, with these attributes: "name": EPG-Field "xmlname": xml-attribute Example: <Xml channel="id=28" xpath="airing"> <Fields> <Field name="#START" xmlname="air_time" /> <Field name="#TITLE" xmlname="title" /> <Field name="#DESCRIPTION" xmlname="description" /> </Fields> </Xml> [/SPOILER] [/QUOTE]

Verification