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

 


Help: OASIS Mailing Lists Help | MarkMail Help

emix-comment message

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


Subject: RE: [emix-comment] interim schemas and xml files that suggest enhancementsto WSCAL and EMIX


Marty,

Thanks for posting this - quick initial feedback:

 Reason for not using ºC is the special character º is difficult to manage in software.

Yes indeed! It's a non-UTF8 char and so this is problematic.  Suggest this is not used in the annotation for //power:ReadingType/eui:unit

Thanks, DW

-------- Original Message --------
Subject: [emix-comment] interim schemas and xml files that suggest
enhancements to WSCAL and EMIX
From: "Marty Burns" <burnsmarty@aol.com>
Date: Mon, January 24, 2011 7:46 am
To: <emix-comment@lists.oasis-open.org>

EMIX Team,
 
The attached are drafts of schema work that was done toward a white paper written for the SGIP by Aaron Snyder and myself. We are seeking review by the participants of the TT meeting. However, Dr. Cox indicated to us that there was urgency to providing a draft of the schema work to this list, and so we have accommodated his recommendations.
 
The white paper which includes an explanation of these will be completed after we have the participants review cycle by the end of this month.
 
It was found that through some small changes in each standard, substantial alignment was achieved. Note that while there is not an exact duplication of components, there is a one to one correspondence of elements in SEP 2.0 to EMIX as revised. EMIX being the standard with greater scope and additional requirements beyond those engaged by SEP 2.0, the focus on enhancement was performed principally there.
 
Note that in all cases, care was taken not to add constraints to any schema, only extension and clarification of capabilities were exploited. By all means, there were probably alternate approaches to the same ends but these revisions are examples that do work and illustrate the possibilities for standards harmonization.
 
To test the validity of the schemas, two EMIX XML examples were constructed – an implementation of EMIX figure 4-1, and, a an implementation of the TT Use Case as implemented similar to SEP2.0.
 
Cheers,
Marty
 
Dr. Martin J. Burns
President
Hypertek Inc.
14624 Country Creek Lane
North Potomac, MD 20878
p-1(301)315-9101
c-1(301)257-9101
 
 
 

--
This publicly archived list offers a means to provide input to the
OASIS Energy Market Information Exchange TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: emix-comment-subscribe@lists.oasis-open.org
Unsubscribe: emix-comment-unsubscribe@lists.oasis-open.org
List help: emix-comment-help@lists.oasis-open.org
List archive: http://lists.oasis-open.org/archives/emix-comment/
Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emix


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