ONIX for Repertoire: message format overview

Size: px
Start display at page:

Download "ONIX for Repertoire: message format overview"

Transcription

1 ONIX for Repertoire: message format overview Version.0, February 2008 CONTENTS LIST Page. Introduction Repertoire Notification Definitions Repertoire Detail Resources Excluded Controlled values and the ONIX IFFRO Dictionary Resource description in ONIX-RP Repertoire Notification types Areas for possible further development Resource Lists ONIX-RP Header ONIX-RP Repertoire Notification RepertoireDetail DetailByResource DetailByResourceClass PriceDefinition ONIX-RP Resource List...8 Earlier versions of this overview were used as the basis for the application guidelines produced by each of the ONIX IFRRO pilots in Immediately before Version.0 was released, a number of final modifications and corrections were made to the format specification, and these may not all be reflected in the pilot documentstion. Please note that, where there is any discrepancy between the pilot guidelines and this overview, the overview should be taken as authoritative.

2 . Introduction This document is an overview of the ONIX for Repertoire (ONIX-RP) format. It should be read in conjunction with the companion document ONIX for Repertoire: message structure, which provides further technical details of the XML structure. The table below gives a top-level view of the revised format: <ONIXRepertoireMessage version=.0 > 2 <Header> A header identifying the sender and receiver, and giving other control information 3 <RepertoireNotification> A composite that notifies new or changed repertoire 4 <ResourceList> An ONIX-RP message consists of (i) a message header (<Header>) which identifies sender and receiver and carries a limited amount of other data pertinent to the message as a whole; (ii) an unlimited number of <RepertoireNotification> composites, which may be of the same or different types, and may relate to the same or different repertoires; and (iii) an unlimited number of <ResourceList> composites (see section 4 below). For the purposes of the ONIX IFRRO messages, a repertoire is defined as a set of resources in which the control of certain rights is held by a particular party, and which is identified typically for the purpose of delegating those rights from one party to another. [For repertoire management from UK publishers to PLS to CLA and onward to CCC (and possibly other agencies), it makes sense to treat the set of resources covered by a publisher s mandate (or more accurately, a Publishing Rights Controller s mandate) as a distinct repertoire with a unique identifier. This is not, however, in any way assumed in the message format. A repertoire may be any set of resources that it is convenient and practical to manage as such, and to which a unique identifier can be assigned by the agency responsible.] 2. Repertoire Notification The <RepertoireNotification> composite, shown in more detail on the next page, is organized into three main parts: (a) A non-repeating <Definitions> composite which, in the present ONIX-RP version, is used only to carry price definitions if required, although it may be required for other things in future extensions of the format; (b) A repeatable <RepertoireDetail> composite carrying statements about rights and resources that are part of the repertoire; and (c) A repeatable <ResourcesExcluded> composite carrying details of resources that are completely excluded from the repertoire (as distinct from being excluded from, say, a particular license in which other resources are included). 2. Definitions The <Definitions> composite carries any entity definitions that are required to support the rest of the content of a <RepertoireNotification> composite. In the present version of the ONIX-RP message, the only circumstance in which entity definitions will be invoked is when repertoire detail involves the specification of prices relating to a particular license or to a particular form of usage. In this case, each price will be defined in a <PriceDefinition> and assigned a label by which it can be referenced elsewhere in a <SubjectToPayment> element. If, however, the repertoire is sub-licensed on the basis of default price rates established by inter-agency agreement, no such definitions need to be carried. In this document we will sometimes refer to a Publishing Rights Controller, or PRC, when talking about a publisher in its role as a delegator of rights. 2

3 <RepertoireNotification> A composite that notifies new or changed repertoire 2 <RepertoireIdentifier> A unique identifier of a repertoire -n 3 <Definitions> A composite that defines entities referred to in a Repertoire Notification 4 <PriceDefinition> A composite that defines a price referred to in a Repertoire Notification 5 <UsageDefinition> A composite that defines a usage referred to in a Repertoire Notification (placeholder for future use) 6 <RepertoireDetail> A composite that specifies rights and resources that together form part of a repertoire 7 <DelegatedRightByLicense> A composite that specifies licenses under which defined resources may be sub-licensed by the delegate 8 <DelegatedRightByUsage> A composite that specifies a usage for which defined resources may be sub-licensed by the delegate 9 <WholeRepertoireExceptAs Specified/> An XML empty element whose presence indicates that the preceding delegated rights detail applies to the whole of the repertoire except as otherwise specified 0 <DetailByResource> A composite that specifies a resource that is part of a repertoire <DetailByResourceClass> A composite that specifies a resource class, together with any exclusions from that class 2 <ExcludingResources> A composite that specifies resources or resource classes that are excluded from a specified class 3 <ResourcesExcluded> A composite that specifies resources to be excluded completely from a repertoire 4 <DetailByResource> A composite that specifies a resource to be excluded completely from a repertoire 5 <DetailByResourceClass> A composite that specifies a resource class to be excluded completely from a repertoire, together with any exclusions from that class 6 <ExcludingResources> A composite that specifies resources or resource classes that are excluded from a specified class 0- -n A <UsageDefinition> is also included, but only as a placeholder, to be specified in detail as and when it becomes clear that there is a need to cover usages that cannot be defined simply by a Dictionary term. In future, particularly if there is a move to specify individual licensable usages instead of relying on standard licenses, it may be necessary to add more entity definitions. The <Definitions> composite precedes the <RepertoireDetail> elements that use the definitions. This sequence is expected to be helpful when a large Repertoire Notification is processed by a receiving system. 2.2 Repertoire Detail Within the <RepertoireDetail> composite, delegated rights can be specified by license or by usage (although the latter functionality remains much less developed than the former, since examples of its practical application are not readily available). Resources can be detailed by individual titles, or by resource classes (again, the latter functionality is less well-developed, for similar reasons); or delegated rights can be specified as applying to the whole repertoire. Exceptions to resource classes can be specified either as subclasses or as lists of individual titles. In this way, an instance of <RepertoireDetail> can fully specify any set of resources that shares a set of delegated rights, and that is part of a repertoire. 3

4 2.3 Resources Excluded The <ResourcesExcluded> composite has the sole function of specifying resources that are to be excluded completely from a repertoire. Excluded resources can be detailed by individual titles, or by resource classes; and exceptions to resource classes can be specified either as sub-classes or as lists of individual titles. The PLS-to-CLA use cases examined in Pilot 2 have found no application for <ResourcesExcluded>; however, this does not necessarily mean that these elements will not be needed elsewhere. 2.4 Controlled values and the ONIX IFFRO Dictionary Wherever the overview refers to ONIX controlled values, this means that the element in question either must or may carry a value taken from the OLT IFRRO Dictionary, which is being developed to provide a value set appropriate to IFRRO member applications as these are specified in detail. Alternatively the element may in certain circumstances carry a local controlled value: see the companion document ONIX IFRRO Dictionary Notes. 2.5 Resource description in ONIX-RP Resource description is limited to title, authorship, publisher and imprint, each represented by a composite that is structured to a similar level as in existing ONIX product information formats. Note that the detailed nomenclature is not the same as in, say, ONIX for Books, in order to maintain the internal consistency of the ONIX IFFRO formats, but there is a very simple mapping. 2.6 Repertoire Notification types As a result of the work carried out in Pilot 2, three major types of repertoire notification have so far been specified: New or Confirmed Mandate: used to notify a new mandate from a rights controller, or confirm in full an existing mandate. Include In Repertoire: used to add resources to a repertoire, usually as a result of their having been traded from one rights controller to another. ChangeTerms: used to communicate changes in delegated rights (license inclusions / exclusions) and prices. From the point of view of the format definition, it is always possible to add other types if found necessary. 2.7 Areas for possible further development Version 0.9 of the format was substantially based on the original Strawman document. As a result of piloting, it has now developed to the point where it is no longer considered useful to maintain a detailed mapping to the elements in the Strawman. However, it should be noted that four areas from the original document are still not fully developed: (a) Contact information for parties associated with the repertoire (see Strawman 6..3d and 6..4d). It is questionable whether a Repertoire Notification is the right place to communicate standing information about the parties involved in delegation of rights, or changes to such information. (b) Constraints on permitted usages ( ). It is difficult to define a suitable structure at this stage, since we have little or no evidence of what the requirements will be if and when ONIX-RP begins to be used for delegation of rights by usage rather than rights by license. (c) Reporting and Other conditions ( b and c). (d) Identifying rights controllers (6.4). The requirement for this needs to be more fully defined. All of these four aspects have been parked for the time being. 4

5 3. Resource Lists During the course of Pilot 2 it became apparent that there was a need under various different circumstances for one RRO to send to another a list of resources that it considered to be part of a rights controller s repertoire, without thereby implying any change either in the definition of the repertoire or in the applicable terms. To accommodate this, the ONIX-RP format has been extended to include, alongside the <Repertoire Notification> entity, a separate and very simple <Resource List> entity, using a limited set of elements taken from the full notification. The two entity types to be sent in a single message, so that, for example, a New Mandate notification may be accompanied by a <ResourceList> that communicates titles that the sender believes to be covered by the mandate, but that do not constitute a definition of the mandate repertoire. As the summary table below indicates, the format consists simply of a few identification and housekeeping elements, followed by an unlimited number of <DetailByResource> composites, each representing a single resource. <ResourceList> 2 <RepertoireIdentifier> A unique identifier of a repertoire -n 3 <DetailByResource> A composite that specifies a resource that is part of a repertoire 5

6 4. ONIX-RP Header <Header> Message header 2 <Sender> The sender of a message (coded identifier or name or both) 3 <SenderRole> A controlled value specifying the role of an ONIX-RP message sender if not the delegator of rights 4 <SenderIdentifier> Composite: a coded identifier of a message sender; repeatable only if a sender has two or more identifiers taken from different schemes 5 <SenderIDType> A code indicating a scheme from which a sender identifier is taken 6 <IDTypeName> The name of a proprietary scheme, if applicable 0-7 <IDValue> An identifier value, from a specified scheme 8 <SenderName> The name of a sender organization 0-9 <SenderContact> The name of a contact person in a sender organization <Sender > An address for a sender contact 0- <Addressee> An addressee of a message (coded identifier or name or both) -n 2 <AddresseeIdentifier> Composite: a coded identifier of a message addressee; repeatable only if an addressee has two or more identifiers taken from different schemes 3 <AddresseeIDType> A code indicating a scheme from which a sender identifier is taken 4 <IDTypeName> The name of a proprietary scheme, if applicable 0-5 <IDValue> An identifier value, from a specified scheme 6 <AddresseeName> The name of an addressee organization 0-7 <AddresseeContact> The name of a contact person in an addressee organization 0-8 <Addressee > An address for an addressee contact 0-9 <Test/> An XML empty element which, if present, specifies that a message is a test 0-20 <MessageNumber> Message sequence number 0-2 <MessageRepeat> A number which distinguishes any repeat transmissions of a message 0-22 <SentDateTime> The date, and optionally the time, when a message was sent 23 <MessageNote> A free-text note about the contents of the message 0-24 <CurrencyCode> An ISO code for the currency of monetary amounts (if any) specified in the message 0- Copyright EDItEUR & IFRRO 6

7 5. ONIX-RP Repertoire Notification <RepertoireNotification> A composite that notifies new or changed repertoire -n 2 <NotificationType> An ONIX controlled value specifying a type of a Repertoire Notification, eg new mandate, change terms 3 <ReasonForNotification> An ONIX controlled value specifying a reason for sending a Repertoire Notification 4 <NotificationID> A sender-assigned identifier that is unique within the sequence of Repertoire Notifications sent by the Sender to the Addressee (replaces composite in Version 0.9) 5 <NotificationEffectiveDate> The date on which the changes notified in the Repertoire Notification become effective, expressed as YYYYMMDD 0-6 <RepertoireIdentifier> A composite that uniquely identifies a repertoire; mandatory, and repeatable -n only if the repertoire has two or more identifiers taken from different schemes. 7 <RepertoireIDType> An ONIX controlled value identifying a scheme from which a repertoire identifier is taken 8 <IDTypeName> A name of a proprietary scheme, if applicable 0-9 <IDValue> An identifier value, from a specified scheme 0 <RepertoireDescription> A title or description given by the sender to the repertoire to which a Repertoire 0- Notification refers <RepertoireAnnotation> A composite that carries an annotation relating to the repertoire to which a Repertoire Notification refers 2 <RepertoireAnnotation An ONIX controlled value specifying a type of a repertoire annotation 0- Type> 3 <AnnotationText> The text of the annotation 4 <RepertoireRelatedAgent> A composite that specifies an Agent that is related to a repertoire, and its relationship to the repertoire, typically used to identify a rights controller who holds or manages rights in the repertoire 5 <RepertoireAgentRelator> An ONIX controlled value specifying a relationship between a repertoire and a related agent 6 <AgentIdentifier> A composite that carries an identifier of an agent; repeatable only if an agent has two or more identifiers taken from different schemes 7 <AgentIDType> An ONIX controlled value identifying a scheme from which an agent identifier is taken 8 <IDTypeName> A name of a proprietary scheme, if applicable 0-9 <IDValue> An identifier value, from a specified scheme 20 <Name> A name of an agent or agent class 0-0- Copyright EDItEUR & IFRRO 7

8 2 <AgentAnnotation> A composite that carries an annotation relating to an agent, typically used to carry an explanatory note about a rights controller 22 <AgentAnnotationType> An ONIX controlled value specifying the type of an agent annotation 0-23 <AnnotationText> The text of the annotation 24 <AgentRelatedName> A composite that specifies a name, typically of an imprint or subsidiary, that is related to an agent. Listing such 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 relationship between an agent and a related name 26 <NameIdentifier> A composite that carries an identifier of a related name; repeatable only if a name has two or more identifiers taken from different schemes 27 <NameIDType> An ONIX controlled value identifying a scheme from which a name identifier is taken 28 <IDTypeName> A name of a proprietary scheme, if applicable 0-29 <IDValue> An identifier value, from a specified scheme 30 <Name> A related name, typically of an imprint or subsidiary 0-3 <NameAnnotation> A composite that carries an annotation relating to a name, typically used to carry an explanatory note about an imprint 32 <NameAnnotation An ONIX controlled value specifying the type of a name annotation 0- Type> 33 <AnnotationText> The text of the annotation 34 <RepertoireRelated Mandate> A composite that specifies a mandate that is related to a repertoire, and its relationship to the repertoire 35 <RepertoireMandate Relator> 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 a scheme from which a mandate identifier is taken; repeatable only if a mandate has two or more identifiers taken from different schemes 38 <IDTypeName> A name of a proprietary scheme, if applicable 0-39 <IDValue> An identifier value, from a specified scheme 40 <Name> A name of a mandate 0-4 <MandateRelatedTime Point> A composite that specifies a date that is related to a mandate, and its relationship to the mandate 0-42 <MandateTimePoint Relator> An ONIX controlled value specifying a relationship between a mandate and a related time point Copyright EDItEUR & IFRRO 8

9 43 <TimePointIdentifier> A composite that carries an identifier of a time point 44 <TimePointIDType> An ONIX controlled value specifying a form of a time point identifier, eg YYYY 45 <IDValue> A time point identifier in a specified form 46 <RepertoireDefinition> An ONIX controlled value that specifies whether a repertoire is defined by the resources specified in successive <RepertoireDetail> elements, or otherwise (eg as all eligible resources controlled by a mandating rights controller) 47 <Definitions> A composite that defines entities referred to in a Repertoire Notification 0-48 <PriceDefinition> A composite that defines a price that is referred to in a Repertoire Notification see expansion in section <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 50 <RepertoireDetail> A composite that specifies rights and resources that together form part of a -n repertoire: repeat for each part of the notified repertoire that has different delegated rights and/or pricing see expansion below 5 <ResourcesExcluded> A composite that specifies resources and/or resource classes to be excluded 0- completely from a repertoire 52 <DetailByResource> A composite that specifies a resource expansion as in <RepertoireDetail> 53 <DetailByResourceClass> A composite that specifies a resource class, together with any exclusions from that class expansion as in <RepertoireDetail> 0- -n Copyright EDItEUR & IFRRO 9

