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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xmile message

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


Subject: Re: [xmile] Very rough draft of section 5: Display and interface structure


Hi Bob,

Thanks for the comment:

1. Format:  I believe that in this case it makes sense to use XML in the conceptual section.  The reason being is that I spent a lot of time talking about where tags go in the tag hierarchy and how the positions of those tags affect their meaning.  The other portion of the conceptual section was dealing with commonly re-used XMILE objects/tags.  So in order to have them be fully specified (and easily referred to later) I felt it was best to include the actual tag.

The reason I did it like this is that I imagine chapter 6 the actual specification will go into great depth about each object (which will be composed of the objects discussed in chapter 5) and I felt it would be much easier to refer to the objects back in chapter 5 then it would be to re-introduce them again in chapter 6 and end up splitting up their discussion

2. Substance: I think I have to be misunderstanding you here: "Since the intention is to allow multiple display representations for any given variable" -- What I hear when you say this is that we want the ability to have multiple symbols (box, arrow, etc etc) representations for a single variable in a model (aliases would be the only case of this and will be covered separately in chapter 6 when we describe each XMILE display object).  That is something I strongly disagree with -- but if you explain why you think its a good idea I can be convinced otherwise.  What I hope you mean is that we want the ability to have different formats, scales, ranges for any single variable.  With that I would agree 100%, and my response would be that the display tag only deals with the symbols, not the number formatting, scales or ranges.

Best,

Billy


On Thu, Sep 19, 2013 at 8:31 AM, Bob Eberlein <bob@astutesd.com> wrote:
Hi Billy,

Thanks for putting this together. I have only gone through this superficially at this point, but it raises two big issue, one of format and one of substance. Both are worth discussing further in the group.

On format I was envisioning that the conceptual sections would stay away from XML and instead use something like the attached - basically an indented list. I find this easier to read and therefore more effective at conveying the logical structure of the model and layout representations. I would like to hear others opinions on this.

The substantive issue is related to the display, something I raised in my earlier notes. Since the intention is to allow multiple display representations for any given variable it seems that including display information inside of the variable definition and parallel to the equations, units and comments definition is undesirable as there will be a well defined way to do this inside a broader display definition. Again I would like to here others' opinions on this.

                                     Bob Eberlein

On 9/12/2013 4:11 PM, Billy Schoenberg wrote:
Hello Folks,

As promised I have put together the 'very rough draft' of section 5: Display and interface structure.

I have not applied any styles etc to this draft as I felt it was a distraction at this point.  I will be happy to apply any OASIS styles etc once Karim creates the document that we discussed a few days ago based off of the document that OASIS has provided us.

In this section I tried to cover all of the broad underlying assumptions behind all visual XMILE objects and I tried to specify all of the commonly used objects/concepts in the display/interface specification.

Please feel free to share any comments/suggestions via e-mail.  At the moment I would please ask that no direct edits to the document are performed until it can be placed in the proper place in version control.  I say this because I am not prepared to merge in a bunch of changes.

Best,

Billy



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



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



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