W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 1996

RE: Attributes in Prelim DAV Spec

From: Yaron Goland <yarong@microsoft.com>
Date: Mon, 11 Nov 1996 10:58:52 -0800
Message-ID: <c=US%a=_%p=msft%l=RED-44-MSG-961111185852Z-30353@mail4.microsoft.com>
To: "'Judith Slein'" <slein@wrc.xerox.com>
Cc: "'w3c-dist-auth@w3.org'" <w3c-dist-auth@w3.org>
You read my mind. I already made that exact change to the spec. =)
		Yaron

>-----Original Message-----
>From:	Judith Slein [SMTP:slein@wrc.xerox.com]
>Sent:	Monday, November 11, 1996 8:45 AM
>To:	Yaron Goland
>Cc:	w3c-dist-auth@w3.org
>Subject:	RE: Attributes in Prelim DAV Spec
>
>At 03:30 PM 11/8/96 PST, Yaron Goland wrote:
>>>The case I'm pointing to is where one attribute itself has attributes.
>>>Maybe the syntax here is just http://foo/bar<Abstract><Author>, where
>>><Author> identifies the person who wrote the <Abstract> attribute of the
>>>bar
>>>resource.
>>>
>>>[Yaron Goland]  This is illegal with the current syntax. It should really
>>>be
>>>done with Abstract.Author. Still that is not a clean solution. I have no
>>>problem extending the syntax to handle this case. Thoughts?
>>>
>>>
>Then let me propose that we make the syntax I used above legal for
>identifying attributes of attributes.  It probably should be legal to nest
>attributes as deep as you like, although it's hard to imagine really wanting
>to go deeper than two levels.
>
>URI = (absoluteURI | relativeURI) *("<" Attribute ">") ["#" fragment]
>
>--Judy
>Name:		Judith A. Slein
>E-Mail:		slein@wrc.xerox.com
>Phone:  	8*222-5169
>Fax:		(716) 265-7133
>MailStop:	128-29E
>
Received on Monday, 11 November 1996 14:05:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:41 GMT