[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (EMIX-349) Sections 1.5 and 3: Addtext addressing why schema versioning is not needed in addition tonamespace versioning/maintenance
[ http://tools.oasis-open.org/issues/browse/EMIX-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William Cox updated EMIX-349:
-----------------------------
Proposal:
Add a sentence to Section 3 near line 344: "Namespace maintenance as described in section 1.5 addresses also addresses the need for schema versioning; we do not specify versions beyond those required by the namespace maintenance policy."
Also eliminate ", in effect,"
was:Add a sentence to Section 3: "Namespace maintenance as described in section 1.5 addresses also addresses the need for schema versioning; we do not specify versions beyond those required by the namespace maintenance policy."
Affects Version/s: wd30
(was: wd22)
Description:
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.
NOTE line number inserted for wd30
was:
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.
Resolution:
Add a sentence to Section 3 near line 344: "Namespace maintenance as described in section 1.5 addresses also addresses the need for schema versioning; we do not specify versions beyond those required by the namespace maintenance policy."
Also eliminate ", in effect,"
Updated to point to the proper place in wd30.
> 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: wd30
> Environment: William Cox
> Reporter: William Cox
> Assignee: Toby Considine
>
> 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.
> NOTE line number inserted for wd30
--
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]