[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (EMIX-349) Sections 1.5 and 3: Addtext addressing why schema versioning is not needed in addition tonamespace versioning/maintenance
Sections 1.5 and 3: Add text addressing why schema versioning is not needed in addition to namespace versioning/maintenance --------------------------------------------------------------------------------------------------------------------------- Key: EMIX-349 URL: http://tools.oasis-open.org/issues/browse/EMIX-349 Project: OASIS Energy Market Information Exchange (eMIX) TC Issue Type: Improvement Components: spec Affects Versions: wd22 Environment: William Cox Reporter: William Cox Assignee: William Cox Independent of namespace maintenance issues (see EMIX-317) versioning the schema (by adding a schemaVersion attribute to major class definitions) has been discussed. There are pluses and minuses with respect to the EMIX information model. Pluses include identification of versions of major artifacts; minuses include overhead for management, of versioning, space in each artifact for the version, and that schemaVersion in addition to namespace versioning and maintenance is a "belt and suspenders" approach. With a number of relatively small objects, the overhead seems a real burden, for little value. Mixing artifacts from different namespace versions seems a recipe for confusion among those using the standard -- incremental update of an EMIX implementation is not something I would anticipate. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]