OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: Architectural Forms and XAF

[ Lists Home | Date Index | Thread Index ]
  • From: David Wang <dwang@mitre.org>
  • To: Arjun Ray <aray@q2.net>
  • Date: Thu, 02 Mar 2000 09:06:43 -0500

> If you mean
>   <foo><bar>baz</bar></foo>  <==>  <foo bar="baz">
> that's right: AFs don't provide for this.  (There a number of "good"
> reasons, but that's a separate debate.  I'm sorely tempted to offer a
> reason or two, but I desist...)

Oh, give in to the temptation! :-)  I'm sorely trying to understand why
this was not allowed in AF.  Is it because of its emphasis on extraction
of information that such associations are not really useful or ?

> > and the other half is the pruning/reordering the morphologically
> > fungible parts.  Is there anything I'm grossly missing?
> The two halves are the same thing.  The rubric is attribute-based
> processing (for which, btw, plenty of precedents exist, e.g. CSS
> styling based on the CLASS attribute), in terms of which generic
> identifiers ("tagnames") are values morphologically.  

Ok, I agree that renaming isn't the point of AFs; I see what you are
saying, that the names are simply identifiers that allow content to be
freely "pruned/reordered" around.  Ahhh...

> You haven't missed anything:)

Cool. Sanity checks out. :-)


This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/threads.html


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS