[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dss-x] DSSX-25: Wording regarding optional elements
Hi Detlef, that's a good way forward! With a upper-case 'OPTIONAL' and the sub-sentence things should be correct and understandable. I'll just give Ernst Jan a chance to veto tomorrow ... Greetings, Andreas > Hi, > > IMHO "MAY" and "OPTIONAL" are equivalent with respect to "softness" or "hardness" > according to RFC 2119: > > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL > NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and > "OPTIONAL" in this document are to be interpreted as described in > RFC 2119. > > ... hence "OPTIONAL" should be set in capital letters, if we it is to be interpreted > as defined in RFC 2119. > > The half sentence ", if it is present" IMHO cures the "felt" contradiction > between "the OPTIONAL ... element MUST ... ". > > > BR, > dh > > -----UrsprÃngliche Nachricht----- > Von: dss-x@lists.oasis-open.org <dss-x@lists.oasis-open.org> Im Auftrag von Andreas Kuehne > Gesendet: Donnerstag, 10. Januar 2019 22:49 > An: dss-x@lists.oasis-open.org > Betreff: Re: [dss-x] DSSX-25: Wording regarding optional elements > > Hi Detlef, > > I guess JC concern was to replace the soft 'optional' with a RFC 2119-styled MAY . > > We once dropped the 'if present' sub clause because of presumed redundancy. > > Greetings, > > Andreas >> Hi, >> >> >> >> a more correct (while readable) approach might be >> >> >> >> âThe optional X509Digest element MUST contain one instance of a sub-component, if it is present.â >> >> BR, >> >> dh >> >> >> >> Von: dss-x@lists.oasis-open.org <dss-x@lists.oasis-open.org> Im >> Auftrag von Andreas Kuehne >> Gesendet: Donnerstag, 10. Januar 2019 22:37 >> An: dss-x <dss-x@lists.oasis-open.org> >> Betreff: [dss-x] DSSX-25: Wording regarding optional elements >> >> >> >> Hi folks, >> >> >> Juan Carlos complained about the way the optionality' of an element is expressed. Currently there is a sentence for elements with maxOccurs=0 or attribues with optional=true: >> >> The optional X509Digest element MUST contain one instance of a sub-component. >> >> Juan Carlos suggests to make it more obvious using a 'MAY': >> >> The X509Digest element MAY be present. This element MUST contain one instance of a sub-component. >> >> Such a sentence was my first approach and I once changed it because of bad readability. >> >> What's your opinion? Explicit or readable texts? >> >> >> >> Greetings, >> >> >> >> Andrreas >> > -- > Andreas KÃhne > phone: +49 177 293 24 97 > mailto: kuehne@trustable.de > > Trustable Ltd. Niederlassung Deutschland Gartenheimstr. 39C - 30659 Hannover Amtsgericht Hannover HRB 212612 > > Director Andreas KÃhne > > Company UK Company No: 5218868 Registered in England and Wales > > > --------------------------------------------------------------------- > 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 > > -- Andreas KÃhne phone: +49 177 293 24 97 mailto: kuehne@trustable.de Trustable Ltd. Niederlassung Deutschland Gartenheimstr. 39C - 30659 Hannover Amtsgericht Hannover HRB 212612 Director Andreas KÃhne Company UK Company No: 5218868 Registered in England and Wales
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]