UtilityClass#

class biopax-explorer.biopax.utilityclass.UtilityClass(*args, **kwargs)[source]#

Bases: object

Class UtilityClass

Definition: This is a placeholder for classes, used for annotating the “Entity”

and its subclasses. Mostly, these are not an “Entity” themselves. Examples include references to external databases, controlled vocabularies, evidence and provenance. Rationale: Utility classes are created when simple slots are insufficient to describe an aspect of an entity or to increase compatibility of this ontology with other standards. Usage: The utilityClass class is actually a metaclass and is only present to organize the other helper classes under one class hierarchy; instances of utilityClass should never be created.

code generator : rdfobj (author F.Moreews 2023-2024).

Methods

get_comment()

Attribute _comment getter

attribute_type_by_name
get_uri_string
object_attributes
set_comment
set_uri_string
to_json
type_attributes

Methods Summary

`attribute_type_by_name`()
`get_comment`()	Attribute _comment getter
`get_uri_string`()
`object_attributes`()
`set_comment`(value)
`set_uri_string`(uristr)
`to_json`()
`type_attributes`()

Methods Documentation

attribute_type_by_name()[source]#

get_comment()[source]#

Attribute _comment getter
Comment on the data in the container class. This property should be used instead

of the OWL documentation elements (rdfs:comment) for instances because information in ‘comment’ is data to be exchanged, whereas the rdfs:comment field is used for metadata about the structure of the BioPAX ontology.

get_uri_string()[source]#

object_attributes()[source]#

set_comment(value)[source]#

set_uri_string(uristr)[source]#

to_json()[source]#

type_attributes()[source]#