You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
17 lines
1.1 KiB
17 lines
1.1 KiB
org.dmia&094212&XML2&6.0.0&&&XML2&&&&N.Y.N.N.N.N.N
|
|
|
|
|
|
|
|
|
|
0.1.o.o.o.N.0&XML2.001&XML2.002&XML2.003&XML2.004&XML2.005&XML2.006&XML2.007
|
|
&?0=0?1=0::undefined.0:1:1:0&?0=0?1=0::undefined.0:1:1:0&?0=0?1=0::undefined.0:1:1:0&?0=0?1=0?2=0?3=0::undefined.0:1:1:0&?0=0?1=0::undefined.0:1:1:0&?0=0?1=0::undefined.0:1:1:0&?0=0?1=0?2=0?3=0::undefined.0:1:1:0
|
|
&?0?xxx::&?0?xxx::&&?0?xxx?xxx?xxx::&?0?xxx::&?0?xxx::&?xxx?xxx?xxx?3::I am currently using XML to transfer transactions from one software to another. I think standards in this area would be a great thing and I would gravitiate towards vendors who could use XML as long as their price for the underlying goods was still competitive. If there are additional costs to utilize XML, I would want them broken out so I could compare the cost of the process against my personell costs of rekeying data so I can evaluate if it reprersents enough of a savings for me to pay the XML costs. The technology is great, but if it doesnt represent cost savings (NET) for distributors, I dont think they will spend the money and time to learn and utilize the technology.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|