RE: [higgins-dev] Constraining a Digital Subject's attributes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

RE: [higgins-dev] Constraining a Digital Subject's attributes

From: "Paul Trevithick" <paul@xxxxxxxxxxxxxxxxx>
Date: Fri, 26 May 2006 02:12:41 -0400
Delivered-to: higgins-dev@xxxxxxxxxxx
Importance: Normal
List-archive: <http://eclipse.org/pipermail/higgins-dev>
List-help: <mailto:higgins-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/higgins-dev>, <mailto:higgins-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/higgins-dev>, <mailto:higgins-dev-request@eclipse.org?subject=unsubscribe>

Jim wrote:

Why do we need the notion of "compound" attributes to be part of the model?

Sorry, I didn’t mean to imply any special kind of compound or not-compound typing.

If an attribute's value is allowed to be any type, then the consumer would discover an attribute's type (I believe this is done using the attribute's identifier).

Yes.

<snip>

References:
- RE: [higgins-dev] Constraining a Digital Subject's attributes
  - From: Jim Sermersheim

Prev by Date: RE: [higgins-dev] IDigitalSubject attribute updates via IContext?
Next by Date: RE: [higgins-dev] Constraining a Digital Subject's attributes
Previous by thread: RE: [higgins-dev] Higgins IRC channel
Next by thread: RE: [higgins-dev] Constraining a Digital Subject's attributes
Index(es):
- Date
- Thread

Breadcrumbs