blocks|key|379865|text|对于XHTML+1.0，您只能使用XHTML+1.0元素和属性：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|379866|Normative+Definition+of+XHTML+1.0|offset|length|379867|379868|这个版本的XHTML提供了严格符合XHTML1.0文档的定义，这些文档仅限于来自XHTML和XHTML1.0名称空间的元素和属性。|blockquote|379869|379870|379871|我的理解是，XHTML2.0的目标是提供一个框架来完成您想要做的事情。|379872|entityMap|0|LINK|mutability|MUTABLE|url|http://www.w3.org/TR/xhtml1/#normative^0|0|0|X|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|F|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|11|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|14|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

For XHTML 1.0 you are restricted to XHTML 1.0 elements and attributes:

<a href="http://www.w3.org/TR/xhtml1/#normative" rel="noreferrer">Normative Definition of XHTML 1.0</a>

<blockquote>
 This version of XHTML provides a definition of strictly conforming XHTML 1.0 documents, which are restricted to elements and attributes from the XML and XHTML 1.0 namespaces.
</blockquote>

My understanding is that XHTML 2.0 aims at providing a framework for doing what you want.

blocks|key|379918|text|据我所知，定义自定义名称空间是完全有效的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|379919|blockquote|379920|379921|379922|不是的。自定义名称空间在XML中格式完全正确，但是“有效”具有特定的含义，即使用的每个元素和属性都是在文档的模式中声明的。该模式可以是DTD、XML模式或其他模式，但您必须声明它。|379923|因此，您可以声明自己的模式来为语言添加自定义属性，而XHTML模块化确实使这一点变得非常简单。您必须将对DTD的引用作为<！XML添加到prolog中；仅仅设置名称空间URI并不会给DOCTYPE>处理程序提供任何钩子来查找模式本身。|379924|但是您所写的是“有效的my-language-+what+-+is+-a-bit-like-XHTML”，而不是“有效的XHTML”。其中一些‘my-language’是众所周知的，比如‘XHTML+%2BMathML%2BSVG’，但是它本身仍然不是XHTML，如果你的客户一心想要“有效的XHTML”，你就不能使用它们中的任何一种。|379925|您还会遇到潜在的浏览器问题，特别是IE，它(IE8之前的版本)对元素.*etAttribute*家族的DOM调用做了一些奇怪的事情。除非您实际将文档作为XML+Content-Type+(+IE也不能处理)提供服务，否则您的所有名称空间实际上并不使用名称空间。|379926|在XHTML5中，有人提议允许用户自定义属性(主要用于脚本目的)包含名称以‘data-’开头的属性。但同时，通常的方法是在另一个属性中隐藏值，例如class：|379927|<div+class="userid-123">...</div>|code-block|syntax|javascript|379928|然后在脚本中通过className使用适当的字符串处理来提取数据。|379929|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|-4|5|C|7|Z|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|E|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|14|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|15|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|16|8|@]|9|@]|A|$]]|$1|P|3|Q|5|R|7|17|8|@]|9|@]|A|$S|T]]|$1|U|3|V|5|6|7|18|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|X|$]]

<blockquote>
 From what I understand, defining custom namespaces is perfectly valid XHTML
</blockquote>

Nope. Custom namespaces are perfectly well-formed in XML, but ‘valid’ has the specific meaning that every element and attribute used is declared in the document's schema. That schema can be a DTD, an XML Schema, or something else, but you've got to declare it.

So you can declare your own schema to add custom attributes to the language, and indeed XHTML Modularization makes this very easy. You'd have to add the reference to the DTD as a &lt;!DOCTYPE> in the prolog; just setting namespace URIs doesn't give an XML processor any hook to find the schema in itself.

But then what you've written is “valid my-language-which-is-a-bit-like-XHTML”, and not “valid XHTML”. Some of these ‘my-languages’ are well-known, like ‘XHTML+MathML+SVG’, but it's still not XHTML as such and if your client is dead set on “valid XHTML” you can't use any of them.

You've also got potential browser problems, particularly with IE, which (pre-IE8) does some weird things with the Element.*etAttribute* family of DOM calls. And unless you're actually serving the document as an XML Content-Type (which IE also can't handle), all of your namespace stuff isn't actually using namespaces anyway.

In [X]HTML5 there is a proposal to allow user custom attributes (primarily for scripting purposes) to go in attributes whose names start with ‘data-’. But in the meantime the usual method is to hide values in another attribute, for example class:

<pre><code>&lt;div class="userid-123"&gt;...&lt;/div&gt;
</code></pre>

and then extract the data using suitable string processing over className in script.

blocks|key|1052530|text|我有一个网站，客户要求是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1052531|有效的。他们使用W3C验证器进行检查。|blockquote|1052532|1052533|1052534|我使用W3C验证器取得了一些成功，使用的不是xmlns=，而是标准的XHTML+DTD，并在末尾添加了一些属性，就像博本斯上面描述的那样。我使用它来添加PHPTAL模板系统使用的属性，比如|offset|length|style|CODE|1052535|<html+metal:define-macro="m">|code-block|syntax|javascript|1052536|我同意您需要的不是XHTML，而是XHTML的超集。但是，如果您的客户端准备简单地通过将W3C验证器指向您的URL来进行测试，那么请继续。有关建议，请参阅WDG|1052537|entityMap|0|LINK|mutability|MUTABLE|url|http://www.htmlhelp.com/design/dtd/customdtd.html^0|0|0|0|0|M|6|0|0|25|3|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|12|8|@]|9|@]|A|$]]|$1|E|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|15|8|@$I|16|J|17|K|L]]|9|@]|A|$]]|$1|M|3|N|5|O|7|18|8|@]|9|@]|A|$P|Q]]|$1|R|3|S|5|6|7|19|8|@]|9|@$I|1A|J|1B|1|1C]]|A|$]]|$1|T|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10]]]]

<blockquote>
 I have a website that a client requires to be XHTML valid. They check it using the W3C
 validator.
</blockquote>

I've had some success with the W3C validator using, not <code>xmlns=</code>, but taking the standard XHTML DTD and adding a few attributes at the end as bobince describes above. I am using this to add attributes used by the PHPTAL templating system, such as

<pre><code>&lt;html metal:define-macro="m"&gt;
</code></pre>

I agree that what you need is not XHTML but a superset of XHTML. However, if your client is prepared to test simply by pointing the W3C validator at your URL, then go ahead. For advice, see <a href="http://www.htmlhelp.com/design/dtd/customdtd.html" rel="nofollow noreferrer">WDG</a>

blocks|key|379990|text|1.0不允许这个.if你真的想这样做，你应该下载现有的dtd并将其保存在你的服务器中，并定义私有而不是公共。但w3c验证未通过，因为它仅针对原始验证|type|unstyled|depth|inlineStyleRanges|entityRanges|data|379991|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

1.0 not allowed this .if you really want to do this you should download existing dtd and save it in your server and define private instead of public. but w3c validation not passed because it validate against the orginal one only

I have a website that a client requires to be XHTML valid. They check it using the W3C validator.

I want to add my own namespace and attributes so I can do things like this:

<pre><code>&lt;div my:userid="123"&gt; ... &lt;/div&gt;
</code></pre>

From what I understand, defining custom namespaces is perfectly valid XHTML, as long as I do this:

<pre><code>&lt;html xmlns="http://www.w3.org/1999/xhtml" xmlns:my="http://www.example.com/my"&gt;
</code></pre>

However, my XHTML fails validation. The problem appears to be that the validator does not actually go out and check my custom DTD document for my custom namespace, it only checks the XHTML against known DTD's. Anyone able to shed any light on how I can solve this problem?

XHTML validation, custom namespaces and attributes

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个网站，客户要求是XHTML有效。他们使用W3C验证器进行检查。我想添加我自己的名称空间和属性，这样我就可以这样做：<div my:userid="123"> ... </div>据我所知，定义自定义名称空间是完全有效的XHTML，只要我这样做：<html xmlns="http://www.w3.org/199...

问XHTML验证、自定义名称空间和属性
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问XHTML验证、自定义名称空间和属性EN