Re: Fwd: [higgins-dev] Higgins data model for attribute values

[Michael McIntosh <mikemci@xxxxxxxxxx>]

higgins-dev-bounces@xxxxxxxxxxx wrote on 01/07/2008 11:25:04 PM:

> 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?

The equivalent of:
      GeneralName ::= CHOICE {
           otherName                       [0]     OtherName,
           rfc822Name                      [1]     IA5String,
           dNSName                         [2]     IA5String,
           x400Address                     [3]     ORAddress,
           directoryName                   [4]     Name,
           ediPartyName                    [5]     EDIPartyName,
           uniformResourceIdentifier       [6]     IA5String,
           iPAddress                       [7]     OCTET STRING,
           registeredID                    [8]     OBJECT IDENTIFIER}

Where the attribute "Name" or "Address" might be the same, but the
potential values have different types/formats.

>
> 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?
>
> =Drummond
>
> From:
> higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx]
> On Behalf Of
> Jim Sermersheim
> Sent:
> Friday, January 04, 2008 6:20 PM
> To:
> higgins-dev@xxxxxxxxxxx
> Subject:
> [higgins-dev] Higgins data model for attribute values
>
>
>
> Before addressing bug #190594, I need to know more about what the
> Higgins data model allows in an attribute's instance data.
>
>
>
> In IdAS, my understanding is that a Digital Subject may have 0..1
> occurrence of a particular Attribute, and that an Attribute may have
> 1..N occurrences of a particular type of Value.
>
>
>
> It's my understanding that each of an Attribute's values must be of
> the same data type, but that restriction isn't obvious to me in the
> Higgins OWL, and in fact, the opposite is reflected in the IdAS
> APIs.  In IdAS, one can state the data type of each value they add
> to an attribute.
>
>
>
> So, we need to agree on the Higgins data model regarding the types
> of attribute values.  Should the Higgins data model dictate that
> they all be of the same type, or should it allow their types to be mixed?
> <ATT00001>
> _______________________________________________
> higgins-dev mailing list
> higgins-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/higgins-dev