[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: semantic overloading
- From: Nicolas LEHUEN <firstname.lastname@example.org>
- To: "'Simon St.Laurent'" <email@example.com>,"'firstname.lastname@example.org'" <email@example.com>
- Date: Thu, 30 Aug 2001 15:36:59 +0200
I'm going to anticipate the upcoming debate here ;). Contrary to what Rick
may think (as a follow-up to the "enlightement" thread) I do agree with the
sentence "avoid semantic overloading when possible". Supporting
context-sensitive local element names does not means that I try to have as
many duplicate element names as possible when designing a schema.
Context-sensitive local elements are just a way to better handle the name
clashes that can appear when a schema evoluates, that's all.
Context-sensitiveness is also a way to allow for richer semantics. It
assumes that a single name is not sufficient to capture all possible
semantics. Sometimes, you have to embed names into other names and so on to
reflect some complex semantics. That's why XML is successfull in
representing documents or complex structures, whereas other technologies
with less possibilities for building context are less efficient.
>De : Simon St.Laurent [mailto:firstname.lastname@example.org]
>Envoyé : mercredi 29 août 2001 19:05
>À : email@example.com
>Objet : semantic overloading
>The W3C has just released a Working Draft of XML Accessibility
>Perhaps especially worth noting in regard to the recent namespace
>discussions is this bit:
>> If an element name may be confused, within the context of the
>> document instance, then it is said to be overloaded. If each element
>> name is unique within context it is easier to access the
>> document semantics.
>I think they mean "document instance context", given the examples which
>It's some genuinely interesting stuff.
>The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
>initiative of OASIS <http://www.oasis-open.org>
>The list archives are at http://lists.xml.org/archives/xml-dev/
>To subscribe or unsubscribe from this elist use the subscription