KMLM List

[Robert Walsh <rwalsh@xxxxxxxxxxxxxxxx>]

Thank you Silade.  The extra information is helpful.  I believe this is an 
instance where the Ext element was not properly added to each location in the 
schema where it should have been.  I will log this as a change request for 
review at the September meeting of the NCIP Implementers Group.

Rob Walsh
EnvisionWare, Inc.
NCIP Maintenance Agency

On Jul 1, 2010, at 9:26 PM, 刘小丰 wrote:

> Hello
> Look at the xml.There is another Ext element below the EnumerationCaption 
> element.But the ChronologyLevelInstance does not contain it.
> <xs:element name="ChronologyLevelInstance">
>         <xs:complexType>
>             <xs:sequence>
>                 <xs:choice>
>                     <xs:element ref="ChronologyCaption"/>
>                     <xs:sequence>
>                         <xs:element ref="ChronologyLevel"/>
>                         <xs:element ref="ChronologyCaption" minOccurs="0"/>
>                     </xs:sequence>
>                 </xs:choice>
>                 <xs:element ref="ChronologyValue"/>
>                 <xs:element ref="Ext" minOccurs="0"/>
>             </xs:sequence>
>         </xs:complexType>
>     </xs:element>
> 
> <xs:element name="EnumerationLevelInstance">
>         <xs:complexType>
>             <xs:sequence>
>                 <xs:choice>
>                     <xs:element ref="EnumerationCaption"/>
>                     <xs:sequence>
>                         <xs:element ref="EnumerationLevel"/>
>                         <xs:element ref="EnumerationCaption" minOccurs="0"/>
>                         <xs:element ref="Ext" minOccurs="0"/>
>                     </xs:sequence>
>                 </xs:choice>
>                 <xs:element ref="EnumerationValue"/>
>                 <xs:element ref="Ext" minOccurs="0"/>
>             </xs:sequence>
>         </xs:complexType>
>     </xs:element>
> Silade
> Insignia
> 
> --- 10年7月1日，周四, Robert Walsh <rwalsh@xxxxxxxxxxxxxxxx> 写道：
> 
> 发件人: Robert Walsh <rwalsh@xxxxxxxxxxxxxxxx>
> 主题: Re: [ncipinfo] ChronologyLevelInstance ,and EnumerationLevelInstance
> 收件人: "刘小丰" <lxf615@xxxxxxxx>
> 抄送: ncipinfo@xxxxxxxxxxxxx
> 日期: 2010年7月1日,周四,下午8:09
> 
> Hello Silade,
> 
> I'm not sure I understand your question, but I'll try to explain the 
> relationship between these elements.
> 
> StructuredHoldingsData may contain either a single HoldingsChronology (which 
> may contain one or more ChronologyLevelInstance elements) OR a 
> HoldingsEnumeration (which may contain one or more EnumerationLevelInstance 
> elements) and (optionally) a HoldingsChronology element.  Each of these 
> elements supports the Ext extension element.  The ChronologyLevelInstance and 
> the EnumerationLevelInstance have parallel structures.
> 
> I don't see any disagreement between the XSD and the data dictionary in the 
> Standard for these elements, and neither is itself an Ext element.
> 
> Can you be more specific about the problem you are reporting?
> 
> Rob Walsh
> EnvisionWare, Inc.
> NCIP Maintenance Agency
> 
> 
> On Jun 30, 2010, at 11:50 PM, 刘小丰 wrote:
> 
>> Hello:
>> there is a difference between difference Chronology Level Instance And 
>> Enumeration Level Instance in xsd file.
>> The EnumerationLevelInstance is more  an Ext element then 
>> ChronologyLevelInstance.But The it seems their structure is the same 
>> according to the document in version 2.0
>> Thank you
>> Silade.
>> 
>>  
> 
> 
>