ONIX for Repertoire: application guidelines

Size: px
Start display at page:

Download "ONIX for Repertoire: application guidelines"

Transcription

1 ONIX for Repertoire: application guidelines Pilot 2: PLS to CLA use cases: change terms, February 2008 CONTENTS LIST Page Introduction...1 Principles...2 Change Terms notification guidelines...3 RepertoireDetail...7 DetailByResource...10 DetailByResourceClass...13 PriceDefinition...15 Example 1: Use Case 3.1, change terms...17 Example 2: Use Case 3.2, exclude title from all licences...22 Example 3: Use Case 3.3, exclude non-mandating PRC s repertoire from all licences...24 Pilot applications were based on interim versions of the ONIX-RP format. Immediately before Version 1.0 was released, and arising from experience in the pilots, a number of final modifications and corrections were made to the format specification, and these may not all be reflected in the pilot documentation. Please note that, where there is any discrepancy between the pilot guidelines and the Version 1.0 ONIX for Repertoire: message format overview, the overview should be taken as authoritative. Introduction This document provides guidelines and worked examples for one of the groups of PLS-to- CLA ONIX-RP use cases analysed as part of Pilot Project 2. The guidelines take the form of a table whose first three columns are a compressed version of the ONIX-RP Overview. The fourth column shows typical content for each individual element, colour-coded to indicate dictionary terms, labels and other data strings in the same way as in other ONIX documentation. (For composite elements, the column carries the word Composite, since in this case the content comprises the included elements.) The fifth column carries application notes and business rules. Elements in the format that are not used are shaded out in grey. Following the guidelines, examples are given of a number of individual use cases. Each use case is briefly described, and the main elements are summarised, followed by a complete XML example.

2 Principles The principles noted here apply specifically to the PLS-to-CLA implementation. They may not necessarily apply to other ONIX-RP implementations. 1. In PLS and CLA practice a repertoire comprises all the titles for which rights are controlled by a publisher (or more accurately a publishing rights controller, or PRC ). Any titles that the PRC chooses to exclude from all CLA and CLA partner licences are still to be regarded as part of its repertoire. 2. In some cases where a large publisher designates different business units to be responsible for different parts of its output (typically for books and journals), PLS treats each business unit as a separate PRC, each with its own mandate and its own repertoire. 3. PLS sends a Change Terms notification to CLA in the following circumstances only: (a) When a mandating PRC has notified PLS that it wishes to change the terms applying to designated parts of its repertoire, normally expressed as lists of titles and/or classes of title. (b) Exceptionally, when PLS has received a request from a non-mandating publisher for the whole of its repertoire to be excluded from all licences. 4. A Change Terms notification may reference any part of the repertoire belonging to a mandating PRC, from a single title upwards. The notification must fully specify licence inclusions/exclusions and prices for every title (or class of title) to which it refers. 5. It is understood that PLS and CLA will share a common name identifier scheme which applies to PRCs, subsidiaries and imprints. PLS will use the PRC s name identifier, taken from this scheme, as the Repertoire Identifier which is required in all Repertoire Notifications. 6. In any Repertoire Notification, where a class of title is specified (eg all printed journals), and some titles in that class are individually listed, the individual listings always take precedence over the listing by class. However, if a change terms notification specifies a class without listing any individual exceptions, then it must be assumed that the new terms apply to the whole of the class, even if some members of the class have previously been designated as exceptions. If the exceptions are intended to remain in force, they must be restated in the change terms notification. To avoid any ambiguity in this respect, it is expected that if a change terms notification sent by PLS to CLA refers to a class, it will always list all previous exceptions belonging to the class, regardless of whether they have been subject to change. 7. At the time of the release of ONIX-RP Version 1.0, local values to be used by CLA and PLS in a ukrro: namespace in a number of coded data elements had not been finalised. Provisional or illustrative values are shown throughout in green. 2

3 Change Terms notification guidelines 1 <RepertoireNotification> A composite that notifies new or changed 1-n Composite repertoire 2 <NotificationType> An ONIX controlled value specifying a type of 1 ifrro:changeterms a Repertoire Notification 3 <ReasonForNotification> An ONIX controlled value specifying a reason for sending a Repertoire Notification 0-1 ifrro:mandatorrequest ifrro:mandatetermination ifrro:nonmandatorrequest ifrro:correction Mandatory in this use case 4 <NotificationID> A sender-assigned identifier that is unique within the sequence of Repertoire Notifications sent by the Sender to the Addressee 5 <NotificationEffectiveDate> The date on which the changes notified in the Repertoire Notification become effective, expressed as YYYYMMDD 6 <RepertoireIdentifier> A composite that uniquely identifies a Repertoire; repeatable only if two or more identifiers of different types are sent. 7 <RepertoireIDType> An ONIX controlled value identifying the scheme from which the identifier in the <IDValue> element is taken /003 Suggested format is: message number / notification sequence number within message When not sent, the default is today s date 1-n Composite One occurrence only in this use case 1 ukrro:plsrepertoireid It has been suggested that PLS will use its PRC identifier as the repertoire identifier. 8 <IDTypeName> A name of a proprietary scheme, if applicable 0-9 <IDValue> An identifier of the type specified in the <RepertoireIDType> element 10 <RepertoireDescription> A title or description given by the sender to the repertoire to which a Repertoire Notification refers 11 <RepertoireAnnotation> A composite that carries an annotation relating to the repertoire to which a Repertoire Notification refers 12 <RepertoireAnnotationType> An ONIX controlled value specifying the type of the annotation 1 PLS This represents the probable format of the ID, subject to confirmation 0-1??????? The form of title or description (if any) to be assigned to a repertoire by PLS is to be determined 0-13 <AnnotationText> The text of the annotation 14 <RepertoireRelatedAgent> A composite that specifies an Agent that is related to a repertoire, and its relationship to the repertoire 0-n Composite Mandatory in this use case, one occurrence only Copyright EDItEUR & IFRRO 3

4 15 <RepertoireAgentRelator> An ONIX controlled value specifying a relationship between a repertoire and a related agent or agent class 16 <AgentIdentifier> A composite that carries an identifier of an agent or agent class 17 <AgentIDType> An ONIX controlled value identifying the scheme from which the identifier in the <IDValue> element is taken 1 ukrro:hasmandatingprc ukrro:hasnonmandating PRC 0-n Composite Mandatory in this use case; one occurrence must give the PRC s name ID. A second occurrence may be used to send an EIN Number, if it has been notified. 1 ukrro:plsclanameid ifrro:einnumber 18 <IDTypeName> A name of a proprietary scheme, if applicable 0-19 <IDValue> An identifier of the type specified in the <AgentIDType> element It is understood that PLS and CLA will share a common name identifier, assumed here to be used for publisher and imprint names 1??????? The format of PLS/CLA name identifiers is to be determined 20 <Name> A name of an agent or agent class 0-1 PRC name Mandatory in this use case 21 <AgentAnnotation> A composite that carries an annotation relating to an agent, typically used to carry an explanatory note about a rights controller 22 <AgentAnnotation Type> An ONIX controlled value specifying the type of the annotation 0-n Composite Used as necessary to carry a note about a PRC 0-23 <AnnotationText> The text of the annotation 1 Free text 24 <AgentRelatedName> A composite that specifies a name, typically of an imprint or subsidiary, that is related to an agent. Listing of names here means that they do not limit the scope of the repertoire, but indicates that publications bearing these names are normally controlled by the rights controller identified in <RepertoireRelated Agent>. 25 <AgentNameRelator> An ONIX controlled value specifying a 0- relationship between an agent and a related name 26 <NameIdentifier> A composite that carries an identifier of a related name 27 <NameIDType> An ONIX controlled value identifying the scheme from which the identifier in the <IDValue> element is taken 28 <IDTypeName> A name of a proprietary scheme, if applicable 0-29 <IDValue> An identifier of the type specified in the <NameIDType> element Copyright EDItEUR & IFRRO 4

5 30 <Name> A name of an imprint or subsidiary 0-31 <NameAnnotation> A composite that carries an annotation relating to a name, typically used to carry an explanatory note about an imprint 32 <NameAnnotationType> An ONIX controlled value specifying the type of the annotation 0-33 <AnnotationText> The text of the annotation 34 <RepertoireRelatedMandate> A composite that specifies a mandate that is related to a repertoire, and its relationship to the repertoire 35 <RepertoireMandateRelator> An ONIX controlled value specifying a relationship between a repertoire and a related mandate 36 <MandateIdentifier> A composite that carries an identifier of a mandate 37 <MandateIDType> An ONIX controlled value identifying the scheme from which the identifier in the <IDValue> element is taken 0-n Composite One instance may be sent in a Change Terms notification to identify the mandate in relation to which the notification is sent. Not used if the notification relates to a non-mandating PRC. 1 ifrro:hasmandate ifrro:hasformermandate 0-n Composite One instance is mandatory in this use case 1 ukrro:plsmandateid The PLS Mandate ID will also be held in the CLA system 38 <IDTypeName> A name of a proprietary scheme, if applicable 0-39 <IDValue> An identifier of the type specified in the <MandateIDType> element 1 PLS <Name> A name of a mandate 0-41 <MandateRelatedTimePoint> A composite that specifies a date that is related to a mandate, and its relationship to the mandate 0-1 Composite Not used 42 <MandateTimePointRelator> An ONIX controlled value specifying a relationship between a mandate and a related time point 43 <TimePointIdentifier> A composite that carries an identifier of a time point 1 Composite Not used 44 <TimePointIDType> An ONIX controlled value specifying a form of a time point identifier, eg YYYY 45 <IDTypeName> A name of a proprietary scheme, if applicable 0-46 <IDValue> A time point identifier in the form specified in the <TimePointIDType> element Copyright EDItEUR & IFRRO 5

