Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • S saref-pipeline
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SAREF
  • saref-pipeline
  • Issues
  • #3

Closed
Open
Created Jul 27, 2020 by Raul Garcia-Castro@garciacastroMaintainer

Fix the turtle serialization of the ontologies

In the repository, the ontologies are serialized using Turtle and the different triples are sorted:

  • Ontology
  • Annotation properties
  • Datatypes
  • Object properties
  • Datatype properties
  • Classes
  • Individuals

Inside each section, the terms are sorted by namespace and alphabetically.

This makes easy to browse the file and understand its contents.

The turtle serialization that is currently published is mixing randomly every term, so it is very difficult to manage and understand.

Besides, right now it is quite difficult to check whether the published version is the same as the one in the repository.

The published turtle file should be the same than that in the repository or, if not, should follow the same structure.

Assignee
Assign to
Time tracking