Re: [xmile] update + some questions

[Karim Chichakly <kchichakly@iseesystems.com>]

Hi Will and Bobby,

Yes, sim_specs should be optional.  That's an oversight.

I agree with you Will that we should suggest an order, not require it,

Bobby, the syntax for the model units was described rather carefully in the past.  It has been changed quite a bit and Bob did all those edits, so I will defer to him to answer that question.  [And no, it's not limited to a single '/'.]

Kairm

On Thu, Jun 26, 2014 at 4:16 AM, Will Glass-Husain <wglass@forio.com> wrote:

Hi Bobby,

The section on includes specifically mentions that other required sections, such as <header> are not required for files that are included.  But it doesn't mention sim_specs - that seems like an oversight.  The schema does not require it.   Should we change section 2.11 to allow <sim_specs> to be optional in included files?

On a related note, I would like to make the standard more flexible for the ordering of tags.  There are many places in the docs that say tags or sections should appear in a certain order, which seems unnecessary to me.  The schema is more flexible on ordering (thanks Gary for pointing this out).    Example (section 2.1):

 

Top level tags MUST occur in this order:

WILL

On Thu, Jun 26, 2014 at 2:44 AM, Bobby Powers <bobbypowers@gmail.com> wrote:

Hi folks, I've been going through the spec, and have a few clarifying questions:

1 - required sim specs.  I'm not sure they should be required by the
spec if we want to support modules/includes of vendor-specific unit
files, styles or macros.   This is sort of covered towards the end of
the overall section with the section on format of include files, but
this is a little confusing to me (suggesting files included are not
necessary XMILE files, but some subset).

2 - Model units.  We don't actually specify the syntax of model units
in the overall part, and the example uses the old-style isee syntax of
'x/(b-c)' to workaround the limit of only allowing a single '/'
character.  I don't mind that example, but would not want to limit the
spec to a single division symbol.

I've commited my changes to the overall section, and will work on the
next sections tomorrow.  Thoughts, comments and criticisms welcome!

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

--

William Glass-Husain   /forio  |  +1 (415) 440 7500 x89  |  forio.com