home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
Improvement Suggestions
Common structure for NFO support in MyVidéos (Maybe XBMC)
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Terra" data-source="post: 857820" data-attributes="member: 97366"><p>I see <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p>Well I think a *.nfo extension is more confusing than *.xml. Usually everyone is familiar with *.NFO files being scene/release information (text-)files with no semantic content.</p><p>*.xml indicates that this file contains semantic markup and can be read and queried by any XML parser. Or maybe invent a new extension like *.mxml (Media XML)</p><p> </p><p>A XML scheme is a defined set of rules which describes what is allowed in this xml file. e.g. you have a <info> node and under this info node is a <title> element. This can be defined in a XML scheme so that the file will be invalid if there is no <title> element under <info>. Or that a <Genre> node can have several <Genre> nodes below and that this information is only optional if available, etc.</p><p> </p><p>Nevertheless maybe a full scheme definition can be made later after defining the content. I just wanted to add that this is the proper way to define a XML file <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p> </p><p>See:</p><p><a href="http://en.wikipedia.org/wiki/Document_Type_Definition" target="_blank">http://en.wikipedia.org/wiki/Document_Type_Definition</a></p><p><a href="http://en.wikipedia.org/wiki/RELAX_NG" target="_blank">http://en.wikipedia.org/wiki/RELAX_NG</a></p></blockquote><p></p>
[QUOTE="Terra, post: 857820, member: 97366"] I see :) Well I think a *.nfo extension is more confusing than *.xml. Usually everyone is familiar with *.NFO files being scene/release information (text-)files with no semantic content. *.xml indicates that this file contains semantic markup and can be read and queried by any XML parser. Or maybe invent a new extension like *.mxml (Media XML) A XML scheme is a defined set of rules which describes what is allowed in this xml file. e.g. you have a <info> node and under this info node is a <title> element. This can be defined in a XML scheme so that the file will be invalid if there is no <title> element under <info>. Or that a <Genre> node can have several <Genre> nodes below and that this information is only optional if available, etc. Nevertheless maybe a full scheme definition can be made later after defining the content. I just wanted to add that this is the proper way to define a XML file :) See: [url]http://en.wikipedia.org/wiki/Document_Type_Definition[/url] [url]http://en.wikipedia.org/wiki/RELAX_NG[/url] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Improvement Suggestions
Common structure for NFO support in MyVidéos (Maybe XBMC)
Contact us
RSS
Top
Bottom