position paper: title-of-paper - oasis-open.org · web viewif a “qualifier term” of an...

Draft Paper: Name Length and Truncation Rules

Draft 01, 10 April 2002

Document identifier:

draft-stuhec-nameTrun-01.doc

Location:

Author:Gunther Stuhec <[email protected]>

Abstract:

This draft paper describes the recommended length of tag names.

Status:

This is V01 of the name length draft paper intended for consideration by the OASIS UBL Naming and Design Rules subcommittee and other interested parties.

If you are on the [email protected] list for subcommittee members, send comments there. If you are not on that list, subscribe to the [email protected] list and send comments there. To subscribe, send an email message to [email protected] with the word "subscribe" as the body of the message.

Copyright © 2002 The Organization for the Advancement of Structured Information Standards [OASIS]

mailto:[email protected]






Table of Contents

1 Introduction............................................................................................................................ 3

2 Reusability.............................................................................................................................. 4

3 Maximum Name Length.........................................................................................................6

3.1 Interfaces and Software Limitations...............................................................................6

3.2 Performance and Processing........................................................................................7

3.3 Human Readability........................................................................................................7

3.3.1 Long Readable Tag Names.......................................................................................7

3.3.2 Coded Tag Names....................................................................................................8

3.4 Recommendation...........................................................................................................8

4 Truncation of Tag Names.....................................................................................................10

4.1 Abbreviations...............................................................................................................12

Appendix A. Recommended List of Abbreviations........................................................................15

Appendix B. Recommended List of Acronyms..............................................................................24

Appendix C. Examples..................................................................................................................25

Appendix D. Notes........................................................................................................................31

2

1 IntroductionXML is the first choice for representing standardized business documents. But it is not a particularly efficient format for processing information by interfaces and applications. It is a text-based, human-readable, and metadata-encoded markup language that operates on the principle that the metadata that describes a message's meaning and context accompanies the content of the message. This might be a advantage for the humans but a disadvantage for the software. The bottleneck for the software will be the markups (tag names) of each document instance. All markups must be processed by text-based functions or parsers. And this slows down the processing speed for many times. But we will not do the definition of business documents without that human readable markups, because it increases the flexibility. It help us the common definition of this business documents and supports the efficient development of interfaces, because a readability must be ensured for the development itself.

One of the bottleneck of parsing will be long tag names. XML's processing overhead, storage requirements, and bandwidth consumption become quite problematic when transaction volumes are high and the tag names are very long. Therefore we’ve to look that we will get as short tag names as possible.

3

2 ReusabilityOne of the moste efforts of the naming of element- and attribute-names will be the consistency and reusability. That means, that always the same names of elements and attributes should be used without any mapping in the following areas:

XML schemas

XML document instances

UML class diagrams

data base tables of xml-based, relational and oo-based databases

user interfaces

application interfaces

print outs

This consistency enables an exchange of XML-instances between this areas without any mapping (see following picture).

4

...<AccountsContact>

<ID>000000101</ID><Name>Schemato Integrato</Name><Phone>+49 (3232) 343-45433</Phone><Fax>+49 (3232) 349-45433</Fax><E-Mail>

[email protected]</E-Mail>

</AccountsContact>...

Class-DiagramApplication Interface

E-MailFaxPhoneNameID

Table:AccountsContact

Database

User-Interface

E-Mail

Fax

Phone

Name

ID

AccountsContact

AccountsContact

-ID : cct:IdentifierType-Name : cct:NameType-Phone : cct:TextType-Fax : cct:TextType-E-Mail : cct:TextType

OrderResponse

XML Schema

...<AccountsContact>

<ID>000000101</ID><Name>Schemato Integrato</Name><Phone>+49 (3232) 343-45433</Phone><Fax>+49 (3232) 349-45433</Fax><E-Mail>

[email protected]</E-Mail>

</AccountsContact>...

Class-DiagramApplication Interface





Database

User-Interface

E-Mail

Fax

Phone

Name

ID

AccountsContact

E-Mail

Fax

Phone

Name

ID

AccountsContact

AccountsContact


OrderResponse

AccountsContact


OrderResponse

XML Schema

This means that all tag-names of elements and attributes must be transferable between all these interfaces. One of the key issues of that is the length of the name itself.

5

3 Maximum Name LengthThe maximum length of element and attribute names is very crucial. On the one hand side we would like to define human readable tag names. This means, the best for us is that we’re doing a 1:1 using of the dictionary entry names. But some of this dictionary entry names will be very long. Therefore we have to think about:

Many of the applications (databases, interfaces, erp-systems, user-interfaces) can not handle directly with tag names, which are longer as 30-40 characters. A mapping (additional processing step) into shorter tag names is necessary.

Many business documents in the real life have over 10.000 positions. Long tag names would decrease the speed of using, processing and transferring, tremendously.

Very long tag names usually are not human readable any more. A mapping into much more understandable tag names is necessary.

3.1 Interfaces and Software LimitationsAs mentioned, the maximum length of element or attribute names should be dependent on the interface and/or software limitations. Therefore, it is necessary, to check the different limitations of interfaces and software which will using all the business information structures directly. This could be databases, user interfaces, ERP-systems, business applications, development & engineering systems, design tools, programming languages, etc. Some examples:

Sybase database interface: 32 characters (a little be less)

Microsoft access database: 150 characters

XML Spy user interface: 50 characters

SAP application interface: 100 characters

Oracle …

Informix ….

Microsoft SQL …

6

3.2 Performance and ProcessingA reason for deciding a correct maximum specified length of characters is the performance of processing, transfer and interpretation of XML instances. We could have many disadvantages with the following ones:

SellersHandlingUnitDespatchLineDespatchedQuantity (49 Bytes)

ManufacturersHandlingUnitDespatchLineOrderLineID (48 Bytes)

ManufacturersTransportEquipmentRefrigerationStatusIndicator (59 Bytes)

It would be not an adavantage for the transfer of messages, because the’re existing some very good XML-compression procedures. All the elements and attributes can be represented by few bits in average (sometimes less than one bit). This procedures usually achieves about twice the compression ratio of gzip at roughly the same speed.

The disadvantage itself will be the processing by interfaces and applications. Very long tag names makes the handling of complete business documents much more difficult and the speed of processing will be slow down tremendously. If the XML becomes somewhat large (>1Mb), in some application interfaces (SAX and DOM), it slows down exponentially as the size of the XML increases. The principal share on this situation will have the length of tag names.

3.3 Human ReadabilityThe biggest advantage of XML for humans is the human readable markup. And the biggest disadvantage of XML for software is the human readable markup.

3.3.1 Long Readable Tag NamesThe max. length of the markups can be infinite. This means that we can create so long tag names as we like. But does very long tag names supports us in developing of business documents or application interfaces?

We should look to the following ones:SellersHandlingUnitDespatchLineDespatchedQuantity (49 Bytes)

ManufacturersHandlingUnitDespatchLineOrderLineID (48 Bytes)

7

ManufacturersTransportEquipmentRefrigerationStatusIndicator (59 Bytes)

Using element names like these, all the programming interfaces will come into troubles, certainly. It althoug creates an environment where style sheets and searching scripts become very large because there is no way to handle elements in a generic sense. That means this kind of human readable tag names are not efficiencly handable by humans any more, too.

Furthermore, it forces the programmer to create a specific instance for every single element type. Such long element names are also hard to remember and are easily mistyped. Other approaches also stymie the ability to quickly modify documents to a language other than English.

3.3.2 Coded Tag NamesA straightforward alternative to using long element names with these mentioned disadvantages is to simply avoid long element names. We can define short codes for XML elements as simply "<a>" or "<b>". While such short tags are definitely an improvement over tags like"< ManufacturersTransportEquipmentRefrigerationStatusIndicator>". But the resulting of this XML is for all practical purposes no longer human readable and it is quite hard to define a flexible code structure for all business semantics and requirements. Better, we can say, this is impossible.

3.4 RecommendationTherefore, we can say:

The maximum name length should be as short as possible - The maximum length of element or attribute name should enables that the name itself is meaningful and readable.

The maximum name length should be as long as possible - The maximum length of element or attribute names should be dependent on the interface and/or software limitations of database management systems, programming application interfaces, development environments.

The smallest on of the examples above is the limit specified by Sybase. The smallest number of characters for the max. length should be not smaller as 32 characters. Otherwise we can get sometimes problems with the meaningful definition of element names (Better: we will get some problems by the automatic extraction of tag names from the dictionary entry names).

8

But the maximum number of characters for max. length should not exceed 40 characters. Otherwise, we will get very unclear tag names and this tag names are not very efficient for the direct implementation by using different interfaces.

Last but not least, we should look that we can get the shortest human readable tag name as possible. For this, some truncation rules for this tag names should be necessary.

9

4 Truncation of Tag NamesSometimes could be the characters longer as the specified maximum length of 40 characters. Therefore, we need naming conventions, which includes some truncation rules to get a short, meaningful and unique tag names.

Following rules are decided until now:

XML names constructed from dictionary entry names must not include periods, spaces, or other separators.

Names must not use acronyms, abbreviations, or other word truncations, with the following list of exceptions:

A Dun & Bradstreet number must appear as “DUNS”.

“Identifier” must appear as “ID”.

“Uniform Resource Identifier” must appear as “URI” (example: the “Uniform Resource. Identifier” portion of the Binary Object. Uniform Resource. Identifier supplementary component becomes “URI” in the resulting XML name). This rule takes precedence over the rule that dictates a substitution of “ID” for “Identifier”.

Names must not contain non-letter characters unless required by language-specific rules.

Names must be in singular form unless the concept itself is plural (example: Goods).

The name of a complex type based on an object class must be the name of the object class, with the separators removed and with the “Details” suffix replaced with “Type”.Example: The Party. Details object class becomes the PartyType complex type.

An element name in a global element declaration based on an object class must be the name of the object class, with the separators removed and with “Details” removed.Example: The Party. Details object class becomes a global Party element.

For every complex type definition based on an object class, its content model must be defined such that it reflects each property of the object class as an element declaration,

10

with its cardinality and positioning within the content model determined by the details of the syntax-neutral model.Example: an optional Party. Address. Address property appearing as the first content of a Party. Details object class becomes the first element declaration inside the PartyType complex type, with a minOccurs value of “0”.

An element name in an element declaration based on a property must be the full dictionary name of the property in the syntax-neutral model, with the separators and object class term removed, and with the property term removed if it is identical or similar to the representation term.

Further rules are recommended:

No special characters (e.g.; hyphen, slashed, etc.) are in the tag name allowed, unless they are a part of an approved acronym.

We should use a lot of more standardized abreviations and acronyms for word truncations. Because this helps us to truncate the tag names very efficiently.

Abbreviations that are needed will be done in right to left fashion, utilizing the standard abbreviations found in the common list of abbreviations. When abbreviations are necessary, the abbreviation standard shall be applied.

Acronyms should always be used, whenever this acronym is commonly known. An acronym is a multi-word abbreviation that usually already exists in industry. All common usable acronyms should be listed in a standardized list.

Prepositions (e.g.: at, bay, for, from, in, of, to) can be truncated except in cases whrere they are required for clarity.

Articles (e.g.: a, an, the) can be truncated.

Conjunctions (e.g.: and, or, but, etc,) can be truncated.

If a BCC (Basic Core Component) defined in a ACC (Aggregated Core Component) with the same “Object Class Term” and same “Object Class Qualifier”, that this “Object Class Term” can be truncated from the BCC – Only usable at venetian blind approach.

If a BBIE (Basic Business Information Entity) defined in a ABIE (Aggregated Business Information Entity) with the same “Object Class Term” and same “Object Class Qualifier”,

11

that this “Object Class Term” can be truncated from the BBIE – Only usable at venetian blind approach.

Redundant information should be always truncated:

If in the ABIE or ACC existing for separating a same term as in its BBIEs or BCCs occurs, too than this term of the ABIE or ACC can be truncated – Only usable at venetian blind approach.

Example: ACC is a “Date Period. Details” and has a two BCCs called “Date Period. Start Date. Date” and “Date Period. End Date. Date”, than the “Date” of “Date Period. Details” can be truncated into “DatePeriod”

If a “Qualifier Term” of an “Object Class Term” or a “Property Term” is a semantically clear understandable and independent information and it is similar to its “Object Class Term” or “Property Term”, than the “Object Class Term” or the “Property Term” can be truncated.

Example: “Invoice_ Document. Details” could be “Invoice” because an “Invoice” is understandable as a document.

If a “Property Term” could have an semantically clear understandable and independent information for representation of a value, than the representation can be truncated.

Example: “Document. Version. Identifier” could be “DocumentVersion” or “DocumentVer” (with an abbreviation).

4.1 AbbreviationsAn abbreviation is a short way of writing a word or a phrase that could a lso be written out in full. Using abbreviations and acronyms is a way to shorten and simplify the name of a data object. Abbreviations must be clearly distinguished from contractions. The key difference is that an abbreviation does not normally have a distinctive pronunciation of its own. An abbreviation is a shortened form of a single word that is developed using a set of guidelines and approved for reuse when needed.

For this purposes the ISO 832:1994 applies the following definitions:

affix: One or more letters attached to the beginning or end of a word or root, or inserted within a word or root and serving to produce a derivative word or an inflectional form.

12

compound word: Word whose component parts are themselves words or combined forms. [Adapted from ISO 4:1984]

contraction: Shortening of a word, syllable, or word group by omission of internal letters. [ISO 4:1984]

derivative: Word formed from another word or root by the addition of affixes other than the inflectional endings.

inflected form: Form undergone by words to mark such distinctions as those of case, gender, number, tense, person, mood or voice.

root: Simple element inferred as the basis from which a word is derived by phonetic change or by extension, as composition or the addition of an affix.

truncation: Shortening of a word by the omission of two or more continuous letters at the end. [ISO 4:1984]

Guidelines:

An abbreviation used in a data object name must make sense to end users.

Select only abbreviations from the approved abbreviation list. See Appendix A

If no suitable abbreviation is found in the list, a new abbreviation may be developed and submitted to UBL or the standardization organization

Do not abbreviate any words that are four or less characters in length. Usually only words that exceed seven characters in length are considered candidates for abbreviations.

An abbreviation is associated with only one unabbreviated word or forms of that word. For example, “Max” is the abbreviation for “Maximum”, and “Maximal”.

Try not to create abbreviations that are themselves English words. For example, do not use “Class” as an abbreviation for “Classification”.

Do not use abbreviations that will conflict with abbreviations used commonly outside the organization. For example, TX (the abbreviation for Texas) used as an abbreviation for “Taxable”.

It is best to have an abbreviation begin with the same letter as the word being abbreviated. For example, use “Excpt” not “Xcpt” for “Exception”.

13

When all the words that make up a tag name have existing approved abbreviations, it is best, whenever possible, to abbreviate all the words rather than mix fully spelled out words and abbreviations in the same name. For example, “MaxID” is a better name than “MaximumID”.

14

Appendix A. Recommended List of Abbreviations Term Long Name Further Names CCT / RT

Abs Absolute

Abs Absolute

Act Action

Addr Address

Admin Administrative Administrator, Administration

Allow Allowance

Amt Amount Amount

Assoc Association

Atm Atmosphere

Cal Calendar

Calc Calculated

Cand Candidate

Cd Code Code

Chg Change

Cnt Count

Co Company

