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-352) Schema issues relatedto emix.xsd wd22



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

William Cox commented on EMIX-352:
----------------------------------

I'm happy with the responses in Toby's comment, with a couple of exceptions.

(2) Added new issue EMIX-378 and updated EMIX-357 (table 4-5) on further examination of "Delivery"-related items.

(6) Ignore

(13) not sure where I found it; ignore.

(14) I'm asking for a comment in emix.xsd near lines 266-280. It's not clear to a reader, hence my note.

> Schema issues related to emix.xsd wd22
> --------------------------------------
>
>                 Key: EMIX-352
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-352
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Sub-task
>          Components: schema
>    Affects Versions: wd22
>         Environment: William Cox
>            Reporter: William Cox
>            Assignee: Toby Considine
>
> This is a list of questions and comments. Line numbers are as shown by XMLspy for emix.xsd.  The package of XML Spy diagrams has been uploaded to the archive under Contributions at http://www.oasis-open.org/committees/download.php/41712/SchemaWd22DiagramsEmixSchema.zip 
> Some issue apply to the specification as well as the schema.
> (1) product is an element (but ProductType is a type). ProductType is annotated as "EMIX Market Tender Product Type" which is overly restrictive. There's also a TEMIX product type; why both with similar annotations?
> (2) DeliveryType - how does this differ from Transportation? the information model includes only injection. Where are the two end points?
> (3) productDescription has measurement as the only attribute. The annotation should say "The respective product schemas extend this abstract class. See e.g. power-products.xsd"
> (4) emix:duration has a run to - emix:DurationType which is xcal:duration and xcal:parameters. I think it's several layers to get to xsd:simplelType duration. Consider documenting this.
> (5) ItemBaseType needs more explanation in the spec.
> (6) QuantityType diagram in Spy isn't useful; the restriction is more clear (base="xs:float")
> (7) A description of the benefits and costs of the approach to units would be valuable in the spec.
> (8) Why not the codes rather than strings in SiScaleType? I believe Anne Hendry raised an issue on that. I like having the selection from units and type subject to automatic validation via schemas.
> (9) The pattern for EmixExtensionType ("x-" prefix) should be explained in the spec with a reference to NIEM.
> (10) product has an annotation ending with "...Usually used in tenders". But the product is key to any price information exchange; why is this limited?  Moreover, the ProductType is distinct from the TemixType, so the transitive products would seem to be related to TemixType not ProductType.
> (11) How does element currency connect to the ISO currency codes? An annotation would be nice (8.2.3)
> (12) The documentation/annotation for emixconstraints is lengthy compared to the other annotations nib e.g. product (see product.png) and not in the same style. Other elements should have brief documentation as should emixconstraints.
> (13) Why is the type "emixconstraints" rather than emixConstraints? doesn't that violate the camelCaseRule?
> (14) Lines 266-280 are commented out. Why? Shouldn't be in Public Review if not used.

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