Skip to main content
  • Home
  • Development
  • Documentation
  • Donate
  • Operational login
  • Browse the archive

swh logo
SoftwareHeritage
Software
Heritage
Archive
Features
  • Search

  • Downloads

  • Save code now

  • Add forge now

  • Help

https://doi.org/10.5281/zenodo.15464115
19 May 2025, 13:09:33 UTC
  • Code
  • Branches (0)
  • Releases (1)
  • Visits
    • Branches
    • Releases
      • 1
      • 1
    • c5b185f
    • /
    • fcatools-contexts-90160eb
    • /
    • README.md
    Raw File Download

    To reference or cite the objects present in the Software Heritage archive, permalinks based on SoftWare Hash IDentifiers (SWHIDs) must be used.
    Select below a type of object currently browsed in order to display its associated SWHID and permalink.

    • content
    • directory
    • snapshot
    • release
    origin badgecontent badge
    swh:1:cnt:dff9692f92f46da3f2cc313995a8c8da89a3a9c1
    origin badgedirectory badge
    swh:1:dir:958a48d9702d70f2cd06425dfd69adf48efdd31c
    origin badgesnapshot badge
    swh:1:snp:ab0f12224a4748b24a698c05119873c0e5bef31d
    origin badgerelease badge
    swh:1:rel:7774785d963560a2b905e6c4c6a7582fecbfa790

    This interface enables to generate software citations, provided that the root directory of browsed objects contains a citation.cff or codemeta.json file.
    Select below a type of object currently browsed in order to generate citations for them.

    • content
    • directory
    • snapshot
    • release
    (requires biblatex-software package)
    Generating citation ...
    (requires biblatex-software package)
    Generating citation ...
    (requires biblatex-software package)
    Generating citation ...
    (requires biblatex-software package)
    Generating citation ...
    README.md
    # Formal Contexts
    
    This repository contains a collection of formal contexts to pursue
    [Formal Concept Analysis](https://upriss.github.io/fca/fca.html).
    
    The metadata for [the
    contexts](https://github.com/fcatools/contexts/tree/main/contexts) is
    contained in [this YAML file](contexts.yaml).
    
    More contexts can be found in the repository for
    [ConExp-CLJ](https://github.com/tomhanika/conexp-clj/tree/dev/testing-data),
    the repository for the [concepts Python
    module](https://github.com/xflr6/concepts/tree/master/examples), and
    on [Uta Priss' page](https://upriss.github.io/fca/examples.html).
    
    ## How to use the contexts
    
    You can either manually download contexts or you can access them
    directly in your program code with a URL generated as follows: append
    the file name of the context (e.g., `livingbeings_en.cxt`) to the
    prefix `https://github.com/fcatools/contexts/raw/main/contexts/`. For
    example, in Python 3 you could do:
    
    ```python
    import urllib.request
    
    url = "https://github.com/fcatools/contexts/raw/main/contexts/livingbeings_en.cxt"
    context = urllib.request.urlopen(url).read().decode("utf-8")
    ```
    
    ## How to contribute contexts
    
    Additional formal contexts are highly welcome if they fulfil the
    following criteria:
    
    1. They should be about real things and not contain invented or random
       data.
    2. They should preferrably be small, that is, have not too many
       attributes and objects (each less than 100).
    
    If you think your context is suitable, then proceed as follows:
    
    1. [Fork this repository](https://github.com/fcatools/contexts/fork)
       and make the following changes in your fork:
       1. Add your ASCII-encoded CXT file to the
          [contexts](https://github.com/fcatools/contexts/tree/main/contexts)
          directory, using a meaningful name (English, all lowercase, with
          two letters indicating the [ISO 639 language
          code](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes)
          at the end, e.g., `bodiesofwater_de.cxt` for the German bodies
          of water context).
       2. Describe your context in [contexts.yaml](contexts.yaml)
          following the example of the other contexts. Try to be concise
          and precise.
    2. Make a pull request to merge your changes into this repository.
    
    ## Working group
    
    The repository is managed by a working group that communicates using a
    [mailing
    list](https://lists.cs.uni-kassel.de/postorius/lists/fca-repo.lists.cs.uni-kassel.de/).
    
    ## Recommended Citations
    
    If you would like to reference a **single dataset** from this
    repository, we suggest that you cite the source given in [the
    metadata](contexts.yaml). This is typically the scholarly work where
    the dataset was first used as a formal context or another publication
    where it was found.
    
    In addition, you can reference a **specific version** of a dataset
    using its versioned URL as follows:
    
    If you would like to reference **several datasets** from this
    repository or the repository itself, we suggest to (additionally) cite
    the article where the idea for the repository has first been
    described:
    
    > Hanika, T., Jäschke, R.: A Repository for Formal Contexts. In:
    > Cabrera, I.P., Ferré, S., and Obiedkov, S. (eds.) *Conceptual
    > Knowledge Structures*. pp. 182–197. Springer Nature Switzerland,
    > Cham 2024.
    > doi:[10.1007/978-3-031-67868-4_13](https://doi.org/10.1007/978-3-031-67868-4_13)
    
    You can also reference a **specific snapshot** of the repository on
    Zenodo.
    
    Further machine-readable citation information can be found in the file
    <file:CITATION.cff>.
    

    back to top

    Software Heritage — Copyright (C) 2015–2026, The Software Heritage developers. License: GNU AGPLv3+.
    The source code of Software Heritage itself is available on our development forge.
    The source code files archived by Software Heritage are available under their own copyright and licenses.
    Terms of use: Archive access, API— Content policy— Contact— JavaScript license information— Web API