KMLM List
View email archives for the history of this mailing list.
|
|
|
|
ncipinfo - Re: [ncipinfo] ChronologyLevelInstance ,and EnumerationLevelInstance
|
Message Thread:
Previous |
Next
|
- To: 刘小丰 <lxf615@xxxxxxxx>
- From: Robert Walsh <rwalsh@xxxxxxxxxxxxxxxx>
- Date: Thu, 1 Jul 2010 08:09:08 -0400
- Cc: ncipinfo@xxxxxxxxxxxxx
- Send Email to ncipinfo@list.niso.org:
- Send new message
- Reply to this message
|
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.
>
>
|
|
By Date:
Previous |
Next
|
Current Thread
|
By Thread:
Previous |
Next
|
- Re: [ncipinfo] ChronologyLevelInstance ,and E, Robert Walsh (you are here)
|
|