Description: A characteristic of a physical entity that can change while the entity still retains its biological identity. Rationale: Two phosphorylated forms of a protein are strictly speaking different chemical molecules. It is, however, standard in biology to treat them as different states of the same entity, where the entity is loosely defined based on sequence. Entity Feature class and its subclassses captures these variable characteristics. A Physical Entity in BioPAX represents a pool of molecules rather than an individual molecule. This is a notion imported from chemistry( See PhysicalEntity). Pools are defined by a set of Entity Features in the sense that a single molecule must have all of the features in the set in order to be considered a member of the pool. Since it is impossible to list and experimentally test all potential features for an entity, features that are not listed in the selection criteria is neglected Pools can also be defined by the converse by specifying features that are known to NOT exist in a specific context. As DNA, RNA and Proteins can be hierarchicaly organized into families based on sequence homology so can entity features. The memberFeature property allows capturing such hierarchical classifications among entity features. Usage: Subclasses of entity feature describe most common biological instances and should be preferred whenever possible. One common usecase for instantiating entity feature is, for describing active/inactive states of proteins where more specific feature information is not available. Examples: Open/close conformational state of channel proteins, "active"/"inactive" states, excited states of photoreactive groups.
Source:http://www.biopax.org/release/biopax-level3.owl#EntityFeature
| Predicate | Object |
|---|---|
| rdf:type | |
| rdfs:comment |
Description: A characteristic of a physical entity that can change while the entity still retains its biological identity.
Rationale: Two phosphorylated forms of a protein are strictly speaking different chemical molecules. It is, however, standard in biology to treat them as different states of the same entity, where the entity is loosely defined based on sequence. Entity Feature class and its subclassses captures these variable characteristics. A Physical Entity in BioPAX represents a pool of molecules rather than an individual molecule. This is a notion imported from chemistry( See PhysicalEntity). Pools are defined by a set of Entity Features in the sense that a single molecule must have all of the features in the set in order to be considered a member of the pool. Since it is impossible to list and experimentally test all potential features for an entity, features that are not listed in the selection criteria is neglected Pools can also be defined by the converse by specifying features that are known to NOT exist in a specific context. As DNA, RNA and Proteins can be hierarchicaly organized into families based on sequence homology so can entity features. The memberFeature property allows capturing such hierarchical classifications among entity features.
Usage: Subclasses of entity feature describe most common biological instances and should be preferred whenever possible. One common usecase for instantiating entity feature is, for describing active/inactive states of proteins where more specific feature information is not available.
Examples: Open/close conformational state of channel proteins, "active"/"inactive" states, excited states of photoreactive groups.,
Description: A characteristic of a physical entity that can change while the entity still retains its biological identity.
Rationale: Two phosphorylated forms of a protein are strictly speaking different chemical molecules. It is, however, standard in biology to treat them as different states of the same entity, where the entity is loosely defined based on sequence. Entity Feature class and its subclassses captures these variable characteristics. A Physical Entity in BioPAX represents a pool of molecules rather than an individual molecule. This is a notion imported from chemistry( See PhysicalEntity). Pools are defined by a set of Entity Features in the sense that a single molecule must have all of the features in the set in order to be considered a member of the pool. Since it is impossible to list and experimentally test all potential features for an entity, features that are not listed in the selection criteria is neglected Pools can also be defined by the converse by specifying features that are known to NOT exist in a specific context. As DNA, RNA and Proteins can be hierarchicaly organized into families based on sequence homology so can entity features. The memberFeature property allows capturing such hierarchical classifications among entity features.
Usage: Subclasses of entity feature describe most common biological instances and should be preferred whenever possible. One common usecase for instantiating entity feature is, for describing active/inactive states of proteins where more specific feature information is not available.
Examples: Open/close conformational state of channel proteins, "active"/"inactive" states, excited states of photoreactive groups.,
Description: A characteristic of a physical entity that can change while the entity still retains its biological identity.
Rationale: Two phosphorylated forms of a protein are strictly speaking different chemical molecules. It is, however, standard in biology to treat them as different states of the same entity, where the entity is loosely defined based on sequence. Entity Feature class and its subclassses captures these variable characteristics. A Physical Entity in BioPAX represents a pool of molecules rather than an individual molecule. This is a notion imported from chemistry( See PhysicalEntity). Pools are defined by a set of Entity Features in the sense that a single molecule must have all of the features in the set in order to be considered a member of the pool. Since it is impossible to list and experimentally test all potential features for an entity, features that are not listed in the selection criteria is neglected Pools can also be defined by the converse by specifying features that are known to NOT exist in a specific context. As DNA, RNA and Proteins can be hierarchicaly organized into families based on sequence homology so can entity features. The memberFeature property allows capturing such hierarchical classifications among entity features.
Usage: Subclasses of entity feature describe most common biological instances and should be preferred whenever possible. One common usecase for instantiating entity feature is, for describing active/inactive states of proteins where more specific feature information is not available.
Examples: Open/close conformational state of channel proteins, "active"/"inactive" states, excited states of photoreactive groups.
|
| owl:disjointWith |
biopax3:BioSource,
biopax3:BioSource,
biopax3:BioSource,
biopax3:ChemicalStructure,
biopax3:ChemicalStructure,
biopax3:ChemicalStructure,
biopax3:ControlledVocabulary,
biopax3:ControlledVocabulary,
biopax3:ControlledVocabulary,
biopax3:DeltaG,
biopax3:DeltaG,
biopax3:DeltaG,
biopax3:EntityReference,
biopax3:EntityReference,
biopax3:EntityReference,
biopax3:Evidence,
biopax3:Evidence,
biopax3:Evidence,
biopax3:ExperimentalForm,
biopax3:ExperimentalForm,
biopax3:ExperimentalForm,
biopax3:KPrime,
biopax3:KPrime,
biopax3:KPrime,
biopax3:PathwayStep,
biopax3:PathwayStep,
biopax3:PathwayStep,
biopax3:Provenance,
biopax3:Provenance,
biopax3:Provenance,
biopax3:Score,
biopax3:Score,
biopax3:Score,
biopax3:SequenceLocation,
biopax3:SequenceLocation,
biopax3:SequenceLocation,
biopax3:Stoichiometry,
biopax3:Stoichiometry,
biopax3:Stoichiometry,
biopax3:Xref,
biopax3:Xref,
biopax3:Xref
|
| rdfs:subClassOf |