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

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

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


Subject: [OASIS Issue Tracker] Commented: (OFFICE-1793) ISO/IEC JTC 1/SC 34N 1078 : DEFECT REPORT NUMBER JP2-1



    [ http://tools.oasis-open.org/issues/browse/OFFICE-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698#action_12698 ] 

Michael Brauer commented on OFFICE-1793:
----------------------------------------

Regarding the resolution of the issue: We should just remove the full paragraph:

"The manner in which the language is represented is similar to the language tag described in [RFC3066]. It consists of a two or three letter Language Code taken from the ISO 639 standard optionally followed by a hyphen (-) and a two-letter Country Code taken from the ISO 3166 standard."

The schema says that the attribute value is a "language". This is defined in chapter 17 already properly.

Regarding Patrick's comment. "<data type="language"> references the W3C "language" datatype. This implies the standard syntax. Where is no need to repeat it.


> ISO/IEC JTC 1/SC 34 N 1078 : DEFECT REPORT NUMBER 	JP2-1
> --------------------------------------------------------
>
>                 Key: OFFICE-1793
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-1793
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>            Reporter: Robert Weir 
>            Assignee: Patrick Durusau
>             Fix For: ODF 1.2, ODF 1.0 Errata 02
>
>
> Transcribed from http://www.itscj.ipsj.or.jp/sc34/open/1078.htm
> Original author: "MURATA Makoto (FAMILY Given)" <eb2m-mrt@asahi-net.or.jp>
> DEFECT REPORT NUMBER 	JP2-1
> QUALIFIER 	clarification required
> REFERENCES IN DOCUMENT 	Clause 3.1.15
> NATURE OF DEFECT 	The second sentence in the second paragraph in this clause does not allow optional subtags, while such subtags are allowed in the referenced document, namely RFC 3066. Does ODF intentionally disallow subtags?
> SOLUTION PROPOSED BY THE SUBMITTER 	Just reference to RFC 3066 and stop there. Do not say anything about what is normatively specified in RFC 3066.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


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