Here you can find the list of the requirements identified for the AURORAL ontology and their main features.
| Identifier | Partner | Competency Question / Natural language sentence (fact) |
Answer | Status | Superseded by | Priority |
|---|---|---|---|---|---|---|
| core-1 | BAV | What are the attributes of an organisation? | Identifier, business identifier, location, skin color, avatar, notes, creation date, update date | |||
| core-2 | BAV | An organisation can contain notifications | ||||
| core-3 | BAV | An organisation can contain audits | ||||
| core-4 | BAV | An organisation is related to users | ||||
| core-5 | BAV | An organisation can contain nodes | ||||
| core-6 | BAV | An organisation can have a partnership with another organisation | ||||
| core-7 | BAV | A partnership is requested by an organisation | ||||
| core-8 | BAV | A partnership is requested to an organisation | ||||
| core-9 | BAV | What are the attributes related to a notification? | Identifier, owner, actor, target, object, type, status, creation date | |||
| core-10 | BAV | A notification can be caused by an actor | ||||
| core-11 | BAV | A notification can affect a target | ||||
| core-12 | BAV | A notification needs an object | ||||
| core-13 | BAV | Examples of notification status are: Waiting, Info, Accepted, Rejected and Responded | ||||
| core-14 | BAV | A notification can be read | ||||
| core-15 | BAV | Types of a notification can be: registrationRequest, itemEnabled, itemDisabled, itemDiscovered, contractRequest, itemUpdated,contractAccepted | ||||
| core-16 | BAV | What are the attributes related to a node? | name, status, creation date, update date, token auth, public key | |||
| core-17 | BAV | A node has an AURORAL identifier | ||||
| core-18 | BAV | A node belongs to an organisation | ||||
| core-19 | BAV | Examples of node types are: vicinity, sharq, auroral | ||||
| core-20 | BAV | A node contains items | ||||
| core-21 | BAV | A node can have two status: active or deleted | ||||
| core-22 | BAV | What are the attributes of an item? | name, status, creation date, update date | |||
| core-23 | BAV | An item has an AURORAL identifier | ||||
| core-24 | BAV | An item is contained in a node | ||||
| core-25 | BAV | An item is related to a user | ||||
| core-26 | BAV | An item belongs to an organisation | ||||
| core-27 | BAV | An item can be represented with an avatar | ||||
| core-28 | BAV | Types of an item privacy policy can be: public, for friends, private | ||||
| core-29 | BAV | An item can be a device | ||||
| core-30 | BAV | An item can be a service | ||||
| core-31 | BAV | Types of an item status can be: disabled, enabled, deleted | ||||
| core-32 | BAV | What are the attributes related to a user? | name, first name, last name, email, contact mail, occupation, location, status, creation date, update date | |||
| core-33 | BAV | A user has an AURORAL identifier | ||||
| core-34 | BAV | A user belongs to an organisation | ||||
| core-35 | BAV | A user can be represented with an avatar | ||||
| core-36 | BAV | Types of an user visibility policy can be: public, for friends, private | ||||
| core-37 | BAV | Types of user status can be: active, deleted | ||||
| core-38 | BAV | A user can be associated to a role | ||||
| core-39 | BAV | Types of roles can be: admin, user, infrastructure operator, service provider, device owner, system integrator, super user, dev ops | ||||
| core-40 | BAV | A user contain can contain a notification | ||||
| core-41 | BAV | A user can contain an audit | ||||
| core-42 | BAV | A user can contain an item | ||||
| core-43 | UPM | Type of service can be: Commodity service, not commodity service | ||||
| core-44 | UPM | A service is applicable to a Geographical area | ||||
| core-45 | UPM | A service is defined in a language | ||||
| core-46 | UPM | What are the attributes of a service | service provider, currents status, hasSub Domain, has requirement, service free, number of Download, version of service, has functionality, description | |||
| core-47 | UPM | A measurement has a readability | ||||
| core-48 | UPM | Dataset is a virtual Thing | ||||
| core-49 | UPM | What are the attributes of a dataset | dataset provider, visibility, access URL, keyword, title, description, license |