6 47 <RepertoireDefinitionType> An ONIX controlled value that specifies whether a repertoire is defined by the resources specified in successive <Repertoire Detail> elements, or otherwise (eg as all eligible resources controlled by a mandating rights controller) 48 <Definitions> A composite that defines entities referred to in a Repertoire Notification only PriceDefinition is used in this version of ONIX-RP 49 <PriceDefinition> A composite that defines a price that is referred to in a Repertoire Notification 50 <UsageDefinition> A composite that defines a usage referred to in a Repertoire Notification: at present, this is a placeholder only the expansion will be added when found necessary 51 <RepertoireDetail> A composite that specifies rights and resources that together form part of a repertoire: repeat for each part of the repertoire that has different delegated rights and/or pricing 52 <ResourcesExcluded> A composite that specifies resources to be excluded completely from a repertoire 53 <DetailByResource> A composite that specifies a resource expansion as in <RepertoireDetail> 54 <DetailByResourceClass> A composite that specifies a resource class, together with any exclusions from that class expansion as in <RepertoireDetail> Composite Required if one or more publisher-set prices are specified in a notification 1-n Composite Required if one or more publisher-set prices are specified in a notification 1-n Composite See next page 0-1 Composite Not used Copyright EDItEUR & IFRRO 6

7 RepertoireDetail 1 <RepertoireDetail> A composite that specifies rights and resources that together form part of a repertoire 1-n Composite One occurrence only in this use case. 2 <DelegatedRightByLicense> A composite that specifies license inclusions and/or exclusions, and if applicable prices, that apply to part of a repertoire 3 <IncludeUnderLicense> A composite that specifies a license or package of licenses under which specified resources are included 4 <LicenseType> An ONIX controlled value that uniquely identifies either a single license (eg CCC APS) or a package of licenses (eg all PLS/CLA core licences) 5 <UsageWithinLicense> A composite that specifies a usage type within a license type that is specifically permitted or prohibited: this is a placeholder, to be fully defined when the requirement is clear 6 <SubjectToPayment> Either (a) an ONIX controlled value specifying a price class, or (b) a label assigned in a Price Definition to identify a price set by a rights controller. Specifies payment(s) applying to usage under the license type(s) listed in preceding <IncludeUnderLicense> elements. 7 <ExcludeFromLicense> A composite that specifies a license or license class from which specified resources must be excluded expansion as for <IncludeUnder License> 8 <LicenseType> An ONIX controlled value that uniquely identifies either a single license (eg CCC APS) or a package of licenses (eg all PLS/CLA core licences) 9 <WithinTerritory> A composite that specifies a territory for which rights are delegated 10 <PlaceIDType> An ONIX controlled value specifying a scheme from which a place identifier is taken, eg ISO country codes 0-n Composite Mandatory in this use case, one occurrence only. 0-n Composite 1 To be defined PLS and CLA will define a list of individual licenses and license packages suitable for this application 0-n ukrro:cladefault UserDefinedPriceLabel 0-n Composite 1 To be defined Omitted if the licence(s) specified in LicenseType do not have any pricing options. Otherwise one occurrence specifying either a default or a publisher-set price from a PriceDefinition. Multiple occurrences would arise if a license specified both a flat fee per transaction and a volume-based fee. Copyright EDItEUR & IFRRO 7

8 11 <IDValue> A value from the specified scheme, repeatable (eg) for multiple countries 12 <FromTimePoint> A composite that specifies a time from which a delegation of rights is effective 13 <TimePointIDType> An ONIX controlled value specifying a form of a time point identifier, eg YYYY 14 <IDValue> A time point identifier in the form specified in the <TimePointIDType> element 15 <ToTimePoint> A composite that specifies a time to which a delegation of rights is effective 16 <TimePointIDType> An ONIX controlled value specifying a form of a time point identifier, eg YYYY 17 <IDValue> A time point identifier in the form specified in the <TimePointIDType> element 18 <DelegatedRightByUsage> A composite that specifies a usage for which all or part of a repertoire may be licensed by the delegate 19 <LicensableUsage> Either (a) an ONIX controlled value specifying a usage or usage class as a defined term, or (b) a label assigned in a Usage Definition to identify a usage or usage class 20 <WithinTerritory> A composite that specifies a territory for which rights are delegated: expansion as in line 7 above 21 <PlaceIDType> An ONIX controlled value specifying a scheme from which a place identifier is taken, eg ISO country codes 22 <IDValue> A value from the specified scheme, repeatable (eg) for multiple countries 23 <FromTimePoint> A composite that specifies a time from which a delegation of rights is effective: expansion as in line 10 above 24 <TimePointIDType> An ONIX controlled value specifying a form of a time point identifier, eg YYYY 25 <IDValue> A time point identifier in the form specified in the <TimePointIDType> element 1-n Not used 0-1 Composite Not used 0-1 Composite Not used 1-n Not used 0-1 Composite Not used Copyright EDItEUR & IFRRO 8

9 26 <ToTimePoint> A composite that specifies a time to which a delegation of rights is effective: expansion as in line 13 above 27 <TimePointIDType> An ONIX controlled value specifying a form of a time point identifier, eg YYYY 28 <IDValue> A time point identifier in the form specified in the <TimePointIDType> element 29 <UsageQuantity> A composite that specifies a quantity attribute of a usage, eg an extent or volume limit permitted for the usage 30 <UsageQuantityType> An ONIX controlled value specifying a type of a quantity 0-1 Composite Not used 31 <UsageQuantityDetail> A composite that carries details of a quantity 1-n Composite Not used 32 <Proximity> An ONIX controlled value specifying a relationship between a quantity and the <Value> stated in the composite, eg is less than, is not more than ; the default is is exactly 0-33 <Value> A decimal numeric value 34 <MeasureUnit> An ONIX controlled value specifying a unit of measure 35 <ReferenceUnit> An ONIX controlled value specifying a unit to which a quantity refers, if this is not implied by the <UsageQuantityType> 36 <SubjectToPayment> Either (a) an ONIX controlled value specifying a price class, or (b) a label assigned in a Price Definition to identify a price set by a rights controller. Specifies payment(s) applying to a usage. 37 <WholeRepertoireExceptAs Specified/> An XML empty element that indicates that the preceding delegated rights detail applies to the whole of the repertoire except for any resources or resource classes that are specified in separate <RepertoireDetail> elements. In other words, it establishes default delegated rights detail for a repertoire. If this element is present, there must be no <DetailByResource> or <DetailBy Resource Class> elements in the same instance of <RepertoireDetail>. 0-1-n Not used 0-1 Empty element Used when specifying the default terms for a repertoire, or a set of terms that applies to the whole repertoire (when no other <Repertoire Detail> elements are present) Copyright EDItEUR & IFRRO 9

10 DetailByResource 38 <DetailByResource> A composite that specifies a resource. Used where Repertoire Detail is expressed wholly or partly in terms of individual titles. Repeat for each title listed in the Repertoire Detail composite. 0-n Composite 39 <ResourceCategory> A composite that specifies a category to which a resource belongs 40 <ResourceCategoryType> An ONIX controlled value specifying a scheme from which a resource category is taken 41 <CategoryTypeName> A name of a proprietary scheme, if applicable 0-42 <CategoryValue> An category value from the specified scheme 43 <ResourceIdentifier> A composite that carries a unique identifier of a resource 44 <ResourceIDType> An ONIX controlled value specifying a scheme from which a resource identifier is taken 0-n Composite One occurrence only to carry an ISBN-13 or ISSN, mandatory in this use case. 1 ifrro:isbn13, ifrro:issn, ifrro:doi, etc 45 <IDTypeName> A name of a proprietary scheme, if applicable 0-46 <IDValue> An identifier value from the specified scheme <ResourceTitle> A composite that carries a title of a resource 0-n Composite Optional 48 <TitleType> An ONIX controlled value specifying the type 0- of a title 49 <TitleText> The text of the title 1 50 <Subtitle> A subtitle associated with a title <Contributor> A composite that identifies and/or names a single author or other contributor in a structured form 52 <ContributorRole> An ONIX controlled value specifying a role that is played by a contributor to a resource, eg author 53 <ContributorIdentifier> A composite that carries an identifier of a contributor: either a <ContributorIdentifier> or a name (or both) must be present in any instance of the <Contributor> composite 54 <ContributorIDType> An ONIX controlled value identifying the scheme from which the identifier in the <IDValue> element is taken 0-n Composite Optional, and not to be regarded as authoritative 1 0-n Composite 1 Copyright EDItEUR & IFRRO 10

11 55 <IDTypeName> A name of a proprietary scheme, if applicable 0-56 <IDValue> An identifier of the type specified in the <ContributorIDType> element 1 57 <PersonName> A composite that specifies a name of a person 0-n Composite 58 <PersonNameForm> An ONIX controlled value identifying a form of 0- a person name 59 <Name> A name of a person (in the form specified, if <PersonNameForm> is included) 1 60 <OrganizationName> A composite that specifies a name of an organization 0-n Composite 61 <OrganizationNameForm> An ONIX controlled value identifying a form of an organization name 0-62 <Name> A name of a person (in the form specified, if <OrganizationNameForm> is included) 1 63 <Publisher> A composite that identifies and/or names a single publisher in a structured form 64 <PublishingRole> An ONIX controlled value specifying a role that is played by a publisher of a resource 65 <PublisherIdentifier> A composite that carries an identifier of a publisher: either a <PublisherIdentifier> or a <Name> (or both) must be present in any instance of the <Publisher> composite 66 <PublisherIDType> An ONIX controlled value identifying the scheme from which the identifier in the <IDValue> element is taken 67 <IDTypeName> A name of a proprietary scheme, if applicable 0-68 <IDValue> An identifier of the type specified in the <PublisherDType> element 69 <Name> A name of a publisher 0-70 <Imprint> A composite that identifies and/or names an imprint or brand in a structured form 0-1 Composite Optional 71 <ImprintIdentifier> A composite that carries an identifier of an imprint or brand: either an <ImprintIdentifier> or a <Name> (or both) must be present in any instance of the <Imprint> composite 0-n Composite 72 <ImprintIDType> An ONIX controlled value specifying a scheme from which an imprint identifier is taken 1 ukrro:plsclanameid Copyright EDItEUR & IFRRO 11

12 73 <IDTypeName> A name of a proprietary scheme, if applicable 0-74 <IDValue> An identifier value from the specified scheme 1 PLS <Name> A name of an imprint or brand 0-1 Harper Reference Mandatory in this use case if <Imprint> is included 76 <ResourceRelated Resource> A composite that specifies a resource that is related to a resource: used here typically in order to specify a parent resource of which the listed resource is a part eg in the case of an article from a journal 77 <ResourceResource Relator> An ONIX controlled value specifying a relationship of a resource to a resource 78 <ResourceIdentifier> A composite that carries an identifier of a resource 79 <ResourceIDType> An ONIX controlled value specifying a scheme from which a resource identifier is taken 0-n Composite Used only if the listed resource is an Open Access article, to specify the journal in which it is published 1 ifrro:ispartof 1 Composite 1 ifrro:issn 80 <IDTypeName> A name of a proprietary scheme, if applicable 0-81 <IDValue> An identifier value from the specified scheme <ResourceRelatedTimePoint> A composite that specifies a time point that is related to a resource: used here in order to specify a date at which a run of a serial resource begins or ends: only the two elements shown below are used in this context 83 <ResourceTimePointRelator> An ONIX controlled value specifying a relationship of a time point to a resource 84 <TimePointIdentifier> A composite that carries an identifier of a time point 85 <TimePointIDType> An ONIX controlled value specifying a form of a time point identifier, eg YYYY 0-n Composite Used only if the listed resource is a run of serial issues defined by a start and/or end date 1 ifrro:publishedfromdate ifrro:publishedtodate 1 Composite 1 ifrro:yyyy ifrro:yyyymm ifrro:yyyymmdd 86 <IDTypeName> A name of a proprietary scheme, if applicable 0-87 <IDValue> A time point identifier in the form specified in the <TimePointIDType> element Copyright EDItEUR & IFRRO 12

13 DetailByResourceClass 88 <DetailByResourceClass> A composite that specifies a resource class that is part of a repertoire, together with any exclusions from that class 89 <ResourceCategory> A composite that specifies a category to which a resource belongs 90 <ResourceCategoryType> An ONIX controlled value specifying a scheme from which a resource category is taken 0-n Composite 0-n Composite 1 ukrro:resourceclass 91 <CategoryTypeName> A name of a proprietary scheme, if applicable 0-92 <CategoryValue> An category value from the specified scheme 1 To be defined 93 <ResourceRelatedAgent> A composite that specifies an agent that is related to a resource class, and its relationship to the resource class 0-n Composite 94 <ResourceAgentRelator> An ONIX controlled value specifying a 1 ukrro:hasprc relationship between a resource and a related agent or agent class 95 <AgentIdentifier> A composite that carries an identifier of an agent or agent class: either an <Agent Identifier> or a <Name> (or both) must be present in any instance of the <Resource RelatedAgent> composite 0-n Composite 96 <AgentIDType> An ONIX controlled value identifying the 1 ukrro:plsclanameid scheme from which the identifier in the <IDValue> element is taken 97 <IDTypeName> A name of a proprietary scheme, if applicable 0-98 <IDValue> An identifier of the type specified in the <AgentIDType> element 1 PLS <Name> A name of an agent or agent class 0-1 Publisher name 100 <ResourceRelatedTimePoint> A composite that specifies a time point that is related to a resource: used here in order to specify a date at which a run of a serial resource begins or ends: only the two elements shown below are used in this context 101 <ResourceTimePointRelator> An ONIX controlled value specifying a relationship of a time point to a resource 102 <TimePointIdentifier> A composite that carries an identifier of a time point 0-n Composite Used only if the resource class refers to serial publications issued during a period defined by a start and/or end date, eg if the PRC sets different prices for older and newer material 1 ifrro:publishedfromdate ifrro:publishedtodate 1 Composite Copyright EDItEUR & IFRRO 13

14 103 <TimePointIDType> An ONIX controlled value specifying a form of a time point identifier, eg YYYY 1 ifrro:yyyy ifrro:yyyymm ifrro:yyyymmdd 104 <IDTypeName> A name of a proprietary scheme, if applicable <IDValue> A time point identifier in the form specified in the <TimePointIDType> element <ResourceRelatedPlace> A composite that specifies a place that is related to a resource class, and its relationship to the resource class 107 <ResourcePlaceRelator> An ONIX controlled value specifying a relationship between a resource and a related place 108 <PlaceIdentifier> A composite that carries an identifier of a place 109 <PlaceIDType> An ONIX controlled value identifying the scheme from which the identifier in the <IDValue> element is taken 110 <IDTypeName> A name of a proprietary scheme, if applicable <IDValue> An identifier of the type specified in the <PlaceIDType> element 112 <Name> A name of a place <ResourceRelatedName> A composite that specifies a name, typically of an imprint or subsidiary, that is related to a resource class, and its relationship to the resource class. An imprint or subsidiary name is listed here only if it defines a section of a repertoire, eg with different terms from the rest. 0-n Composite 114 <ResourceNameRelator> An ONIX controlled value specifying a relationship between a resource and a related name 115 <NameIdentifier> A composite that carries an identifier of a related name: either a <NameIdentifier> or a <Name> (or both) must be present in any instance of the <ResourceRelatedName> composite 116 <NameIDType> An ONIX controlled value identifying the scheme from which the identifier in the <IDValue> element is taken 1 ifrro:hasimprintname ifrro:hassubsidiaryname 0-n Composite Mandatory in this use case, one occurrence only 1 ukrro:plsclanameid 117 <IDTypeName> A name of a proprietary scheme, if applicable 0- Copyright EDItEUR & IFRRO 14

15 118 <IDValue> An identifier of the type specified in the <NameIDType> element 1 PLS <Name> 0-1 Harper Reference Mandatory in this use case 120 <ExcludingResources> A composite that specifies resources or resource classes to be excluded from the class specified in an instance of <DetailByResourceClass> 0-1 Composite Not used 121 <DetailByResource> A composite that specifies a resource: expansion as from line <DetailByResourceClass> A composite that specifies a resource class: expansion as from line 49 PriceDefinition 1 <PriceDefinition> A composite that defines a price that is referred to in a Repertoire Notification 2 <PriceLabel> A label assigned here to the price for unambiguous internal reference within the ONIX <RepertoireNotification> document only 3 <PriceAnnotation> A composite that carries an annotation relating to a price 4 <PriceAnnotationType> An ONIX controlled value specifying the type of an annotation 1-n Composite Used only if the repertoire includes titles with publisher-set prices. One occurrence for each publisher-set price that is specified in the Repertoire Notification. 1 UserDefinedPriceLabel Values may be assigned as desired, provided that each price has a label that is unique within the Repertoire Notification (NB not necessarily within the message as a whole) 0-5 <AnnotationText> The text of the annotation 6 <PriceAmount> The amount of a price as a decimal number <CurrencyCode> An ISO currency code if the price amount is not in a default currency specified in the message header 8 <ChargeUnit> An ONIX controlled value specifying a unit of content or activity to which a price applies, eg page, article 0-1 iso:usd Required if not the default, or if no default was specified 1 ifrro:articlecopy ifrro:pagecopy Copyright EDItEUR & IFRRO 15

16 9 <PriceQuantity> A composite that specifies a quantity attribute of a price, eg an extent limit permitted for the stated price 10 <PriceQuantityType> An ONIX controlled value specifying a type of a quantity 11 <PriceQuantityDetail> A composite that carries details of a quantity 1-n Composite Not used 12 <Proximity> An ONIX controlled value specifying a relationship between a quantity and the <Value> stated in the composite, eg is less than, is not more than ; default is exactly 0-13 <Value> A decimal numeric value 14 <MeasureUnit> An ONIX controlled value specifying a unit of measure 15 <ReferenceUnit> An ONIX controlled value specifying a unit to which a quantity refers, if this is not implied by the <PriceQuantityType> 16 <VolumeDiscount> An ONIX controlled value specifying an applicable volume discount or discount class that is standard in a particular context: <VolumeDiscount> and <VolumeDiscount Detail> are mutually exclusive in any instance of <PriceDefinition> 17 <VolumeDiscountDetail> A composite that specifies a volume discount set by an individual rights controller 18 <VolumeUnit> An ONIX controlled value specifying a unit of volume, eg copies 19 <MinimumVolume> The minimum volume required to qualify for a specified volume discount: integer 20 <MaximumVolume> The maximum volume qualifying for a specified volume discount: integer 21 <PercentageDiscount> A discount expressed as a percentage of the <PriceAmount>: either <PercentageDiscount> or <DiscountedPriceAmount> must be present in any instance of <VolumeDiscountDetail>: decimal number less than <DiscountedPriceAmount> A discounted price expressed as an absolute amount per unit, in the currency of the <PriceAmount> above ukrro:cladefault If default discounts apply 0-n Composite If publisher-set discounts apply: each instance of the composite defines a discount rate band. Not used at present Copyright EDItEUR & IFRRO 16

