[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: [3] Namespace: CSS in addition to prefix (was: CSS instead

• From: "bryan rasmussen" <rasmussen.bryan@g...>
• To: "Dmitry Turin" <dev3os@n...>
• Date: Thu, 21 Feb 2008 11:08:51 +0100

On Thu, Feb 21, 2008 at 8:19 AM, Dmitry Turin <dev3os@n...> wrote:
> Manos,
>
>  BR> CSS is useful for  ... what is inessential to understanding of the data
>
>  Agreed.
>
>  BR> namespaces (as currently defined) are an essential
>  BR> part of understanding what the data is.
>
>  Empty words.
well thank you

>
>  Certainly, i'm disagreed.
>  Look at XInclude - namespace describes behaviour (already existed in CSS).
>  Look at XLink - namespace describes presentation (compare with
>   http://www.w3.org/TR/css3-ui/#appearance ).
>
The difference between these two specifications and a data
specification such as UBL or FPML is that the data of the former
describes behavior and the data of the latter describe financial data.
Executable instructions are still data to a computer. The typical
scenario described for namespaces are that there is an element with
the same name in two namespaces with radically different meanings and
we want to combine these two sources of data, in such a case we need
to have a way to differentiate between the combined data otherwise we
do not know what the meaning is of the data. Namespaces are thus
essential to understanding the meaning of the data, whether said data
is 'behavioral' or of the sort that people more generally talk of when
they discuss 'DATA'

• Follow-Ups:
  • [main] Namespace: file with rules instead of tag's prefix (was: Namespace: CSS in addition to prefix (was: CSS instead of Namespace)}
    • From: Dmitry Turin <dev3os@n...>

• References:
  • CSS instead of Namespace
    • From: Dmitry Turin <dev3os@n...>
  • Re: CSS instead of Namespace
    • From: Manos Batsis <manos_lists@g...>
  • [3] Namespace: CSS in addition to prefix (was: CSS instead of Namespace)
    • From: Dmitry Turin <dev3os@n...>