
Fri 17 Nov 2006 - SINGLE AS 4590 AND SUPPLY CHAIN COMMUNITIES Please submit your comments by 17:00 Fri 24 Nov 2006 to Stephen GOULD
08:32 Fri 17 Nov 2006 REF:XCOAAEN1 TO: Nick CARR cc Members of Parliament Organiser Standards Australia OASIS XML AUSTRALIA AS 4590 Interest Parties SINGLE AS 4590 ADDRESS & SUPPLY CHAIN COMMUNITIES Nick - as the organiser of the OASIS XML Conferences for the last 4 years you will have the contacts that will understand the problems with two (2) electronic address formats in the Australian eCommerce XML Standard AS 4590. The Business Community needs to ensure there is a single address format in AS4590 hence the proposal for you as Mr OASIS Australia to invite contacts to assist Standards Australia to reconvene the IS/11 eCommerce Standards Committee A Federal & State Government committed to XML B Standards Australia & IS/11 Committee C Port Systems and eCommerce D Next Steps A FEDERAL GOVERNMENT COMMITTED TO XML The Federal Government is committed to XML - ref the Federal Research Contract with OIC members in 2001 It is part of the Australian Federal and State Government Policy with the Electronic Transaction Act Each State passed similarly legislation in 2000 - 2003 B STANDARDS AUSTRALIA AND RECONVENED IS/11 COMMITTEE Standards Australia has said that it wants to reconvene IS/11 as the Australian eCommerce Standards Committee and it needs Volunteers for that Committee. As I have pointed out in my email to Standards Australia it has to make sure that the rules are followed and vested interests do not "Stack" the Committee again Not only is this issue of a single address very important for Local Government but it critically important for the 38 Ports around Australia that have endured considerable problems with their eCommerce Applications for the last 10 years An example of the problems is the report submitted by Ben ANSON Sydney Ports Consultant to the Federal Government Expert Group on eCommerce Inquiry in Nov 2003 C PORT SYSTEMS AND ECOMMERCE The Victorian Department of Infrastructure has just published an EOI for an eCommerce Pilot system at the Port of Melbourne This Specification has a Supply Chain Community which is common to every port "1.2 Port of Melbourne Supply Chain Community The following participants comprise the Port of Melbourne supply chain community: a Shipping Lines/Agents b Freight Forwarders c Customs Brokers d Stevedores e Port of Melbourne Community [PoMC] f Transport Companies g Exporters h Importers" In 1987/88 I was involved with developing a demonstration with the RUBAC EII methodology for the same requirement for the NSW Maritime Service Board As I said in my presentation on 27 Oct there needs to be a Parallax View of eCommerce because it can never work while vested interests keep trying to "paper 21st century techniques over 19th Century procedures and enforce the employment of very expensive Value Added Network Suppliers [VANS]" ref John RAVEN Facilitation Adviser IAPH If there are 2 different address formats for AS 4590 the eCommerce problems for the Ports Communities will become very expensive to resolve for the Supply Chain Community and not assist the Australian Import/Export Strategy. Part of the OTMG Tender Information Management System [TIMS] provides a link to legislation that may be relevant to a tender/EOI The Federal Government Hazardous Goods Act is key legislation for this EOI NEXT STEPS This is why we need to resolve the AS 4590 problem of two address formats quickly Would you be prepared to circulate the attendees of the OASIS XML Conferences for the last 4 years to ask who would be prepared to participate in the IS/11 Committee ? I would be prepared to draft an email for you to distribute Regards Stephen GOULD Chair XML & eCommerce Special Interest Group [XZIG] OPEN INTERCHANGE CONSORTIUM 10:29 F 2006/11/17 Syd 2065 E: sggould@oic.org M: 0416-009-468 W: XML & eCommerce Seminars 2000-2006 On 15 Nov 06, at 9:19, Nick Carr wrote: > > Hi Stevan, > > I'm not actually the Convenor of OASIS Australia. I don't > even think that there is an OASIS Australia but you could > ask Ram Kumar. Unfortunately we aren't involved in any > address standardisation so we probably wouldn't participate > in this initiative. > > Nick
![]()