Overview of Rules

Provided next is an overview of all the rules formulated in this specification:

Rules concerning usage of data types:

• Units

• Discrete units

• Other units according to TRADE/CEFACT/2001/20

• EAN code

• ILN

• ItemIdentification

• BasePriceType

• ItemType

• Usage of units

Rules for servers:

• Default URL

• URL binding

• XML-POST binding

• Transaction life cycle

• Operation: GetStatus

• Operation: Rollback

• Operation: CreateOrder

• Serialization: OrderRequestLine

• OrderRequestLine

• RequestReplacement

• ItemReplacement

• ReplacementCode

• Availability

• AvailabilityCode

• Operation: UpdateOrder

• Operation: FinishOrder

• Operation: ViewOrder

• Operation: GetItemDetails

• Operation: GetItemDetailsList

• Transaction: OrderInOnlineShop

• Transaction: TextSearch

• Operation: CreateTextSearch

• Operation: SearchResult

• Operation: GetClassificationScheme

• Rule: ItemInformation

• Test operation

• Downward compatibility

• Upward compatibility

Rules for clients:

• Error messages

• Default URL

• URL binding

• XML-POST binding

• HTTP protocol

• Serialization: OrderRequestLine

• OrderRequestLine

• OrderResponse

• UpdateOrderRequest

• Serialization: GetItemDetailsRequest

• Serialization: GetItemDetailsListRequest
  
  

3.3.4. Operations and transactions

The following operations must be implemented by a Veloconnect-compliant server:

• GetProfile, in the URL or URL-S binding

• CreateOrder

• UpdateOrder

• FinishOrder

• ViewOrder

• GetItemDetails

• GetItemDetailsList

• CreateTextSearch

• SearchResult

The CreateOrder, UpdateOrder, FinishOrder, and ViewOrder operations are used in the Order and OrderInOnlineShop transactions. At least one of these two transactions must be implemented. The TextSearch transaction must also be implemented.