[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [clr-dev] Re: Where to put information about a version change of a code list?
Hi Ken, Now I'm the person with the tardy response. Please excuse, I was on vacation and then very busy. Thank you so much for your answer and the detailed discussion of the alternatives. I see your point regarding the more accessible information in an additional column. On the other hand we probably understand the change information more as a property of the controlled vocabulary itself and not only of a specific code. It is still not decided yet. I'll keep you posted. Cheers, Achim -- GESIS - Leibniz Institute for the Social Sciences Department: Monitoring Society and Social Change Unit: Social Science Metadata Standards Visiting address: B2 1, 68159 Mannheim, Germany Postal address: P.O. Box 122155, 68072 Mannheim, Germany Phone: +49 (0)621 1246 262 Fax: +49 (0)621 1246 100 E-mail: joachim.wackerow@gesis.org www.gesis.org/en/institute/ > -----Original Message----- > From: G. Ken Holman [mailto:gkholman@CraneSoftwrights.com] > Sent: Samstag, 31. März 2012 03:45 > To: clr-dev@lists.oasis-open.org > Subject: [clr-dev] Re: Where to put information about a version change of a > code list? > > Please forgive my tardy response but I've been on holiday. > > What you have done is perfectly acceptable and a good example for > others to follow. This presents the change information as metadata > about the *maintenance* of the code as opposed to metadata about the > code itself. > > If you wanted the change status to be a property of the coded value, > then you could have created another column and put the information > there. That would have made it more accessible to users. But, is > that important? > > So, I would decide between the two approaches based on how accessible > you wanted the change information to be for the user. To make it > easier, make it a property of the coded value and in a column. If it > doesn't need to be easily accessible to users, what you have is > perfectly fine. It is accessible, just not as easily accessible as a > column value. And I see it as a property of the maintenance of the > coded value rather than a property of the value itself (though one > could go either way across that very fine line). > > I hope this helps. > > . . . . . . . . . Ken > > At 2012-02-14 03:39 +0000, Wackerow, Joachim wrote: > >Ken and others, > > > >As you might know, the DDI Alliance is using Genericode for > >controlled vocabularies in the domain of statistical (meta-)data. See: > ><http://www.ddialliance.org/Specification/DDI- > CV/>http://www.ddialliance.org/Specification/DDI-CV/ > >http://www.ddialliance.org/controlled-vocabularies. > > > >We would like to publish now a new version of one of these code > >lists. The information on the changes in the new version should be > >included. I didn't find a specific element for this purpose. > > > >I see the possibility to invent a custom class in the > >annotation/description section for a specific Row or specific column > >Value. Like: > ><SimpleCodeList> > > <Row> > > <Annotation> > > <Description> > > <h:div xml:lang="en-US" class="Change"> > > <h:p>New entry.</h:p> > > </h:div> > > </Description> > > </Annotation> > > <Value ColumnRef="Code"> > > <SimpleValue>Individual</SimpleValue> > > </Value> > > <Value ColumnRef="Term"> > > <Annotation> > > <Description> > > <h:div xml:lang="en-US" class="Change"> > > <h:p>wording change.</h:p> > > </h:div> > > </Description> > > </Annotation> > > <ComplexValue> > > <ddi-cv:Value xml:lang="en-US">Individual person</ddi-cv:Value> > > </ComplexValue> > > </Value> > > > >Are there other common ways to express this? > >Any advice is appreciated. > > > >Cheers, > >Achim > > > > > > > -- > Public XSLT, XSL-FO, UBL and code list classes in Europe -- May 2012 > Contact us for world-wide XML consulting and instructor-led training > Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm > Crane Softwrights Ltd. http://www.CraneSoftwrights.com/c/ > G. Ken Holman mailto:gkholman@CraneSoftwrights.com > Google+ profile: https://plus.google.com/116832879756988317389/about > Legal business disclaimers: http://www.CraneSoftwrights.com/legal > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: clr-dev-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: clr-dev-help@lists.oasis-open.org
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]