arago / ogit Goto Github PK

I think would be beneficial to have a new entity ogit/Comment.

We already have the entity ogit/Person.

The ogit/Comment should have mandatory attributes:
- Author (that is a Person)
- Body (a string value containing the comment)

We therefore have the possibility to link through verbs any entity to a Comment.

Would be very helpful if the cardinality of a verb could be defined, to specify if a connection can be present one or multiple times for a single node.

For example a MARS node can be related to many other MARS nodes (isRelatedToMARSNode is 1:n) but can have only one single data tree structure associated (hasMARSData is 1:1).

After analyzing the structure of the KIs, examples and some discussions, here are the results from the new parts of the ontology (discussed with Cy & M. Fehse):

New entities:

Entity name: Trigger
Description: Trigger of a KI having a set of Subitems.
Mandatory attributes: ogit/description

Entity name: Subitem
Description: Item (e.g. Request) or subitem to search for within the issues , which triggers the Trigger

Mandatory attributes: ogit/name, ogit/mode (new)
Optional attributes: ogit/value (new)

New connections:

ogit/has
KnowledgeItem -> Trigger
Subitem -> Trigger

ogit/consistsOf
Subitem -> Subitem

Let me know if any additional info is needed.

Please change description for attribute ogit/ITService/pricing to:

Contains the reference to the pricesheet, namely priceSheetUUID

Please add the attribute ogit/ITService/id as optional.

Hi,

please create an optional attribute for kis where we can put a changelog of the changes of the ki.
Or: advise if there already is an attribute which we can use.

To stick with the rest, i would name it:

arago/knowledgeItemChangelog

As you can see in the pic below, there are missing/incorrect the edges(verbs) identified with red:

I did a comparison of:
(1) https://blog.tech.arago.de/ogit/graph.php?dataset=ontology

Against existing yaml's:
(2) https://github.com/arago/OGIT/tree/master/SGO/sgo/verbs

Conclusion for missing/wrong verbs:
requires - present in (2), not present in (1)
proves - not present in (1) neither (2)
implements - present in (2) but​ edge connecting wrong entities - needs to be updated
​

• find attribute name (like "allowAnyAttribute", boolean)
• decide whether this is inherited
• add to core yaml

CRUD of service sub categories is a functionality in ITOP, typically created while defining a service. e.g Apache is a subcategory for Webhosting Service.

This is similar to ogit/ITService/Service however little bit of difference. Shall we use the same and add free attributes to distinguish between main service and a subcategory?
Alternative - we would need a new entity for this.

Please suggest.

Thanks,
Satish

Hi Peter,
could you please create the entity ogit/Device according to what we reviewed?

Descr: Any type of device

Optional attributes:
ogit/id
ogit/name
ogit/purchaseDate
ogit/Datacenter/moveProductionDate
ogit/endOfWarranty
ogit/powerConsumption

Within the cleaning up of OGIT according to the guidelines, the KI related entities should be populated #138

It is completly sufficient to have only two parts in the IDs. For example in the ID http://www.purl.org/ogit/SGO/attributes/_id "ogit" is a namespace in authority of SGO and "_id" is a unique term in this namespace. "SGO/attributes" contains only redundant informations. It is adequate if only the URL target explains this details. A shorter link http://www.purl.org/ogit/_id is easily to notice and to use.

Please add attribute "discreteValue" for ogit/Pricing/PriceSpecification
with description: "Concrete value for the pricing element"

e.g. #170 #162

of course I'll try an keep the pull requests merge-able as often as possible.

ITOP Service Family is similar to group of CI's.

We are mapping Services to ogit/ITService/Service. However there is no mapping for Service Family.

An entity like ogit/ITService/ServiceFamily would be required to map this along with an edge with ogit/ITService/Service.

Thanks,
-Satish

The following verbs should be implemented

ogit/ITService/Parameter proves ogit/ITService/Parameter

ogit/ITService/Offering specifies arago/MARSNode (-Template)

Free attributes should be allowed in ogit/ITService/*

Please add new connection to ogit/describes:
ogit/ITService/Parameter->ogit/ITService/Service

Many tks.

Known Error's are represented in ITOP with following set of attributes. We do not have a corresponding entity in GraphIT.

Attributes :
Name
Customer
Related Problem (Edge with Problem)
Error Code
Domain
Vendor (Edge)
Model
Version
Symptom
Root Cause
Workaround
Solution
Edge with CI's (Mars nodes).
Edge with Attachments.

We need an entity to represent this along with free attributes.

Thanks,
Satish

Create new entity State with the [mandatory] attributes: id, name, status category.

In Jira an issue Status is more complicated than a String value. Therefore, for capturing the information of the issue state we should have a new entity. This entity should also be general to capture the state of many others entities within Ogit.

For example:

Entity Ticket can be connected to an entity State with:
id:
name:
status category: ejected, resolved etc.

Entity Person can be connected to an entity State with
id:
name:
status category: married, single etc.

Please change description of attribute ogit/ITSM/lastUpdatedAt to:
Defines latest date and time when a ticket or it's comment was updated. The format of this value should be according to ISO 8601.

Please add new connection for edge ogit/isRelatedTo :

from: ogit/ITService/Report
to: arago/MARSNode

We plan to use the ogit/Catalog/Catalog to map Software Catalog from ITOP. However it does not allow free attributes. We need free attributes to store ITOP specifc data.

Thanks,
-Satish

In Ticket we currently have optional attributes:
ogit/ServiceManagement/externalTicketSource
ogit/ServiceManagement/externalTicketId
which could correspond to an external source of the tool (e.g. BMC) we are importing the ticket from (e.g. Ticket coming to BMC from ATOS)

we also need optional attribute:
ogit/ServiceManagement/ticketId
which would correspond to the id of the ticket in BMC
Description for this attribute: ID of the ticket in the source system, e.g. the ID of the ticket in BMC

instead of having an attribute ticketSource for Incident, we should have an edge:
ogit/Software/Application -> ogit/creates ogit/ServiceManagement/Ticket

Tks.

Please create new entity: ogit/Comment
Description: Defines comments for a ticket, issue or another type of entity. Also known as WorkLog, ChangeLog or HistoryEntry.

Mandatory attribute: ogit/body
(Description of ogit/body: Contains the body of a message or comment)

Optional attributes: ogit/ITSM/lastUpdatedAt

Edge: ogit/comments From: ogit/Comment To: ogit/Comment
Edge: ogit/comments From: ogit/Comment To: ogit/Ticket
Edge: ogit/createdBy From: ogit/Comment To: ogit/Person

(Description of ogit/comments: Comments a ticket or a comment itself)

This issue is related to #159 and #153

New entity name: ogit/Set
New entity description: An entity to represent any type of set/grouping of other entities.

Optional attrs: ogit/name, ogit/description

Edge ogit/belongsTo:
from arago/MARSNode to ogit/Set

Hi,

last year we developed some part of the ontology which is autopilot frontend specific.

I'll paste the ontology here. My questions

• could you please review and suggest better names :/
• could you please suggest where to put it

when I have your feedback, I will create a pull request with the updated things in order to minimize your work.

thank you :)

- Entity:
    id:   http://www.purl.org/arago/av/Note
    name: Note
    description: |
      Defines A note of the AV-UI-Framework
    valid-from: 2014-09-15 00:00:00
    valid-until:
    creator: SP
    deleter:
    created:  2014-10-06
    modified: 2014-10-06
    admin-contact: [email protected]
    tech-contact: [email protected]
    scope: SGO
    parent: http://www.purl.org/arago/av/Note
    history:
      - id: 1
        date: 2014-10-06
        description: initial
        modified-by: SP

    attributes:
      mandatory:
        - http://www.purl.org/ogit/name
        - http://www.purl.org/ogit/content
      optional:

- Entity:
    id:   http://www.purl.org/arago/av/Worksheet
    name: Worksheet
    description: |
      Defines A worksheet of the AV-UI-Framework
    valid-from: 2014-09-15 00:00:00
    valid-until:
    creator: SP
    deleter:
    created:  2014-10-06
    modified: 2014-10-06
    admin-contact: [email protected]
    tech-contact: [email protected]
    scope: SGO
    parent: http://www.purl.org/arago/av/Worksheet
    history:
      - id: 1
        date: 2014-10-06
        description: initial
        modified-by: SP

    attributes:
      mandatory:
        - http://www.purl.org/ogit/name
        - http://www.purl.org/ogit/content
        - http://www.purl.org/ogit/description
      optional:
        - http://www.purl.org/arago/av/deviceId

- Entity:
    id:   http://www.purl.org/arago/av/Device
    name: Device
    description: |
      Defines A device of the AV-UI-Framework
    valid-from: 2014-09-15 00:00:00
    valid-until:
    creator: SP
    deleter:
    created:  2014-10-06
    modified: 2014-10-06
    admin-contact: [email protected]
    tech-contact: [email protected]
    scope: SGO
    parent: http://www.purl.org/arago/av/Device
    history:
      - id: 1
        date: 2014-10-06
        description: initial
        modified-by: SP

    attributes:
      mandatory:
        - http://www.purl.org/ogit/name
      optional:

- Attribute:
    id: http://www.purl.org/arago/av/deviceId
    name: device Id
    description: |
      Contains A device of the AV-UI-Framework
    valid-from: 2014-09-05 00:00:00
    valid-until: 
    creator: SP
    deleter: 
    created:  2014-10-06
    modified: 2014-10-06
    admin-contact: arago AG
    tech-contact: arago AG
    validation-type:
    validation-parameter:
    history:
      - id: 1
        date: 2014-09-05
        description: initial
        modified-by: SP  

Please add the following new edges between SLA entity and Incident / ChangeRequest/ Problem:

ogit/ServiceManagement/Incident => ogit/ complies ogit/ServiceManagement/SLA
ogit/ServiceManagement/ChangeRequest => ogit/complies ogit/ServiceManagement/SLA
ogit/ServiceManagement/Problem => ogit/complies ogit/ServiceManagement/SLA

For the external tools that the connectors will deal with i suggest adding the following attributes for the SLA entity as optional attributes:

• startTime: Creation time of the SLA
• actualTimeLeft: Time remaining until SLA breach
• actualTimeElapsed: time between start time and now (minus pause duration).
• plannedEndTime: When the SLA will become breached
• stage: Stage values which are defined for task SLA records (In progress, Breached, Achieved, Cancelled, Completed, Paused)

Please add missing connection (already previously defined):
Order->MarsModel (implements)

related to #139

Please add new connection:

ogit/MARSTemplate -> ogit/MARSTemplateNode

Hi,

I noticed some links to purl might be missing, e.g. requesting the page:
http://www.purl.org/ogit/Asset

returns: "Purl: /ogit/Asset has been tombstoned and cannot be resolved."

other links are not working properly:
http://www.purl.org/ogit/Person

returns: "The proxy server could not handle the request GET /doxygen-graphit/group__httpwwwpurlorgogitPerson.html.
Reason: Error during SSL Handshake with remote server"

Some might to be missing at all from purl:
http://www.purl.org/ogit/_version
http://www.purl.org/ogit/corresponds

returns: "HTTP 404 Not Found."

1. change connections for ogit/implements
   remove:
   arago/MARSModel => ogit/ITService/Offering
   add:
   ogit/MARSTemplate => ogit/ITService/Order
2. change connections for ogit/specifies
   remove:
   ogit/ITService/Offering => arago/MARSModel
   add:
   ogit/ITService/Offering => ogit/MARSTemplate
3. change connections for ogit/plansCostsFor
   remove:
   CostModel/PlanningTemplate => arago/MARSModel
   add:
   CostModel/PlanningTemplate => ogit/MARSTemplate
4. delete connection for ogit/has :
   ogit/MARSTemplate => arago/MARSNode
5. new edge ogit/isRelatedToMARSTemplateNode
   Description: Relation between MARSTemplateNode's. The MARSTemplate should only allow connections between MaschineNode and SoftwareNode, SoftwareNode and ResourceNode, ResourceNode and ApplicationNode.

add connection:
ogit/MARSTemplateNode => ogit/MARSTemplateNode

1. change connections for ogit/hasCost
   add:
   ogit/MARSTemplateNode => CostModel/CostElement

Thank you in advance.

Please create new entity ogit/ITSM/ServiceRequest with:

parent ogit/ITSM/Ticket

mandatory fields:
ogit/name
ogit/ITSM/solution
ogit/ITSM/resolutionCode

optional fields:
ogit/ITSM/actualStartAt
ogit/ITSM/actualFinishAt
ogit/ITSM/scheduledStartAt
ogit/ITSM/scheduledFinishAt

outgoing edges:

ogit/isRelatedTo => ogit/ITService/Order
ogit/isRelatedTo => arago/MARSNode
ogit/ITSM/requestedBy => ogit/Person

Many thanks.

ogit/Schema undepend an the type (xsd,rdf...) have a unique schema identifier. For XML schemas using the target namespace URI seems best. The Schema type self can be resolved from the content and if will be defined should be an automaticaly computed one. The attribute content is needed to can store the schema instance for usage in the closed environments.

https://github.com/arago/OGIT/blob/master/SGO/sgo/verbs/manages.yaml

software can be managed by individuals too, not just by organizations (?)

environmentType
environmentStatus
criticalityClass
soxRelevant
application
hostingLocation
environmentName
supportedOsVersion
webhostingVersion
webProtocol

I have been watching the progress of #169, as in the TabTab pull request #170 I used the ogit/Set entity. Now it has been removed.

I am struggling to understand the usage of the word semantic is relation to the graph entities/verbs/attributes. I thought it meant to be as specific as needed and as general as possible. Therefore an arbitrary collection of entities could be grouped with an ogit/Set node quite happily. It seems I was wrong, which may mean a lot of the pull request will need reworking.

Does the removal of ogit/Set mean that we should instead be requesting creation of entities like ogit/NTO/SetOfThingA or ogit/NTO/ThingA/Set? What is the preferred definition for group entities?

Thanks for the clarification, I am requesting a lot of changes, and want to understand what will work best in OGIT.

A CI (Configuration Item) in ITOP is currently mapped with respective MARS Node in GraphIT.

However ITOP allows to create CI groups with following set of attributes -

Name
Status
Parent Group (edge with other Group).
Organization (edge)
Associated CI (edges with MARS Nodes)
Description
Type

We need an GraphIT entity for this.

Thanks and Regards,
-Satish

Please create the entity:

ogit/MARSTemplateNode
parent: arago/MARSNode
desc: MARS node used to create ogit/MARSTemplate's, which could be used for defining a vendor implementation template of a given service offering and for enabling definition of cost elements (CostModel/CostElement) attached to it

Add connections for ogit/assignedTo:
CostModel/CostElement -> ogit/MARSTemplateNode

Change existing entities:

ogit/MARSTemplate - define parent as arago/MARSModel

Please remove optional attribute:
1.ogit/Pricing/factor

Please add optional attribute:
1.ogit/Pricing/target
description: Where to apply the factor (Node/Tree/Attribute)
2.ogit/Pricing/targetAttribute
description: Attribute to which the factor will be applied to (If target == Attribute)
3.ogit/Pricing/value
description: Value of the factor

Many tks.

I think in ogit/ITSM/Ticket we need an optional attribute ogit/Project.Here we should save the Project id for which the issue belongs to. As shown in the attachment, a company can have many projects. Each project has a number of issues. These issues are mapped to tickets in Graphit. For reverse mapping (From Graphit to the issue ticketing system) we we need to scan through all the issues to find the right project. Eg. "ticket 5" in Graphit has no information about the Project. Currently, to find that ticket 5 belongs to Project 3, we need to scan through all the issues.

This attribute is also necessary since in many (if not all) issue-ticketing systems we have the element of "Product", "Project".

Please change direction from:
ogit/ITService/Order => arago/MARSModel
to:
arago/MARSModel => ogit/ITService/Order

Please add connection:
arago/MARSModel => ogit/ITService/Offering

we shortened all ids.

for attributes, we even omitted the namespace prefix http://www.purl.org, so
http://www.purl.org/ogit/_id would become ogit/_id

will we be also doing that for all the other things in graphit?

e.g.:
http://www.purl.org/ogit/Person -> will it be the type ogit/Person or http://www.purl.org/ogit/Person ?

For defining which attributes should be added to ogit/_content we need additional block in each entity which will contain a list of attributes which will be indexed for ngram search. Block could be optional and then nothing will be put to ogit/_content (default). GraphIt plugin will read from ontology on start which entities have defined attributes and do indexing as listener.

Hi Caratina,

We need an edge between Person and MARSNode.

ITOP CI's can be assigned with one or more persons.

Today, we dont have any edge between Person and MarsNode.

Can you please add an edge between the two?

e.g
ogit/communicatesWith <= ogit/Person

Thanks,
Satish

The Entity Oder should connect a factual MARS with an Offering.

ogit/ITService/Order

Attributes:

orderUUID

Verbs :
ogit/ITService/Order fullfills ogit/ITService/Offering
arago/MARSNode implements ogit/ITService/Order

Please change parent for entity ogit/ITService/Order to:

ogit/ITSM/Ticket

Depending on answer from Peter Larem (see mail sent below), we should save pricesheetUUID either in:

ogit/ITService/Offering::ogit/ITService/pricing
or
ogit/gr/PriceSpecification::pricesheetUUID (if free attributes will be allowed)

Additionally we'd need the following edges (to be requested to PL):

Parameter -> describes -> Offering
Parameter -> hasPriceSpecification -> PriceSpecification​

Sent to Peter Larem at Do 02.10.2014 12:32

entity: ogit/gr/PriceSpecification

has no allowed free attributes. Can we change this in order to allow them?
This way we could save information for a pricing element within the service offering (namely: factor, price, range, timeUnitSeconds) ​in this entity.

Hi,

GraphIT does have entity to define SLA's but not SLT's. As per ITIL in general, SLT's actually define the metrics in the service level management. SLA's may not be complete without having appropriate SLT's.

We need an entity to define the SLT's from ITOP.

Thanks,
-Satish

Hi Peter, please allow the entities Person and Organization to have free attributes

https://github.com/arago/iTOP-Vendor-Implementation/issues/2

tks