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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-iic message

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


Subject: Re: [ebxml-iic] TestProfile


Jacques,

I agree, that is a good feature to have. Thanks! I will incorporate it.

Cheers,

Matt

On Monday, July 1, 2002, at 06:13 PM, Jacques Durand wrote:

Matt:

Looks sufficient. Two comments:

- I am wondering whether we should authorize profile definitions
that "override" keywords like OPTIONAL or RECOMMENDED for some
items in the Test Req base, but only in the upgrade direction,
i.e. make the feature a MUST for this profile.
I would lean toward making this possible, at least when feature
is initially RECOMMENDED.
If there is a consensus on this, your TestRequirementRef element
below should have an optional attribute "requirementlevel" (e.g. requirementlevel="MUST"),
or should we craft an entire new Test Req item in such case?
(but that means the Test Req base is no longer stable...)


- A master Test Req file could also have a "reqsversion" attribute, that matches
the spec version # (in addition, the name of the master f may of course change, e.g. reqs_V3.xml).  If we do so, we can also have same version # attribute in the


 Profile definition, and so manage more easily a set of versioned profiles,
with same name (we may not want to change a profile name with each spec version,
as profiles have "user" exposure and business meaning, unlike the master f name).
 


<TestProfile requirementsLocation="http://www.geek.ca/reqs_V3.xml"
reqsversion="3.0" name="Matt's Profile" description="Additional requirements for use on the Matt Network">
  <Dependency name="Core Modules" profileRef="http://oasis/iic/msg/corereq.xml" />
- <TestRequirementRef id="matt-1" >
<TestRequirementRef id="matt-2" requirementlevel="MUST">
<TestRequirementRef id="matt-3" >
  <Comment>This requirement is added to the profile because ... blah blah</Comment>
  </TestRequirementRef>
  </TestProfile>


Jacques

-----Original Message-----
From: Matthew MacKenzie [mailto:matt@xmlglobal.com]
Sent: Monday, July 01, 2002 11:29 AM
To: ebxml-iic@lists.oasis-open.org
Subject: [ebxml-iic] TestProfile



As promised during the call today, here is a first stab at defining an
XML Schema which allows us to organize TestRequirements into
TestProfiles by ID reference.


Comments?



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


Powered by eList eXpress LLC