18.51 db:enable-sql92-check (ODF1.2)

["Alex Brown" <alexb@griffinbrown.co.uk>]

Patrick hi

This raises a problem specific to ODF 1.2.

How does referencing the SQL 2008 version invoke restrictions that were
apparently only in force for SQL 92?

What is different about the behaviour if this attribute is set "true"
rather than "false"?

In other words, isn't this citation (and the note) here, wrong?

- Alex.


> -----Original Message-----
> From: Patrick Durusau [mailto:patrick@durusau.net]
> Sent: 27 September 2009 00:59
> To: Alex Brown
> Cc: office-comment@lists.oasis-open.org
> Subject: Re: [office-comment] 18.51 db:enable-sql92-check (ODF all
versions)
> 
> Alex,
> 
> I should read all of my incoming mail before responding. ;-)
> 
> The correct citation is:
> 
> [SQL]    ISO/IEC 9075-1:2008 Information Technology -- Database
Language
> -- SQL -- Part 2: Foundation (SQL/Foundation), , 2008 Hope you are
having a
> great weekend!
> 
> Patrick
> 
> Alex Brown wrote:
> > Dear all,
> >
> > Sorry that comment is not for "ODF all version", but only "ODF
1.0/1.1".
> >
> >
> >> Dear all,
> >>
> >> ----
> >> The db:enable-sql92-check attribute specifies that the names of
> >>
> > tables,
> >
> >> views, columns, and queries must be conform to ISO/IEC 9075
> >>
> > Information
> >
> >> Technology - Database Language SQL: 2002.
> >> ----
> >>
> >> * I can find no reference to a 2002 version of this Standard, but
can
> >> find this 2003 version:
> >> http://www.iso.org/iso/catalogue_detail.htm?csnumber=34133 . Note
> the
> >> title is different, and this Standard has since been revised
(2008).
> >>
> >> * "must be conform" -> "shall conform to the naming conventions
of".
> >>
> >> * I cannot find the naming prohibition described in the following
> >> note (in the ODF spec). For convenience, please cite the clause
where
> >> this is defined.
> >>
> >> * Or ... is the 1992 version of 9075 meant (
> >> http://www.iso.org/iso/catalogue_detail.htm?csnumber=16663 )? This
> >> has been withdrawn and so should not be cited; instead the relevant
> >> provisions need to be stated in full in the ODF spec itself
(perhaps
> >> beef-up the note).
> >>
> >> - Alex.
> >>
> >>
> >>
> >>
> >>
> >> --
> >> This publicly archived list offers a means to provide input to the
> >> OASIS Open Document Format for Office Applications (OpenDocument)
> TC.
> >>
> >> In order to verify user consent to the Feedback License terms and
to
> >> minimize spam in the list archive, subscription is required before
> >> posting.
> >>
> >> Subscribe: office-comment-subscribe@lists.oasis-open.org
> >> Unsubscribe: office-comment-unsubscribe@lists.oasis-open.org
> >> List help: office-comment-help@lists.oasis-open.org
> >> List archive: http://lists.oasis-open.org/archives/office-comment/
> >> Feedback License: http://www.oasis-
> >> open.org/who/ipr/feedback_license.pdf
> >> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
> >> Committee: http://www.oasis-
> >> open.org/committees/tc_home.php?wg_abbrev=office
> >>
> >
> >
> >
> 
> --
> Patrick Durusau
> patrick@durusau.net
> Chair, V1 - US TAG to JTC 1/SC 34
> Convener, JTC 1/SC 34/WG 3 (Topic Maps)
> Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-
> Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)