W3C home > Mailing lists > Public > public-owl-wg@w3.org > May 2008

"Should" sanity check

From: Boris Motik <boris.motik@comlab.ox.ac.uk>
Date: Wed, 28 May 2008 20:15:28 +0100
To: <public-owl-wg@w3.org>
Message-ID: <006c01c8c0f7$30d21ab0$7212a8c0@wolf>


I just went though all the documents and have checked the usage of "should" in them. I have corrected the usage in several places;
here are the diffs:


RDF mapping:

XML syntax:


Structural specification:

After this clean-up, only the structural specification contains occurrences of "should" in the text (profiles contain "should" in
reviewers' comments, but not in the text). All usages of "should" in the structural spec are now in the sense "should do unless
there is some really good reason not to".

For the moment, I left all the letters in lower case. I did this because of two reasons:

- I really didn't understand what the outcome of the discussion at the teleconf was.
- Writing "SHOULD" instead of "should" in places such as examples seemed to me really ugly.

I tried to reformulate the examples in a way that doesn't use should; however, the text then becomes really weird.

If the general consensus is that we should use "SHOULD" in the normative part of the document, then I propose to use lowercase
"should" in places that are not normative, such as examples. In all cases, I will use "should" and "SHOULD" in the same sense; it is
just that using the stressed "SHOULD" in nonnormative parts of the document such as examples seems quite strange to me.


Received on Wednesday, 28 May 2008 19:17:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:42:04 UTC