Re: [syndication] Progress with Scripting News in OPML

["Dave Winer" <dave@userland.com>]

Hi Dave.

That's a FAQ.

When I design an important XML format, before I write any code or specs, I
create a sample document and edit it until I feel it reflects the data it's
trying to represent.

That the text attribute is just an attribute reflects my belief that text is
just an attribute. (Sounds kind of obvious, eh?)

The structure of the outline is the reason for OPML existing, so I didn't
want anything interfering with that.

It is even possible to imagine an OPML document whose outlines don't even
have text attributes.

Maybe that's all there is to say right now -- but the format appears to be
working pretty well, so far. ;->

Dave

----- Original Message -----
From: <dave.cantrell@gunter.af.mil>
To: <syndication@yahoogroups.com>
Sent: Monday, September 24, 2001 7:29 AM
Subject: RE: [syndication] Progress with Scripting News in OPML


> Hi Dave,
>
> I have a technical/design question regarding your OPML format. Since I've
> never really looked into OPML other than a quick look when you first
created
> it a while back, maybe there is an obvious answer to this -- if so please
> educate me.
>
> Why do you escape elements and stuff them into attributes, rather than
nest
> them as standard XML/XHTML elements inside of the OPML outline element? I
> can see the argument of allowing for those who write vanilla HTML without
> proper nesting, but it really takes minimal effort for someone to switch
> from plain HTML to properly-nested HTML. You could even make this an
option
> in Manila to impose strict element nesting on all inputs (and therefore
> return an error if someone attempts to create/edit an item without proper
> nesting) or use standard HTML. By imposing this small restriction, it
allows
> aggregators to access the full document in all it's semantic richness.
>
> Of course you already have products developed around this spec and design
so
> I don't expect you to change it. I'm just trying to "get my head around
it"
> and understand the thoughts that went into this particular design
approach.
>
> Thanks,
> -dave
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>