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


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-ndrsc message

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

Subject: Re: [ubl-ndrsc] Rule: 71 PeriodDetails

This is even weaker than the BC Duration requirements. Also there is an 
explanation of the design that I don't think should be in the rule.

Here is how I would change this based upon current design, if you agree we 
should be more specific in the requirements, then may would change to must.

>[R 71]  A period MAY be expressed using the ACC

Also we are not consistent in how acronyms are spelled out. BCC used 
without an explanation but here we spell out ACC. There should be a 
standard glossary that has all these terms with maybe a pointer to control 
documentation for the definition.

At 08:02 AM 7/11/2003 -0500, Lisa-Aeon wrote:
>Rules for Voting:  Each email will have only one rule in it, I will try to
>mark the rules that group with it, or rules that might duplicate it.  The
>membership has 5 working days to bring forth objection or discussion, after
>the 5 working days, if there are no objections, the rule will be assumed to
>be "ACCEPTED" and be given to the LCSC for their implementation.
>Please Reply leaving first email in Reply.
>Voting period on this rule ends:  July 17, 2003
>[R 71]  A period can be expressed using the Aggregate Core Component (ACC)
>PeriodDetails. The ACC is divided into 3 representation types, Date, Time
>and DateTime. One of these must be selected. Each option has a start and end
>date, start and end time or start DateTime and end DateTime.
>ATG Decision:  rule has not yet been discussed by ATG2
>File has not been scanned
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.498 / Virus Database: 297 - Release Date: 7/8/2003

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