Col Column

Conc Concentration Concentrated

15

Term Long Name Further Names CCT / RT

Cond Condition

Corp Corporation

Corr Correction

Cust Customer

Dec Decimal

Decr Decrease

Deg Degree

Del Delete

Dept Department

Desc Description

Dia Diameter

Diff Different

Dir Directory

Dist Distance

Distr Distribution

Div Division

Doc Document

Dt Date Date

Dup Duplicate Duplicated, Duplication

Dur Duration Duration

16


Ed Edition Editional

Eff Effective

Elem Elementary Element

Emp Employee

Ent Entity

Equip Equipment

Est Estimated

Eval Evaluation

Excp Exception

Exec Execution Executive

Exp Expiration Expiratory

Ext External

Extn Extension Extended, Extinguisher,

Fam Family

Fax Facsimile

Fed Federal

Fig Figure

Fin Finacial

Fld Fluid

Freq Frequency

17


Frt Freight

Frz Frozen

Func Function Functional

Gen General

Gov Governmet

Grp Group

Hist History

ID Identifier Identification Identifier

Idx Index

Ill Illustration Illustrator

Inc Incorporated

Incl Included Including

Incr Increase

Ind Indicator Indicator

Info Information

Inh Inhouse

Insp Inspiratory Inspire

Inst Institution

Int Integer Integer

Intro Introduction

Jr Junior

18


Lab Laboratory

Lang Language

Lect Lecturer

Len Length

Lev Level

Lib Library

Lmt Limit

Loc Location

Ltd Limited

Maint Maintenance

Manu Manuscript

Mat Material

Math Mathematics

Max Maximum Maximal

Mea Measure Measure

Med Medical

Mgmt Management

Mid Middle

Mil Military

Min Minimum Minimal

Misc Miscellaneous

19


Mod Model

Msg Message

Mtg Meeting

Mult Multiple

Natl National

Neg Negative

No Number

Obj Object Objective

Occ Occasional

Org Organization Organizational, Organisation

Orig Original

Pct Percent Percent

Perf Performance

Pers Person Personnel

Pg Page

Pgm Program

Pkg Package

Pos Position

Pr Pair

Pri Primary

20


Prod Production

Prog Program

Proj Projection Project

Prov Provision

Prt Printer

Pt Point

Pub Publishing Published

Qty Quantity Quantity

Rec Record

Recv Received

Ref Reference

Reg Registered Registration

Rej Rejected

Rep Representative

Req Request

Res Resident Residency, Residence

Restr Restriction Restrict

Rev Revision Revised

Rpt Report

Rsn Reason

21


Rtn Return

Sal Salary

Sc Score

Sec Secondary

Sect Section

Sep Separated Separation

Seq Sequence

Ser Serie Series

Sev Several

Shpmt Shipment

Sig Signature

Sm Small

Sp Speed

Spec Specification

Sq Square

Src Source

Stat Statistics

Std Standard

Str Street

Subj Subject

Sz Size

22


Tbl Table

Tech Technology Technical

Tel Telephone Phone

Temp Temperature

Trans Transport

Tot Total

Txt Text Text

Usr User

Util Utility

Val Value

Var Variable

Veh Vehicle

Ver Version

Vol Volume

Yr Year Year

Zip Zip Code Postal Zone

This are some examples only. It could be added with further sensible and standardized abbreviations.

23

Appendix B. Recommended List of AcronymsElement Long Name Further Names

URI Uniform Resource Identifier

LDAP Lightwight Directory Access Protocol

UUID Universal Unique Identifier Scheme

FTP File Transfer Protocol

DUNS Duns & Bradstreet Number

ISBN International Standard Book Number

ISSN International Standard Serial Number

24

Appendix C. ExamplesThe following table shows some examples of short tag names in both aproaches: the venetian blind approach and the garden of eden approach.

Venetian Blind Garden of Eden (short) Garden of Eden (long) BIE Dictionary Entry Name