10 5. RepertoireDetail <RepertoireDetail> A composite that specifies rights and resources that together form part of a repertoire 2 <DelegatedRightBy License> 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: either <includeunderlicense> or <Exclude FromLicense> must be present in any instance of <DelegatedRightByLicense> 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 0- resources must be excluded 8 <LicenseType> An ONIX controlled value that uniquely identifies either a single license (eg -n 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 0 <PlaceIDType> An ONIX controlled value specifying a scheme from which a place identifier is taken, eg ISO country codes <IDValue> An identifier value from a specified scheme, repeatable (eg) for multiple -n countries 2 <FromTimePoint> A composite that specifies a time from which a delegation of rights is effective 0-3 <TimePointIDType> An ONIX controlled value specifying a form of a time point identifier, eg YYYY 4 <IDValue> A time point identifier in the form specified in the <TimePointIDType> element 5 <ToTimePoint> A composite that specifies a time to which a delegation of rights is effective 0-6 <TimePointIDType> An ONIX controlled value specifying a form of a time point identifier, eg YYYY 7 <IDValue> A time point identifier in the form specified in the <TimePointIDType> element -n Copyright EDItEUR & IFRRO 0

11 8 <DelegatedRightBy Usage> A composite that specifies a usage for which all or part of a repertoire may be licensed by the delegate 9 <LicensableUsage> Either (a) an ONIX controlled value specifying a usage as a defined term, or (b) a label assigned in a Usage Definition to identify a usage 20 <WithinTerritory> A composite that specifies a territory for which rights are delegated 2 <PlaceIDType> An ONIX controlled value specifying a scheme from which a place identifier is taken, eg ISO country codes 22 <IDValue> An identifier value from a specified scheme, repeatable (eg) for multiple -n countries 23 <FromTimePoint> A composite that specifies a time from which a delegation of rights is effective 0-24 <TimePointIDType> An ONIX controlled value specifying a form of a time point identifier, eg YYYY 25 <IDValue> A time point identifier in a specified form 26 <ToTimePoint> A composite that specifies a time to which a delegation of rights is effective 0-27 <TimePointIDType> An ONIX controlled value specifying a form of a time point identifier, eg YYYY 28 <IDValue> A time point identifier in a specified form 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 usage quantity 3 <UsageQuantityDetail> A composite that carries details of a quantity -n 32 <Proximity> An ONIX controlled value specifying a relationship between a quantity and a 0- <Value> stated in the composite, eg is less than, is not more than ; the default is is exactly 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 0- not implied by the <UsageQuantityType> 36 <SubjectToPayment> Either (a) an ONIX controlled value specifying a price class, or (b) a label -n assigned in a Price Definition to identify a price set by a rights controller. Specifies payment(s) applying to a usage. 37 <WholeRepertoireExcept AsSpecified/> 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 ResourceClass> elements in the same instance of <RepertoireDetail>. 0- Copyright EDItEUR & IFRRO

12 5.2 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 <RepertoireDetail> 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 4 <CategoryTypeName> A name of a proprietary scheme, if applicable 0-42 <CategoryValue> An category value from a specified scheme 43 <ResourceIdentifier> A composite that carries a unique identifier of a resource; repeatable only if a resource has two or more identifiers taken from different schemes 44 <ResourceIDType> An ONIX controlled value specifying a scheme from which a resource identifier is taken 45 <IDTypeName> A name of a proprietary scheme, if applicable 0-46 <IDValue> An identifier value from a specified scheme 47 <ResourceTitle> A composite that carries a title of a resource 48 <TitleType> An ONIX controlled value specifying a type of a title 0-49 <TitleText> The text of a title 50 <Subtitle> A subtitle associated with a title 0-5 <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; repeatable only if a contributor has two or more identifiers taken from different schemes: each instance of the <Contributor> composite must carry either a <Contributor Identifier> or a name or both. 54 <ContributorIDType> An ONIX controlled value specifying a scheme from which a contributor identifier is taken 55 <IDTypeName> A name of a proprietary scheme, if applicable 0-56 <IDValue> An identifier value from a specified scheme Copyright EDItEUR & IFRRO 2

13 57 <PersonName> A composite that specifies a name of a person 58 <PersonNameForm> An ONIX controlled value identifying a form of a person name: the default is unspecified, but the inclusion of this element will make it possible in future to control the format of person names, if so required 59 <Name> A name of a person, in the form specified, if <PersonNameForm> is included 60 <OrganizationName> A composite that specifies a name of an organization 6 <OrganizationName An ONIX controlled value identifying a form of an organization name: the 0- Form> default is unspecified, but the inclusion of this element will make it possible in future to control the format of organization names, if so required 62 <Name> A name of a person, in the form specified, if <OrganizationNameForm> is included 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 in the publishing of a resource 65 <PublisherIdentifier> A composite that carries an identifier of a publisher; repeatable only if a publisher has two or more identifiers taken from different schemes: either a <PublisherIdentifier> or a <Name> (or both) must be present in any instance of the <Publisher> composite 66 <PublisherIDType> An ONIX controlled value specifying a scheme from which a publisher identifier is taken 67 <IDTypeName> A name of a proprietary scheme, if applicable 0-68 <IDValue> An identifier value from a specified scheme 69 <Name> A name of a publisher 0-70 <Imprint> A composite that identifies and/or names an imprint or brand in a structured 0- form 7 <ImprintIdentifier> A composite that carries an identifier of an imprint or brand; repeatable only if an imprint has two or more identifiers taken from different schemes: either an <ImprintIdentifier> or a <Name> (or both) must be present in any instance of the <Imprint> composite 72 <ImprintIDType> An ONIX controlled value specifying a scheme from which an imprint identifier is taken 73 <IDTypeName> A name of a proprietary scheme, if applicable 0-74 <IDValue> An identifier value from a specified scheme 75 <Name> A name of an imprint or brand 0-0- Copyright EDItEUR & IFRRO 3

14 76 <ResourceRelated Resource> 77 <ResourceResource Relator> 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 An ONIX controlled value specifying a relationship of a resource to a resource 78 <ResourceIdentifier> A composite that carries an identifier of a resource; repeatable only if a resource has two or more identifiers taken from different schemes 79 <ResourceIDType> An ONIX controlled value specifying a scheme from which a resource identifier, is taken 80 <IDTypeName> A name of a proprietary scheme, if applicable 0-8 <IDValue> An identifier value from a specified scheme 82 <ResourceRelatedTime Point> 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 <ResourceTimePoint An ONIX controlled value specifying a relationship of a time point to a resource Relator> 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 86 <IDValue> A time point identifier in a specified form -n Copyright EDItEUR & IFRRO 4

15 5.3 DetailByResourceClass 87 <DetailByResourceClass> A composite that specifies a resource class that is part of a repertoire, together with any exclusions from that class 88 <ResourceCategory> A composite that specifies a category to which a resource belongs, when a category is part of the definition of a resource class 89 <ResourceCategoryType> An ONIX controlled value specifying a scheme from which a resource category is taken 90 <CategoryTypeName> A name of a proprietary scheme, if applicable 0-9 <CategoryValue> An category value from a specified scheme 92 <ResourceRelatedAgent> A composite that specifies an agent or agent class that is related to a resource class, when a relationship to an agent or agent class is part of the definition of a resource class 93 <ResourceAgentRelator> An ONIX controlled value specifying a relationship between a resource class and a related agent or agent class 94 <AgentIdentifier> A composite that carries an identifier of an agent or agent class; repeatable only if an agent has two or more identifiers taken from different schemes 95 <AgentIDType> An ONIX controlled value identifying a scheme from which an agent identifier is taken 96 <IDTypeName> A name of a proprietary scheme, if applicable 0-97 <IDValue> An identifier value, from a specified scheme 98 <Name> A name of an agent or agent class 0-99 <ResourceRelatedTime Point> 00 <ResourceTimePoint Relator> A composite that specifies a time point that is related to a resource class, and its relationship to the resource class An ONIX controlled value specifying a relationship between a resource and a related time point 0 <TimePointIdentifier> A composite that carries an identifier of a time point 02 <TimePointIDType> An ONIX controlled value specifying a form of a time point identifier, eg YYYY 03 <IDValue> A time point identifier in a specified form 04 <ResourceRelatedPlace> A composite that specifies a place that is related to a resource class, and its relationship to the resource class; repeatable only if a place has two or more identifiers taken from different schemes 05 <ResourcePlaceRelator> An ONIX controlled value specifying a relationship between a resource and a related place Copyright EDItEUR & IFRRO 5

16 06 <PlaceIdentifier> A composite that carries an identifier of a place; repeatable only if a place has two or more identifiers taken from different schemes 07 <PlaceIDType> An ONIX controlled value identifying a scheme from which a place identifier is taken 08 <IDValue> An identifier value, from a specified scheme 09 <Name> A name of a place 0-0 <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. <ResourceNameRelator> An ONIX controlled value specifying a relationship between a resource and a related name 2 <NameIdentifier> A composite that carries an identifier of a name; repeatable only if a name has two or more identifiers taken from different schemes: either a <NameIdentifier> or a <Name> (or both) must be present in any instance of the <Resource RelatedName> composite 3 <NameIDType> An ONIX controlled value identifying a scheme from which a name identifier is taken 4 <IDTypeName> A name of a proprietary scheme, if applicable 0-5 <IDValue> An identifier value, from a specified scheme 6 <Name> 0-7 <ExcludingResources> A composite that specifies resources or resource classes to be excluded from 0- the class specified in an instance of <DetailByResourceClass> 8 <DetailByResource> A composite that specifies a resource: expansion as on previous pages 9 <DetailByResourceClass> A composite that specifies a resource class: expansion as on previous pages Copyright EDItEUR & IFRRO 6

17 5.4 PriceDefinition <PriceDefinition> A composite that defines a price that is referred to in a Repertoire Notification -n 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 a type of a price annotation 0-5 <AnnotationText> The text of an annotation 6 <PriceAmount> The amount of a price as a decimal number 7 <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 for which a charge is made, eg page, article 9 <PriceQuantity> A composite that specifies a quantity attribute of a price, eg an extent limit permitted for the stated price 0 <PriceQuantityType> An ONIX controlled value specifying a type of a price quantity <PriceQuantityDetail> A composite that carries details of a quantity -n 2 <Proximity> An ONIX controlled value specifying a relationship between a quantity and the 0- <Value> stated in the composite, eg is less than, is not more than ; the default is is exactly 3 <Value> A decimal numeric value 4 <MeasureUnit> An ONIX controlled value specifying a unit of measure 5 <ReferenceUnit> An ONIX controlled value specifying a unit to which a quantity refers, if this is 0- not implied by the <PriceQuantityType> 6 <VolumeDiscount> An ONIX controlled value specifying an applicable volume discount or discount 0- class that is standard in a particular context: <VolumeDiscount> and <VolumeDiscountDetail> are mutually exclusive in any instance of <PriceDefinition> 7 <VolumeDiscountDetail> A composite that specifies a volume discount set by an individual rights controller 8 <VolumeUnit> An ONIX controlled value specifying a unit of volume, eg copies 9 <MinimumVolume> The minimum volume required to qualify for a specified volume discount 20 <MaximumVolume> The maximum volume qualifying for a specified volume discount 0-2 <PercentageDiscount> A discount expressed as a percentage of the <PriceAmount>: either 0- <PercentageDiscount> or <DiscountedPriceAmount> must be present in any instance of <VolumeDiscountDetail> 22 <DiscountedPriceAmount> A discounted price expressed as an absolute amount per unit 0- Copyright EDItEUR & IFRRO 7 0-

18 6. ONIX-RP Resource List <ResourceList> A composite that lists resources that belong to a repertoire 2 <ReasonForNotification> An ONIX controlled value specifying a reason for sending a Resource List 3 <NotificationID> A sender-assigned identifier that is unique within the sequence of Resource Lists sent by the Sender to the Addressee 4 <RepertoireIdentifier> A composite that uniquely identifies a repertoire with which a Resource List is -n associated; mandatory, and repeatable only if the repertoire has two or more identifiers taken from different schemes. 5 <RepertoireIDType> An ONIX controlled value identifying the scheme from which the identifier in the <IDValue> element is taken 6 <IDTypeName> A name of a proprietary scheme, if applicable 0-7 <IDValue> An identifier of the type specified in the <RepertoireIDType> element 8 <DetailByResource> A composite that specifies a resource. Repeat for each title listed in the <ResourceList> composite. Expansion as in <RepertoireDetail> -n Copyright EDItEUR & IFRRO 8

ONIX for Repertoire: application guidelines

ONIX for Repertoire: application guidelines 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

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

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

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

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

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

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

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 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

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

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

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 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

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 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

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

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

JISC PALS2 PROJECT: ONIX FOR LICENSING TERMS PHASE 2 (OLT2)

JISC PALS2 PROJECT: ONIX FOR LICENSING TERMS PHASE 2 (OLT2) JISC PALS2 PROJECT: ONIX FOR LICENSING TERMS PHASE 2 (OLT2) Functional requirements and design specification for an ONIX-PL license expression drafting system 1. Introduction This document specifies a

More information

AMWA Specification. AMWA Specification Policy Application Specification UL Guidelines May 24, 2016 (rev 1.1) Executive Summary

AMWA Specification. AMWA Specification Policy Application Specification UL Guidelines May 24, 2016 (rev 1.1) Executive Summary AMWA Specification AMWA Specification Policy Application Specification UL Guidelines May 24, 2016 (rev 1.1) Executive Summary This document describes requirements and recommended practices for creating

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

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

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

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

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

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

EMV Contactless Specifications for Payment Systems

EMV Contactless Specifications for Payment Systems EMV Contactless Specifications for Payment Systems Book B Entry Point Specification Version 2.6 July 2016 pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is

More information

CANADIAN PAYMENTS ASSOCIATION ASSOCIATION CANADIENNE DES PAIEMENTS STANDARD 005 STANDARDS FOR THE EXCHANGE OF FINANCIAL DATA ON AFT FILES

CANADIAN PAYMENTS ASSOCIATION ASSOCIATION CANADIENNE DES PAIEMENTS STANDARD 005 STANDARDS FOR THE EXCHANGE OF FINANCIAL DATA ON AFT FILES CANADIAN PAYMENTS ASSOCIATION ASSOCIATION CANADIENNE DES PAIEMENTS STANDARD 005 STANDARDS FOR THE EXCHANGE OF FINANCIAL DATA ON AFT FILES 2017 CANADIAN PAYMENTS ASSOCIATION 2017 ASSOCIATION CANADIENNE

More information

JD Edwards World. User Defined Data for Distribution Guide Release A9.3 E

JD Edwards World. User Defined Data for Distribution Guide Release A9.3 E JD Edwards World User Defined Data for Distribution Guide Release A9.3 E21563-03 April 2013 JD Edwards World User Defined Data for Distribution Guide, Release A9.3 E21563-03 Copyright 2013, Oracle and/or

More information

Reliability Standard Audit Worksheet 1

Reliability Standard Audit Worksheet 1 Reliability Standard Audit Worksheet 1 PRC-004-3 Protection System Misoperation Identification and Correction This section to be completed by the Compliance Enforcement Authority. Audit ID: Registered

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

Reliability Standard Audit Worksheet 1

Reliability Standard Audit Worksheet 1 Reliability Standard Audit Worksheet 1 PRC-004-3 Protection System Misoperation Identification and Correction This section to be completed by the Compliance Enforcement Authority. Audit ID: Registered

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

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

ONIX-PL full view Go to top License documents

ONIX-PL full view Go to top License documents ONIX-PL full view The full view of an ONIX-PL expression which is generated by the OPLE editing software provides a single navigable HTML representation of the complete expression in a readable format.

More information

Terms and Conditions of Website Use

Terms and Conditions of Website Use Terms and Conditions of Website Use This website (the "Site") is owned and operated by Hoshizaki Lancer Pty Ltd (ABN 84 007 706 461) ("Hoshizaki Lancer") and may contain material from Hoshizaki Lancer

More information

Beta Testing Licence Agreement

Beta Testing Licence Agreement Beta Testing Licence Agreement This Beta Testing Licence Agreement is a legal agreement (hereinafter Agreement ) between BullGuard UK Limited ( BullGuard ) and you, either an individual or a single entity,

More information

FTP FILENAMING STANDARD Issue 4

FTP FILENAMING STANDARD Issue 4 Jointly with Book Industry Study Group (US) and Book Industry Communication (UK) FTP FILENAMING STANDARD Issue 4 BACKGROUND AND PRINCIPLES 1. The purpose of these filenaming conventions is to enable FTP

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

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

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

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

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

Inbound ANSI X Version 04010

Inbound ANSI X Version 04010 Inbound ANSI X12 850 Version 04010 For CLP License Ordering Version: ANSI X12 850 4010 Author: Adobe EDI Modified: 06/09/2010 CLP_X12_ANSI8504010_060910.ecs 1 For internal use only 850 Purchase Order Functional

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

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

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

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

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

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

850 Purchase Order. X12/V4010/850: 850 Purchase Order

850 Purchase Order. X12/V4010/850: 850 Purchase Order 850 Purchase Order X12/V4010/850: 850 Purchase Order Company: General Mills Modified: 1/11/2018 Notes: Production Orders for copack and warehousing partners. Table of Contents 850 Purchase Order............................................................................................................................

More information

820 Payment Order/Remittance Advice

820 Payment Order/Remittance Advice 820 Payment Order/Remittance Advice X12/V4010/820: 820 Payment Order/Remittance Advice Version: 1.0 Draft Author: Charles Mackey Company: C.H. Robinson Publication: 8/6/2009 Trading Partner: Created: 8/6/2009

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

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

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 B2B - ORDERS Purchase order message

COLES B2B - ORDERS Purchase order message COLES B2B - ORDERS Purchase order message EDIFACT/D01B/EANCOM 2002/ORDERS: ORDERS Purchase order message Version: 1.6 Author: Coles COLES_B2B_D01B_ORDERS_V1.6.ecs 1 Ver 1.6 ORDERS Purchase order message

More information

Additional License Authorizations for HPE OneView for Microsoft Azure Log Analytics

Additional License Authorizations for HPE OneView for Microsoft Azure Log Analytics Additional License Authorizations for HPE OneView for Microsoft Azure Log Analytics Product Use Authorizations This document provides Additional License Authorizations for HPE OneView for Microsoft Azure

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

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

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

Purchase Order Change Request - Buyer Initiated

Purchase Order Change Request - Buyer Initiated 860 Purchase Order Change Request - Buyer Initiated Functional Group= PC Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Change Request

More information

RIGHTMOVE PRODUCT GUIDELINES New Homes. Core Membership means the basic Services to which You are entitled in return for your Core Membership Fee.

RIGHTMOVE PRODUCT GUIDELINES New Homes. Core Membership means the basic Services to which You are entitled in return for your Core Membership Fee. RIGHTMOVE PRODUCT GUIDELINES New Homes DEFINITIONS Core Membership means the basic Services to which You are entitled in return for your Core Membership Fee. Additional Products means the additional Services

More information

Inbound X Version 04010

Inbound X Version 04010 Inbound X12 850 Version 04010 For Value Incentive Plan (VIP) License Ordering Version: ANSI ASC X12 850 4010 Author: Adobe EDI Company: Adobe Systems Inc Modified: 8/31/2015 850 Purchase Order Functional

More information

824 Application Advice

824 Application Advice 824 Application Advice X12/V4010/824: 824 Application Advice Version: 1.0 Final Author: IBM Publication: Trading Partner: P2P Modified: 08/17/2006 Notes: Table of Contents 824 Application Advice.................................................................................................

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

Functional Acknowledgment

Functional Acknowledgment 997 Functional Acknowledgment Functional Group=FA Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Functional Acknowledgment Transaction Set (997)

More information

Liquor - Direct to Store Purchase order message - ORDERS D01B

Liquor - Direct to Store Purchase order message - ORDERS D01B Liquor - Direct to Store Purchase order message - ORDERS D01B EDIFACT/D01B/EANCOM 2002/ORDERS: ORDERS Purchase order message Version: 1.0 Author: Coles Group CGL_LL_D01B_ORDERS_V1.0.ecs 1 Ver 1.0 ORDERS

More information

Abstract. Background. 6JSC/ALA/Discussion/5 31 July 2015 page 1 of 205

Abstract. Background. 6JSC/ALA/Discussion/5 31 July 2015 page 1 of 205 page 1 of 205 To: From: Joint Steering Committee for Development of RDA Kathy Glennan, ALA Representative Subject: Machine-Actionable Data Elements for Measurements, Extent of the Carrier, Pagination and

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

ISO/IEC INTERNATIONAL STANDARD. Information technology Metadata registries (MDR) Part 3: Registry metamodel and basic attributes

ISO/IEC INTERNATIONAL STANDARD. Information technology Metadata registries (MDR) Part 3: Registry metamodel and basic attributes INTERNATIONAL STANDARD ISO/IEC 11179-3 Second edition 2003-02-15 Information technology Metadata registries (MDR) Part 3: Registry metamodel and basic attributes Technologies de l'information Registres

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

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

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

GLEIF Global LEI Data Quality Report Dictionary

GLEIF Global LEI Data Quality Report Dictionary GLEIF Global LEI Data Quality Report Dictionary Global LEI Data Quality Report Dictionary 2 19 Contents Data Quality Report Glossary... 3 1. Chapter 1: Preface... 4 1.1. Purpose of the Data Quality Report...

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

ESIS. EDI Implementation Guide. Purchase Order Change X Version 4010 Release 8.0. EDI_Guide_Change_Order_X12_860_Version_4010_Release_8-0.

ESIS. EDI Implementation Guide. Purchase Order Change X Version 4010 Release 8.0. EDI_Guide_Change_Order_X12_860_Version_4010_Release_8-0. EDI Implementation Guide ESIS Purchase Order Change X12 860 Version 4010 Release 8.0 Page 1 of 37 EDI Implementation Support Information EDI Contact Name: ESIS, E-Commerce Provider of Raytheon EDI Contact

More information

Building Information Modeling and Digital Data Exhibit

Building Information Modeling and Digital Data Exhibit Document E203 2013 Building Information Modeling and Digital Data Exhibit This Exhibit dated the day of in the year is incorporated into the agreement (the Agreement ) between the Parties for the following

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

810 IBM Subset - Invoice To Customer - (004010)

810 IBM Subset - Invoice To Customer - (004010) 810 IBM Subset - Invoice To Customer - (004010) Functional Group ID=IN Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set

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

3. What is the name of the organisation that runs your business registry?

3. What is the name of the organisation that runs your business registry? Sida 1 av 20 International Business Registers Survey 2016 Questions in this survey should be answered for the period January 1 to December 31, 2016, unless otherwise specified. The survey is accompanied

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

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

* 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

Taxonomies and controlled vocabularies best practices for metadata

Taxonomies and controlled vocabularies best practices for metadata Original Article Taxonomies and controlled vocabularies best practices for metadata Heather Hedden is the taxonomy manager at First Wind Energy LLC. Previously, she was a taxonomy consultant with Earley

More information

Adobe - EDIFACT SLSRPT D93.A

Adobe - EDIFACT SLSRPT D93.A Adobe - EDIFACT SLSRPT D93.A Sales Data Report Message Version: RSLSRPTD93Av1 Final Modified: 11/24/2004 Notes: 10/26/2004 - In an effort to validate that 100% of a partners reporting locations has been

More information

CALIFORNIA INDEPENDENT SYSTEM OPERATOR CORPORATION FERC ELECTRIC TARIFF ORIGINAL VOLUME NO. III Original Sheet No. 977 METERING PROTOCOL

CALIFORNIA INDEPENDENT SYSTEM OPERATOR CORPORATION FERC ELECTRIC TARIFF ORIGINAL VOLUME NO. III Original Sheet No. 977 METERING PROTOCOL ORIGINAL VOLUME NO. III Original Sheet No. 977 METERING PROTOCOL ORIGINAL VOLUME NO. III Original Sheet No. 978 METERING PROTOCOL Table of Contents MP 1 OBJECTIVES, DEFINITIONS AND SCOPE MP 1.1 Objective

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

JR Simplot Food Group Purchase Order Acknowledgment

JR Simplot Food Group Purchase Order Acknowledgment JR Simplot Food Group - 855 Purchase Order Acknowledgment UCS/V4010/855: 855 Purchase Order Acknowledgment Version: 1.0 Company: JR Simplot Company Publication: 6/1/2016 Notes: edi@simplot.com Table of

More information

COLES B2B INVOIC Invoice message

COLES B2B INVOIC Invoice message COLES B2B INVOIC Invoice message EDIFACT/D01B/EANCOM 2002/INVOIC: INVOIC Invoice message Version: 1.4 Author: Coles COLES_B2B_D01B_INVOIC_V1.4.ecs 1 Ver 1.4 INVOIC Invoice message Message Status=13 A message

More information

A national valuation database as a risk assessment tool

A national valuation database as a risk assessment tool A national valuation database as a risk assessment tool Let s talk Your guidelines Guidelines on the development and use of a national valuation database as a risk assessment tool Publisher World Customs

More information

Zappos EDI Guideline. X12/V4010/860: 860 Purchase Order Change Request - Buyer Initiated. Version: 1.0

Zappos EDI Guideline. X12/V4010/860: 860 Purchase Order Change Request - Buyer Initiated. Version: 1.0 Zappos EDI Guideline X12/V4010/860: 860 Purchase Order Change Request - Buyer Initiated Version: 1.0 Author: Zappos Created: 07/06/2011 Last updated: 01/15/2014 Electronic Data Interchange 860 Purchase

More information

IBM Managed Security Services for Security

IBM Managed Security Services for  Security Service Description 1. Scope of Services IBM Managed Security Services for E-mail Security IBM Managed Security Services for E-mail Security (called MSS for E-mail Security ) may include: a. E-mail Antivirus

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

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

Secure Messaging Mobile App Privacy Policy. Privacy Policy Highlights

Secure Messaging Mobile App Privacy Policy. Privacy Policy Highlights Secure Messaging Mobile App Privacy Policy Privacy Policy Highlights For ease of review, Everbridge provides these Privacy Policy highlights, which cover certain aspects of our Privacy Policy. Please review

More information

Wheeling Charge Exemptions Due to ETCs

Wheeling Charge Exemptions Due to ETCs Objective Wheeling Charge Exemptions Due to ETCs Process to notify the ISO of wheeling charge exemptions due to existing transmission contracts. Overview Wheeling charges are assessed to energy exported

More information

JR Simplot Food Group Grocery Products Purchase Order. UCS/V4010/875: 875 Grocery Products Purchase Order Version: 1.0

JR Simplot Food Group Grocery Products Purchase Order. UCS/V4010/875: 875 Grocery Products Purchase Order Version: 1.0 JR Simplot Food Group - 875 Grocery Products Purchase Order UCS/V4010/875: 875 Grocery Products Purchase Order Version: 1.0 Company: JR Simplot Company Modified: 9/4/2018 Table of Contents 875 Grocery

More information

SIX Trade Repository AG

SIX Trade Repository AG SIX Trade Repository AG March 2018 Table of contents 1.0 Purpose 4 2.0 Structure of the 4 3.0 Application requirements 4 3.1 Reporting obligation 4 3.2 Connection to the trade repository system 5 3.3 Technical

More information

816 Organizational Relationships

816 Organizational Relationships 816 Organizational Relationships X12/V4010/816: 816 Organizational Relationships Version: 1.0 Final Company: Oshkosh Corporation Publication: 3/1/2013 Modified: 2/24/2013 2/24/2013 Oshkosh Corporation

More information

AGREEMENT FOR RECEIPT AND USE OF MARKET DATA: ADDITIONAL PROVISIONS

AGREEMENT FOR RECEIPT AND USE OF MARKET DATA: ADDITIONAL PROVISIONS EXHIBIT C AGREEMENT FOR RECEIPT AND USE OF MARKET DATA: ADDITIONAL PROVISIONS 21. NYSE DATA PRODUCTS (a) SCOPE This Exhibit C applies insofar as Customer receives, uses and redistributes NYSE Data Products

More information