17 Example 1: Use Case 3.1, change terms This example shows a simple case of a change terms notification from PLS to CLA, specifying new prices and licence inclusions/exclusions applying to a single book title and a single journal title. Repertoire Notification Type Delegator Delegate Mandating Publisher (PRC) Mandate ID Changed terms - 1 Changed terms - 2 ChangeTerms PLS: not explicitly expressed, on the basis that by default the Delegator is assumed to be the sender of the message CLA: not explicitly expressed, on the basis that by default the Delegate is assumed to be the addressee of the message QQQ M5678 Book: ISBN , title For Love and Money : include in all licences with new per-page prices where applicable Journal: ISSN , title Journal of Irreproducible Results : include in all licences except BL Doc Del with new per-article prices where applicable Example 1 1 <RepertoireNotification> 2 <NotificationType>ifrro:ChangeTerms</NotificationType> 3 <ReasonForNotification>ifrro:MandatorRequest</ReasonForNotification> 4 <NotificationID>57633/003</NotificationID> 5 <NotificationEffectiveDate> </NotificationEffectiveDate> 6 <RepertoireIdentifier> 7 <RepertoireIDType>ukrro:PLSRepertoireID</RepertoireIDType> 8 <IDValue>PLS </IDValue> 9 </RepertoireIdentifier> 10 <RepertoireDescription>???????</RepertoireDescription> 11 <RepertoireRelatedAgent> 12 <RepertoireAgentRelator>ukrro:HasMandatingPRC</RepertoireAgentRelator> 13 <AgentIdentifier> 14 <AgentIDType>ukrro:PLSCLANameID</AgentIDType> 15 <IDValue>PLS </IDValue> 16 </AgentIdentifier> 17 <Name>QQQ</Name> Name of mandating PRC 18 </RepertoireRelatedAgent> Copyright EDItEUR & IFRRO 17

18 19 <RepertoireRelatedMandate> 20 <RepertoireMandateRelator>ifrro:HasMandate</RepertoireMandateRelator> 21 <MandateIdentifier> 22 <MandateIDType>ukrro:PLSMandateID</MandateIDType> 23 <IDValue>M5678</IDValue> 24 </MandateIdentifier> 25 </RepertoireRelatedMandate> 26 <Definitions> 27 <PriceDefinition> 28 <PriceLabel>PriceA</PriceLabel> 29 <PriceAmount>2.50</PriceAmount> 30 <CurrencyCode>iso:GBP</CurrencyCode> 31 <ChargeUnit>ifrro:PageCopy</ChargeUnit> 32 </PriceDefinition> 33 <PriceDefinition> 34 <PriceLabel>PriceB</PriceLabel> 35 <PriceAmount>4.75</PriceAmount> 36 <CurrencyCode>iso:USD</CurrencyCode> 37 <ChargeUnit>ifrro:PageCopy</ChargeUnit> 38 </PriceDefinition> 39 <PriceDefinition> 40 <PriceLabel>PriceC</PriceLabel> 41 <PriceAmount>10.00</PriceAmount> 42 <CurrencyCode>iso:GBP</CurrencyCode> 43 <ChargeUnit>ifrro:ArticleCopy</ChargeUnit> 44 </PriceDefinition> 45 <PriceDefinition> 46 <PriceLabel>PriceD</PriceLabel> 47 <PriceAmount>17.50</PriceAmount> 48 <CurrencyCode>iso:USD</CurrencyCode> 49 <ChargeUnit>ifrro:ArticleCopy</ChargeUnit> 50 </PriceDefinition> 51 </Definitions> Copyright EDItEUR & IFRRO 18

19 52 <RepertoireDetail> This RepertoireDetail element is for ISBN <DelegatedRightByLicense> This group covers licences for which the PRC cannot set prices 54 <IncludeUnderLicense> 55 <LicenseType>ukrro:PLSCLACore</LicenseType> Include under all licences agreed between PLS and CLA as core to PLS mandating publishers 56 </IncludeUnderLicense> 57 <IncludeUnderLicense> Placeholder for enumeration of all CLA optional licences except those 58 <LicenseType>..</LicenseType> listed below 59 </IncludeUnderLicense> 60 <SubjectToPayment>ukrro:CLADefault</SubjectToPayment> CLA default prices 61 </DelegatedRightByLicense> 62 <DelegatedRightByLicense> This group covers UK licences for which the PRC can set prices 63 <IncludeUnderLicense> 64 <LicenseType>ukrro:CLAHighVolDocDel</LicenseType> 65 </IncludeUnderLicense> 66 <IncludeUnderLicense> 67 <LicenseType>ukrro:CLABLDS</LicenseType> 68 </IncludeUnderLicense> 69 <SubjectToPayment>PriceA</SubjectToPayment> Price specified in PriceDefinition as PriceA 70 </DelegatedRightByLicense> 71 <DelegatedRightByLicense> This group covers US licences for which the PRC can set prices 72 <IncludeUnderLicense> 73 <LicenseType>ukrro:CCCAPS</LicenseType> 74 </IncludeUnderLicense> 75 <IncludeUnderLicense> 76 <LicenseType>ukrro:CCCTRS</LicenseType> 77 </IncludeUnderLicense> 78 <SubjectToPayment>PriceB</SubjectToPayment> Price specified in PriceDefinition as PriceB 79 </DelegatedRightByLicense> 80 <DetailByResource> 81 <ResourceIdentifier> 82 <ResourceIDType>ifrro:ISBN13</ResourceIDType> 83 <IDValue> </IDValue> 84 </ResourceIdentifier> Copyright EDItEUR & IFRRO 19

20 85 <ResourceTitle> 86 <TitleText>For Love and Money</TitleText> 87 </ResourceTitle> 88 </DetailByResource> 89 </RepertoireDetail> 90 <RepertoireDetail> This RepertoireDetail element is for ISSN <DelegatedRightByLicense> 92 <IncludeUnderLicense> 93 <LicenseType>ukrro:PLSCLACore</LicenseType> Include under all licences agreed between PLS and CLA as core to PLS mandating publishers 94 </IncludeUnderLicense> 95 <IncludeUnderLicense> Placeholder for enumeration of all CLA optional licences except those 96 <LicenseType>..</LicenseType> listed below 97 </IncludeUnderLicense> 98 <SubjectToPayment>ukrro:CLADefault</SubjectToPayment> CLA default prices 99 </DelegatedRightByLicense> 100 <DelegatedRightByLicense> This group covers UK licences for which the PRC can set prices 101 <IncludeUnderLicense> 102 <LicenseType>ukrro:CLAHighVolDocDel</LicenseType> 103 </IncludeUnderLicense> 104 <SubjectToPayment>PriceC</SubjectToPayment> Price specified in PriceDefinition as PriceC 105 </DelegatedRightByLicense> 106 <DelegatedRightByLicense> 107 <ExcludeFromLicense> 108 <LicenseType>ukrro:CLABLDS</LicenseType> Exclude from BL licence 109 </ExcludeFromLicense> 110 </DelegatedRightByLicense> 111 <DelegatedRightByLicense> This group covers US licences for which the PRC can set prices 112 <IncludeUnderLicense> 113 <LicenseType>ukrro:CCCAPS</LicenseType> 114 </IncludeUnderLicense> 115 <IncludeUnderLicense> 116 <LicenseType>ukrro:CCCTRS</LicenseType> 117 </IncludeUnderLicense> Copyright EDItEUR & IFRRO 20

21 118 <SubjectToPayment>PriceD</SubjectToPayment> Price specified in PriceDefinition as PriceD 119 </DelegatedRightByLicense> 120 <DetailByResource> 121 <ResourceIdentifier> 122 <ResourceIDType>ifrro:ISSN</ResourceIDType> 123 <IDValue> </IDValue> 124 </ResourceIdentifier> 125 <ResourceTitle> 126 <TitleText>Journal of Irreproducible Results</TitleText> 127 </ResourceTitle> 128 </DetailByResource> 129 </RepertoireDetail> 130 </RepertoireNotification> Copyright EDItEUR & IFRRO 21

22 Example 2: Use Case 3.2, exclude title from all licences This example shows how a single title exclusion requested by a mandating PRC is communicated from PLS to CLA as a change terms notification. Repertoire Notification Type Delegator Delegate Mandating Publisher Mandate ID Title excluded ChangeTerms PLS: not explicitly expressed, on the basis that by default the Delegator is assumed to be the sender of the message CLA: not explicitly expressed, on the basis that by default the Delegate is assumed to be the addressee of the message Publisher BBB M2345 Book: ISBN , title: This Title s Not For Copying Example 2 1 <RepertoireNotification> 2 <RepertoireNotificationType>ifrro:ChangeTerms</RepertoireNotificationType> 3 <ReasonForNotification>ifrro:MandatorRequest</ReasonForNotification> 4 <RepertoireNotificationID>57633/004</RepertoireNotificationID> 5 <RepertoireNotificationEffectiveDate> </RepertoireNotificationEffectiveDate> 6 <RepertoireIdentifier> 7 <RepertoireIDType>ukrro:PLSRepertoireID</RepertoireIDType> 8 <IDValue>PLS </IDValue> 9 </RepertoireIdentifier> 10 <RepertoireDescription>???????</RepertoireDescription> 11 <RepertoireRelatedAgent> 12 <RepertoireAgentRelator>ukrro:HasMandatingPRC</RepertoireAgentRelator> 13 <AgentIdentifier> 14 <AgentIDType>ukrro:PLSCLANameID</AgentIDType> 15 <IDValue>PLS </IDValue> 16 </AgentIdentifier> 17 <Name>BBB</Name> 18 </RepertoireRelatedAgent> 19 <RepertoireRelatedMandate> 20 <RepertoireMandateRelator>ifrro:HasMandate</RepertoireMandateRelator> Copyright EDItEUR & IFRRO 22

23 21 <MandateIdentifier> 22 <MandateIDType>ukrro:PLSMandateID</MandateIDType> 23 <IDValue>M2345</IDValue> 24 </MandateIdentifier> 25 </RepertoireRelatedMandate> 26 <RepertoireDetail> 27 <DelegatedRightByLicense> 28 <ExcludeFromLicense> 29 <LicenseType>ukrro:AllCLAAdministeredLicenses</LicenseType> All licences operated by CLA, or CLA partners under bilateral agreements 30 </ExcludeFromLicense> 31 </DelegatedRightByLicense> 32 <DetailByResource> 33 <ResourceIdentifier> 34 <ResourceIDType>ifrro:ISBN13</ResourceIDType> 35 <IDValue> </IDValue> 36 </ResourceIdentifier> 37 <ResourceTitle> 38 <TitleText>This Title s Not For Copying</TitleText> 39 </ResourceTitle> 40 </DetailByResource> 41 </RepertoireDetail> 42 <RepertoireNotification> Copyright EDItEUR & IFRRO 23

24 Example 3: Use Case 3.3, exclude non-mandating PRC s repertoire from all licences This example shows how a request from a non-mandating PRC to have its entire repertoire excluded from all licences is communicated from PLS to CLA as a change terms notification. Repertoire Notification Type Delegator Delegate Non-mandating Publisher Mandate ID Title excluded ChangeTerms PLS: not explicitly expressed, on the basis that by default the Delegator is assumed to be the sender of the message CLA: not explicitly expressed, on the basis that by default the Delegate is assumed to be the addressee of the message Publisher XXX Not applicable Whole repertoire Example 3 1 <RepertoireNotification> 2 <RepertoireNotificationType>ifrro:ChangeTerms</RepertoireNotificationType> 3 <ReasonForNotification>ifrro:NonMandatorRequest</ReasonForNotification> 4 <RepertoireNotificationID>57633/004</RepertoireNotificationID> 5 <RepertoireNotificationEffectiveDate> </RepertoireNotificationEffectiveDate> 6 <RepertoireIdentifier> 7 <RepertoireIDType>ukrro:PLSRepertoireID</RepertoireIDType> 8 <IDValue>PLS </IDValue> 9 </RepertoireIdentifier> 10 <RepertoireDescription>???????</RepertoireDescription> 11 <RepertoireRelatedAgent> 12 <RepertoireAgentRelator>ukrro:HasNonMandatingPRC</RepertoireAgentRelator> 13 <AgentIdentifier> 14 <AgentIDType>ukrro:PLSCLANameID</AgentIDType> 15 <IDValue>PLS </IDValue> 16 </AgentIdentifier> 17 <Name>XXX</Name> 18 </RepertoireRelatedAgent> 19 <RepertoireDetail> 20 <DelegatedRightByLicense> Copyright EDItEUR & IFRRO 24

25 21 <ExcludeFromLicense> 22 <LicenseType>ukrro:AllCLAAdministeredLicenses</LicenseType> All licences operated by CLA, or CLA partners under bilateral agreements 23 </ExcludeFromLicense> 24 </DelegatedRightByLicense> 25 <WholeRepertoireExceptAsSpecified/> Exclusions apply to whole repertoire, since no exceptions are listed 26 </RepertoireDetail> 27 <RepertoireNotification> Copyright EDItEUR & IFRRO 25

ONIX for Repertoire: message format overview

ONIX for Repertoire: message format overview ONIX for Repertoire: message format overview Version.0, February 2008 CONTENTS LIST Page. Introduction...2 2. Repertoire Notification...2 2. Definitions...2 2.2 Repertoire Detail...3 2.3 Resources Excluded...4

More information

ONIX for Price Catalog

ONIX for Price Catalog Version. March 202 EDItEUR invites comments on this specification and the associated XML schema. Please send comments and suggestions for improvement to info@editeur.org. ONIX-PC Version. revision notes

More information

DOI METADATA FOR MONOGRAPHIC WORKS

DOI METADATA FOR MONOGRAPHIC WORKS DOI METADATA FOR MONOGRAPHIC WORKS ONIX subset specification by EDItEUR on behalf of medra This document specifies an ONIX subset with a number of newly-defined elements intended to provide a communication

More information

ONIX for Price Catalog Format Overview

ONIX for Price Catalog Format Overview Format Overview Version.. September 202, with minor corrections and updates to the documentation, June 204 EDItEUR invites comments on this specification and the associated XML schema. Please send comments

More information

How to Map ONIX for RROs to Your System

How to Map ONIX for RROs to Your System How to Map ONIX for RROs to Your System Based upon the ONIX for RROs message suite: ONIX for Distribution (ONIX DS), schema version 1.1 ONIX for Repertoire (ONIX RP), schema version 1.0 PREPARED BY COPYRIGHT

More information

DOI METADATA FOR MONOGRAPHIC PRODUCTS

DOI METADATA FOR MONOGRAPHIC PRODUCTS DOI METADATA FOR MONOGRAPHIC PRODUCTS ONIX subset specification by EDItEUR on behalf of medra This document specifies an ONIX subset with a number of newly-defined elements intended to provide a communication

More information

ONIX DOI METADATA FOR SERIAL TITLES

ONIX DOI METADATA FOR SERIAL TITLES ONIX DOI METADATA FOR SERIAL TITLES Message specification, Version 2.0, January 2011 (document version n.2, April 2014) This document specifies an ONIX subset with a number of newly-defined elements intended

More information

NISO/EDItEUR Joint Working Party. ONIX for Serials. Serials Online Holdings (SOH) format overview Version 1.1

NISO/EDItEUR Joint Working Party. ONIX for Serials. Serials Online Holdings (SOH) format overview Version 1.1 NISO/EDItEUR Joint Working Party ONIX for Serials Serials Online Holdings (SOH) format overview Version 1.1 Version 1.1: June, 2007 (last updated October, 2007) Changes made to this document in October,

More information

ONIX for Books Product Information Message. Application Note: Describing Open Access monographs in ONIX 3.0

ONIX for Books Product Information Message. Application Note: Describing Open Access monographs in ONIX 3.0 ONIX for Books Product Information Message Application Note: Describing Open Access monographs in ONIX 3.0 Open Access monographs are e-books and possibly also some conventional printed products that are

More information

BIC EDI Standards and Implementation Guidelines. RETURNS Returns Request. The RETANN message

BIC EDI Standards and Implementation Guidelines. RETURNS Returns Request. The RETANN message BIC EDI Standards and Implementation Guidelines RETURNS Returns Request The RETANN message October 2012 R.3. USING THE RETANN MESSAGE FOR RETURNS REQUESTS June 2018 Changes are shown in Green throughout

More information

ONIX for Price Catalog Format Overview

ONIX for Price Catalog Format Overview Format Overview Version.2 Draft to support pilot exchanges, November 205 EDItEUR invites comments on this specification and the associated XML schema. Please send comments or suggestions for improvement

More information

ONIX DOI METADATA FOR MONOGRAPH CHAPTERS

ONIX DOI METADATA FOR MONOGRAPH CHAPTERS ONIX DOI METADATA FOR MONOGRAPH CHAPTERS Message specification, Version 2.0, January 2011 This document specifies an ONIX subset with a number of newly-defined elements intended to provide a communication

More information

ONIX DOI METADATA FOR SERIAL ARTICLES

ONIX DOI METADATA FOR SERIAL ARTICLES ONIX DOI METADATA FOR SERIAL ARTICLES Message specification, Version 1.0, 10 November 2004 doi: 10.1392/specsa This document specifies an ONIX subset with a number of newly-defined elements intended to

More information

ONIX DOI METADATA FOR MONOGRAPHS

ONIX DOI METADATA FOR MONOGRAPHS ONIX DOI METADATA FOR MONOGRAPHS Message specification, Version 1.1, March 2007: corrected February 2008 1 This document specifies an ONIX subset with a number of newly-defined elements intended to provide

More information

S.3 USING THE DESPATCH ADVICE FOR JOURNAL ISSUE NOTIFICATIONS OR DESPATCH ADVICES

S.3 USING THE DESPATCH ADVICE FOR JOURNAL ISSUE NOTIFICATIONS OR DESPATCH ADVICES EDItEUR Implementation Guidelines for Serials, Version 1.3 S.3 USING THE DESPATCH ADVICE FOR JOURNAL ISSUE NOTIFICATIONS OR DESPATCH ADVICES S.3.0 CHANGES FROM VERSION 1.2 Page S-3-4 Page S-3-6 Page S-3-7

More information

ICEDIS New Order Message Format Overview

ICEDIS New Order Message Format Overview Format Overview DRAFT Version 0. June 204 Incorporating changes arising during schema generation and internal review Please note that this document is a working draft. EDItEUR invites comments on this

More information

ONIX DOI Serial Article Version Application Profile to access medra/crossref services

ONIX DOI Serial Article Version Application Profile to access medra/crossref services ONIX DOI Serial Article Version 2.0 - Application Profile to access medra/crossref services This document describes the specification for the DOI registration for the Serial Article Version 2.0 according

More information

ONIX for Books release 3.0.2

ONIX for Books release 3.0.2 ONIX for Books release 3.0.2 Contents ONIX for Books release 3.0.2... 1 Contents... 1 1. Repositioning of within ... 1 2. New license information for e-publications... 2

More information

NISO/EDItEUR Joint Working Party. ONIX for Serials. Coverage Statement, Version 1.0. March 2012

NISO/EDItEUR Joint Working Party. ONIX for Serials. Coverage Statement, Version 1.0. March 2012 NISO/EDItEUR Joint Working Party ONIX for Serials Coverage Statement, Version 1.0 March 2012 This specification has been prepared by the NISO/EDItEUR Joint Working Party, Coverage subgroup, chaired by

More information

ABC Business Magazines Reporting Standards (UK)

ABC Business Magazines Reporting Standards (UK) July 2017 ABC Business Magazines Reporting Standards (UK) Changes have been agreed to the ABC Business Magazine Reporting Standards. We have updated the latest Reporting Standards to incorporate these

More information

T.6 USING THE ORDER STATUS ENQUIRY FOR ORDER CHASERS

