Results 1 - 10
of
6,591
Table 1: Stored meta-data information for each feature. An aggregated feature value is calculated for each feature and shot.
"... In PAGE 8: ... Each aggregated feature value is normalized to the interval [0; 1]. Table1 lists the features that are relevant for the selection process of the summary. The stored meta-data information and the length of the video segment is listed for each feature.... ..."
Table 1: Description of metadata files in NTFS (Solomon amp; Russinovich, 2000) Metadata file Description $MFT Store MFT record $MFTMirr Contain partial backup of MFT $LogFile Transaction logging file
"... In PAGE 2: ..., $Bitmap, $Boot, $BadClus, $Secure, $Upcase and $Extend. Table1 show the description of some of the metadata files. Table 1: Description of metadata files in NTFS (Solomon amp; Russinovich, 2000) Metadata file Description $MFT Store MFT record $MFTMirr Contain partial backup of MFT $LogFile Transaction logging file ... ..."
Table 3. The certificate stored with each ex- tent includes fields to bind the data to its owner and other metadata fields.
2005
"... In PAGE 5: ...3 An API for extent-based storage Table 2 presents an interface for an extent-based storage system like the one described above. All operations that modify data stored in the system require the client to pro- vide a certificate authenticating the change; Table3 lists the contents of a certificate. To support the extent-based model, the interface extends the traditional put()/get() inter- face, shown in Table 1, defining additional operations for key-verified data.... ..."
Cited by 4
Table 3. The certificate stored with each ex- tent includes fields to bind the data to its owner and other metadata fields.
"... In PAGE 5: ...3 An API for extent-based storage Table 2 presents an interface for an extent-based storage system like the one described above. All operations that modify data stored in the system require the client to pro- vide a certificate authenticating the change; Table3 lists the contents of a certificate. To support the extent-based model, the interface extends the traditional put()/get() inter- face, shown in Table 1, defining additional operations for key-verified data.... ..."
Table 2: Content Metadata
1999
"... In PAGE 3: ...ithin video data (i.e., objects and interpretations within video data or across structural elements). Some of the information extracted from news video data is shown in Table2 . Information such as the objects present in visuals, the category of a news item, and the main concept (focus or center [7]) depicted by the new item are stored as metadata.... ..."
Cited by 4
Table 2: Content Metadata
1999
"... In PAGE 3: ...ithin video data (i.e., objects and interpretations within video data or across structural elements). Some of the information extracted from news video data is shown in Table2 . Information such as the objects present in visuals, the category of a news item, and the main concept (focus or center [7]) depicted by the new item are stored as metadata.... ..."
Cited by 4
Table 2 Database table: metadata
2003
"... In PAGE 5: ...able 1 Java object storing the link structure................................................................... 8 Table2 Database table: metadata .... ..."
Table 1. Table of metadata.
"... In PAGE 2: ... First of all, this system chooses the shot from the video material according to the cinematic rules stored in the production memory. Each cut of video material is stored in the MySQL database indexed by the metadata shown in Table1 . The engine of the video editing system is forward- chaining production system, implemented in Prolog.... In PAGE 3: ...ig. 2. Snapshot of the editing process. The first column of the Table1 shows the name of the metadata. The next column indicates the explanation of the metadata.... In PAGE 4: ...Table1 . We propose the mining method that can extract the frequent cinematic rules from the multi-streams of data in Fig.... ..."
Table 2: a metadata entry.
"... In PAGE 5: ...7); There might be hundreds ofapplication processes, with hundreds ofinterleaved, concurrently arriving messages per process, so we might need tens ofthousands ofthese structures-too many to store on the interface card.2 We chose one mechanism to solve all ofthese problems: a 128-byte metadata entry is provided for each expected message ( Table2 ). These entries are arranged in a vector, called a metadata area, whose base and bound are stored in a slotdata structure.... ..."
Table 1: Metadata management proposals
2007
"... In PAGE 2: ...i.e., a block) of a tuple [12] or a complex XML element [3]. A common denominator of the approaches in Table1 is the use of metadata in querying. Some use it to restrict query results, which may [6, 16] or may not [5] include metadata alongside the actual data results.... In PAGE 2: ... Others query and retrieve metadata independently of the data to which it is associated [15]. It is also worth observing that each entry in Table1 is tailored to specific kinds of metadata, and is not directly applicable to other kinds, at least not without some major modifications. Past attempts at building generic metadata stores (e.... In PAGE 2: ... A simple, elegant approach to uniformly model and query data, arbitrary metadata and their association has been elusive. Another observation from Table1 is that metadata has to be ex- plicitly associated with each data item it refers to. There are, how- ever, practical scenarios in which an intensional association may be more appropriate.... ..."
Cited by 2
Results 1 - 10
of
6,591