eMessaging
FAQ's
Below are some of the frequently asked questions in regards to eMessaging.
- Question 1. What is my EDI mailbox number, where can I find it?
- Question 2. Does it cost anything for a Global Location Number (GLN)?
- Question 3. What is a VAN?
- Question 4. What are the prerequisites for using XML?
- Question 5. How has the GS1 XML schemas been developed?
- Question 6. Have core components been used in the development of the document models?
- Question 7. What is the modelling methodology?
- Question 8. What tool/s has been used to create the models and schemas?
- Question 9. Where can I get further information?
Answers
Question 1. What is my EDI mailbox number, where can I find it?
GS1 Australia can issue Australian registered companies a Global Location Number (GLN)
. GLN's are commonly used as an EDI mailbox number with third party Value-Added Network providers (VAN).
A GLN is a thirteen digit non-significant reference number that can be used to identify; registered companies, specific departments within a company, or physical entities and also EDI mailbox numbers.
Where can I find it?
If you are not a member, then please contact the GS1 Australia administration to request one.
Question 2. Does it cost anything for a Global Location Number (GLN)?
No - GS1 Australia can issue a GLN to all legally registered Australian companies at no cost.
Question 3. What is a VAN?
A value-added network (VAN) is a third party network provider that is contracted by a company to facilitate electronic data interchange (EDI) or provide other network services.
Before the advent of the Internet, many companies used value-added networks to move data from their company to other companies. With the arrival of the Internet though many companies found it more cost-efficient to move their data over the web instead of paying fees to a VAN. However, modern third party network providers offer additional services such as EDI translation, message encryption, secure email, reporting, and other extra services for their customers.
Question 4. What are the prerequisites for using XML?
In its simplest configuration, you need a software tool to edit and validate the XML documents. The software tools can be either embedded into the application used to view the XML document or standalone.
Although XML documents can be edited with any word processor, using a dedicated tool significantly simplifies it and reduces the number of errors.
The validating tool verifies whether the XML document - the actual business message - conforms to the XML schema - the standardised structure and content definition of the message.
Question 5. How has the GS1 XML schemas have been developed?
GS1 XML
schemas have been developed following GS1's own methodology, known as the GS1 eBusiness methodology. The goal of the eBusiness methodology is to capture business requirements in a consistent manner. The eBusiness methodology draws from international standards, parts of ebXML, the UN/CEFACT Modelling Methodology (UMM) and the World Wide Web consortium (W3C).
eBusiness methodology broken down into four areas:
- GS1 Modelling Methodology - using UMM and UML (Unified Modelling Language) notation to document business needs.
- GS1 Core Components methodology - based on ebXML (Core Components Technical Specification).
- XML Design rules for GS1 - standard way to convert class diagrams to XML representation, GS1 have now built a new tool called Autogen for UML to XML conversion using Java, XML/XSD technologies.
- GS1 XML communications architecture - specifies how to build a standard business message for sending. Also recommending use of UN/CEFACT SBDH (Standard Document Business Header)
Question 6. Have core components been used in the development of the document models?
Yes - GS1 XML schemas have been built following GS1 CC (core components) methodology, based on ebXML specification. Core components, Business Information Entities (BIE’s) are stored in GS1's GDD (Global Data Dictionary). The GDD is dynamic, new data attributes can be requested, however are subject to business need and approval via GSMP.
Question 7. What is the modelling methodology?
Modelling methodology used is the GS1 Modelling Methodology, the methodology is compliant to the UN/CEFACT Modelling Methodology (UMM), using UML (Unified Modelling Language) notation.
Question 8. What tool/s has been used to create the models and schemas?
- Models - Rational Rose was used for modelling diagrams in documents.
- Schemas - XMLSPY 4.4 and higher for schema development, testing was also completed with other XML validators such as:
- - XML Schema Validator (XSV)
- - XML Schema Validator from University of Edinburgh/W3C
- - Xerces (exposes Java API)
Question 9. Where can I get further information?
Further information can be found at the following links:

