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

Re: misprocessing namespaces (was Re: There is

• To: <xml-dev@l...>
• Subject: Re: misprocessing namespaces (was Re: There is a meaning, but it's not in the data alone)
• From: "Rick Jelliffe" <ricko@a...>
• Date: Tue, 5 Feb 2002 13:10:58 +1100
• References: <5.1.0.14.2.20020203204729.024ed7c0@p...> <5.1.0.14.2.20020131082226.02822ec0@p...> <4XOKTPSQ3W1VLJ9607AZVUSBAUOYX05.3c586905@MChamp> <093701c1a9f2$71c37820$0a2e249b@n...> <3C589A61.95139DF@p...> <5.1.0.14.2.20020131082226.02822ec0@p...> <5.1.0.14.2.20020203204729.024ed7c0@p...> <5.1.0.14.2.20020204123240.020f76b0@p...> <3C5F01EB.1060305@r...>

 From: "John Cowan" <jcowan@r...>

> The remedy is probably (in XML 2.0) to have xml:char and xml:charref
> attributes, for defining entities and referring to files of
> entity definitions.
> 
> The value of xml:char could be something like
> "name hex name hex ..." where hex is a 1-5 digit Unicode
> code point.  xml:charref would be a URI, obviously.
 
So 

<x:x  xmlns:x="some namespace"
    xml:charref="some file of entity definitions  
    some other file of entity definitions  
    some further file of entity definitions  ">
    &xxx;
</x>

rather than

 <!DOCTYPE ... [
   <!ATTLIST x:x: xmlns:x="some namespace" >
   <!ENTITY % ent1 SYSTEM "some file of entity definitions">  %ent1;
   <!ENTITY % ent2 SYSTEM "some other file of entity definitions">   %ent2;
   <!ENTITY % ent3 SYSTEM "some further file of entity definitions">   %ent3;
 ]>

<x:x>
    &xxx;
</x:x>

Would the xml:charref be scoped?   Would editors of the text have to propogate
the references during cut-and-paste?

Cheers
Rick Jelliffe

• Follow-Ups:
  • Re: misprocessing namespaces (was Re: Thereis a meaning, but it's not in the data alone)
    • From: John Cowan <cowan@m...>

• References:
  • Re: misprocessing namespaces (was Re: There is a meaning, but it's not in the data alone)
    • From: Tim Bray <tbray@t...>
  • Re: misprocessing namespaces (was Re: There is a meaning, but it's not in the data alone)
    • From: Tim Bray <tbray@t...>
  • Re: misprocessing namespaces (was Re: There is a meaning, but it's not in the data alone)
    • From: John Cowan <jcowan@r...>

• Prev by Date: Re: Categories of Web Service messages: data-oriented v s action-oriented
• Next by Date: RE: Categories of Web Service messages: data-oriented v s action-oriented
• Previous by thread: Re: misprocessing namespaces (was Re: There is a meaning, but it's not in the data alone)
• Next by thread: Re: misprocessing namespaces (was Re: Thereis a meaning, but it's not in the data alone)
• Index(es):
  • Date
  • Thread