T.6 USING THE ORDER STATUS ENQUIRY FOR ORDER CHASERS T.6 USING THE ORDER STATUS ENQUIRY FOR ORDER CHASERS T.6.1 PRINCIPLES The order status enquiry message may be used to request latest status information on an outstanding order or orders (in other words,

More information

SWG-F D6 MESSAGE IMPLEMENTATION GUIDELINE OF THE UN/EDIFACT SECURE AUTHENTICATION & ACKNOWLEDGEMENT MESSAGE AUTACK. DRAFT 0.6m

SWG-F D6 MESSAGE IMPLEMENTATION GUIDELINE OF THE UN/EDIFACT SECURE AUTHENTICATION & ACKNOWLEDGEMENT MESSAGE AUTACK. DRAFT 0.6m SWG-F D6 MESSAGE IMPLEMENTATION GUIDELINE OF THE UN/EDIFACT SECURE AUTHENTICATION & ACKNOWLEDGEMENT MESSAGE AUTACK DRAFT 0.6m This simplified Message Implementation Guide is designed to accommodate the

More information

AUTACK. Secure authentication and acknowledgement message. Edition 2016

AUTACK. Secure authentication and acknowledgement message. Edition 2016 EANCOM 2002 S4 Secure authentication and acknowledgement message Edition 2016 1. Introduction... 2 2. Message Structure Chart... 3 3. Branching Diagram... 4 4. Segments Description... 5 5. Segments Layout...

More information

Service Segments. Edition 2012

Service Segments. Edition 2012 EANCO 2002 S3 Service Segments Edition 2012 essage Structure Chart... 2 Branching Diagram... 3 Segments... 4 Segments Layout... 5 2. essage Structure Chart UNA 1 C 1 - Service string advice UNB 2 1 - Interchange

More information

Joint ISO/TC 154 UN/CEFACT Syntax Working Group (JSWG) publication of ISO

Joint ISO/TC 154 UN/CEFACT Syntax Working Group (JSWG) publication of ISO Joint ISO/TC 154 UN/CEFACT Syntax Working Group (JSWG) publication of ISO 9735-1 equivalent to the official ISO publication: ISO 9735-1 (First edition 1998-10-01) Electronic data interchange for administration,

More information

KEYMAN. Security key and certificate management message. Edition 2016

KEYMAN. Security key and certificate management message. Edition 2016 EANCOM 2002 S4 Security key and certificate management message Edition 2016 1. Introduction... 2 2. Message Structure Chart... 3 3. Branching Diagram... 4 4. Segments Description... 5... 6 6. Example(s)...

More information

Use of RMI in the Online Delivery of Text-based content: Standards for the expression of publisher/library licenses

Use of RMI in the Online Delivery of Text-based content: Standards for the expression of publisher/library licenses Use of RMI in the Online Delivery of Text-based content: Standards for the expression of publisher/library licenses Brian Green EDItEUR 1 EDItEUR International umbrella body for book industry standards

More information

AUTACK. Secure authentication and acknowledgement message. Edition 2012

AUTACK. Secure authentication and acknowledgement message. Edition 2012 Secure authentication and acknowledgement message Edition 2012 1. Introduction... 2 2. Message Structure Chart... 3 3. Branching Diagram... 4 4. Segments Description... 5 5. Segments Layout... 6 6. Example(s)...

More information

GENRAL. General purpose message. Edition 2016

GENRAL. General purpose message. Edition 2016 EANCOM 2002 S4 Edition 2016 1. Introduction... 2 2. Message Structure Chart... 3 3. Branching Diagram... 4 4. Segments Description... 5... 7 6. Example(s)... 28 EANCOM 2002 S4 The Messages 1. Introduction

More information

EDItEUR Book Trade EDI Implementation Guidelines Orders to Invoices: DESADV, Status 3

EDItEUR Book Trade EDI Implementation Guidelines Orders to Invoices: DESADV, Status 3 T.7 USING THE DESPATCH ADVICE TO NOTIFY DELIVERIES T.7.1 PRINCIPLES The DESADV message enables a supplier to communicate to a customer the content of a delivery which includes items from either a single

More information

Electronic data interchange for administration, commerce and Transport (EDIFACT) - Application level syntax rules

Electronic data interchange for administration, commerce and Transport (EDIFACT) - Application level syntax rules ISO 9735 : 1988 (E) Electronic data interchange for administration, commerce and Transport (EDIFACT) - Application level syntax rules 1 Scope This International Standard gives syntax rules for the preparation

More information

Book Industry Communication

Book Industry Communication Book Industry Communication Library Interoperability Standards Library Data Communication Framework for Terminal Applications (LCF) 1 Version 1.0, 10 January 2014 This document defines data frameworks

More information

HCHETTE BOOK GROUP USA 855 Purchase Order Acknowledgement VERSION 4010 IMPLEMENTATION GUIDE

HCHETTE BOOK GROUP USA 855 Purchase Order Acknowledgement VERSION 4010 IMPLEMENTATION GUIDE HCHETTE BOOK GROUP USA 855 Purchase Order Acknowledgement VERSION 4010 IMPLEMENTATION GUIDE 1 Purchase Order Acknowledgement 855 4010 Functional Group PR This Draft Standard for Trial Use contains the

More information

Workgroup Document version: 2. Version 4.0. SECTION Infrastructure Messages 06 IMBNOT Imbalance Notice Message

Workgroup Document version: 2. Version 4.0. SECTION Infrastructure Messages 06 IMBNOT Imbalance Notice Message SECTION II Infrastructure Messages 06 IMBNOT Imbalance Notice Message Version 4.0 Edig@s EASEE-gas/Edig@s Workgroup Document version: 2 IMBNOT Version 4.0 / 2011-08-30 II-06-1 COPYRIGHT & LIABILITY The

More information

Message Definition ORDERS Purchasing order ECR-Austria EANCOM 2002 (Syntax 3) Version 1.6

Message Definition ORDERS Purchasing order ECR-Austria EANCOM 2002 (Syntax 3) Version 1.6 Message Definition ORDERS Purchasing order ECR-Austria EANCOM 2002 (Syntax 3) Version 1.6 Message Type: Message Version: Responsible Agency: Directory Name: Directory Version: ORDERS 010(EANCOM) GS1-Austria

More information

Book Industry Communication

Book Industry Communication Book Industry Communication BIC Library Web Services API Standards Retrieve ARC Product Information Version 2.0, 29 October 2018 This document: http://www.bic.org.uk/files/pdfs/bicwsarcproductinformation-v2.0.pdf

More information

Administrative Guideline. SMPTE Metadata Registers Maintenance and Publication SMPTE AG 18:2017. Table of Contents

Administrative Guideline. SMPTE Metadata Registers Maintenance and Publication SMPTE AG 18:2017. Table of Contents SMPTE AG 18:2017 Administrative Guideline SMPTE Metadata Registers Maintenance and Publication Page 1 of 20 pages Table of Contents 1 Scope 3 2 Conformance Notation 3 3 Normative References 3 4 Definitions

More information

MediaSaturn VMI ORDRSP (EAN009) S3

MediaSaturn VMI ORDRSP (EAN009) S3 Message Implementation Guideline MediaSaturn VMI ORDRSP (EAN009) S3 based on ORDRSP Purchase order response message EANCOM 2002 S3 Version: 2002 - Edition 2010 Variant: Issue date: 26.10.2016 Author: Robert

More information

Service Segments. Edition 2012

Service Segments. Edition 2012 EANO 2002 S4 Service Segments Edition 2012 essage Structure hart... 2 Branching Diagram... 3 Segments... 4 Segments Layout... 5 EANO 2002 S4 Part II 2. essage Structure hart UNA 1 1 - Service string advice

More information

THE COMDIS MESSAGE EANCOM97/EDIFACT D.96A. agreed-upon by EDI Working Group of ECR Poland. Issue 1.0, April 2011

THE COMDIS MESSAGE EANCOM97/EDIFACT D.96A. agreed-upon by EDI Working Group of ECR Poland. Issue 1.0, April 2011 Polska THE COMDIS MESSAGE EANCOM97/EDIFACT D.96A Issue 1.0, April 2011 agreed-upon by EDI Working Group of ECR Poland The document contains only these segments and data elements that were agreed and accepted

More information

APERAK. Application error and acknowledgement message. Edition 2016

APERAK. Application error and acknowledgement message. Edition 2016 EANCOM 2002 S3 Application error and acknowledgement message Edition 2016 1. Introduction... 2 2. Message Structure Chart... 4 3. Branching Diagram... 5 4. Segments Description... 6... 8 6. Example(s)...

More information

Open Access. Green Open Access

Open Access. Green Open Access Open Access Green Open Access At any German Institution that signs up to one of the agreed packages, any author at that institution, or the institution itself is free to place any articles published by

More information

CONDRA. Drawing administration message. Edition 2012

CONDRA. Drawing administration message. Edition 2012 EANCOM 2002 S4 Edition 2012 1. Introduction... 2 2. Message Structure Chart... 5 3. Branching Diagram... 6 4. Segments... 9... 11 6. Example(s)... 27 EANCOM 2002 S4 Part II The Messages 1. Introduction

More information

Conformance Requirements Guideline Version 0.1

Conformance Requirements Guideline Version 0.1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 Editors: Conformance Requirements Guideline Version 0.1 Aug 22, 2001 Lynne Rosenthal (lynne.rosenthal@nist.gov)

More information

Book Industry Communication

Book Industry Communication Book Industry Communication Price and Availability Request and Response Version 1.2, 23 April 2009, updated 5 ay 2009 Re-issued with additional text describing CF use cases, 18 July 2011 This document

More information

Mapping License Terms. Traversing the Licensing Terrain: Emerging Issues and Innovative Solutions NISO/PALINET Forum - June 11, 2007

Mapping License Terms. Traversing the Licensing Terrain: Emerging Issues and Innovative Solutions NISO/PALINET Forum - June 11, 2007 Mapping License Terms Ted Koppel Ex Libris Traversing the Licensing Terrain: Emerging Issues and Innovative Solutions NISO/PALINET Forum - June 11, 2007 Combined presentation ONIX for Licensing Terms from

More information

BIC EDI Standards and Implementation Guidelines. The Book Trade. TRADACOMS File format specifications. The Acknowledgement of Order File

BIC EDI Standards and Implementation Guidelines. The Book Trade. TRADACOMS File format specifications. The Acknowledgement of Order File BIC EDI Standards and Implementation Guidelines The Book Trade TRADACOMS File format specifications The Acknowledgement of Order File August 2008 ACKMNT format for book trade acknowledgements ACKNOWLEDGEMENTS

More information

FINSTA. Financial statement of an account message. Edition 2008

FINSTA. Financial statement of an account message. Edition 2008 EANCOM 2002 S3 Financial statement of an account message Edition 2008 1. Introduction... 2 2. Message Structure Chart... 4 3. Branching Diagram... 5 4. Segments... 8... 10 6. Example(s)... 32 EANCOM 2002

More information

APERAK. Application error and acknowledgement message. Edition 2012

APERAK. Application error and acknowledgement message. Edition 2012 EANCOM 2002 S4 Application error and acknowledgement message Edition 2012 1. Introduction... 2 2. Message Structure Chart... 4 3. Branching Diagram... 5 4. Segments... 6... 7 6. Example(s)... 21 Application

More information

memorandum Syntax and structure of EDI messages Regulation F: EDI communication Appendix report 1: April 2007 Rev. 1

memorandum Syntax and structure of EDI messages Regulation F: EDI communication Appendix report 1: April 2007 Rev. 1 memorandum Regulation F: EDI communication Appendix report 1: Syntax and structure of EDI messages April 2007 Rev. 1 In case of any discrepancy between the Danish text and the English translation, the

More information

Co-Ordinated Retail Market Message Guide

Co-Ordinated Retail Market Message Guide Co-Ordinated Retail Market Message Guide ROI Implementation - Customer Data and Agreements Document Information Business Area: Status: Author/s: ESB Networks Final ESBN Version Number: 3.1 Reason for Change

More information

Category 2 Financial Institution Transfers

Category 2 Financial Institution Transfers SWIFTStandards Category 2 Financial Institution Transfers November 2003 Standards Release 1 Legal Notices Legal Notices IMPORTANT NOTE: You may install and use this publication only if you have entered

More information

810 Invoice. Version: 1.0 Final. X12/V4010/810: 810 Invoice. Company: Baker & Taylor Modified: 10/26/2010 Notes:

810 Invoice. Version: 1.0 Final. X12/V4010/810: 810 Invoice. Company: Baker & Taylor Modified: 10/26/2010 Notes: 810 Invoice X12/V4010/810: 810 Invoice Version: 1.0 Final Author: Baker & Taylor Company: Baker & Taylor Modified: 10/26/2010 Notes: Table of Contents 810 Invoice... 1 ISA Interchange Control Header...

More information

373 Prices and Eligibility

373 Prices and Eligibility Commercial Letters: Media Mail Prices and Eligibility 373 373.1.6.1 373 Prices and Eligibility Overview 1.0 Prices and Fees for Media Mail 2.0 Content Standards for Media Mail Flats 3.0 Price Eligibility

More information

ANNEX ANNEX. to the COMMISSION IMPLEMENTING REGULATION (EU)

ANNEX ANNEX. to the COMMISSION IMPLEMENTING REGULATION (EU) Ref. Ares(2018)1944240-11/04/2018 EUROPEAN COMMISSION Brussels, XXX [ ](2018) XXX draft ANNEX ANNEX to the COMMISSION IMPLEMENTING REGULATION (EU) laying down minimum requirements implementing the provisions

More information

Air Transport & Travel Industry. Principles, Functional and Business Requirements PNRGOV

Air Transport & Travel Industry. Principles, Functional and Business Requirements PNRGOV Air Transport & Travel Industry Principles, Functional and Business Requirements Version 15.1 Endorsed by WCO Council in July 2016 Table of Contents 1 INTRODUCTION... 3 1.1 PURPOSE... 3 1.2 SCOPE... 3

More information

L.5 USING THE PURCHASE ORDER RESPONSE FOR ORDER RESPONSES AND REPORTS

L.5 USING THE PURCHASE ORDER RESPONSE FOR ORDER RESPONSES AND REPORTS L.5 USING THE PURCHASE ORDER RESPONSE FOR ORDER RESPONSES AND REPORTS L.5.0 CHANGES FROM VERSION 1.1 Page L-5-5 Page L-5-7 Page L-5-10 References to the use of the IMD segment to send enhanced bibliographic

More information

CERTIFIED MAIL LABELS TERMS OF USE and PRIVACY POLICY Agreement

CERTIFIED MAIL LABELS TERMS OF USE and PRIVACY POLICY Agreement CERTIFIED MAIL LABELS TERMS OF USE and PRIVACY POLICY Agreement Welcome to Certified Mail Envelopes and Certified Mail Labels web sites (the Site ) a website, trademark and business name owned and operated

More information

SUBMISSION GUIDELINES EBOOKS

SUBMISSION GUIDELINES EBOOKS SUBMISSION GUIDELINES EBOOKS The information below is intended to outline some common preferred criteria and practices in order to send electronic data to EBSCO Information Services. These guidelines describe

More information

ASX - AU - Austraclear SWIFT Messaging - V1 - DRAFT_900_Confirmation of Debit (Response to inward MT103/MT202 Message)

ASX - AU - Austraclear SWIFT Messaging - V1 - DRAFT_900_Confirmation of Debit (Response to inward MT103/MT202 Message) ASX - AU - Austraclear SWIFT Messaging - V1 - DRAFT_900_Confirmation of Debit (Response to inward MT103/MT202 Message) ASX - AU - Austraclear SWIFT Messaging - 2015 This document describes a usage guideline

More information

173 Prices and Eligibility. 1.0 Media Mail Prices and Fees

173 Prices and Eligibility. 1.0 Media Mail Prices and Fees 173173.1.5 173 Prices and Eligibility Overview 1.0 Media Mail Prices and Fees 2.0 Basic Eligibility Standards for Media Mail 3.0 Content Standards 4.0 Attachments and Enclosures 1.0 Media Mail Prices and

More information

D-Cinema Packaging Caption and Closed Subtitle

D-Cinema Packaging Caption and Closed Subtitle SMPTE STANDARD SMPTE 429-12-2008 D-Cinema Packaging Caption and Closed Subtitle Page 1 of 11 pages Table of Contents Page Foreword... 2 Intellectual Property... 2 1 Scope... 3 2 Conformance Notation...

More information

GovX Purchase Order. X12/V5010/850: 850 Purchase Order

GovX Purchase Order. X12/V5010/850: 850 Purchase Order 850 Purchase Order X12/V5010/850: 850 Purchase Order Company: GovX.com 1 4/12/2013 Purchase Order - 850 10/16/2015 Added TD5 segment 1/7/2016 Added new value UP in PO106 2 Table of Contents 850 Purchase

More information

ELECTRONIC SUBMISSION FRAMEWORK (ESF)

ELECTRONIC SUBMISSION FRAMEWORK (ESF) ELECTRONIC SUBMISSION FRAMEWORK (ESF) LEXIS (Log Export Information System) SUBMISSION GUIDE FOR PROVINCIAL APPLICATIONS Client: Ministry of Forests Information Management Group Date: April 8, 2008 Revision:

More information

When and what information does Kantar Worldpanel collect?

When and what information does Kantar Worldpanel collect? Shoppix Privacy Policy [16 th march 2017] Kantar Worldpanel (herein referred to as we or us ) which operates Shoppix, recognises that your privacy is important and that you have the right to know what

More information

Standard Elements Importer

Standard Elements Importer 1 Standard Elements Importer The Standard Elements Importer (import tool) is a utility that can be used to import data from formatted CSVs into Elements via the Elements API. Glossary Category: The category

More information

* Free calls from landlines and public phones. Some standard network charge applies.

* Free calls from landlines and public phones. Some standard network charge applies. WESTERN UNION MONEY TRANSFER SM ( TRANSFERS ) AND COMMERCIAL PAYMENT ( COMMERCIAL PAYMENTS ) SERVICES (COLLECTIVELY, SERVICES ) ARE PROVIDED ON THE FOLLOWING TERMS AND CONDITONS Transfers can be sent and

More information

997 Functional Acknowledgment

997 Functional Acknowledgment 997 Functional Acknowledgment VANTAGE GROUP accepts functional acknowledgments for all EDI documents we send. We send functional acknowledgments to trading partners that send us EDI documents. For all

More information

SECTION. 0 General Message Guidelines. Version Workgroup Document version: 3. Version 5.

SECTION. 0 General Message Guidelines. Version Workgroup Document version: 3. Version 5. 1 2 3 SECTION 0 General Message Guidelines 4 Version 5.1 Edig@s 5 6 7 8 EASEE-gas/Edig@s Workgroup Document version: 3 Version 5.1 / 2015-09-02 0-1 9 COPYRIGHT & LIABILITY 10 11 12 13 14 15 16 17 18 19

More information

DSW Shoe Warehouse 832 Price/Sales Catalog Vendor Direct

DSW Shoe Warehouse 832 Price/Sales Catalog Vendor Direct DSW Shoe Warehouse 832 Price/Sales Catalog Vendor Direct X12/V4010/832: 832 Price/Sales Catalog Version: 1.0 Final Author: Publication: Trading Partner: All Notes: Brand Technology Services Table of Contents

More information

MOBILE APP DEVELOPMENT AGREEMENT

MOBILE APP DEVELOPMENT AGREEMENT MOBILE APP DEVELOPMENT AGREEMENT This is a binding agreement between PocketApp.in & the Client listed below. Client Details Company: Authorized Person: Address: Phone: Mob: E-mail address: Proposed Mobile

More information

850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Final Publication: 1/21/2009 Notes:

850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Final Publication: 1/21/2009 Notes: 850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Final Publication: 1/21/2009 Notes: Table of Contents 850 Purchase Order...1 ISA Interchange Control Header...3 GS Functional Group Header...5

More information

3. Individual s details supported by third party evidence that is less than five years old

3. Individual s details supported by third party evidence that is less than five years old Definition Copies sent free to a defined group of individuals. Principles 1. Single copy per issue, distributed to an individual 2. Individual falls within defined criteria (Terms of Control) 3. Individual

More information

Corporates Cash Management

Corporates Cash Management SWIFT Certified Applications Corporates Cash Management Technical validation Guide 2017 Version 1.1 February 2017 Legal notices Copyright SWIFT 2017. All rights reserved. You may copy this publication

More information

ISO20022 Messages types and flows in future RTGS services. 14 February 2017 Ad-hoc Workshop on messages for the Future RTGS Services

ISO20022 Messages types and flows in future RTGS services. 14 February 2017 Ad-hoc Workshop on messages for the Future RTGS Services ISO00 Messages types and flows in future RTGS s February 07 Ad-hoc Workshop on messages for the Future RTGS Services messages and message flow in TARGET (I) Background information for the RTGS s (today

More information

PUBLIC CONSULTATION ON EBA XBRL TAXONOMY V2.1 EBA/CP/2014/ March Consultation Paper

PUBLIC CONSULTATION ON EBA XBRL TAXONOMY V2.1 EBA/CP/2014/ March Consultation Paper EBA/CP/2014/03 21 March 2014 Consultation Paper On XBRL Taxonomy (v2.1) related to remittance of supervisory data under Regulation (EU) No 575/2013 Contents 1. Responding to this Consultation 3 2. Executive

More information

163 Rates and Eligibility. 1.0 Bound Printed Matter Rates and Fees

163 Rates and Eligibility. 1.0 Bound Printed Matter Rates and Fees 163163.1.4 163 Rates and Eligibility Overview 1.0 Bound Printed Matter Rates and Fees 2.0 Basic Eligibility Standards for Bound Printed Matter 3.0 Content Standards 4.0 Attachments and Enclosures 1.0 Bound

More information

ONIX for Books: Code Lists Issue 11

ONIX for Books: Code Lists Issue 11 ONIX for Books: Code Lists Issue 11 Final, 18 March 2010 General A number of minor corrections have been made to the wording of individual code descriptions to ensure that cross-references are valid for

More information

CVS/Caremark. Implementation Guide. 810 DSD Invoice. Version X

CVS/Caremark. Implementation Guide. 810 DSD Invoice. Version X CVS/Caremark Implementation Guide 810 DSD Invoice Version X12-4010 810 Mapping Specifications v4010 i Table of Contents 810 Invoice... 1 ISA Interchange Control Header... 2 GS Functional Group Header...

More information

860 Purchase Order Change Request - Buyer Initiated

860 Purchase Order Change Request - Buyer Initiated 860 Purchase Order Change Request - Buyer Initiated X12/V4010/860 :860 Purchase Order Change Request - Buyer Initiated Company: General Mills Modified: 1/11/2018 Notes: Table of Contents 860 Purchase Order

More information

GovX Purchase Order. X12/V5010/850: 850 Purchase Order

GovX Purchase Order. X12/V5010/850: 850 Purchase Order 850 Purchase Order X12/V5010/850: 850 Purchase Order Company: GovX.com 1 4/12/2013 Purchase Order - 850 10/16/2015 Added TD5 segment 1/7/2016 9/19/2018 Added new value UP in PO106 Added TD512 segment Table

More information

Policy for Certification of Private Label Products Within the Cradle to Cradle Certified Certification Scheme. Version 1.0.

Policy for Certification of Private Label Products Within the Cradle to Cradle Certified Certification Scheme. Version 1.0. Policy for Certification of Private Label Products Within the Cradle to Cradle Certified Certification Scheme Version 1.0 March 2015 Copyright, Cradle to Cradle Products Innovation Institute, 2015 Cradle

More information

Breakfasts Welcome to July s BIC Breakfast: Migrating to ONIX 3.0 An Update on Progress, Benefits & Challenges Kindly sponsored by

Breakfasts Welcome to July s BIC Breakfast: Migrating to ONIX 3.0 An Update on Progress, Benefits & Challenges Kindly sponsored by Breakfasts 2015 Welcome to July s BIC Breakfast: Migrating to ONIX 3.0 An Update on Progress, Benefits & Challenges Kindly sponsored by ONIX 2.1 to 3.0 Transition twilight update Graham Bell EDItEUR BIC

More information

Guideline Data Format. Version 2.0

Guideline Data Format. Version 2.0 Guideline Data Format Version 2.0 1 introduction...2 1.1 purpose...2 2 amount...3 3 binary objects...3 4 code types...4 5 time...4 6 dates...5 7 identifiers...5 8 indicators...6 9 measures and quantity...6

More information

867 Bill Back itradenetwork OMS

867 Bill Back itradenetwork OMS 867 Bill Back itradenetwork OMS X12/V4010/867: 867 Product Transfer and Resale Report Version: 1.3 Final Company: itradenetwork Publication: 12/23/2013 Trading Partner: Current: 4/3/2015 Table of Contents

More information

SDMX self-learning package No. 3 Student book. SDMX-ML Messages

SDMX self-learning package No. 3 Student book. SDMX-ML Messages No. 3 Student book SDMX-ML Messages Produced by Eurostat, Directorate B: Statistical Methodologies and Tools Unit B-5: Statistical Information Technologies Last update of content February 2010 Version

More information

850 Purchase Order

850 Purchase Order 850 Purchase Order - 4010 Version: 1.0 Author: Land O' Lakes Inc. V4010 1 850 Purchase Order Functional Group=PO This Draft Standard for Trial Use contains the format and establishes the data contents

More information

COLES DSD INVOIC Invoice message

COLES DSD INVOIC Invoice message COLES DSD INVOIC Invoice message EDIFACT/D01B/EANCOM 2002/INVOIC: INVOIC Invoice message Version: 1.5 Author: Coles 1 Ver 1.5 INVOIC Invoice message Message Status=13 A message claiming payment for goods

More information

SDMX self-learning package No. 5 Student book. Metadata Structure Definition

SDMX self-learning package No. 5 Student book. Metadata Structure Definition No. 5 Student book Metadata Structure Definition Produced by Eurostat, Directorate B: Statistical Methodologies and Tools Unit B-5: Statistical Information Technologies Last update of content December

More information

INSTRUCTION Concerning the Operating Procedures for the Croatian Large Value Payment System

INSTRUCTION Concerning the Operating Procedures for the Croatian Large Value Payment System Pursuant to Article 18, paragraph (1) of the Decision on the rules of operation of the Croatian Large Value System (Official Gazette 55/2011), the Governor of the Croatian National Bank hereby issues the

More information

Location Intelligence Infrastructure Asset Management. Confirm. Contractor Access Version v18.10b.am

Location Intelligence Infrastructure Asset Management. Confirm. Contractor Access Version v18.10b.am Location Intelligence Infrastructure Asset Management Confirm Contractor Access Version v18.10b.am Information in this document is subject to change without notice and does not represent a commitment on

More information

EDI 850 Version 4010 ANSI X12 Purchase Order Specifications

EDI 850 Version 4010 ANSI X12 Purchase Order Specifications EDI 850 Version 4010 ANSI X12 Purchase Order Specifications Coupa Software, Inc. 1855 S. Grant St. 5 th Floor San Mateo, CA 94402 www.coupa.com Contents Purchase Order Details 3 Introduction 3 File Format

More information

Manual OPplus AT Payment

Manual OPplus AT Payment Manual OPplus Prepared for Customers and Partners Project OPplus Prepared by Contents General Information... 3 Manual Structure... 3 Description of Icons... 3 OPplus Navigation Area... 4 OPplus License

More information

MER Data Reference Guide - Introduction

MER Data Reference Guide - Introduction Electronic Reporting MER Data Reference Guide - Introduction Version: 4 Issued: 7 October 2009 Document History Version Date Description 1.0 23/03/2007 Initial version 2 31/08/2007 Updated to include shared

More information

Health Care Eligibility Benefit Inquiry and Response (270/271)

Health Care Eligibility Benefit Inquiry and Response (270/271) X12 Standards for Electronic Data Interchange Technical Report Type 3 Health Care Eligibility Benefit Inquiry and Response (270/271) Change Log : 005010-007030 JULY 2018 Intellectual Property X12 holds

More information

850 Purchase Order - v4030

850 Purchase Order - v4030 850 Purchase Order - v4030 X12/V4030/850 Version: 1.0 Final Author: Inovis Publication: April 1, 2008 PepBoys850_4030_FINAL.ecs 1 Ver 1.0 Revision History Date Version Revision Approved By April 1, 2008

More information

Release Management Process and Implementation Guidelines

Release Management Process and Implementation Guidelines Release Management Process and Implementation Guidelines Adopted by the IAIABC EDI Council on March 9, 2017 and revised on November 9, 2017 Introduction This document is intended to ensure greater stability,

More information

BWI Group. Supplier EDI Specification. Remittance Advice Message REMADV. EDIFACT REMADV D.99.B BWI Version 1.0

BWI Group. Supplier EDI Specification. Remittance Advice Message REMADV. EDIFACT REMADV D.99.B BWI Version 1.0 BWI Group Supplier EDI Specification Remittance Advice Message REMADV EDIFACT REMADV D.99.B BWI Version 1.0 Implementation Guideline BWI Group REMADV Version 1.0 / 06/23/2010 II.M01-1 CHANGE CONTROL Document

More information

JR Simplot Corporate 810 Invoice

JR Simplot Corporate 810 Invoice JR Simplot Corporate 810 Invoice X12/V4010/810: 810 Invoice Version: 1.0 Company: JR Simplot Company Modified: 3/2/2018 Notes: edi@simplot.com Table of Contents 810 Invoice.......................................................................................................................................

More information

CORRECTING INVOICE CONFIRMATION. Message. Version 1.0 EANCOM 97/EDIFACT D.96A

CORRECTING INVOICE CONFIRMATION. Message. Version 1.0 EANCOM 97/EDIFACT D.96A CORRECTING INVOICE CONFIRMATION Message Version 1.0 EAN 97/EDIFACT D.96A agreed-upon by EDI Working Group of ECR Poland Club The document contains only those segments and data elements that were agreed

More information