You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Protein modification and activity types are now namespace values. The specification mentions a default namespace and implies that it should have both sets of protein modification and activity types.
Is this set accurate with respect to the BEL 2.0 specification? This default namespace is not defined as part of the specification so I'm unsure.
Also it seems reasonable to implement this as a namespace supported by OpenBEL. Users could then use this namespace as the DEFAULT in BEL Script using:
DEFINE DEFAULT NAMESPACE AS URI "http://www.openbel.org/bel/namespace/default"
act(p(HGNC:AKT1), ma(kin))
p(HGNC:AKT1, pmod(phosphorylation, Ser, 473))
What about the amino acid? Should the usual suspects be included in the default namespace?
The protein modification and activity types were moved out of the specification to a namespace to facilitate the addition of new modifications and activities without requiring a BEL version change.
It should be OK to leave the amino acids as part of the BEL specification because they are unlikely to change. The intent is to support both 1 letter and 3 letter amino acid codes (and treat as equivalent, similar to function short/long forms).
Protein modification and activity types are now namespace values. The specification mentions a default namespace and implies that it should have both sets of protein modification and activity types.
Set of values:
Is this set accurate with respect to the BEL 2.0 specification? This default namespace is not defined as part of the specification so I'm unsure.
Also it seems reasonable to implement this as a namespace supported by OpenBEL. Users could then use this namespace as the DEFAULT in BEL Script using:
What about the amino acid? Should the usual suspects be included in the default namespace?
/cc @ncatlett @wshayes
The text was updated successfully, but these errors were encountered: