On Aug 27, 2010, at 12:38 AM, Patrice Krakow wrote:

> - Thanks for the ISO/TS 20625:2002, I was not (really) aware about it, but I 
> always have the same issue with ISO documents, 158.00 CHF = 121.20 EUR = 
> 153.83 USD for a 55 pages PDF, that's quite expensive :-/ Anyway, I fully 
> agree with your philosophy: << My philosophy is not to reinvent things >> 
> when talking about specifications, regarding implementations, it's clear that 
> I like to re-invent ;-)

I understand and agree that the cost of ISO documents is rather high. I have 
the advantage, because of my participation within the standardization work, to 
get these documents for free.

> * You did not keep the idea of having two different namespaces, one for the 
> envelope and one for the message. I am thinking about this in order to 
> associate them later with different schemas, one schema for the envelope and 
> one schema for message, but now I am realizing that I may have a problem with 
> the fact that you put the UNH within the message... What do you think?

I am not a firm supporter of namespaces as their use is overrated, and in what 
I am using it for I know what schema I am looking for, the ones I created. I 
use the same approach as with EDI, the UNB tells me what syntax version, and 
therefore the definitions of the service envelops, and the UNH the directory 
version the message is defined in.

However, if you need to use it, go ahead and do so.

As to the UNH being within the message, that is because the standard defines it 
that way, remember the segment name is "Message Header".

> * I would put the version within the message tag name, or maybe within its 
> namespace:
> 
> - <M_ORDERS.D.97A>
> - <M_ORDERS xmlns=".../D/97A/">
> 
> Now, I am wondering if the ISO/TS 20625:2002 would not help me to answer my 
> questions... Could you help me?

TS 20625 does not say much about namespace usage for the UNH, the only place 
are within two examples within that document which may help you:

<M_ORDERS xmlns:din="http://www.din.de/examples/orders"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://www.din.de/examples/orders order1.xsd">

<M_ORDERS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:noNamespaceSchemaLocation="order1.xsd">

Klaus



------------------------------------

...
Please use the following Message Identifiers as your subject prefix: <SALES>, 
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work: <JOBS> IS 
REQUIRED in the subject line as a prefix.Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/EDI-L/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/EDI-L/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Reply via email to