search

abdelazer / openpub

Automatically exported from code.google.com/p/openpub
0 stars 0 forks source link

Develop examples of broken catalogs #12

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Please develop a set of OPDS Catalogs that exhibit common mistakes that 
have been observed in the wild and add them to 
http://openpub.googlecode.com/svn/trunk/schemas/tests/files/

Original issue reported on code.google.com by abdela...@gmail.com on 10 Mar 2010 at 3:33

GoogleCodeExporter commented 9 years ago 
Since these are simply XML files, I suggest comments be inserted that point to 
the 
particular problem or show what information is missing and causing the failure.

Original comment by rsperb...@gmail.com on 10 Mar 2010 at 4:03

GoogleCodeExporter commented 9 years ago

Original comment by liza31337@gmail.com on 21 Apr 2010 at 2:44

GoogleCodeExporter commented 9 years ago

Original comment by liza31337@gmail.com on 3 May 2010 at 3:35

GoogleCodeExporter commented 9 years ago

Original comment by abdela...@gmail.com on 25 May 2010 at 5:44

GoogleCodeExporter commented 9 years ago 
To update my earlier request: any files that do not fulfill the spec 
requirements ought to include comments pointing out what specific problem the 
file has and also what requirement it fails to meet.

As we develop the schema to validate all aspects of the spec, it will be useful 
to have as many samples as possible and it won't always be immediately clear 
what the sample file is testing. If a file validates that is expected to fail, 
we'll need to confirm the sample isn't itself at issue before going in and 
revising the schema.

Original comment by rsperb...@gmail.com on 14 Jul 2010 at 7:34

GoogleCodeExporter commented 9 years ago

Original comment by abdela...@gmail.com on 4 Aug 2010 at 3:41