Skip to content

Consider changing the URI of entries in the GSBPM scheme + consider renaming ActivityCategory to ActivityType #109

Open

Description

@tfrancart

Right now we have http://id.unece.org/activities/subProcess/1.2. I suggest http://id.unece.org/activityCategories/subProcess/1.2 to be inline with the class name, and avoid confusion between prov:Activities and activity categories.

Also, I think the name ActivityCategory could be renamed to ActivityType which would be more consistent with our use of dcterms:type to relate activities to their category/type. In which case the URI of GSBPM entries should be http://id.unece.org/activityTypes/...

Activity

  1. tfrancart commented on Oct 12, 2023

    @tfrancart
    CollaboratorAuthor

    This also raises the question of the IRI of the ConceptScheme itself, which is right now http://id.unece.org/activities/gsbpm. i suggest http://id.unece.org/activiyCategories/gsbpm

  2. tfrancart commented on Oct 12, 2023

    @tfrancart
    CollaboratorAuthor

    Or even simpler, http://id.unece.org/gsbpm

  3. tfrancart commented on Oct 13, 2023

    @tfrancart
    CollaboratorAuthor

    Other possibilities include:

    http://id.unece.org/vocabularies/gsbpm
    http://id.unece.org/vocabularies/gamso

    --> this naming choice would be agnostic wrt the OWL classes (no part "activities" or "activityCategories" or "activityTypes"), it coulw consistent for GSBPM and GAMSO (and potentially others), plus it would enable in the future to have dedicated browsing interface or content negostiation on the same IRI path "/vocabularies".

  4. tfrancart commented on Oct 13, 2023

    @tfrancart
    CollaboratorAuthor

    Related to Concepts IRI policy, a common pattern is to derive their IRI from the base ConceptScheme IRI, e.g.
    http://id.unece.org/vocabularies/gsbpm/subProcess/1.2

    I would also advise against putting the level (here "subProcess") in the IRI, to have a better garantee of stability over time. So:

    http://id.unece.org/vocabularies/gsbpm/1.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions