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

Re: Co-operating with Architectural Forms

• To: xml-dev@l...
• Subject: Re: Co-operating with Architectural Forms
• From: Joe English <jenglish@f...>
• Date: Thu, 31 Jan 2002 12:53:05 -0800
• In-reply-to: <5.1.0.14.2.20020131165520.00a7ece8@p...>
• References: <5.1.0.14.2.20020131165520.00a7ece8@p...> <3C58F0CA.C6D43D92@r...> <3C58F0CA.C6D43D92@r...> <NCBBKFMJCLIMOBIGKFMJMEAIHCAA.ldodds@i...> <200201301936.g0UJaOj12628@d...>

Sean McGrath wrote:
> >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.

All of it, but that's comparing apples and screwdrivers :-)

The AFDR, if viewed as a transformation language, is extremely
lightweight; there's not much you can do with it.  Although
it could be used to turn a full newsfeed into an RSS channel
or DocBook into HTML (but not the kind of HTML you'd want
to build a web site out of), it's much more useful as a
design tool.

The basic idea is, instead of writing software to work on
a particular concrete document type, write it as an architectural
processor; most of the time this just means keying off of #FIXED
attributes instead of element type names.  Then it can work
with any concrete document type that conforms to the architecture;
most of the time this can be accomplished just by adding a
few #FIXED attributes to the DTD.

Now the HyTime AFDR mechanism is clearly inappropriate for XML,
since it relies heavily on DTDs for ease-of-use, but the concepts
behind it should be useful.


--Joe English

  jenglish@f...

• Follow-Ups:
  • Re: Co-operating with Architectural Forms
    • From: Sean McGrath <sean.mcgrath@p...>

• References:
  • Re: Co-operating with Architectural Forms
    • From: Sean McGrath <sean.mcgrath@p...>
  • 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...>

• Prev by Date: Re: Co-operating with Architectural Forms
• Next by Date: RE: Co-operating with Architectural Forms
• Previous by thread: Re: Co-operating with Architectural Forms
• Next by thread: Re: Co-operating with Architectural Forms
• Index(es):
  • Date
  • Thread