ONIX

Aus AkiWiki

Version vom 16. Juli 2017, 15:27 Uhr

ONIX

http://www.editeur.org/8/ONIX/

http://info.vlb.de/verlage/thema-klassifikation/thema-in-onix-21.html

https://groups.yahoo.com/neo/groups/ONIX_IMPLEMENT/info ... mehr als 1000 tln-innen ... wow

https://info.vlb.de/files/best_practices_zeichensatz.pdf ... informativ

ISTC infos an OS2016

XML im AKI-wiki

http://hilfe.vlb.de/vlb-onix-empfehlungen/bundle.html ... informativ

ONIX Codelists Issue 38

The latest Issue 38 of the codelists for use with ONIX 3.0 (only) is now available. I have attached the document that lists all the additions and clarifications in this issue, and as usual, complete listings of the codelists in PDF, HTML, plus various TXT and XML-based formats can be downloaded from the website.

• Issue 38 stand-alone codelist documentation<http://www.editeur.org/14/Code-Lists/#code%20lists> as readable PDF or HTML
• Issue 38 TXT, CSV, XML, JSON<http://www.editeur.org/14/Code-Lists/#code%20list%20files> files for loading into your data management applications
• Issue 38 XSD, RNG, DTD<http://www.editeur.org/14/Code-Lists/#code%20list%20files> schema modules for use with existing ONIX 3.0 XSD and RNG schemas and DTD
• Issue 38 has also been incorporated into the Specification and Best Practice Guide documentation packages for ONIX 3.0<http://www.editeur.org/93/Release-3.0-Downloads/>

As agreed and previously announced by the ONIX International Steering Committee, Issue 36 was the last issue that is fully compatible with ongoing use of ONIX 2.1. Issue 38 does not contain certain codelists that are ONLY used with 2.1, so issue 38 cannot be used for schema validation of 2.1 messages. The original issue 36 can be obtained from the Archived Previous Releases<http://www.editeur.org/15/Archived-Previous-Releases#2.1%20Downloads> page of the website. DTD validation of 2.1 messages will continue to work, because the limited validation the DTD affords does not check the use of codes from the codelists. In the documentation, new additions to shared codelists are clearly marked as ‘only for use with 3.0'.

Issue 39

Issue 38 of the codelists is planned for publication in October 2017 – any requests or suggestions should be discussed within your ONIX national group, or directly with EDItEUR if you are not in contact with a national group. In order to ensure adequate time for discussion of proposals with the national groups, and for the proposals to be considered and ratified by the ONIX International Steering Committee, initial requests for Issue 39 should be forwarded to EDItEUR by Friday August 25th at the latest. I already have suggestions to hand that were submitted too late for inclusion in issue 38.

ONIX 3.0 extended validation

We are preparing a version of the ONIX 3.0 XSD schema that makes use of XSD 1.1 technology to carry out further checks on the validity of the data in ONIX 3.0 files. This XSD 1.1 is not for everyone – not all XML parsers are compatible with XSD 1.1 – so it will not replace the existing schema based on XSD 1.0. However, XSD 1.1 technology can add an optional extra layer of validation, for example checking that the check digits in ISBNs, ISNIs, SANs, GLNs and so on are valid, that various co-occurrence constraints are followed (e.g. if it’s an e-book, then it should not have a <Measure> composite), or that dates ‘make sense’.

If you are a recipient of ONIX data (particularly but not exclusively ONIX 3.0) then it would be useful for us to know what kinds of data issues in apparently-valid files cause you the most problems, or which would be most useful to isolate prior to importing into your database. While not every type of data issue can be tackled with enhanced validation, it will help us at EDItEUR to know what checks would benefit you most.

I look forward to your suggestions.

Regards Graham

140717 via https://groups.yahoo.com/neo/groups/ONIX_IMPLEMENT

ONIX Codelists Issue 35

The latest Issue 35 of the codelists for use with ONIX 3.0 and ONIX 2.1 is now available. I attach a summary of all the changes, and complete listings of the codelists in PDF, HTML and various TXT and XML formats can be downloaded from the website:

• Issue 35 stand-alone codelist documentation<http://www.editeur.org/14/Code-Lists/#code%20lists> as readable PDF or HTML

• ONIX 3.0 updated XSD, RNG, DTD schema files<http://www.editeur.org/93/Release-3.0-Downloads/#Schema%20defs>

• Issue 35 TXT, CSV<http://www.editeur.org/14/Code-Lists/#code%20list%20files>, XML, JSON<http://www.editeur.org/14/Code-Lists/#code%20list%20files> files for loading into your data management applications

• as usual, the code lists are also available as comma or tab-separated files, in a simple XML format and as JSON<http://www.editeur.org/14/Code-Lists/#code%20list%20files>

011116 via ONIX_IMPLEMENT@yahoogroups.com ... eine super liste incl. graham, der beste listenredakteur, den ich kenne. k.

RDA/ONIX Guidelines and Linked Data

bit.ly/1NX7eRi 150616 via Dublin Core @DublinCore

Software

onixedit.com ...

http://www.onixedit.com/fr/Blogue/tabid/100/entryid/26/Default.aspx ... 161215

onixedit.com/en-us/.../welcome-to-exa-editor-users- Today we have officially terminated the site EXA Editor. ONIXEDIT is the new software that will take care of your ONIX files. And it is fully compatible with files ...

onixsuite.com

GiantChair has a long history of helping book publishers create and distribute book catalogue information of extraordinary quality. With more than 100 publishers and distributors in multiple countries using our metadata management platform Onixsuite, GiantChair is on the cutting edge of metadata management and e-commerce for the book publishing industry. http://www.onixsuite.com/about-us/

The Metadata Handbook

themetadatahandbook.com/partners/ Onixsuite gives you control of your metadata and its distribution, ... ONIXEDIT title management software is based on the ONIX standard.

Journals

bookbusinessmag.com

http://www.bookbusinessmag.com/article/publishers-switch-from-onix-21-onix-30/

Artikel aus 2007 zu RDA und ONIX

http://www.dlib.org/dlib/january07/dunsire/01dunsire.html

incl.

References

[1] RDA: Resource Description and Access : Prospectus <http://www.collectionscanada.ca/jsc/rdaprospectus.html>.

[2] ONIX (Online Information Exchange) <http://www.bisg.org/onix/index.html>.

[3] ONIX Books Code Lists, Issue 6, July 2006 <http://www.editeur.org/codelists/ONIX_Code_Lists_Issue_6.PDF>.

[4] RDA/ONIX framework for resource categorization, version 1.0, August 2006 <http://www.collectionscanada.ca/jsc/docs/5chair10.pdf>.

[5] ISO/CD 26324: Information and documentation -- Digital object identifier (DOI) system <http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=43506&scopelist=PROGRAMME>.

[6] Dublin Core Collection Description Application Profile <http://dublincore.org/groups/collections/collection-application-profile/>.

[7] DCMI Type Vocabulary <http://dublincore.org/documents/dcmi-type-vocabulary/>.

[8] Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types <http://www.isi.edu/in-notes/rfc2046.txt>.

[9] Definition of the CIDOC Conceptual Reference Model <http://cidoc.ics.forth.gr/docs/cidoc_crm_version_4.2.pdf>.

[10] DDEX: Digital Data Exchange <http://www.ddex.net/index.htm>.

[11] ONIX for Licensing Terms <http://www.editeur.org/onix_licensing.html>.

onix2marc

http://www.loc.gov/marc/onix2marc.html