NAMM B2B XML v2012 Implementation Guide and SpecificationsNamespace declaration
Submitted by mdelmundo on Mon, 02/09/2009 - 10:41am.
A third party EDI provider pointed out that we may be missing the correct namespace declaration.
Below is what we have which he points out is generic to all namespace declarations.
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
He thinks we need to add something more specific like-
“b2b.namm.org/B2B/Schemas/Party_v2009-1.xsd"
What does everyone think?
Now, we all know that I am
Now, we all know that I am NOT the XML Xpert in the group, but here's my understanding of this...
Everytime I use a program to validate an XML document, I add the path to the schema where it is indicated in this particular namespace. Actually, I thought it should not have anything there, as it is the pointer to the local location (URL, path, folder, etc). Although, if it points to the .xsd on the website, I suppose it could work... haven't tried validating to a schema that doesn't "live" on my own PC.
That's all I got!
Paul
This is just a unique prefix
This is just a unique prefix for your elements and attributes, may be required if you are going to bring one xml doc into another xml/html doc. I don't think anyone is doing that or this would have come up already. We all basically take the document sent to us, validate it against the schema and then load into our database, xml file get archived. So we all use the default namespace or no namespace.
This isn't a path to the schema for validation, it is just the node prefix if multiple schemas are going to be used. Prevents node name and data type collisions.
NAMM:id comes from NAMM="http://namm.org/B2B/Schemas/PO/2009.1"
KORG:id comes from KORG=" http://korg.com/PO"
I can combine the NAMM PO with one of my docs and we can bith have a node called id of different types, meaning...again I don't think anyone is doing this.
Makes sense to add it in the next version, maybe keep in sync with the versioning:
NAMM="http://namm.org/B2B/Schemas/PO/2009.1"
Bill