• To: clbullar@i... ("Bullard, Claude L (Len)")
• Subject: Re: linking, 80/20
• From: John Cowan <jcowan@r...>
• Date: Mon, 19 Aug 2002 16:41:13 -0400 (EDT)
• Cc: martind@n... ('Didier PH Martin'), xml-dev@l...
• In-reply-to: <2C61CCE8A870D211A523080009B94E430752B824@HQ5> from "Bullard, Claude L (Len)" at Aug 19, 2002 02:56:03 PM

"Bullard, Claude L (Len)" scripsit:
> 
> To parse it for well-formedness, no.  To do anything
> past that, yes.  It will be in the documentation.  As 
> Jonathan said, progress is made in the semantic world 
> by having a precise formal kind of documentation for 
> the namespace.   Umm... from genCoding to Document 
> Type Definitions.  We seem to be deja re-viewing.
> 
> Choose:
> 
> NOTATION - tell me where the processor for this 
> element is (inline)

NOTATIONs are types.

> MIME - give me a name for finding a processor for 
> this document is (objects are ortho-docs)

Media types.

> namespace - tell me where to find the instructions 
> for building a processor for this guy is, or for 
> finding the directions to where the processor for 
> this guy is, or where the processor is and 
> I can figure out the scope of this guy if you 
> did it all correctly

Naah.  Namespaces are designed to prevent name collisions and that's it.
Anything else is all in your head.

-- 
De plichten van een docent zijn divers,         John Cowan
die van het gehoor ook.                         jcowan@r...
      --Edsger Dijkstra                         http://www.ccil.org/~cowan

• Follow-Ups:
  • Re: linking, 80/20
    • From: Elliotte Rusty Harold <elharo@m...>

• References:
  • RE: linking, 80/20
    • From: "Bullard, Claude L (Len)" <clbullar@i...>

• Prev by Date: Re: linking, 80/20
• Next by Date: Re: linking, 80/20
• Previous by thread: RE: linking, 80/20
• Next by thread: Re: linking, 80/20
• Index(es):
  • Date
  • Thread