Create ontology GUI

[sofiag]

Resolves #241

[sofiag]

Implement split screen for the ontology editor GUI - angular-split (wip)

[sofiag]

The knora-base ontology classes, that can be used as resource types in the GUI:

knora-api:Annotation: {},
knora-api:AudioFileValue: {},
knora-api:AudioRepresentation: {},
knora-api:BooleanBase: {},
knora-api:BooleanValue: {},
knora-api:ColorBase: {},
knora-api:ColorValue: {},
knora-api:DDDFileValue: {},
knora-api:DDDRepresentation: {},
knora-api:DateBase: {},
knora-api:DateValue: {},
knora-api:DecimalBase: {},
knora-api:DecimalValue: {},
knora-api:DocumentFileValue: {},
knora-api:DocumentRepresentation: {},
knora-api:FileValue: {},
knora-api:ForbiddenResource: {},
knora-api:GeomValue: {},
knora-api:GeonameValue: {},
knora-api:IntBase: {},
knora-api:IntValue: {},
knora-api:IntervalBase: {},
knora-api:IntervalValue: {},
knora-api:LinkObj: {},
knora-api:LinkValue: {},
knora-api:ListNode: {},
knora-api:ListValue: {},
knora-api:MovingImageFileValue: {},
knora-api:MovingImageRepresentation: {},
knora-api:Region: {},
knora-api:Representation: {},
knora-api:Resource: {},
knora-api:StandoffBooleanTag: {},
knora-api:StandoffColorTag: {},
knora-api:StandoffDataTypeTag: {},
knora-api:StandoffDateTag: {},
knora-api:StandoffDecimalTag: {},
knora-api:StandoffIntegerTag: {},
knora-api:StandoffInternalReferenceTag: {},
knora-api:StandoffIntervalTag: {},
knora-api:StandoffLinkTag: {},
knora-api:StandoffTag: {},
knora-api:StandoffUriTag: {},
knora-api:StillImageFileValue: {},
knora-api:StillImageRepresentation: {},
knora-api:TextFileValue: {},
knora-api:TextRepresentation: {},
knora-api:TextValue: {},
knora-api:UriBase: {},
knora-api:UriValue: {},
knora-api:User: {},
knora-api:Value: {},
knora-api:ValueBase: {},
knora-api:XSLTransformation: {},
knora-api:knoraProject: {}

In bold the classes we can start with.

@benjamingeer, what is the difference again between a class and the value class (i.e. ColorBase and ColorValue)? I thought I understood it and now I'm not sure anymore...

[benjamingeer]

The knora-base ontology classes, that can be used as resource types in the GUI:

This isn't correct. Resource types must be subclasses of knora-api:Resource. For convenience, subclasses of knora-api:Resource are marked with:

"knora-api:isResourceClass" : true

These are the classes that users can actually create subclasses of:

• knora-api:Resource
• knora-api:Annotation
• knora-api:AudioRepresentation
• knora-api:DDDRepresentation
• knora-api:DocumentRepresentation
• knora-api:MovingImageRepresentation
• knora-api:StillImageRepresentation
• knora-api:TextRepresentation
• knora-api:LinkObj
• knora-api:Region

(The two others are knora-api:ForbiddenResource and knora-api:Representation. It wouldn't make sense to create a subclass of these. I think it's currently possible to do so, though; I'll fix this.)

what is the difference again between a class and the value class (i.e. ColorBase and ColorValue)? I thought I understood it and now I'm not sure anymore

Resources have values, which belong to subclasses of Value, e.g. DateValue. Text values can have standoff markup tags, which can also have data types, e.g. StandoffDateTag. So both DateValue and StandoffDateTag are subclasses of DateBase. This is just to simplify knora-base.

Users aren't allowed to make their own subclasses of Value. The ontology API currently doesn't allow creating standoff tag classes, so users can't make their own subclasses of ValueBase, either.

[benjamingeer]

The documentation on knora-base is now here:

https://docs.knora.org/paradox/02-knora-ontologies/knora-base.html

See especially these sections:

• Resources
• Values

[benjamingeer]

Probably it would also help to read the explanation of the example project ontology incunabula:

https://docs.knora.org/paradox/01-introduction/example-project.html

[sofiag]

Ok, so I was right about the representations, but I thought we could also use the -Base classes. I hadn't seen the "knora-api:isResourceClass" : true and I was looking for something like it, so thank you for that! I have seen the new documentation, I am going through it slowly ;-)

[benjamingeer]

No worries, glad I can help.

[sofiag]

@kilchenmann can you check out this branch and tell me what you think so far about the styling idea?
There is still a lot to do. I also need to find a solution for dnd among ontologies, resources and properties. But right now I still need to connect the three, so that the resources, are children of ontologies and the properties children of the resources, etc. Right now they are each separate objects and I have not made a connection yet.

[kilchenmann]

I will try to have a look on it today...

[kilchenmann]

Right now it doesn't have the whole functionality. It's more a kind of mockup.