Skip to content

Review descriptions of approved BIBO terms for completeness #91

@tombaker

Description

@tombaker

Properties and classes are defined in slightly different ways between BIBO and DC Terms - see 'usage' issue 132 for details. For the sake of consistency between existing and new terms in BIBO, I propose that we use the following properties, as appropriate:

  • rdfs:label for the human-readable "label"
  • rdfs:comment for the definition
  • rdf:type with owl:Class, owl:DatatypeProperty, or owl:ObjectProperty, as appropriate.
  • rdfs:domain and rdfs:range for domain and range, as needed.
  • rdfs:subClassOf or rdfs:subPropertyOf, as needed.
  • rdfs:isDefinedBy with object "http://purl.org/ontology/bibo/"^^<http://www.w3.org/2001/XMLSchema#anyURI> subject possibly to future change as discussed in 'bibo' issues 3 and 4.
  • dcterms:description with a scope note, if needed.
  • I propose that we start using dcterms:issued for the date on which the BIBO term was first published, starting with the new properties and classes.

I paste below the descriptions of all BIBO terms we have approved to date and ask you to confirm that the term descriptions are complete. I have filled some obvious gaps, such as range of rdfs:Literal for dateRetracted. Please note if you think any more domains, ranges, subclasses or subproperty relations should be added.

If you have reservations about the systematic use of rdfs:isDefinedBy with a literal object of type xsd:anyURI (the BIBO style), please post your comments on BIBO issue 4.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    In Progress

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions