OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Namespace: CSS in addition to prefix (was: CSS instead of Namespace)


XML itself is only data, without any behaviour or presentation.

Namespace exists to specify behaviour (XInclude) or possible
behaviour (XLink), traditionaly identified with presentation
(with <a href>).

And single destination of personal namespace (not interpreting by
User Agent) is only to prevent distribution of standardized namespaces
(e.g. XInclude, XLink) to your personal XML-elements.

Are you agree with this primary position ?

Certainly, i'm sure, that
'http://www.w3.org/2001/' is redundant in
  'xmlns:x="http://www.w3.org/2001/xinclude', and
  'xmlns:x="xinclude' is enough; as well as
'http://www.w3.org/1999' is redundant in
  'xmlns:x="http://www.w3.org/1999/xlink', and
  'xmlns:x="xlink' is enough;

>> RK> What happens when the same name appears in two different namespaces?

The same, independently where name is specified: in prefix or in
separate file.

Of course, i count this question quite artificial:
if user chose one name for two and much namespaces, he make mistake;
if one name with different namespace definitions is in different
XML-files, then applying of name is limited by border of file.

Dmitry Turin
HTML6     (6. 5.4)  http://html60.euro.ru
SQL5      (5.11.3)  http://sql50.euro.ru
Unicode7  (7. 2.1)  http://unicode70.euro.ru
Computer2 (2. 0.2)  http://computer20.euro.ru

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS