Uploaded image for project: 'Ed-Fi Data Standard'
  1. Ed-Fi Data Standard
  2. DATASTD-526

Naming convention for versions

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Major
    • Data Standard v2.0 - RFC
    • Data Standard v2.0 - RFC
    • None
    • None
    • Impediment

    Description

      Versions are used throughout the draft2.0 xsd.

      example:
      new simpleTypes: ContentStandardVersion
      new simpleTypes: ContentVersion
      Version

      elements:
      ContentStandard.Version
      ContentStandardType.Version
      EducationContent.Version
      Assessment.Version
      AssessmentIdentity.Version
      AssessmentIdentityType.Version

      Is the naming convention right? (should Assessment.Version be renamed Assessment.AssessmentVersion)

      Should there be one definition of version for everything? Use a string or numeric?

      Attachments

        Issue Links

          Activity

            People

              chris.moffatt Chris Moffatt
              RMH3 Richard Heim
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 hours
                  4h

                  Salesforce