[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: @office:process-content / schema defect? (ODF 1.2 CD01)
Dear all, 1.4.5 has this: ----b Foreign elements may have an office:process-content attribute attached that has the value true or false. If the attribute's value is true, the element's content may be interpreted by conforming processors regardless of its ancestor elements. If the attribute's value is false, conforming processors should not interpret the element's content, but may only preserve its content, regardless of the foreign element's ancestor elements. The office:process-content attribute is deprecated. Note: In OpenDocument 1.0 and 1.1, the content of foreign elements should be process unless there was an office:process-content attribute with value false. ----e * Suggested re-write of first para: Conforming OpenDocument consumers may interpret foreign elements that have an office:process-content attribute with a value of "true". They shall not interpret, but may preserve, foreign elements that have an office:process-content attribute with a value of "false". * In para 2, this is the first use of the word "deprecated" in the spec. What are the semantics of deprecation in ODF? This should be clearly defined. In general, the text would be greatly improved in quality if it had a formal Terms and Definitions section as per the ISO/IEC Directives. * I believe the note that ends this extract is unhelpful and should be removed. It is not the function of a specification to offer passing commentary on how it differs from some of its predecessor versions. However, if this note remains then "process" -> "processed". * In the schema accompanying the spec, the following pattern is declared: <define name="office-process-content"> <optional> <attribute name="office:process-content" a:defaultValue="true"> <ref name="boolean"/> </attribute> </optional> </define> However this pattern is not subsequently used and so will never play any part in validation -- it is useless as is. Was the intent here to enforce the values of the office:process-content attribute described above? I note the attribute declared here has a default value of "true", was the intent to convey that foreign elements not having this attribute, should be processed in the same was as if the attribute was always present with a value of "true" ? - Alex.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]