1. ODF-Specific Identifier Usage

1.1 ODF-specific nfoWorks identifiers can be for implementation-dependent/-defined features allowed for in an ODF specification. 

1.2 ODF-specific nfoWorks identifiers can be for extensions to a version of ODF.  In that case, the identifier occurrences arise as foreign-element tags, foreign attribute names, or foreign attribute values.

1.3 Extensions and implementation-dependent/defined features can also be for provisional features that are proposed in an OASIS ODF TC Committee Draft.  The nfoWorks-defined provisional identifiers are always different than reserved identifiers in the Committee Draft.  Upon approval of the reserved feature, smooth migration from provisional identifiers to reserved identifiers is possible.

1.4 ODF-specific nfoWorks identifiers can be used in RDF annotations and in OWL schemas associated with ODF documents without any particular conditions on being used in that manner.  Any recommended semantics for RDF usage will be provided in the specification of the identifier.

1.5 The definitions of each nfoWorks identifier and/or namespace specify the individual usage cases that apply:

• identification of an implementation-dependent/-defined feature
• identification of a supplemental extension involving foreign elements, attributes, or attribute values
• identification of a provisional feature that is introduced as an extension or implementation-dependent/-defined feature in anticipation of a reserved ODF feature becoming approved.

2. Application to ODF Versions

2.1 The version of ODF for which an identifier is first introduced is defined in the next segment of the identifier URI.  Applicability to earlier and subsequent versions of ODF is also specified in the definition of the nfoWorks identifier.

2.2 The current sub-segments are: