 |
 |
I like Ian's intellectual approach to deciding if an element should repeat or have multiple values. My reality so far in creating metadata scheme for our new virtual library under design this past year has been that "implementation" as Robina mentions ends up being the deciding factor. Our developer designing the underlying data structure in the relational database needs the data one way or the other and makes the call. The good news is that he does not do this on his own. He makes this decision after talking with me and we take a look at all the dependencies. But in the end, he makes the call. ~Vivian Vivian Bliss Knowledge Management Analyst MS Knowledge Network Group Microsoft Corp. 425.703.7212 [log in to unmask] -----Original Message----- From: Ian Stuart [mailto:[log in to unmask]] Sent: Thursday, September 13, 2001 3:10 AM To: [log in to unmask] Subject: Re: Repeating DC elements On Thu, 2001-09-13 at 10:23, Clayphan, Robina wrote: > Hi, > > I have been asked for the rationale for repeating a DC element rather than > putting multiple values in one occurence of an element. This is not > something I have thought about in terms of stating a general principle and > cannot find any specific information. My personal fealing is that an element contains a piece of data, thus you do whatever the data requires. Using your dc:Creator example: If you have one piece of data (which happens to have several names, then you use one element. If, on the other hand, you have several seperate pieces of data (Creators), then you use more than one element. My reading of the schema is that you may have more than one dc:Creator elenent.. -- --==++ Ian Stuart A man in serious need of a Brain Transplant