The benefits for publishe.ppt

The benefits for publisheThe problem: ConfusionLibraries manage myriad electronic resources and struggle with managing what who can do with which resources.Contributing to this are variations in:Licensors and their contractual terms and conditionsCopyright laws where the end-user is located where an intermediary (e.g. library or aggregator) is located where the resource is published and/or locatedContract law in all of the above placesVaried resource types (even among the same content provider, e.g. journals and books)Possible responsesGet rid of copyrightGet rid of contracts Modify copyright legislation Educate library staff and usersAgree on a single model licensePromote collective licensing to reduce number of license variations (e.g. consortial licensing)Use technology to manage the complexity Digital Rights Management (DRM) Rights Expression Languages Standards for rights and licenses + content (e.g. ONIX for Licensing)Strategic issues Publishers understand the issue and there are a lot of possible responses, each having various implications, but any effort:Will require investment to better manage rights information Will require coherent licensing/rights/use policies within publishing organizationsShould lead to coherence across publishing organizations (but recognizing that strict laws regulate what competitors can and can not share)Practical issuesWhile publishers see this effort as an opportunity to work together to clarify “rules of the road,” to be successful it should:Use a standard, automated approach to keep costs down for allUse standards based on those already embedded in workflows (e.g. ONIX, DOIs) Reflect the needs of all parties Wileys roleWhy does Wiley support a standard XML expression for licensing terms?Publishers want to help libraries understand the terms of the licenses they negotiateIf it helps librarians (e.g. by having terms displayed and conditions clarified), it helps us since libraries are our customers It helps libraries know and comply with terms It may promote usage by clearly delineating authorized rightsIt helps improve our own license terms It maintains flexibility and avoids the “LCD” approachWiley and ONIXWhy does Wiley support this specific approach? (i.e. ONIX for Licensing Terms)ONIX has become accepted as the de facto standard in publishing for the transmission of product dataActionable ONIX terms can be held within XML records; non-actionable terms (i.e. those that are too complicated to encode) can be linked to from the XML expression. Payment details, for example, are likely to be held in a separate file.ONIX should stand a better than average chance of being accepted by the communityProject involvement helps us influence the standard. We have a lot of respect for the other project partners and the project management team (Cranfield; RightsCom; EDItEUR).