Web This site Trusted
30 result(s) for “if com target site whattodrink com site spec openapi org site:www.w3.org” of 49 matched · 754 ms
Scope: Nishi’s own index (our crawl + Common Crawl) — not the whole live web. Some sites block all automated crawlers (anti-bot walls), so their pages may be absent here even though we never filter lawful content.
Did you mean if com target site whattodrink com site spec openai org site:www.w3.org?
Freshness: newest result fetched 23 d ago · median age of these results 23 d · 18 of 30 carry a fetch time
org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www
from the top result below
https://www.w3.org/TR/2025/WD-shacl12-core-20250318/
org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www
https://www.w3.org/TR/2012/WD-xslt-30-20120710/
If access to that system is not feasible, you may send your comments to the W3C XSLT/XPath/XQuery public comments mailing list, public-qt-comments@w3
https://www.w3.org/TR/2026/REC-pointerevents3-20260630/
PointerEvent) {
// if Pointer Events are supported, only listen to pointer events
target
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29865
I've submitted a slew of tests - my apologies if it spoils your weekend
https://www.w3.org/XML/Query/test-suite/XQTSReport.html
com/site2/doc/latest/cxx/html/classzorba_1_1DiagnosticHandler
https://www.w3.org/TR/REC-xml/
com>François Yergeau
The previous errata for this document, are also available
https://www.w3.org/TR/2001/WD-xslt11-20010824/
com>
This specification defines the syntax and semantics of XSLT, which is a language for transforming XML documents into other XML documents
https://www.w3.org/community/reports/
org, that enable discovery of accessible content
https://www.w3.org/TR/epub-a11y-11/
org/TR/2024/REC-epub-a11y-11-20241017/ Latest published version: https://www
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29602
1 spec refers to the "option parameter conventions" which define the common (cross-function) rules for option parameters
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29889
org/Archives/Public/public-xsl-wg/2016Sep/0001
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29696
org/Archives/Public/public-xsl-wg/2016Jun/0000
https://www.w3.org/Guide/documentreview/
org if needed (in case the default notice sent to that list is not enough)
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29819
org/2005/xpath-functions/math; plus functions defined in this specification in namespace http://www
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29507
org/Archives/Public/public-xsl-wg/2016Mar/0000
https://www.w3.org/TR/2025/WD-css-gaps-1-20250417/
org/TR/2025/WD-css-gaps-1-20250417/ Latest published version: https://www
https://www.w3.org/TR/page-visibility-2/
org/TR/2022/DISC-page-visibility-2-20220623/ Latest published version: https://www
https://www.w3.org/TR/audiobooks/
org/TR/2020/REC-audiobooks-20201110/ Latest published version: https://www
https://www.w3.org/TR/2017/PR-css-ui-3-20171214/
org/TR/2017/PR-css-ui-3-20171214/ Latest published version: https://www
https://www.w3.org/TR/dx-prof/
org/ns/dx/prof/, however, PROF makes use of terms from other vocabularies, in particular Dublin Core [DCTERMS]
https://www.w3.org/TR/wai-aria-1.2/
A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29933
29933 – [XSLT30] Discrepancy between serialization spec and XSLT spec on undeclare-prefixes
Bugzilla – Bug 29933 [XSLT30] Discrepancy between serialization spec and XSLT spec on undeclare-prefixes Last modified: 2016-10-13 19:28:06 UTC
This is an archived snapshot of W3C's public bugzilla bug tracker
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29431
” I wonder if
it’s worth observing that this is logically possible only through
some API or other interface that is out of scope for this spec
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29482
I think my preference is NOT to make this guaranteed streamable: (a) it complicates the spec; (b) complicates my implementation; (c) I think it's not easy to convince ourselves that we aren't opening up lots of unintended consequences if we make a change here
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29453
Comment 4 Max Toro 2016-03-02 15:43:15 UTC
It would be very helpful if you could elaborate on the import precedence issues, the spec already disallows declarations that are homonymous with accepted and overriding components
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29763
I don't think this was an intended behavior and if the WG agrees, I would like this behavior to be an error scenario: an xsl:param cannot be overridden by an xsl:variable, or the other way around
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29604
org/TR/xslt-30/#stream-examples
Bugzilla – Bug 29604 [XSLT30] Request for clarification of statement in section https://www
https://www.w3.org/International/i18n-activity/i18n-wg/
Minutes and summaries of all teleconferences and face-to-face meetings can be found in the meeting minute browser and the www-international mail archive
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29256
3 says (just below the definition of error 3060):
A package is executable if and only if it contains no component whose visibility is abstract
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29455
This is not an empty sequence, it is not a zero-length text node, and it is not a document node with no children, therefore according to the spec (whether we like it or not