-
ca.uhn.hl7v2.model.Segment
Represents an HL7 message segment, which is a unit of data that contains multiple fields.
@author Bryan Tripp (bryan_tripp@sourceforge.net)
-
com.asakusafw.compiler.flow.stage.ShuffleModel.Segment
-
com.asakusafw.runtime.directio.FilePattern.Segment
-
com.barrybecker4.simulation.snake.geometry.Segment
A segment of a snakes body. It is composed of edges and particles The structure of the segment looks like this:
p3<-------e2<-------p2 left edge ^ \ / ^ | e7 e6 | | \ / | all edges in the middle point to p4 e3 \ / e1 ^ /p4\ ^ | / \ | | e4 e5 | | / \ | p0------->e0------->p1 right edge
@author Barry Becker
-
com.dianping.cat.consumer.dependency.model.entity.Segment
-
com.dianping.cat.consumer.metric.model.entity.Segment
-
com.dianping.cat.consumer.problem.model.entity.Segment
-
com.esri.core.geometry.Segment
A base class for segments. Presently only Line segments are supported.
-
com.evelopers.unimod.glayout.graph.containers.Segment
Graph Segment is a special term segment is G segment to G' (already planarized) but we set a planarized graph as a graph of segment. Edges may not be edges of associated planar
@author MKorotkov
-
com.google.gdata.data.analytics.Segment
-
com.sirenian.hellbound.domain.Segment
This class should be immutable.
-
com.sun.pdfview.font.ttf.CMapFormat4.Segment
@author jkaplan
-
com.taobao.metamorphosis.server.store.MessageStore.Segment
-
com.volantis.mcs.layouts.Segment
-
de.anomic.search.Segment
-
de.lmu.ifi.dbs.elki.evaluation.clustering.pairsegments.Segment
A segment represents a set of pairs that share the same clustering properties. As such, for each ring (= clustering), a cluster number (or the constant {@link #UNCLUSTERED}) is stored.
-
ds.moteur.route.cc.elements.Segment
Cette classe repr�sente un �l�ment de type segment.
@author Yannick BISIAUX
-
etc.aloe.data.Segment
Stores a list of LabeledMessages, associated with an unique ID for the segment (auto-increment, zero-index)
@author Michael Brooks
-
gnu.java.awt.java2d.Segment
-
grammar.model.verbs.Segment
-
io.druid.segment.Segment
-
isovaleur.Segment
@author lotfi
-
javax.swing.text.Segment
-
joshua.decoder.segment_file.Segment
This interface represents an individual segment for translation, corresponding with a single {@link joshua.decoder.chart_parser.Chart}. Each segment contains approximately one sentence or one utterance, and can additionally contain some constraints representing initial items for seeding the chart.
The {@link Segment}, {@link ConstraintSpan}, and {@link ConstraintRule}interfaces are for defining an interchange format between a SegmentFileParser and the Chart class. These interfaces should not be used internally by the Chart. The objects returned by a SegmentFileParser will not be optimal for use during decoding. The Chart should convert each of these objects into its own internal representation during construction. That is the contract described by these interfaces.
@author wren ng thornton
@version $LastChangedDate: 2009-03-26 15:06:57 -0400 (Thu, 26 Mar 2009) $
-
krati.core.segment.Segment
Segment Storage Version: 1 The segment header section uses the first 128 bytes, but only the first 16 bytes are used. The segment data section stores varying-length data in the format of repeated [length][data ... ...]. Header Section: 0x00 long -- 8 bytes lastForcedTime 0x08 long -- 8 bytes storageVersion 0x10 long -- 8 bytes reserved 0x18 long -- 8 bytes reserved 0x20 long -- 8 bytes reserved 0x28 long -- 8 bytes reserved 0x30 long -- 8 bytes reserved 0x38 long -- 8 bytes reserved 0x40 long -- 8 bytes reserved 0x48 long -- 8 bytes reserved 0x50 long -- 8 bytes reserved 0x58 long -- 8 bytes reserved 0x60 long -- 8 bytes reserved 0x68 long -- 8 bytes reserved 0x70 long -- 8 bytes reserved 0x78 long -- 8 bytes reserved
Data Section: [length1][data1 ... ...] [length2][data2 ... ... ... ... ... ...] [length3][data3 ... ... ... ...] [length4][data4 ...] ...
@author jwu
-
net.htmlparser.jericho.Segment
Represents a segment of a {@link Source} document.
Many of the tag search methods are defined in this class.
The span of a segment is defined by the combination of its begin and end character positions.
-
net.sourceforge.gpstools.jpeg.JpegStructure.Segment
-
net.yacy.search.index.Segment
-
org.apache.batik.ext.awt.geom.Segment
An interface that path segments must implement.
@version $Id: Segment.java,v 1.2 2005/03/27 08:58:32 cam Exp $
-
org.apache.commons.imaging.formats.jpeg.segments.Segment
-
org.apache.commons.math3.geometry.euclidean.twod.Segment
Simple container for a two-points segment.
@since 3.0
-
org.apache.ctakes.typesystem.type.textspan.Segment
-
org.apache.drill.common.logical.data.Segment
-
org.apache.flex.forks.batik.ext.awt.geom.Segment
An interface that path segments must implement.
@version $Id: Segment.java,v 1.2 2005/03/27 08:58:32 cam Exp $
-
org.apache.harmony.pack200.Segment
A Pack200 archive consists of one (or more) segments. Each segment is standalone, in the sense that every segment has the magic number header; thus, every segment is also a valid archive. However, it is possible to combine (non-GZipped) archives into a single large archive by concatenation alone. Thus all the hard work in unpacking an archive falls to understanding a segment. This class implements the Pack200 specification by an entry point ( {@link #parse(InputStream)}) which in turn delegates to a variety of other parse methods. Each parse method corresponds (roughly) to the name of the bands in the Pack200 specification. The first component of a segment is the header; this contains (amongst other things) the expected counts of constant pool entries, which in turn defines how many values need to be read from the stream. Because values are variable width (see {@link Codec}), it is not possible to calculate the start of the next segment, although one of the header values does hint at the size of the segment if non-zero, which can be used for buffering purposes. Note that this does not perform any buffering of the input stream; each value will be read on a byte-by-byte basis. It does not perform GZip decompression automatically; both of these are expected to be done by the caller if the stream has the magic header for GZip streams ( {@link GZIPInputStream#GZIP_MAGIC}). In any case, if GZip decompression is being performed the input stream will be buffered at a higher level, and thus this can read on a byte-oriented basis.
@author Alex Blewitt
@version $Revision: $
-
org.apache.harmony.unpack200.Segment
A Pack200 archive consists of one or more segments. Each segment is stand-alone, in the sense that every segment has the magic number header; thus, every segment is also a valid archive. However, it is possible to combine (non-GZipped) archives into a single large archive by concatenation alone. Thus all the hard work in unpacking an archive falls to understanding a segment. The first component of a segment is the header; this contains (amongst other things) the expected counts of constant pool entries, which in turn defines how many values need to be read from the stream. Because values are variable width (see {@link Codec}), it is not possible to calculate the start of the next segment, although one of the header values does hint at the size of the segment if non-zero, which can be used for buffering purposes. Note that this does not perform any buffering of the input stream; each value will be read on a byte-by-byte basis. It does not perform GZip decompression automatically; both of these are expected to be done by the caller if the stream has the magic header for GZip streams ( {@link GZIPInputStream#GZIP_MAGIC}). In any case, if GZip decompression is being performed the input stream will be buffered at a higher level, and thus this can read on a byte-oriented basis.
-
org.apache.jackrabbit.oak.plugins.segment.Segment
-
org.apache.sanselan.formats.jpeg.segments.Segment
-
org.apache.tez.runtime.library.common.sort.impl.TezMerger.Segment
-
org.broad.igv.data.seg.Segment
@author jacob
@date 09/01/09
-
org.elasticsearch.index.engine.Segment
-
org.gbcpainter.geom.Segment
Defines a segment.
The segment is described by its extremities. Coordinates of the extremities are integers.
The first is named "A". The second point is named "B".
@author Lorenzo Pellegrini
-
org.ictclas4j.segment.Segment
-
org.jboss.dna.graph.properties.Path.Segment
-
org.jboss.dna.graph.property.Path.Segment
-
org.jitterbit.integration.data.structure.text.Segment
@author Frank Chu
-
org.jpedal.jbig2.segment.Segment
-
org.milyn.edisax.model.internal.Segment
-
org.modeshape.jcr.value.Path.Segment
-
org.nutz.lang.segment.Segment
字符串片段。你可以通过这个接口的函数,为片段中的占位符设值。
@author zozoh(zozohtnt@gmail.com)
-
org.w3c.jigsaw.ssi.Segment
Represents a segment within the parsed content
@author Antonio Ramirez
@author Benoit Mahe
@author Yves Lafon
-
ru.dubov.primitives.Segment
Represents a segment.
@author Mikhail Dubov
-
systole.domain.signals.Segment
Represents a sign of dots arranged temporarily.
@author juan
-
tool.editors.ToolContentOutlinePage.Segment
-
vazkii.botania.client.core.handler.LightningHandler.LightningBolt.Segment