Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-2309

Improve XSD schema defintitions for KEW XML so that they can be utilized by XML tools

    Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Development
    • Labels:
    • Similar issues:
      KULRICE-1599Developer-friendly XSD URIs
      KULRICE-1130improve performance of xml ingestion
      KULRICE-805Come up with a method for generating documentation about our XML document structure (XSD schema)
      KULRICE-2634Implement support for better XML export, XML import and migration features
      KULRICE-1993Create a reference guide for our Ingestable XML configuration (DocumentType, RuleAttribute, etc.)
      KULRICE-3961Add some additional xml parsing fields for ingestion of KEW users
      KULRICE-4202XML Schema Versioning
      KULRICE-1855KEN XSD Schema validation for notifications being sent into KEN via the XML based String input service fails for non-UTF-8 DBs
      KULRICE-1642Merge EDL bootstrap XML into the main KEW bootstrap XML
      KULRICE-2639Document changes to workgroup XML schema and include in upgrade notes
    • Rice Module:
      KEW

      Description

      Currently, because of the way the namespaces are defined for our KEW XSD files, it makes it impossible for an XML editor to validate them. For example, all of our XSD files include a reference to common.xsd but the only way to resolve it is by using our custom EntityResolver. It would be nice if the namespaces were defined in such a way that a tool could recognize these. In DTD you typically do this by having your DTD available at some URL. I'm not sure what the best practice is for XSD schemas.

      When working on this, if we make changes to the schema namespace definitions we can preserve backward compatibility with existing XML by allowing our custom EntityResolver to still resolve the old entities.

        Issue Links

          Activity

          Hide
          Eric Westfall added a comment -

          Moving to 1.1 as it's not critical for 1.0 release but I really want to get this improved for the 1.1 release.

          Show
          Eric Westfall added a comment - Moving to 1.1 as it's not critical for 1.0 release but I really want to get this improved for the 1.1 release.

            People

            • Assignee:
              Unassigned
              Reporter:
              Eric Westfall
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Time Tracking

                Estimated:
                Original Estimate - 2 days
                2d
                Remaining:
                Remaining Estimate - 2 days
                2d
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Structure Helper Panel