• To: xml-dev@l...
• Subject: Re: Co-operating with Architectural Forms
• From: Sean McGrath <sean.mcgrath@p...>
• Date: Thu, 31 Jan 2002 16:57:52 +0000
• In-reply-to: <200201311618.g0VGIYj17673@d...>
• References: <3C58F0CA.C6D43D92@r...><3C58F0CA.C6D43D92@r...><NCBBKFMJCLIMOBIGKFMJMEAIHCAA.ldodds@i...><200201301936.g0UJaOj12628@d...>

>Architectural processing as defined in the HyTime AFDR appendix
>(<URL: http://www.ornl.gov/sgml/wg8/docs/n1920/html/clause-A.3.html >)
>can:
>         + rename elements (ArcForm)
>         + rename attributes (ArcNames)
>         + map #PCDATA content to an attribute value (#CONTENT)
>         + map an attribute value to #PCDATA content (#ARCCONT)
>         + "unwrap" elements (ignore the element but process its children)
>         + ignore entire subtrees (ArcSupr)
>
>When used in combination with IMPLICIT LINK, all of these mappings
>can be context-sensitive based on ancestor elements (#USELINK)
>or previous siblings (#POSTLINK).

I'd be interested to know how much of this functionality is
available today in various humble, unassuming, non-meta-infused
tools like XML::Twig for example or XPath based mapping
systems.

Sean

• Follow-Ups:
  • Re: Co-operating with Architectural Forms
    • From: Paul Prescod <paul@p...>

• References:
  • Re: Co-operating with Architectural Forms
    • From: Ronald Bourret <rpbourret@r...>
  • Co-operating with Architectural Forms
    • From: "Leigh Dodds" <ldodds@i...>
  • Re: Co-operating with Architectural Forms
    • From: Joe English <jenglish@f...>
  • Re: Co-operating with Architectural Forms
    • From: Joe English <jenglish@f...>

• Prev by Date: Re: Auto-completion in editors (RE: ANN: XML Origin, the XML Editor & XSLT Debugger Released)
• Next by Date: "Query by example" (was Re: misprocessing namespaces)
• Previous by thread: Re: Co-operating with Architectural Forms
• Next by thread: Re: Co-operating with Architectural Forms
• Index(es):
  • Date
  • Thread