Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NIEM schema

Status
Not open for further replies.

somsally

Technical User
Aug 1, 2001
8
IN
Hi,

Can someone help me in understanding the NIEM schemas. I have got the overall idea about the NIEM model (Also I *can* understand simple schemas :) ). What I specifically need to know is few of the schema design "patterns" throughout the NIEM model like

<ns2:DriverLicenseIdentification ns1:id="1" ns1:metadata="metadata" ns1:linkMetadata="linkMetadata">
<ns2:IdentificationID ns1:id="id0" ns1:metadata="metadata_ID1" ns1:linkMetadata="link_ID1">IdentificationID_0</ns2:IdentificationID>
<ns2:IdentificationCategoryDescriptionText ns1:id="id0" ns1:metadata="metadata_ID1" ns1:linkMetadata="link_ID1"/>
<ns2:IdentificationSourceText ns1:id="id0" ns1:metadata="metadata_ID1" ns1:linkMetadata="link_ID1" />
</ns3:DriverLicenseIdentification>

If you see DriverLicenseIdentification has child nodes like IdentificationID, IdentificationCategoryDescriptionText, IdentificationSourceText.

What I want to know is why such a pattern is used and what that pattern is called as?

NIEM documentation provided in the NIEM site seems to be too much detailed. any links with simple tutorial would be helpful

Thanks
 
I can only say from the general perspective.

[1] Q: >why such a pattern is used
A: It is because the document can only be sufficiently rendered justice to the inter-related ideas derived from multiple namespaces. In each namespace, the vocabulary is defined pertinent to it. In that particular case, DriverLicenseIdentification is defined in the namespace prefixed ns2. However, it contains an attribute id defined outside of its namespace (ns2). The id attribute is defined in the namespace corresponding to the prefix ns1, a bit like a foreign key in the dbase design. That id in the namespace would be defined as a global xs:attribute in the schema of targetNamespace pointing to what corresponds to the prefix ns1. That schema would be "imported" into the schema document of targetNamespace corresponding to what the prefix ns2 is pointing to. The rest is more or less the same kind of understanding...

[2] Q: >what that pattern is called as?
A: What do you mean by called as?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top