getParametri.ERROR: 008
Version not found in DS N of configuration file

1 - Overview 2 - Processes 3 - Documents 4 - Transactions 5 - Resources 6 - Decoding tables 7 - Dictionary 8 - Atlas Printable version

Introduction to the current version of eBIZ/TC Upstream (2011-1)

Version management in eBIZ/TC Upstream

The official versions of eBIZ/TC Upstream (named with the year and a number, ex. '2004-1') after the release are public and cannot modified; they are available on-line and can be used also after the release of the further versions.
A version is made of:

  • collaboration processes analisys (reference samples)
  • different templates for the different kind of messages, XML documents, (XML Schemas, used to validate the documents) and the related User guides.
  • a dictionary of terms and of their coding
  • optionally stylesheets (XSL) to show the message content and samples

The current official version (click here) should be always used as the reference.

The Draft version (click here) , differently, is a working version, accessible to the workgroup and to the focus group members (in the final phases also registered users can access them) and is under published for comments. It can be modified many times before the release of an official version.
Comments are welcome on all the versions (the last official and the draft ones): the comments must be addressed to the staff (click HERE).

These documents and software can be freely downloaded and used, they cannot be sold but you can embed them in your products and commercial solution (you must only inform that they are present and developed by the eBIZ initiative).

XML documents and software of draft version can be freely downloaded and used;
WARNING, before to embed them into products and commercial packages be aware that they could exist only temporarily and not being included in the next official version.

Moda-ML, 2011-1 version
Version 2011-1 version
Release date 18/11/2011
Presentation THIS VERSION is the 2011-1

The main modifications are:

  • The capability of managing booking and unlocking for an order
  • The capability of representing a project code in a Textile Order
  • The capability of specifying, in the fabric product code, the selvedge code top
  • The managing of fax and phone data within the person type
  • The strengthening of the note field, to make it computer processable

Technical details DETAILS

a) Preparation of the operating scenario for order booking and unlocking
In TEXOrder and ACS order, it can be specified if they have been intended for booking, using the attribute “Order Type” (TOtype). In the NT11 code table, there is a new code “P”, which stay for “Booking”.

b) Managing of order unlocking datate
A date type that can be used as unlocking date (that is the last date in which the booking is valid) has been added in the following messages: TEXOrder and ACSOrder.
In order to use the unlocking date, in the Complex Types Toheader and Txheader, the element validityEnd has been added with repetitiveness 0-1

c) Managing of the project code
In the messages TEXOrder and ACSOrder, a project code can be indicated.
At this aim the element project has been created. It is a Simple Type string, with max length of 25 characters. It is used for assigning pieces/accessories to a specific Client project
In order to use this code: in the complex types texComInfo and acsComInfo the element project has been added with repetitiveness 0-1
NOTE: Points b) an c) are valid for Orders, but also for Order Responses

d) Selvedge code managing
In the data group used to specify the fabric pr>oduct code (texCode) and accessory product code (texCode), it is possible to specify a selvedge code, using the attribute added
In the T44 code table, there is a new code “SE” = Selvedge code

e) Phone and Fax numbers managing
Attributes for fax number and phone number have been added to the person type.
This, in Moda-ML schemas, means that the person type now has three attributes:

  • person 0-1
  • @email [Optional]
  • @phone [Optional]
  • @fax [Optional]

f) “Qualified” Note element managing
Functionalities of the Note element have been strengthened, adding the capabilities of making it processable by computers, through the use of attributes “noteLabel” and “codeList”.
The first enable the qualification of the topic of the note through a proper code, the second enable the acces to the table which contains codes used by the previous.
Then:

  1. The attribute type “note qualifier” (string, Simple Type, maxLength = 35) has been created. Its instance is
  2. The element type “free text note”, whose instance s /, has be transformed in “general note” (Complex Type Simple Content) and the following attributed has been associated to it:
    • @ label (optional)
    • @ codelist (optional)
    • @ numberingOrg (optional)
    Its description become: free text or structured (computer processing) note. For note structuring use the attributes "noteLabel" and "codelist"
    In detail:
    • “noteLabel” is the qualificatore that specifies the topic of the note
    • “codeList” is the URL of the list of codes used in noteLabel