This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Are any of the functions in F&O 3.0 optional?
Or perhaps more relevantly, should the F+O specification allow host languages to cherry-pick which functions they want to support? In practice host languages will probably feel entitled to do so whether we license this or not.
Conformance to F&O is specified in the document defining the host language (e.g., XQuery), so it's not necessary to discuss such conformance issues in the F&O spec itself.