...
The simplest way to transfer your data is via the Internet by way of an email attachment or FTP (file transfer protocol). First time submissions which contain an imprint or publisher name and new code may also need to be accompanied by an Excel or text file that lists the imprint or publisher's name and corresponding code. This will ensure that the codes are associated with the correct buying channels for purchasing. The retailer or distributor verifies the data and then translates it into the information you see on a web page.
...
ONIX 2.1
...
T
North America continues to use ONIX 2.1
...
Sunset date for ONIX 2.1
ONIX 2.1 will be 'sunsetted' at the end of 2014.
At the beginning of 2012, the ONIX International Steering Committee – the group that guides the future development of the ONIX standard – announced that full support for ONIX version 2.1 would end at the end of 2014, and that all users were strongly advised to update their systems and migrate to ONIX 3.0. The three year notice period ensured that adequate time was available for planning, budgeting and development of updated systems.
This sunset date is now less than six months away. Note that ONIX 2.1 will not ‘stop working’ on 1st January 2015 – it will still be usable, but will not receive the level of support that it currently has. In particular, documentation will be archived and online DTD/XSD support for XML validation will be removed.
Any organisation using ONIX 2.1 (and even a few using 2.0) should ensure that a plan for migration to ONIX 3.0 is in place.
...
at this time but now that EDItEUR has
However, not every ONIX user has been able to migrate yet, and in November, EDItEUR published advice for those organisations continuing to use 2.1 after sunset. In particular, this advice details a workaround to avoid validation failures in production systems. The advice was downloaded around 1500 times during December and January. At sunset (in fact on 2nd January), the online DTDs for ONIX 2.1 were removed. During January, there were 1.2 million failed requests to download these files – roughly the same number of requests as in any other month during 2014 (though of course, prior to sunset, these requests succeeded, and post sunset, the numbers are likely boosted by re-tries). During February, the number of failed requests will be around 600,000, which shows that organisations are implementing the workarounds. Reports from key national groups where 2.1 is still widely used have suggested that sunset has not caused anything other than a few isolated problems.
Some organisations have sought to work around sunset by changing the DOCTYPE declaration in ONIX 2.1 files, to point to their own local copies of the 2.1 DTD. This is not recommended at all, and is not valid ONIX. The required DOCTYPE declaration in ONIX 2.1 files is:
and this remains true even though there is no actual file at that address. (Obviously, 'reference' in the URI may be replaced by 'short'.) If you are changing the URI for any reason, this must be for purely internal use, and the standard DTD URI should be included in all files sent externally. Use of a non-standard URI simply causes problems for recipients who have implemented proper workarounds.
If you need help identifying these, contact biblio@booknetcanada.ca. Whatever version of ONIX you use, you should try to support the most current code list.
ONIX 3.0 Revision 2
ONIX 3.0 is the new version on ONIX with better support for Digital Products and capable of a much higher degree of accuracy to support truly international data exchange. There have been a couple of major structural changes since it's inital release in 2009 and any implementer should ensure that they are using ONIX 3.0.1.
...
Current ONIX Is Defined By:
Version 3.0 Revision 1Revision 2
Version 2.1 Revision 02 or 03 (04 is largely about changes for Japan)
Code Lists Issue 27 28 (See the changes the changes for List 2728)
BISAC Subject Code list 2013 2014 edition and Regional Themes
The overview of ONIX for Books at the Editeur website.
...
