metadata ::= annotation annotation ::= '@' {@link Identifier qualified} ('.' {@link SimpleIdentifier identifier})? {@link ArgumentList arguments}?
@coverage dart.engine.ast
Annotation is a little note that can be added to a page on a document.
@see Element
@see Anchor
Wrapping the attribute value into an Annotation object guarantees that adjacent text runs don't get merged even if the attribute values are equal, and indicates to text containers that the attribute should be discarded if the underlying text is modified. @see AttributedCharacterIterator @since 1.2
annotation structure. An instance of this class is returned by getAnnotations() in AnnotationsAttribute or in ParameterAnnotationsAttribute.
@see javassist.bytecode.AnnotationsAttribute#getAnnotations()
@see javassist.bytecode.ParameterAnnotationsAttribute#getAnnotations()
@see MemberValue
@see MemberValueVisitor
@see AnnotationsWriter
@author Bill Burke
@author Shigeru Chiba
@author Adrian Brock
Annotations may be associated with a specific timeseries, in which case the tsuid must be configured with a valid TSUID. If no TSUID is provided, the annotation is considered a "global" note that applies to everything stored in OpenTSDB. Global annotations are stored in the rows [ 0, 0, 0, <timestamp>] in the same manner as local annotations and timeseries data.
The description field should store a very brief line of information about the event. GUIs can display the description in their "main" view where multiple annotations may appear. Users of the GUI could then click or hover over the description for more detail including the {@link #notes}field.
Custom data can be stored in the custom hash map for user specific information. For example, you could add a "reporter" key with the name of the person who recorded the note. @since 2.0
Arbitrary annotation associated with one or more objects.
Biological information often does not fit design patterns very well, and can be a jumble of facts and relationships. Annotation objects provide a standard way for you to store this mess as a property of an object.
Annotations may contain keys that have Annotations as values. In this way, annotations can be shared among multiple Annotatable objects, and you can represent semi-structured data.
It is perfectly possible to wrap up almost any tree-like or flat data structure as Annotation.
Other than when using the constructor, you should be able to interact with nearly all Annotation implementations via this API. @author Matthew Pocock @author Thomas Down @see org.biojavax.RichAnnotation @since 1.0
Annotation: NormalAnnotation MarkerAnnotation SingleMemberAnnotation@since 3.1
Annotations are typed, can have an associated text and can be marked as persistent and deleted. Annotations which are not explicitly initialized with an annotation type are of type "org.eclipse.text.annotation.unknown".
To get the annotation associated with a component, use {@link org.zkoss.zk.ui.sys.ComponentCtrl#getAnnotation(String)}. To get the annotation associated with a component's property, use {@link org.zkoss.zk.ui.sys.ComponentCtrl#getAnnotation(String,String)} @author tomyeh @see org.zkoss.zk.ui.sys.ComponentCtrl#getAnnotation(String) @see org.zkoss.zk.ui.sys.ComponentCtrl#getAnnotation(String,String) @see org.zkoss.zk.ui.sys.ComponentCtrl#getAnnotations() @see org.zkoss.zk.ui.sys.ComponentCtrl#getAnnotations(String)
Many modern IM clients offer functionality that enables users to make notes about items in their roster. This comes in handy if users don't have meaningful information in their vCard or if you need to remember additional things related to a roster item.
This specification defines a protocol for storing annotations about a given set of entities. Its primary goal is to enable users to store some personal piece of information with their roster items.
Annotations are stored using server-side private XML storage (the 'jabber:iq:private' namespace).
@author Christian Schudt @see XEP-0145: Annotations @see XML Schema | |
| |
| |
| |
| |
| |
| |
| |
| |
| |