- From: <bugzilla@jessica.w3.org>
- Date: Thu, 29 Mar 2012 08:14:59 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16232
Tim Mills <tim@cbcl.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CLOSED |REOPENED
Resolution|FIXED |
--- Comment #5 from Tim Mills <tim@cbcl.co.uk> 2012-03-29 08:14:59 UTC ---
I think there may be yet more dependencies which should be noted.
Any function which takes an explicit $collation parameter depends not only on
the static context (available collations), but also on the dynamic context
(dynamic base URI), since the argument may be a relative URI which would
require resolution against the dynamic base URI.
I'm assuming that when the collation is implicit, the default collation is
always resolved to an absolute URI (against the static base URI), and therefore
there is no dependency on the dynamic base URI in this case.
I'm of the opinion that the dependency on the dynamic base URI is unfortunate.
Since the available collations are part of the static context, and therefore
the collation URIs are known statically, it seems strange that collation URIs
would not be resolved against the static base URI (as in F&O 1.0) rather than
the dynamic base URI.
The functions format-dateTime, format-date and format-time depend on the
dynamic context default language, deffault calendar and default place
properties.
The functions doc, doc-available, collection, uri-collection, unparsed-text,
unparsed-text-available and unparsed-text-lines depend on the dynamic base URI
(in addition to the dependencies already listed in the specification).
The specification often says that a funciton depends on the "base uri", rather
than "dynamic base uri".
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 29 March 2012 08:16:54 UTC