AccountsContact AccountsContact AccountsContact Accounts_ Contact. Details

ID ContactID AccountsContactID Accounts_ Contact. Identification

Name Name AccountsContactName Accounts_ Contact. Name

Tel Tel AccountsContactTel Accounts_ Contact. Phone. Text

Fax Fax AccountsContactFax Accounts_ Contact. Fax. Text

EMail EMail AccountsContactEMail Accounts_ Contact. E-mail. Text

ActualPkg ActualPkg ActualPkg Actual_ Package. Details

ID PkgID ActualPkg ID Actual_ Package. Identification

Qty Qty ActualPkg Qty Actual_ Package. Quantity

ReturnableMatInd ReturnableMatInd ActualPkg ReturnableMatInd Actual_ Package. Returnable_ Material. Indicator

25

Contained ContainedPkg ActualPkgContainedPkg Actual_ Package. Contained_ Package

ActualShpmt ActualShpmt ActualShpmt Actual_ Shipment. Details

ID ShpmtID ActualShpmtID Actual_ Shipment. Identification

ServiceLevCd ServiceLevCd ActualShpmtServiceLevCd Actual_ Shipment. ServiceLevel. Code

HandlingInstructions HandlingInstructions ActualShpmtHandlingInstructions Actual_ Shipment. Handling_ Instructions. Text

HandlingTypeCd HandlingTypeCd ActualShpmtHandlingTypeCd Actual_ Shipment. Handling_ Type. Code

HandlingCd HandlingCd ActualShpmtHandlingCd Actual_ Shipment. Handling_ Code

Info Info ActualShpmtInfo Actual_ Shipment. Information. Text

GrossWeightMea GrossWeightMea ActualShpmtGrossWeightMea Actual_ Shipment. Gross_ Weight. Measure

NetWeightMea NetWeightMea ActualShpmtNetWeightMea Actual_ Shipment. Net_ Weight. Measure

NetNetWeightMea NetNetWeightMea ActualShpmtNetNetWeightMea Actual_ Shipment. Net Net_ Weight. Measure

GrossVolMea GrossVolMea ActualShpmtGrossVolMea Actual_ Shipment. Gross_ Volume. Measure

NetVolMea NetVolMea ActualShpmtNetVolMea Actual_ Shipment. Net_ Volume. Measure

DeliveryRequirement ShpmtDeliveryRequirement ActualShpmtShpmtDeliveryRequirement Actual_ Shipment. Delivery Requirement

TransportContract ShpmtTransportContract ActualShpmtShpmtTransportContract Actual_ Shipment. Transport_ Contract

Stage ShpmtStage ActualShpmtShpmtStage Actual_ Shipment. Shipment Stage

TransEquip TransEquip ActualShpmtTransEquip Actual_ Shipment.

26

Transport EquipmentAddr Addr Addr Address. Details

ID AddrID AddrID Address. Identification

Postbox Postbox AddrPostbox Address. Postbox. Text

Building Building AddrBuilding Address. Building. Text

Floor Floor AddrFloor Address. Floor. Text

Room Room AddrRoom Address. Room. Text

Str Str AddrStr Address. Street. TextAddStr AddStr AddrAddStr Address. Additional_

Street. Text

House HouseName AddrHouseName Address. House_ Name

HouseNo HouseNo AddrHouseNo Address. House_ Number. Text

InhMail InhMail AddrInhMail Address. Inhouse Mail. Text

Dept Dept AddrDept Address. Department. Text

City CityName AddrCityName Address. City_ Name

Zip Zip AddrZip Address. Postal Zone. Text

CountrySubEntity CountrySubEntity AddrCountrySubEntity Address. Country Sub-entity. Text

CountrySubEntityCd CountrySubEntityCd CountrySubEntityCd Address. Country

27

Sub-entity Code. Code

Region Region AddrRegion Address. Region. Text

District District AddrDistrict Address. District. Text

TimezoneOffsetMea TimezoneOffsetMea AddrTimezoneOffsetMea Address. Timezone Offset Measure. Text

Country Country AddrCountry Address. Country

AllowanceCharge AllowanceCharge AllowanceCharge Allowance Charge. Details

ID AllowanceChargeID AllowanceChargeID Allowance Charge. Identification

Ind AllowanceChargeInd AllowanceChargeInd Allowance Charge. Charge Indicator. Indicator

MultiplierReasonCd MultiplierReasonCd AllowanceChargeMultiplierReasonCd Allowance Charge. Multiplier_ Reason. Code

MultiplierFactorQty MultiplierFactorQty AllowanceChargeMultiplierFactorQty Allowance Charge. Multiplier_ Factor. Quantity

CurrencyCd CurrencyCd AllowanceChargeCurrencyCd Allowance Charge. Currency_ Code

PrePaidCollectInd PrePaidCollectInd AllowanceChargePrePaidCollectInd Allowance Charge. Pre-paid Collect_ Indicator

28

SeqVal SeqValNo AllowanceChargeSeqValNo Allowance Charge. Sequence Value. Numeric

Tax Tax AllowanceChargeTax Allowance Charge. Tax

PaymentMeans PaymentMeans AllowanceChargePaymentMeans Allowance Charge. Payment Means

AlternativeOrderLine AlternativeOrderLine AllowanceChargeAlternativeOrderLine Alternative_ Order Line. Details

BuyersID OrderLineuyersID AllowanceChargeBuyersID Alternative_ Order Line. Buyer's_ Identification

ExtensionAmount LineExtensionAmount AllowanceChargeLineExtensionAmount Alternative_ Order Line. Line Extension_ Amount

Qty Qty OrderLinety Alternative_ Order Line. Quantity

MinQty MinQty OrderLineinQty Alternative_ Order Line. Minimum_ Quantity

MaxQty MaxQty OrderLineMaxQty Alternative_ Order Line. Maximum_ Quantity

MaxBackOrderQty MaxBackOrderQty OrderLineMaxBackOrderQty Alternative_ Order Line. Maximum_ Backorder Quantity. Quantity

MInBackOrderQty MInBackOrderQty OrderLineMInBackOrderQty Alternative_ Order Line. Minimum_ Backorder Quantity.

29

QuantitySubstitutionStatusCd SubstitutionStatusCd OrderLineSubstitutionStatusCd Alternative_ Order

Line. Substitution_ Status. Code

Item OrderLineItem OrderLineOrderLineItem Alternative_ Order Line. Item

DeliveryRequirement DeliveryRequirement OrderLineDeliveryRequirement Alternative_ Order Line. Delivery Requirement

AllowanceCharge AllowanceCharge OrderLineAllowanceCharge Alternative_ Order Line. Allowance Charge

BasePrice BasePrice OrderLineBasePrice Alternative_ Order Line. Base Price

BasePrice BasePrice BasePrice Base Price. Details

Amt PriceAmt BasePricePriceAmt Base Price. Price_ Amount

Qty BaseQty BasePriceBaseQty Base Price. Base_ Quantity

MaxQty MaxQty BasePriceMaxQty Base Price. Maximum_ Quantity

MinQty MinQty BasePriceMinQty Base Price. Minimum_ Quantity

MaxAmt MaxAmt BasePriceMaxAmt Base Price. Maximum_ Amount

MinAmt MinAmt BasePriceMinAmt Base Price. Minimum_ Amount

30

Appendix D. NotesOASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS's procedures with respect to rights in OASIS specifications can be found at the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification, can be obtained from the OASIS Executive Director.

OASIS invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to implement this specification. Please address the information to the OASIS Executive Director.

Copyright © The Organization for the Advancement of Structured Information Standards [OASIS] 2001. All Rights Reserved.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself does not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document must be followed, or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an “AS IS” basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

31

position paper: title-of-paper - oasis-open.org · web viewif a “qualifier term” of an...

Documents