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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xmile-comment message

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


Subject: Re: [xmile-comment] Issue with XMILE schema


Hi Robert,

The Technical Committee just approved an errata to the XSD file that fixes this.  We also verified the other Chapter 6 attributes in case any others did not match the written specification, but did not find any.  It isn't official until after a 15-day review and another vote, but the corrected file is here:

https://www.oasis-open.org/committees/document.php?document_id=57266&wg_abbrev=xmile

Best regards,

Karim


On Thu, Jan 7, 2016 at 9:29 AM, Chet Ensign <chet.ensign@oasis-open.org> wrote:
Hi Karim, 

Sorry, I have to correct you. Per OASIS rules, if there is a discrepancy between the documentation in a spec and a schema, the schema is authoritative. So I think you definitely want to fix this. 

As Paul notes in his email, the way to do this is via an errata. 

Best, 

/chet


On Wed, Jan 6, 2016 at 6:22 PM, Karim Chichakly <kchichakly@iseesystems.com> wrote:
Hi Robert,

The schema was largely developed before the final spec.  We tried to update it to match, but apparently missed that part.  "interval" is correct, as per the spec.  [The spec is definitive, the schema suggestive.  We should update the schema.]

Best regards,

Karim

On Wed, Jan 6, 2016 at 2:10 PM, Robert Ward <codecraftsman1@gmail.com> wrote:
I have encountered a disagreement between the XMILE standard document and the published XMILE schema.

In section 6.4.4, the standard document requires that reports support an attribute named "interval", but in the schema, this attribute is named "report_interval". As a work-around, I suggest that implementations should serialize models using the attribute name "interval", but recognize both "interval" and "report_interval" as synonyms for the same attribute when deserializing models. It would help reduce potential issues between hand-written and generated parsers, if the published schema was either corrected, or modified to allow either symbol.

--
Robert Ward
Software Engineer
This email has been sent from a virus-free computer protected by Avast.
www.avast.com




--

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 



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