Ana səhifə

Technical Blueprint version 10


Yüklə 0.54 Mb.
səhifə3/8
tarix24.06.2016
ölçüsü0.54 Mb.
1   2   3   4   5   6   7   8

2.1Fixed data


Fixed data are reference data that will, in principle, be captured in the supply chain partners’ business applications only once; such reference data need not be repeatedly included in the information exchange about floricultural business transactions. In the technical data model, these fixed data are represented as blue rectangles.
The administration of fixed reference data is taken care of by VBN, who will secure the correctness, completeness and mutual consistency of the data. The distribution of these fixed data is centrally tended to as well. Hereby, Linnaeus provides floricultural supply chain partners with the opportunity to keep their internal reference data continuously updated and mutually synchronised.

2.2Variable data


Variable data are attributes of floricultural products which may vary with the lot to which they belong. This data will need to be captured in the database each time a product is featured in a lot and has to be explicitly included in the information exchange about lots at every turn.
In the technical data model, these variable data are represented as yellow rectangles.

2.3Data model notation


The model presented below will largely follow the classical entity-relationship notation, presenting entity types as rectangles and relationships as possibly forked line sections:




1-to-1-or-more relationship between two entity types

n-to-0-or-1 relationship between a blue entity type, representing fixed product data, and a yellow entity type, embodying variable lot data
1-to-n relationship between a blue (fixed) entity type and a blue/yellow one, representing fixed data in a product context and variable data in the context of a lot transaction. A dotted line with a red triangle is used for improved readability of relationships with names.
the green entity type has been included for migration purposes


2.4Technical data model



The entity types and relationships, belonging to the fixed reference data will be defined and explained in the next section.


Chapter 5 will clarify how the variable transaction data about floricultural lots will be mapped to the FlorEcom EDI messages.


3.Linnaeus code lists


This chapter will describe the code lists used to electronically distribute the fixed Linnaeus reference data.

3.1Common code list aspects


All code lists exhibit the following generic characteristics.

3.1.1Field names


It is assumed that the lists will also be applied by foreign business partners (growers, traders). The Linnaeus code list will therefore become available in various languages. The names of code lists and fields follow the ISO/IEC 11179 convention.

3.1.2Update fields


Each item in any code list contains the following fields:


  • entry date: the date at which a new item will or has become valid within the industry; this may be a future date

  • expiry date: the last effective date on which an item is still generally useful within the sector. This can indicate a future date or be left blank. An item is still considered “generally useful within the sector” on the expiration date itself.

  • change date/time: the date and time at which an item was last updated (entered, changed or expired).

For further explanation about the use of these fields in detecting updates, please refer to § 4.1 of this document.



3.1.3Code list description


For each code list, the following information will be given:


  • definition of the involved entity type

  • description of the relationships with other entity types (except those with NAME)

  • example of a filled-out code list item (which may differ from reality since VBN may still need to define some codes)

  • explanation or remark (if any).

For each code list field the following will be specified:




  • field number: field sequence number

  • field name: name of the field

  • occurrence type: M = mandatory (field needs to be filled) or

C = conditional (filled under certain conditions)

  • format: N = numeric, AN = alpha/numeric, number of digits fixed: n, or variable ..n

  • key fields: P#: primary key, F#: foreign key, PF#: both primary and foreign key.


1   2   3   4   5   6   7   8


Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©atelim.com 2016
rəhbərliyinə müraciət