Re: [ebxml-iic] Groups - Deployment Profile Template(Deployment_Profile_Template-5.doc) uploaded

[Monica J Martin <Monica.Martin@Sun.COM>]

Jacques,
Thanks for pushing this forward. I have a few questions/comments on this 
(thinking about how this could be a computable XML representation 
sometime in the future):

    * For "alignment", more than one dependency or context may exist.
      Therefore I would suggest we have an alignment type and allow for
      multiple alignments to be specified.
    * Specification dependencies: Often times, you may see operational
      semantics that supplement how a particular XML capability is
      defined in the context of the schema and associated instance (For
      example, in BPSS, our BT patterns and their use in the ebBP schema
      and associated instance). Therefore a specificaiton reference may
      have additional operational semantics that bound it. How can we
      represent (or perhaps differentiate) dependencies as syntactic,
      semantic, other and show their relationship?
    * Notes: I would suggest we consider an approach that will lend
      itself to computability later. Maybe this could be as simple as
      putting a type on each note to differentiate. For example, a note
      of description or annotation is different from one that restricts
      when specific conditions exist (which raises the question if it is
      a dependency or constraint). If we can limit how notes are used,
      we may be able to more effectively use them later.

I apologize for missing Monday's call. I did ring in late but no one was 
present.