On 21 April 2010 17:46, Dustin Puryear <[email protected]> wrote:
> Can you be a little more specific in what you're trying to do? What kind
> of data are you going to store? Do you need to do any serious
> computations based on that data?
>
> Yes, I do. The data are the triplets of an ontology. I'm looking at it as a
means of keeping, and updating, status and other details of strings of
records of an ontology. Here's some pseudo code that I hope gives a flavour:
attributetype (
1.3.6.1.4.1.4203.666.42.40
NAME 'responsible'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.12'
SINGLE-VALUE )
attributetype (
NAME 'status'
SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
objectclass (
1.3.6.1.4.1.4203.666.42.50
NAME 'service-status'
SUP leaf
ABSTRACT
MAY (status $ responsible) )
objectclass (
1.3.6.1.4.1.4203.666.42.70
NAME 'SDP'
SUP top
AUXILIARY
DESC 'Service Design Package'
MAY ( service-status $ service-name $
service-owner $
SDP-Version ) )
Obviously there'd be much more to it than this, but the authorised person
ought to be able to update the status whilst others can read it, with the
status being, effectively, an enum or enumerated type.
Does this make it any clearer?
