Child pages
  • Standards Committee review, June 2014
Skip to end of metadata
Go to start of metadata

Te table below captures the comments from the standards committee review:

SubmitterCommentStaff commentsWorking group recommendation
RehakEditorial: Page 10: "Commonly used datatypes aredefined in the" -- no space between are and definedCorrect spacing. 
RehakEditorial: Page 18-24:  Inconsistent spacing before colons, e.g., "general:identifier:catalog" vs. "lifecycle: status: value".  Multiple similar instances in the table.Correct spacing. 
RehakEditorial:  Throughout:  No space in footer before page numbers, e.g., "Page22".Correct spacing. 
RehakTechnical:  Section 7.4:  LeastCompetent and MostCompetent are defined as xsd:int.  This implies both can be zero or negative.  Are such values allowed or is a more restrictive data type needed?I think we wanted to allow for users to define the scale however they wanted. That would mean we leave as is. That said, we've not seen any scales that would use negative numbers. If we decide we should only allow positive numbers, we would want to change the rest of the score related elements, too. 
RehakTechnical:  Section 7.4: As defined the value of MostCompetent may be less that the value of LeastCompetent.  Is this correct, or is there an additional semantic constraint that More >= Least?That was our intent, as 1 may be most competenct or least competent on a scale of 1 to 5. We modeled that after what we say in ISO standards. 
RehakTechnical:  Page 35:  As defined the value of MinimumAcceptableScore may be zero or negative.  Are such values allowed or is a more restrictive data type needed?I think if we allow scales to include 0 and negative numbers, we should allow the thresholds to as well.  
RehakTechnical:  Page 37:  May two AdditionalElements with the same label have the same value for the position attribute, or does position need to be unique?Good point, We should probably add to the spec that position should be unique within the scope of for AdditionalInformation with the same label for a single element. 
RehakTechnical:  Page 41:  DisplayOrder is defined in the narrative as positive integer, but the datatype is integer.  Should it be positive integer (and use xsd:postiveInteger)?Agree! 
RehakTechnical:  Page 43:  As defined the value of SingleValue may be zero or negatives.  Are such values allowed or is a more restrictive data type needed?I think if we allow scales to include 0 and negative numbers, we should allow the scores to as well.  
RehakTechnical:  Section 7.5.4.3:  MinScore and MaxScore are defined as xsd:int.  This implies both can be zero or negative.  Are such values allowed or is a more restrictive data type needed?I think if we allow scales to include 0 and negative numbers, we should allow the scores to as well. 
RehakTechnical:  Section 7.5.4.3: As defined the value of MaxScore may be less that the value of MinScore.  Is this correct, or is there an additional semantic constraint that Max >= Min?It really depends on the direction the scale is going. If the scale has 1 being most competent and 5 being least competenct, you would want the MaxScore to be lower than the MinScore. 
RehakTechnical:  Throughout:  Several elements are defined as datatype NonNullStringType.  Is there any need to indicate the language of the string?Framework authors can specify the language of the framework as a whole in the metadata.  I will clarify with the working group if new frameworks are defined for each language or if multilingual frameworks are preferred.  
Jacobs

There is no further input from the AAMC on this standard, and the vote is to approve.

  
HaraczWe have reviewed the document and ABIM has no comments to submit at this time  
  • No labels