sbol3.subcomponent
==================

.. py:module:: sbol3.subcomponent


Classes
-------

.. autoapisummary::

   sbol3.subcomponent.SubComponent


Functions
---------

.. autoapisummary::

   sbol3.subcomponent.build_subcomponent


Module Contents
---------------

.. py:class:: SubComponent(instance_of: Union[Identified, str], *, role_integration: Optional[str] = None, locations: Union[Location, List[Location]] = None, source_locations: Union[Location, List[Location]] = None, roles: List[str] = None, orientation: str = None, name: str = None, description: str = None, derived_from: List[str] = None, generated_by: List[str] = None, measures: List[SBOLObject] = None, identity: str = None, type_uri: str = SBOL_SUBCOMPONENT)

   Bases: :py:obj:`sbol3.feature.Feature`


   The SubComponent class can be used to specify structural
   hierarchy. For example, the Component of a gene might contain four
   SubComponent objects: a promoter, RBS, CDS, and terminator, each
   linked to a Component that provides the complete definition. In
   turn, the Component of the promoter SubComponent might itself
   contain SubComponent objects defining various operator sites, etc.



   .. py:method:: accept(visitor: Any) -> Any

      Invokes `visit_sub_component` on `visitor` with `self` as the only
      argument.

      :param visitor: The visitor instance
      :type visitor: Any
      :raises AttributeError: If visitor lacks a visit_sub_component method
      :return: Whatever `visitor.visit_sub_component` returns
      :rtype: Any




   .. py:attribute:: instance_of


   .. py:attribute:: locations


   .. py:attribute:: role_integration
      :type:  sbol3.typing.uri_singleton


   .. py:attribute:: source_locations


.. py:function:: build_subcomponent(identity: str, type_uri: str = SBOL_SUBCOMPONENT) -> Identified

   Used by Document to construct a SubComponent when reading an SBOL file.