|Re: Fwd: [higgins-dev] Higgins data model for attribute values|
Thanks for the feedback, all.
This is as I expected. I have heard some use cases for allowing an attribute's values to be different data types -- similar to specifying that an element in an xml schema be of xsd:any type. One case I remember that Daniel brought up was like: What if I have an attribute which represents a telephone number and I want to allow different data types (strings as well as numbers) to be stored?
Daniel or others can probably provide more compelling arguments.
>>> "Markus Sabadello" <msabadello@xxxxxxxxxxxxx> 01/07/08 1:38 PM >>>
Begin forwarded message:
From: Paul Trevithick <paul@xxxxxxxxxxxxx >
Date: January 7, 2008 3:13:12 PM EST
To: "Higgins (Trust Framework) Project developer discussions" <higgins-dev@xxxxxxxxxxx >
Cc: "Higgins (Trust Framework) Project developer discussions" <higgins-dev@xxxxxxxxxxx>
Subject: Re: [higgins-dev] Higgins data model for attribute values
Wrt the higgins data model all values must be of the same type.
As for higgins.owl, I'm working on a rev that will address this and other related issues
On Jan 7, 2008, at 1:13 PM, Drummond Reed <drummond.reed@xxxxxxxxxxxx> wrote:
Good question, Jim. My assumption would have been that if an Attribute allows multiple values, they all would be of the same data type. Is there a use case for an Attribute having multiple values with different data types?
Back to the top