abdelazer / openpub

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

Summarize changes between current OPDS Catalogs and previous versions #9

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Please draft a section of text for the specification that lists the changes 
between the current Catalog specification and both the initial OPDS draft and 
the pre-OPDS Stanza catalogs. This will be used by implementors to help 
understand how to either support all versions or migrate from earlier versions 
to the current spec.

Both are attached for future reference.

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

Attachments:

GoogleCodeExporter commented 9 years ago

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

GoogleCodeExporter commented 9 years ago
* Addition of OPDS namespace: xmlns:opds="http://opds-spec.org/2010/catalog"

* Recommended use of Dublin Core namespace for metadata such as dc:publisher, 
dc:language inside 
entries.

* Use of profile and type arguments in link elements that point to other OPDS 
catalogs, e.g.:

  [link rel="self"  href="/opds-catalogs/new.xml" type="application/atom+xml;type=feed;profile=opds-
catalog"/]

* New link relations specific to cover image and thumbnails:  
rel="http://opds-spec.org/cover",  
rel="http://opds-spec.org/thumbnail"    

* Link relation specific to acquisition links: 
rel="http://opds-spec.org/acquisition"

* Allowance of non-epub file type, e.g. type="application/x-mobipocket-ebook"

* Recommended use of dc:format inside link element: 
[dc:format]application/x-mobipocket-
ebook[/dc:format]

* Specific recommendation to use OpenSearch and OpenSearch descriptors.

* Addition of opds:price element to describe for-pay resources.

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

GoogleCodeExporter commented 9 years ago
partial/full entries

Original comment by liza31337@gmail.com on 21 Apr 2010 at 3:05

GoogleCodeExporter commented 9 years ago
Added as [SummaryOfChangesFromStanzaCatalogs standalone wiki page] and linked 
from the historical draft 
page.

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

GoogleCodeExporter commented 9 years ago
In calibre2opds, I generated all the different sorts of thumbnail and cover 
links
(from what Stanza originally supported, to the current spec, via all the 
history of
the spec) because the clients are in different states now, and I need my 
catalogs to
be compatible with all the existing clients...

Original comment by dpier...@gmail.com on 4 May 2010 at 8:22

GoogleCodeExporter commented 9 years ago
I use the User Agent for this case. We can't have both the old and the new rel 
values 
in the spec.

Original comment by hadrien....@gmail.com on 4 May 2010 at 10:57

GoogleCodeExporter commented 9 years ago
Well my case is special, I generate a static set of catalogs... I can't rely on 
the user-agent, and I have to 
support all the different clients, which in turn have implemented a different 
version of the spec.
I didn't say that the spec must include every possible variation, I just wanted 
to note that each time it 
changed, an app somewhere died ;)

Original comment by dpier...@gmail.com on 4 May 2010 at 5:55

GoogleCodeExporter commented 9 years ago
David: If you want to be pragmatic, you should probably consider inserting two 
groups of links:

One pair to be OPDS Catalog 1.0-compliant:
{{{
    <link type="image/png" rel="http://opds-spec.org/cover"     href="http://opds-
spec.org/covers/4561.lrg.png"/>   <!-- big -->
   <link type="image/gif" rel="http://opds-spec.org/thumbnail" href="http://opds-
spec.org/covers/4561.thmb.gif"/>  <!-- less than 120 in either width or height 
-->
}}}

One other pair to be able to support legacy clients (just Stanza, right?):
{{{
    <link type="image/png" rel="x-stanza-cover-image"     href="http://opds-
spec.org/covers/4561.lrg.png"/>   <!-- big, old -->
   <link type="image/gif" rel=""x-stanza-cover-image-thumbnaill" href="http://opds-
spec.org/covers/4561.thmb.gif"/>  <!-- small, old -->
}}}

Do you have any other images that are actually used by anything? ("all the 
different sorts")

Original comment by abdela...@gmail.com on 4 May 2010 at 6:22

GoogleCodeExporter commented 9 years ago

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