From 5522f9b99e0449ec7721aa406d2ff3e2bfad8ece Mon Sep 17 00:00:00 2001 From: William Victor Mote Date: Sun, 8 Dec 2002 23:03:34 +0000 Subject: This file corresponds to fop4.xsd, revision 1.1, checked in by pbwest. Original log message: fop4f.xsd with s stripped at tabstops of 2. git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@195738 13f79535-47bb-0310-9956-ffa450edef68 --- docs/foschema/fop.xsd | 8534 ++++++++++++++++++++++++------------------------- 1 file changed, 4267 insertions(+), 4267 deletions(-) (limited to 'docs') diff --git a/docs/foschema/fop.xsd b/docs/foschema/fop.xsd index 40f19d0b4..9b5a625ba 100644 --- a/docs/foschema/fop.xsd +++ b/docs/foschema/fop.xsd @@ -1,4292 +1,4292 @@ - - + + - I'm not sure where to place this. - It applies to the page context (NOT implemented) - - - I have not coded for the functions described in 5.10 Core Function Library - They need to be segregated into groups and then inserted in the types - - common_functions - object inherited-property-value(NCName) - object from-parent( NCName) - object from-nearest-specified-value( NCName) - object merge-property-values( NCName) - - font_functions - object system-font( NCName , NCName) - - length_functions - numeric floor( numeric) - numeric ceiling(numeric) - numeric round(numeric) - numeric min( numeric , numeric) - numeric max(numeric , numeric) - numeric abs( numeric) - - table_cell_or_descendants_functions - object from-table-column( NCName) + I'm not sure where to place this. + It applies to the page context (NOT implemented) + + + I have not coded for the functions described in 5.10 Core Function Library + They need to be segregated into groups and then inserted in the types + + common_functions + object inherited-property-value(NCName) + object from-parent( NCName) + object from-nearest-specified-value( NCName) + object merge-property-values( NCName) + + font_functions + object system-font( NCName , NCName) + + length_functions + numeric floor( numeric) + numeric ceiling(numeric) + numeric round(numeric) + numeric min( numeric , numeric) + numeric max(numeric , numeric) + numeric abs( numeric) + + table_cell_or_descendants_functions + object from-table-column( NCName) - color_functions - color rgb(numeric , numeric , numeric) - color rgb-icc(numeric , numeric , numeric , NCName , numeric , numeric) - color system-color( NCName) + color_functions + color rgb(numeric , numeric , numeric) + color rgb-icc(numeric , numeric , numeric , NCName , numeric , numeric) + color system-color( NCName) - label_functions - numeric body-start() - numeric label-end() - - (defined) - table-column_functions - numeric proportional-column-width( numeric) - - This schema has been developed in order to validate XSL FO documents for FOP - All of the elements need to be prefixed with fo: - The namespace prefix is xmlns:fo = "http://www.w3.org/1999/XSL/Format". + label_functions + numeric body-start() + numeric label-end() + + (defined) + table-column_functions + numeric proportional-column-width( numeric) + + This schema has been developed in order to validate XSL FO documents for FOP + All of the elements need to be prefixed with fo: + The namespace prefix is xmlns:fo = "http://www.w3.org/1999/XSL/Format". - This schema, as delivered, may either validate the full spec, or, just the FOP portion. - (What it validates depends upon what I was doing with it when released.) - - If you want to restrict it to just those elements and attributes implemented by FOP, - you need to edit the and tags to exclude the groups ending with _Not + This schema, as delivered, may either validate the full spec, or, just the FOP portion. + (What it validates depends upon what I was doing with it when released.) + + If you want to restrict it to just those elements and attributes implemented by FOP, + you need to edit the and tags to exclude the groups ending with _Not - Some schema tools complain about the placement of comments in this schema and will remove or reorder them - There are fop_result and fop_fail comments on specific features not implemented by FOP + Some schema tools complain about the placement of comments in this schema and will remove or reorder them + There are fop_result and fop_fail comments on specific features not implemented by FOP - FOP does not enforce the following schema requirements + FOP does not enforce the following schema requirements - fo:simple-page-master model = "(region-body,region-before?,region-after?,region-start?,region-end?)" - elements can be in any order + fo:simple-page-master model = "(region-body,region-before?,region-after?,region-start?,region-end?)" + elements can be in any order - fo:table-cell model = "(%block;)+" - Can be empty + fo:table-cell model = "(%block;)+" + Can be empty - fo:flow model = "(%block;)+" - Can be empty + fo:flow model = "(%block;)+" + Can be empty - This schema allows the length attribute to be negative for some elements like margins. - There may be instances where I've entered %integer_Type; and it should be positive-integer or number - The schema trys to handle the text based rules re: fo:markers, fo:float, footer and fo:initial-property-set - But, allows you to do illegal things if you want because I couldn't figure out how to constrain against the illegal actions. + This schema allows the length attribute to be negative for some elements like margins. + There may be instances where I've entered %integer_Type; and it should be positive-integer or number + The schema trys to handle the text based rules re: fo:markers, fo:float, footer and fo:initial-property-set + But, allows you to do illegal things if you want because I couldn't figure out how to constrain against the illegal actions. - Please e-mail your comments to cpaussa@myrealbox.com + Please e-mail your comments to cpaussa@myrealbox.com - Contribution by Oleg Tkachenko - (Declarations able to include non-xsl children) - - This declaration assumes that all elements must come before other stuff, - which is not required by spec, but I cannot see any way to express such constraints in schema, - one could use instead of , but this way we lose control over (color-profile)+ constraint. + Contribution by Oleg Tkachenko + (Declarations able to include non-xsl children) + + This declaration assumes that all elements must come before other stuff, + which is not required by spec, but I cannot see any way to express such constraints in schema, + one could use instead of , but this way we lose control over (color-profile)+ constraint. - - + + - - - - - - - - - empty group so cannot be defined - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - empty group so cannot be defined - - - - - - - - - - - - - - empty group - - - - - - - - - - - - - - + + + + + + + + + empty group so cannot be defined + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + empty group so cannot be defined + + + + + + + + + + + + + + empty group + + + + + + + + + + + + + + - - - - - - - - - - + + + + + + + + + + - - - - - - - - - - - + + + + + + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - Removed because I'm not sure how to handle this - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Inheritable - - - - - - - - - - - - - - - - - - - - - - - - - - Inheritable - - - - - - - - - - - - - - - - Inheritable - - - - - - - - - - - - - - - - - Inheritable - - - - - - - - - - - - - - Inheritable attributes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Inherited - - - - - - - - - - - - - - - - - - - - - - Inherited - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Inherited - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Font properties are all inheritable - - - - - - - - - - - Font properties are all inheritable - - - - - - - - - - - - - - - - The hyphenation properties are all inheritable and so superceeded by that list - - - - - - - - - - - - - The hyphenation properties are all inheritable and so superceeded by that list - - - - - - - - - - - - - - - - - - Indent properties are inheritable - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + Removed because I'm not sure how to handle this + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Inheritable + + + + + + + + + + + + + + + + + + + + + + + + + + Inheritable + + + + + + + + + + + + + + + + Inheritable + + + + + + + + + + + + + + + + + Inheritable + + + + + + + + + + + + + + Inheritable attributes + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Inherited + + + + + + + + + + + + + + + + + + + + + + Inherited + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Inherited + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Font properties are all inheritable + + + + + + + + + + + Font properties are all inheritable + + + + + + + + + + + + + + + + The hyphenation properties are all inheritable and so superceeded by that list + + + + + + + + + + + + + The hyphenation properties are all inheritable and so superceeded by that list + + + + + + + + + + + + + + + + + + Indent properties are inheritable + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - Simple Types definitions - - - - - - A signed integer value which consists of an optional '+' or '-' character followed by a sequence of digits. A property may define additional constraints on the value. - - - - - - - - - - - - - - - A signed real number which consists of an optional '+' or '-' character followed by a sequence of digits followed by an optional '.' character and sequence of digits. A property may define additional constraints on the value. - - - - - - - - - - - - - A signed length value where a 'length' is a real number plus a unit qualification. A property may define additional constraints on the value. - - - - - - - - - - - - - - - - A compound datatype, with components: minimum, optimum, maximum. Each component is a . If "minimum" is greater than optimum, it will be treated as if it had been set to "optimum". If "maximum" is less than optimum, it will be treated as if it had been set to "optimum". A property may define additional constraints on the values. - - - - - - - - - - - - - - - - - - - - - A compound datatype, with components: length, conditionality. The length component is a . The conditionality component is either "discard" or "retain". A property may define additional constraints on the values. - - - - - - - - - - - - - - - - - - - - - - - - A compound datatype, with components: block-progression-direction, and inline-progression-direction. Each component is a . A property may define additional constraints on the values. - - - - - - - - - - - - - - - - - - - - - A compound datatype, with components: minimum, optimum, maximum, precedence, and conditionality. The minimum, optimum, and maximum components are s. The precedence component is either "force" or an . The conditionality component is either "discard" or "retain". If "minimum" is greater than optimum, it will be treated as if it had been set to "optimum". If "maximum" is less than optimum, it will be treated as if it had been set to "optimum". - - - - - - - - - - - - - A representation of an angle consisting of an optional '+' or '-' character immediately followed by a immediately followed by an angle unit identifier. Angle unit identifiers are: 'deg' (for degrees), 'grad' (for grads), and 'rad' (for radians). The specified values are normalized to the range 0deg to 360deg. A property may define additional constraints on the value. - - - - - - - - - - - - - A signed real percentage which consists of an optional '+' or '-' character followed by a sequence of digits followed by an optional '.' character and sequence of digits followed by '%'. A property may define additional constraints on the value. - - - - - - - - - - - - - - - - - - - - - - - - - - - - A string of characters representing a name. It must conform to the definition of an NCName in - - - - - - - - - - A string of characters identifying a font. - - - - - - - - - - - - - - - - - - - - - - - Either a string of characters representing a keyword or a color function defined in . The list of keyword color names is: aqua, black, blue, fuchsia, gray, green, lime, maroon, navy, olive, purple, red, silver, teal, white, and yellow. - - - - - - - - - - - - The function proportional-column-width(N[0]) - This returns a width as a fraction of the available width as ( N[0] / sum1 ) * available space - The parent table must have width="x" and table-layout="fixed" - - - - - - - - - - - , , proportional-column-width, or common-functions - - - - - - - - -