-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 the transport format is standard but you can translate it, which is the way it normally is done, usually at the other site.
so say have a ftl template that converts it to their format then sends it, if they are not able to do the conversion. madppiper sent the following on 3/23/2009 12:08 PM: > Ah, > > so in an overly-simplified manner: we'll simply exchange xml files as > defined in the dtds directory using the oagis-services, correct? And any > exchange will then be listed on the UI, right? > > Well, if that's it, than you are perfectly right: it is exactly what I was > looking for :) > > A follow-up though: can I edit the dtds in a way that is more fitting to our > logistics partner, or is the whole idea of OAGIS a standardized concept that > has been agreed upon from the OAGIS Group? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJx+O9rP3NbaWWqE4RArr4AKCWx08/7VmyPo0t4T9/2QODJthHZACggUO+ KGv9XsV/lqxOFnZ64KTrwic= =Ir+n -----END PGP SIGNATURE-----
