W3C home > Mailing lists > Public > w3c-sgml-wg@w3.org > May 1997

Re: Link-1: Syntax

From: Weichel Bernhard (K3/EES4) <Bernhard.Weichel@pcm.bosch.de>
Date: Tue, 20 May 1997 05:39:36 +0900
Message-Id: <9705201910.AA05559@si0887.si.bosch.de>
To: "w3c-sgml-wg@w3.org" <IMCEAX400-c=DE+3Ba=DBP+3Bp=BOSCH-01+3Bo=X400+3Bou1=MAIL02+3Bdda+3ASMTP=w3c-sgml>



> ----------
> Von: 	Tim Bray[SMTP:tbray@textuality.com]
> Gesendet: 	Sonntag, 18. Mai 1997 20:37
> An: 	w3c-sgml-wg@w3.org
> Betreff: 	Link-1: Syntax
> 
> We have a botch at the moment in that the hyperlink #HERE is
> ambiguous,
> does it mean the linking element, or does it mean ID(HERE)?  We need
> to
> fix the syntax to solve this.  Solutions I have thought of include:
> 
> (1) putting the whole xpointer in parentheses, unless it's just an ID
> value
>     e.g. HREF="#(HERE), or 
> 
The comma would not be required?

I Really treat this one as the best solution. It does not conflict with
existing HTML - links.
I do not like languages, with many reserved words resp. where tokens can
only be identified with regard to the context.

> (2) requiring that keywords such as HERE always be followed by a
> comma, 
>     even if there's nothing after the comma,
>     e.g. HREF="#HERE,"
> 
This proposal resolves the ambiguity at the end of the expression.
Having nothing after the comma isnīt smart either.


> Regards/Mit freundlichen Gruessen
> ======================================================================
> ========
> Bernhard Weichel              Phone:  (49) 711 811 8322
> Robert Bosch GmbH               Fax:  (49) 711 811 8262
> Dept. K3/EES4                 eMail:  bernhard.weichel@pcm.bosch.de
> P.O. Box 30 02 40                     
> D-70442 Stuttgart
> Germany
> 


Received on Tuesday, 20 May 1997 15:11:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:26 UTC