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

 


Help: OASIS Mailing Lists Help | MarkMail Help

emix message

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


Subject: [OASIS Issue Tracker] Commented: (EMIX-390) Restructure Section 3,Guide to the Schema Structures



    [ http://tools.oasis-open.org/issues/browse/EMIX-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25877#action_25877 ] 

Anne Hendry  commented on EMIX-390:
-----------------------------------

line numbers as per wd28 ...

The Section 3 schema description section (3.0?) requires no 'definitions' as it is simply a description of the schemas.

Table 3-2 would go away and the information in it reordered as in table 3-1.

Table 3-1 is an example of how the information for each of these groups could be displayed (one table for each schema 'group').  So for instance, table 3-1 would become 'EMIX Schema', table 3-2 would become 'Power Schema', etc, depending on the final groups/names.

There are currently 3 (4?) schema 'groups' (emix, power, resource, siscale?).

Each table could have the namespace, the list of schema files for that namespace/group, and description (and any other information desired) for each of the schema 'groups' as in table 3-1.

The three bullets at lines 290 - 295 would go into the 'description' row for each schema 'group'.

The statements in lines 296 - 299 could also go in the 'description' row of the respective tables for power and resource schema.

Bill requested that a rationale for the different groupings/structure of the schema files be added to this section ( http://tools.oasis-open.org/issues/browse/EMIX-386 ).  That could go in a new row, or in the 'description' row for each schema 'group'.

That would take care of all the information currently in that first part of Section 3.

Other suggestions welcome, this was just a quick pass attempt at consolidating and ordering the information for readability and ease of understanding.


> Restructure Section 3, Guide to the Schema Structures
> -----------------------------------------------------
>
>                 Key: EMIX-390
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-390
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Improvement
>         Environment: Anne Hendry
>            Reporter: Anne Hendry 
>            Assignee: Anne Hendry 
>
> 'Definition' column in this table of various schema types is actually a continuation of the descriptions in bulleted list above this table.
> Suggest merging these sections of information and either :
> - do not use table structure, use bulleted or subheadings instead and make each of those into separate paragraphs as already in the paragraphs above
> or
> - use table structure, including all information in the table, and change the 'Definition' column heading to something else, such as 'Description', 'Components', or any other term so as not to confuse with the Element Definitions.  The information in that column is not a definition, is more of a description.
> Really best to do something that distinguishes as separate from the Element tables.

-- 
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]