ubl — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
RE: [ubl] Information items in 2-prd2-cd minimal instances
Hello UBL TC,
according to my past experience I agree it is difficult to find the right
minimum subset for evry document/information.
However I know the same problems have been experienced and solved with
UN/EDIFact where the base standard was not immediately sufficient for all
use cases.
This way some user groups was born around UN/CEFACT to address such kind
of problems.
Their main task was the creation of guidelines for
UN/EDIFact messages real use on specific areas (transportation, shipping,
...)
Major companies from shipping and transportation make use of these
guidelines and they are members of these bodies.
-------------------------------------------------------------------------
About IMO the mandatory minimum data is:
IMO
HAZARD CODE
Hazard code identification:
- IMDG Class Number
- IMDG Sub-Class Number
- RID Class Number
- CFR49 Codes
...but there are more info about at
http://www.smdg.org/itigg/index.jsp
under
Documents->Downloads->...
Transport Freight Movements - version 2.0
-------------------------------------------------------------------------
There are many user group for different areas, the once I know for
transportation and shipping are grouped under SMDG:
*************************************************************************
The International Transport Implementation Guidelines Group
http://www.smdg.org/itigg/index.jsp
ITIGG is an international group of experts engaged in the development and
implementation of
UN/EDIFACT standard messages for electronic trading in the transport
industry.
ITIGG is a sub-group of TBG3, the UN/EDIFACT Message Development Group for
Transport.
ITIGG develops recommendations which provide software developers with a
series of simple, straightforward tools to assist in designing
applications which can be used for trading electronically throughout the
world, and to clarify the intentions of the designers of key UN/EDIFACT
messages.
In the longer term the group aims to harmonise messages used in the
transport sector, so that the same message specifications can be used
anywhere in the world.
*************************************************************************
http://www.smdg.org/BEST/
BEST (Business Group for Electronic Commerce Standards in Transport) was
established in 1994 by a group of companies and organisations in the
transport sector primarily to support the work of the European EDIFACT
Transport Group EEG2.
BEST is involved in the Electronic Commerce standards, including:
- EDI (Electronic Data Interchange).
- Internet communication especially ebXML.
- Automatic identifications techniques for transported goods: barcoding,
such as the Multi Industry Transport Label (MITL), Radiofrequency tags?
etc.
- Mobile datacommunication.
*************************************************************************
User Group for Shipping Lines and Container Terminal
(SMDG - Shiplanning Message Development Group)
http://www.smdg.org/
SMDG is a non-profit foundation, run by and on behalf of companies and
organizations working in the maritime industry, like container terminals,
ocean carriers and related companies and organizations.
SMDG develops and promotes UN/EDIFACT EDI-messages for the Maritime
Industry and is an official Pan European User Group, recognised by the
UN/EDIFACT Board.
------------------------------------------------------------------------
------------------------------------------------------------------------
I hope into these sites you can find some more info to have a good minimum
data subset, however both the shipping and transportation sectors are not
so precise and advanced as we could imagine, they are really different
from banking or others fields.
For some countries like US there is a "Container Security" project which
is embracing also Ports security, into this direction there could be some
more mandatory data for a set of documents where exchanged to/from the US.
By now as we are talking about shipping maybe is not an actual requirement.
Hope my info are useful in some way, moroever I think some of or all of
these user group should have a contact with us in the future even if they
have already a contact with UN/CEFACT.
Best regards
UBL ITLSC
co-chair
Roberto Cisternino
Sylvia Webb wrote:
---------------------------------------------------------------------------
Ken,
Based on my experience, I have serious reservations that there can be a
universal minimum subset defined by the UBL TC. Such a subset can run afoul
of local, regional, and international laws which specify minimum data
requirements for specific transactions. Additionally, purchasing or contract
law can dictate what a minimum subset should be between trading partners.
As an example, if I establish a business relationship with a EU company or
government agency, I have different minimum data requirements that may be
specified in their subsets or guidelines plus additional requirements
specified by U.S. and California laws. If I am shipping hazardous goods, I
have yet another minimum subset of data required. Finally, depending on what
is specified in any purchase order or contract that I receive, I can have
multiple minimum subset requirements based on the legally binding
requirements of those documents. These minimum data requirements do not
include additional data that I may wish to include to satisfy any best
practices which my company wishes to follow.
IMO, there isn't any way that a standards body can have access to all of the
subject matter experts needed to consider all of the business rules and laws
which would be needed to determine an internationally acceptable minimum
subset.
Regards,
Sylvia
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]