OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

coel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (COEL-62) Combine COEL model json files into one file

    [ https://issues.oasis-open.org/browse/COEL-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62726#comment-62726 ] 

David Snelling commented on COEL-62:

Basically I like your proposal for COEL-62.This links with COEL-57. This comment will go in both places.

I think we should settle on a version system for the model. I propose the following:

Level 1: Must increment when a non-backwards compattible change is made, e.g. ne structure or changing the value of an exusting field. Must run through OASIS Process.
Level 2: Is incremented for any release that is agreed by the Committee and runs the OASIS process, but is backwards compatiable,e.g. only new fields.
Level 3: Experimental. This is incremented to working draft publications that we want to make available for people to use, but have not been through a full ratification process.
Level 4: We could drop this, or simply say it is for development outside the OASIS TC and will always be "0" in any OASIS version.

> Combine COEL model json files into one file
> -------------------------------------------
>                 Key: COEL-62
>                 URL: https://issues.oasis-open.org/browse/COEL-62
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: Task
>            Reporter: Paul Bruton
>            Assignee: David Snelling
> Create a single file from the existing four JSON files using key/value pair and update any ad-hoc tools we are using for compatibility.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]