Re: [higgins-dev] FW: Changes to higgins.owl (incorporated in v1.9)

["Jim Sermersheim" <jimse@xxxxxxxxxx>]

>From: Paul Trevithick [mailto:paul@xxxxxxxxxxxxxxxxx] 
>Sent: Thursday, October 19, 2006 12:01 AM
>To: 'Higgins (Trust Framework) Project developer discussions'
>Subject: Changes to higgins.owl (incorporated in v1.9)
>
>I have just committed my first batch of changes to higgins.owl. I
>thought
>I'd start with the less controversial changes first:
>
>- uniqueIdentifier now has a range of StringSimpleAttribute (and is thus
>just another Attribute, and less of a special case)

I'd like to hear feedback on how this is represented in IdAS.  Basically, whether we should:
a) treat it like any other attribute in terms of access and query (remove IDigitalSubject.getUniqueID() and IFilterCUIDAssertion)
b) allow access and query via the attribute, but retain IDigitalSubject.getUniqueID() (only remove IFilterCUIDASsertion)
c) allow access and query via either (retain the IDigitalSubject.getUniqueID() as well as the IFilterCUIDASsertion)
 
I slightly prefer (b) as I think the CUID may be useful enough to provide a convenience method for reading. I don't see any value in retaining IFilterCUIDASsertion (was only there due to there being no other way to add the CUID to a query), so I dislike (c).
 
Do others see enough utility in the IDigitalSubject.getUniqueID() method to retain it (same thought apples to IContext.getSubject(String cuid) as this is just a convenience for calling IContext.getSubject(IFilter))?

>- added higgins:simpleMetadata and higgins:complexMetadata as metadata
>"markers"

>From my read, this aligns the current IdAS with the owl in terms of metadata.

>- made the following sub-properties of complexMetadata
>  o timeSpan
>  o source
>
>- made the following sub-properties of simpleMetadata
>  o lastVerifyAttempt
>  o lastVerifiedFromSource
>  o syncConflict
>  o lastModified
>  o validTo
>  o validFrom
>
>The last two (validTo, validFrom) were not really necessary, but I
>thought harmless.

I haven't added any convenience methods for accessing any of this metadata (I've always imagined IdAS consumers would just read these things from the set of metadata).  Does anyone see a need to add specific methods as convenient ways of reading any of these?

Jim