#
Term
Action
#19Process Support InputRemove all Process Input subtypes
#19Parameter InputRemove all Process Input subtypes
#19Transformable InputRemove all Process Input subtypes
#19Transformed OutputRemove all Process Output subtypes
#19Process MetricRemove all Process Output subtypes
#10RepresentationRename to Presentation
#1Unit TypeNew object
#13Analysis UnitRemove all Unit subtypes
#13 Analysis PopulationRemove all Population subtypes
#13 *Frame Population (to be removed)Remove all Population subtypes
#13 Observation UnitRemove all Unit subtypes
#13 Survey PopulationRemove all Population subtypes
#13 *Target Population (to be removed)Remove all Population subtypes
#3*Design Context (to be removed)Remove Object
#6Non Structured DatasetRemove Object
#32Instrument ImplementationRename to Represented Instrument
#30PENDING:New abstract question objectwith subtypes Question and Multiple Question Item
#36Channel Activity SpecificationRemove Object
#36  Channel design SpecificationRemove object
#4*Dissemination Service (to be removed)Make subtype of Business Service
   
#26

Index (Classification Index)

Index Entry (Classification Index Entry)

Ensure only have relationships to Classification objects and not to nodesets.

1 Comment

  1. user-8e470

    The Reference Period is defined as an attribute of StatisticalProgramCycle, it is mentioned in the definitions of StatisticalActivity and its subtypes AcquisitionActivity, DisseminationActivityand ProductionActivity, as well as in the explanatory text of AcquisitionDesign.

     

    However, it is not part of the definition of a Variable and does not take part in the definition or description of Population, Unit or Dataset. So, how does one know what ReferencePeriod a certain set of data (in a DataSet) describes?

     

    Do we need to somehow include ReferencePeriod in the application of a Variable in the context of a ProgramCycle such that it is explicitly kept with the data (as part of the metadata)?