From: Martin E. <mar...@ru...> - 2008-08-08 12:30:51
|
Hi! The schema now contains the most important primary and foreign key constraints. That means, id attributes must be unique within their schema hierarchy level and ..._ref attributes must point to correct and existing elements (identified by their id attribute). If not, schema-validation results in an error message like (XMLSpy): 'The value "bla" matched by the <keyref> identity constraint "bla2" was not matched by the referenced key "bla3" within the scope of element <AnalysisXML>.' I tried to make "bla2" following a simple nomenclature, e.g. FK_DATAADSILSIR_SD Meaning: SpectraData_ref (SD) attribute of element DataCollection(DATA)/AnalysisData(AD)/SpectrumIdentificationList(SIL)/SpectrumIdentificationResult(SIR) must point to a SpectraData element. XMLSpy jumps to the wrong reference, so human parsing of the FK_guru_meditation is normally not necessary... Bye Martin |