OK. I see you're caught up on the word "similar". Replace it if you want
with "The manner in which the language is represented is pretty" or "The
manner in which the language is represented is wicked awesome", or
whatever you want. The fact is that statement is merely an observation
and does not state a normative provision of the standard. However, it is
immediately followed by a full definition of what is required. That
following statement conforms to the schema definition and the Dublin Core
Usage Guide.
So editorial quibbling aside, if you were implementing or testing an
implementation, would you have any difficulties, given the current text,
determining what the requirements for dc:language were?
I think it is clear. If you disagree, then please suggest a wording
change.
Regards,
-Rob
"Dave Pawson" <> wrote on 07/03/2008 11:34:29 AM:
> Again.
>
> > "Dave Pawson" <> wrote on 07/03/2008 07:55:52 AM:
> >
> From 1.1
> >> The manner in which the language is represented is similar to the
>
> ^^^^^^^^^^^
>
> >> language tag described in [RFC3066].
> >>
> >> yet the schema calls up relax NG 'language' data type.
> >> http://www.w3.org/TR/xmlschema-2/#language
> >>
> >> language represents natural language identifiers as defined by by
[RFC
> >> 3066]
>
> So one *is* RFC compliant.
> The other is *similar* to RFC...
>
>
>
> --
> Dave Pawson
> XSLT XSL-FO FAQ.
> http://www.dpawson.co.uk
>
> --
> 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:
> Unsubscribe:
> List help:
> 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
>
