From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/5871
Path: main.gmane.org!not-for-mail
From: Simon Pepping <spepping@scaprea.hobby.nl>
Newsgroups: gmane.comp.tex.context
Subject: XML attributes
Date: Sat, 13 Oct 2001 23:08:22 +0200
Sender: owner-ntg-context@let.uu.nl
Message-ID: <20011013230822.A897@scaprea>
NNTP-Posting-Host: coloc-standby.netfonds.no
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: main.gmane.org 1035396437 5346 80.91.224.250 (23 Oct 2002 18:07:17 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Wed, 23 Oct 2002 18:07:17 +0000 (UTC)
Original-To: ntg-context@ntg.nl
Xref: main.gmane.org gmane.comp.tex.context:5871
X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:5871

I have been experimenting a bit with attributes, e.g. in this phrase:
<item>And even worse<ref/>, <ref name="att"/> attributes <ref/> will not be the
same as in &context;.</item>

1. In the third ref element, the value \XMLpar{ref}{name}{\relax} is
   not relax. Because the element has no (rather an implicit)
   attribute name, the context value is left as it was set by the
   preceding ref element. I think it would be better if attribute
   values are local to the element, and there exists a command that
   lets the user store the value in a control sequence, much like
   \defXMLstring\command.

2. When I use the attribute like this:
   \doifXMLparelse{ref}{name}{(ref:\XMLpar{ref}{name}{})}{}, it would
   be nice to have a shorter way to access the attribute value, say
   \XMLattvalue. The above code contains two implicit if/then branches
   for the attribute, the second not very useful.

Regards, Simon

-- 
Simon Pepping
email: spepping@scaprea.hobby.nl