hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.1.10.1 issuerUniqueID | This field is optional and appears in X.509 v2 or v3 only. It enables to reuse the IssuerName over time. It is redundant with the issuer Name, and it is proposed here that this field be not parsed by the client. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.1.10.2 subjectUniqueID | This field is optional and appears in X.509 v2 or v3 only. It enables to reuse the subjectName over time. It is redundant with the subject Name, and it is proposed here not to use this field. The subject name may be carried in the subject field and/or the subjectAltName extension. If the subject is a CA (e.g. the basic... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.1.11 SubjectPublic Key Info | This field is used to carry the public key which is certified and identifies the algorithm with which the key is used. The algorithm is identified using the AlgorithmIdentifier structure (see clause 12.11.1.2, "signatureAlgorithm") and the public key is represented as a bitstring. SubjectPublicKeyInfo ::= SEQUENCE { al... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.1.12 Unique Identifiers | These fields may only appear if the version is 2 or 3. The subject and issuer unique identifiers are present in the certificate to handle the possibility of reuse of subject and/or issuer names over time. This profile recommends that names not be reused for different entities and that Internet certificates not make use... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.1.13 Extensions | This field may only appear if the version is 3 and is optional. If present, this field is a SEQUENCE of one or more certificate extensions. Extensions ::= SEQUENCE SIZE (1..MAX) OF Extension Extension ::= SEQUENCE { extnID OBJECT IDENTIFIER, critical BOOLEAN DEFAULT FALSE, extnValue OCTET STRING } The extensions are de... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.2.1 Authority key identifier | This extension is used where an issuer has multiple signing keys. It provides a means of finding the public key that can be used to check the signature of the certificate. The identification can be based on either the keyIdentifier or the on the pair (authorityCertIssuer, AuthorityCertSerialNumber). It is recommended t... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.2.2 Subject key identifier | This extension provides of identifying certificates that contain a particular public key. SubjectKeyIdentifier ::= KeyIdentifier |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.2.3 Key usage | The key usage extension defines the purpose of the key contained in the certificate. keyUsage ::= BIT STRING { digitalSignature (0), nonRepudiation (1), keyEncipherment (2), dataEncipherment (3), keyAgreement (4), keyCertSign (5), cRLSign (6), encipherOnly (7), decipherOnly (8) } |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.2.4 Private key usage period | This field is used to defined a period of validity for the private key which is different from the period of validity of the certificate. This is only meaningful for digital signature keys. privateKeyUsagePeriod EXTENSION ::= { SYNTAX PrivateKeyUsagePeriod IDENTIFIED BY id-ce-privateKeyUsagePeriod } PrivateKeyUsagePeri... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.2.5 Certificate policies | This field is used to define a policy defining the purpose for which the certificate may be used. Applications may have a list of specific policies they will accept, the certificate validation software must be able to compare the policy OIDs found in the certificate to that list. certificatePolicies EXTENSION ::= { SYN... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.2.6 Policy mappings | This field is used to define equivalence between policies from different CA's policy Domain. policyMappings EXTENSION ::= { SYNTAX PolicyMappingsSyntax IDENTIFIED BY id-ce-policyMappings } PolicyMappingsSyntax ::= SEQUENCE SIZE (1..MAX) OF SEQUENCE { issuerDomainPolicy CertPolicyId, subjectDomainPolicy CertPolicyId } |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.2.7 Subject Alternative Name | This field is used to define additional identities for the subject name of the certificate (such as an internet email address). subjectAltName EXTENSION ::= { SYNTAX GeneralNames IDENTIFIED BY id-ce-subjectAltName } GeneralNames ::= SEQUENCE SIZE (1..MAX) OF GeneralName GeneralName ::= CHOICE { otherName [0] INSTANCE O... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.2.8 Issuer Alternative Name | This field is similar to the previous one for the issuer identity. issuerAltName EXTENSION ::= { SYNTAX GeneralNames IDENTIFIED BY id-ce-issuerAltName } |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.2.9 Subject Directory attributes | This field is used to carry optional directory attributes associated with the subject. subjectDirectoryAttributes EXTENSION ::= { SYNTAX AttributesSyntax IDENTIFIED BY id-ce-subjectDirectoryAttributes } AttributesSyntax ::= SEQUENCE SIZE (1..MAX) OF Attribute ETSI ETSI TS 102 728 V1.2.1 (2011-09) 237 |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.2.10 Basic Constraints | This field indicates if the subject of the certificate is a certification authority and how deep a certification path may exist through that path. This extension shall appear in every CA Certificates. It will be used to prevent unauthorized entities to act as a CA. basicConstraints EXTENSION ::= { SYNTAX BasicConstrain... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.2.11 Name Constraints | This field indicates a namespace within which all subject names in subsequent certificates in a certification path shall be located. nameConstraints EXTENSION ::= { SYNTAX NameConstraintsSyntax IDENTIFIED BY id-ce-nameConstraints } NameConstraintsSyntax ::= SEQUENCE { permittedSubtrees [0] GeneralSubtrees OPTIONAL, exc... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.2.12 Policy Constraints | This field is only used in CA's certificate (i.e. not in end entity certificate). It is used to prohibit policy mapping or to require that each certificate in a path contain an acceptable policy identifier. policyConstraints EXTENSION ::= { SYNTAX PolicyConstraintsSyntax IDENTIFIED BY id-ce-policyConstraints } PolicyCo... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.2.13 Extended key usage field | This field is an extensions of the previous field keyUsage. It is used to define more purposes for which the certified public key may be used. extKeyUsage EXTENSION ::= { SYNTAX SEQUENCE SIZE (1..MAX) OF KeyPurposeId IDENTIFIED BY id-ce-extKeyUsage } KeyPurposeId ::= OBJECT IDENTIFIER ETSI ETSI TS 102 728 V1.2.1 (2011-... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 12.11.2.14 CRL Distribution points | This field defines how CRL (Certificate revocation list) information can be obtained. cRLDistributionPoints EXTENSION ::= { SYNTAX CRLDistPointsSyntax IDENTIFIED BY id-ce-cRLDistributionPoints } CRLDistPointsSyntax ::= SEQUENCE SIZE (1..MAX) OF DistributionPoint DistributionPoint ::= SEQUENCE { distributionPoint [0] Di... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13 Graphics reference model | 13.1 Introduction The current document provides tools to control the positioning of: video on an output device, interface components such as buttons and lists, as well as raw graphical primitives. Each screen connected to a GEM has three planes which are, from back to front, a background plane, a video plane and a grap... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.1.1 Interapplication interaction | If the presentations of different applications overlap, the areas obscured by other applications are clipped. Therefore where an application is translucent it will be blended with the video or background image behind it rather than being blended with another application. ETSI ETSI TS 102 728 V1.2.1 (2011-09) 242 |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.2 General Issues | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.2.1 Coordinate Spaces | The present document includes a number of coordinate systems for different purposes and includes the means to transform between these as needed: • Input video space. This considers post upsampling MPEG pixels. • Device space. Logical pixels in the various display devices. There may be different device spaces for the va... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.2.1.1 Normalized screen space | A normalized screen coordinate system supports references to positions and sizes in the video output from a GEM device without reference to any form of pixels. This coordinate system describes the top left corner of the screen as {0, 0} and the bottom right corner of the screen as {1, 1}. This coordinate system is used... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.2.1.2 User space | The coordinate space for graphics used in java.awt is defined by applications through the creation of an HGraphicsDevice. The root container, an instance of the class org.havi.ui.HScene can be placed within the normalized coordinate system. The HSceneTemplate class allows applications to express requirements for their ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.2.1.3 Pixel Aspect Ratio | A pixel orientated coordinate system does not say anything about the pixel aspect ratio. The pixel aspect ratio (ARx pixel / ARy pixel) is defined by the aspect ratio of the display (ARx display / ARy display, 4:3 or 16:9), the area that is covered by the HGraphicsDevice (wn, hn) and the pixel resolution of the HGraphi... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.2.1.4 Video space | The coordinate space for video is that defined by the input video signal after any scaling required by the platform (e.g. that required by ETR154). Scaling and clipping of video can be achieved using the JMF control org.dvb.media.VideoPresentationControl. The JMF control VideoFormatControl allows applications to query ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.2.2.1 Principles | Under some circumstances there are dependencies between configurations of the various HAVi screen devices that are composed together to be output as a single screen. Two example reasons for this are the following: • The video output signal for a screen must have a single aspect ratio - either 4:3 or 16:9 for standard d... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.2.2.2 Usage examples for standard definition, 625-line markets | If the aspect ratio of the video output signal is 4:3 then the configuration of each HAVi HScreenDevice that contributes to that signal must have a configuration shown in table 82, "Sets of coherent configurations for standard definition - 625-line markets" as having a screen aspect ratio of 4:3. Similarly if the aspec... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.2.2.3 High definition usage examples | The minimum requirements for support of HD are defined in clause G.1.1.3, "High definition" of the present document. These requirements result in 5 coherent sets of HAVi screen device configurations. These are shown below for 625-line/50 Hz markets. For 525-line/60 Hz markets, 720 x 576, 64/45 and 56/45 should be repla... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.2.2.4 Scalability and extensibility | GEM terminals may support additional HAVi screen devices and configurations beyond the minimum requirements defined in clause G.1.1, "Device capabilities" of the present document. No particular issues arise where the minimum required HAVi screen devices support additional configurations. GEM applications may discover t... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.3 Graphics | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.3.1 Modelling of the GEM display stack composition | The following clauses describes the theoretical model of the GEM display stack. Unfortunately, certain real world constraints may apply see clause 13.6, "Approximations". The "Graphics, Video and Subtitle pipeline" is illustrated in figure 22. Figure 22 shows the conceptual model of the "graphical content" pipelines fr... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.3.2 AWT Reference Model in the GEM | In the AWT all graphics rendering of the lightweight components is done via the java.awt.Graphics class. When a component needs to be redrawn it issues a repaint command which gets passed from component to component from top to bottom until a heavyweight component is reached. Although the enhanced and interactive profi... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.3.3 HAVi devices and AWT components | The top level user interface container for DVB-J applications is represented by the org.havi.ui.HScene class. DVB-J applications may obtain an instance of this class from an instance of org.havi.ui.HSceneFactory. The HSceneFactory class provides a number of methods which may be used to obtain an HScene depending on the... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.3.3.1 Video and graphics pixel aligned | The VIDEO_GRAPHICS_PIXEL_ALIGNED relationship between the pixels in the HGraphicsDevice and the pixels in the HVideoDevice is shown in figure 26. NOTE: The relationship applies to the pixels in HVideoDevice after "Decoder Format Conversion" processing, and the pixels in HGraphicsDevice. As a result of this relationship... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.3.3.2 Zero graphics impact | Constants ZERO_GRAPHICS_IMPACT and ZERO_VIDEO_IMPACT can be used by applications to prevent changes to the HGraphicsDevice or the HVideoDevice respectively, in the case that changes are not intended. In general a change of the configuration of the HGraphicsDevice may lead to an automatic change of the configuration of,... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.3.4 Composition | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.3.4.1 AWT paint rule | The normal AWT paint rules shall be followed. That is the root container (the HScene) is painted and then its components are painted recursively. The observed behaviour shall be such that of each component drawing directly into the root component. Any use of temporary storage or double buffering shall not affect the fi... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.3.5 Composition Rules | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.3.5.1 Components generally | By setting an appropriate DVBAlphaComposite rule on a DVBGraphics and using translucent colours blending may be achieved. By repeated placement of components complex scenes can be described. In figure 28 the background picture (of the harbour) is representative of the video plane. The translucent grey rectangle is draw... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.3.6 Extensions to the AWT graphics capabilities | For graphics the GEM specification mainly uses AWT facilities defined in PBP 1.1 [4]. However, certain extensions are made. In order to allow compositing in GEM applications, the graphics capabilities of PBP 1.1 [4] have been extended by providing the org.dvb.ui package. ETSI ETSI TS 102 728 V1.2.1 (2011-09) 255 The pa... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.3.6.1 Graphics Objects in GEM applications | The class org.dvb.ui.DVBGraphics extends the normal java.awt.Graphics class by adding support for alpha compositing. In a GEM application each platform-created graphics object shall be an instance of org.dvb.ui.DVBGraphics. DVBGraphics and DVBAlphaComposite has a principle support of 8 different Porter-Duff compositing... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.3.6.2 Buffered Image | The class DVBBufferedImage in the package org.dvb.ui adds the support for an accessible, transparent Image which can be used e.g. for off screen buffers. Two different platform dependent sample models are supported by DVBBufferedImage. When doing compositing in the TYPE_BASE sample model approximations may be applied (... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.3.6.3 DVBColor | NOTE: The general philosophy of this class has been to imitate the features of JDK 1.2 dealing with colour. Unless explicitly specified otherwise, the internal implementation of the platform (e.g. java.awt) shall use the org.dvb.ui.DVBColor class instead of the java.awt.Color where technically possible (e.g. not the co... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.3.6.3.1 Modified packed colour representation | The most significant byte of the integer representation of an RGB colour is defined to hold an alpha value as is illustrated in figure 29. This data type is used in various of the constructors and methods described in the API documentation. It is referred to in the API documentation as TYPE_INT_ARGB. Figure 29: GEM col... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.3.7 14:9 Aspect Ratio Support | Support for the 14:9 aspect ratio is optional in GEM terminal specifications. As well as the real display aspect ratios of 4:3 and 16:9, GEM defines a 14:9 aspect ratio. When this is in effect, all text will be subject to moderate aspect ratio distortion. However, broadcasters will be able to predict text flow without ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.3.8 Interaction between graphics from GEM and resident applications | If application graphics are wholly or partly obscured by graphics from resident applications (e.g. the GEM navigator), then either: a) the resident application shall restrict itself to the use of opaque colours; or b) the composition between the graphics of the resident application and those of GEM applications shall b... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.4 Video | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.4.1 Component-based players and background players | Video is received by a GEM application as an MPEG sequence of compressed frames, each of which contains a large number of picture elements (pels) arranged in rows and columns. The GEM application decodes the MPEG stream to a presented stream which may be placed either in the video plane, or in a component in the graphi... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.4.2 Modelling MPEG decoding and presentation pipeline | Figure 30 illustrates the underlying format conversion control process in a TS 101 154 [2] compliant SD digital receiver. In this model the video decoder produces "full-screen" video from the MPEG data (i.e. the decoder resolves any sub-sampling in the MPEG broadcast). Subsequent "Decoder Format Conversion" adapts this... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.4.3 Coordinate Spaces | The input to the Decoder Format Conversion block is always full screen video. If necessary, the MPEG video decoder block performs up-sampling as required by TS 101 154 [2] to get full screen video. An application expresses the video clipping in terms of the pixel-based coordinate space of the full screen video. For 50 ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.4.4 Video components | A scaled portion of a video can be presented as a component within the AWT hierarchy. The controls that influence this presentation are parts of AWT and JMF. ETSI ETSI TS 102 728 V1.2.1 (2011-09) 259 Video components are treated just like any other component. However, it shall be noted that pixels within the video have... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.5 Subtitles | This clause only applies to GEM terminal specifications for which subtitling is available. If subtitling signalling is available, the presentation of subtitles shall follow the model specified here. Further, the introduction to subtitles contained in clause 13.1 and the components related to subtitles in figure 17 clau... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.5.1 Language and presentation setting | The following reference model shows the how the presentation of subtitles is controlled. The selection of the subtitles language depends by default on the user's preferences, the audio language and can be overridden by the application. The end user can set the subtitles on or off where the default depends on the prefer... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.5.2 Relation to graphics | Ideally, subtitles should be presented on top of the video plane but below the graphics plane(s). However, GEM terminals conforming to the present document are only required to support subtitles in areas where they are not overlapped by application graphics (i.e. by an HScene for a DVB-J application). If any GEM applic... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.5.3 Coordinate Spaces | Subtitles are decoded into a plane with the same coordinate system and position as the HVideoDevice. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.6 Approximations | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.6.1 Approximations in composition | The GEM specification references the Porter-Duff rules for composition (see Porter-Duff).The minimum set of operations required is defined in (clause G.1.3.1, "Composition rules"), in addition the implementation of the compositions may be approximated as detailed below. ETSI ETSI TS 102 728 V1.2.1 (2011-09) 261 |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.6.1.1 Implementation of modes | Typical implementations have a hardware blending process that blends the graphics plane over the video using SRC_OVER (see figure 35). This places certain practical limitations on the purity of the display model. Figure 35: Typical current technology implementation The SRC rule simply requires that the colour and alpha... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.6.1.1.1 Graphics directly over video | When drawing graphics directly over video: • The effect of SRC_OVER mode is as expected as the alpha value of the drawn graphics is used to control blending of the graphics with the video. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.6.1.1.2 Graphics over other graphics | 13.6.1.1.2.1 SRC If graphics are painted over other graphics using SRC mode the result is as expected. 13.6.1.1.2.2 SRC_OVER If graphics are painted over other graphics using SRC_OVER mode the result will be implementation dependent when 0 < alpha < 1. Drawing with colour where alpha = 0 (i.e. fully transparent) shall ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.6.1.2 Approximation of alpha | The precision of implementation of alpha depends on the DVBGraphics object concerned. The minimum requirements are specified in Annex G, "Minimum platform capabilities". The actual colour used for a given colour can be queried using org.dvb.ui.DVBGraphics.getBestColorMatch(). ETSI ETSI TS 102 728 V1.2.1 (2011-09) 263 |
238e580d718f360a78b094505f1c62e3 | 102 728 | 13.6.1.3 Approximation of colour | Logically the colour model is a "true colour" one. However, colour approximation is allowed as described in clause G.1.5, "Colour capabilities". |
238e580d718f360a78b094505f1c62e3 | 102 728 | 14 System integration aspects | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 14.1 Namespace mapping | GEM does not mandate any particular format for locators. Note, however, that clause 14.8, "Locators and content referencing" requires that terminal specifications based on GEM define some text representation for certain entities. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 14.2 Reserved names | File names starting with the characters "dvb." are reserved for use as "well known" files defined in this or future specifications. Authors shall not use file names with this form to avoid possible collision with standards defined files. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 14.3 XML notation | These XML notation rules only apply to XML file formats defined in GEM. These rules shall apply to the processing and encoding of all the files where XML is used as an encoding format in a GEM application. Rules for encoding of the XML formatted files: • The file shall be a well-formed XML document (but not necessarily... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 14.4 Network signalling (error behaviour) | The behaviour of GEM terminals when receiving incorrectly formatted data, however transmitted or otherwise acquired, is implementation dependent except where a specific error behaviour is required by GEM or referenced specifications. GEM terminals may implement whatever strategy they like for this situation. It is an a... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 14.5 Text encoding of application identifiers | Where an organisation_id or application_id is encoded in textual form it shall be encoded as follows: • A hexadecimal representation of the value. • Lower case letters. • No extra leading zeros (as would be produced by Integer.toHexString). ETSI ETSI TS 102 728 V1.2.1 (2011-09) 266 Where both an organisation_id and app... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 14.6 Filename requirements | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 14.6.1 Persistent storage | Receivers shall support path and file names as specified by persistentpath and persistentfilename in the following BNF: lowalpha = "a" | "b" | "c" | "d" | "e" | "f" | "g" | "h" | "i" | "j" | "k" | "l" | "m" | "n" | "o" | "p" | "q" | "r" | "s" | "t" | "u" | "v" | "w" | "x" | "y" | "z" upalpha = "A" | "B" | "C" | "D" | "... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 14.6.2 DSMCC object carousel | Receivers shall support object carousels at least matching these requirements; • File paths (i.e. the concatenation of directory names, directory separators and a filename) must be ≤ 1 024 bytes long. • Within the file path requirement, file and directory names must be ≤ 255 bytes. • The OC file system shall be case se... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 14.6.3 Stored applications | Receivers shall support file and path names in stored applications as defined for the object carousel in clause 14.6.2, "DSMCC object carousel" except as follows: • File systems for stored applications shall be either case sensitive or "case preserving". Applications to be stored shall be written to work on both of the... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 14.7 Files and file names | The locator format shall be able to reference any valid file name; at least the minima specified in clause B.2.1 shall be supported. The GEM specification defines how applications can use the names of files in order to access content held in files. It is intentionally silent about the file systems and file system names... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 14.8 Locators and content referencing | Table 59 lists the types of entity that may be addressed by locators in GEM, and defines the entities for which a text representation is required. In the case of locators, where a text representation is required GEM does not specify what that representation is, however GEM terminal specifications shall supply an unambi... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 14.9 Content referencing for IPTV/ OTT | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 14.9.1 Introduction (informative) | Java TV defines the concepts of transport independent locators and transport dependent locators. Services are equal if their Locators are equal which requires their external forms are equal. GEM permits both of the following: • transport independent references to a service where there is no requirement for GEM applicat... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 14.9.2 Details | Table 60 shows the different forms of locators which are applicable to GEM. Table 60: Locators and URLs Type of reference Class External Form Transport independent org.davic.net.dvb.DvbLocator "dvb:" as in MHP [1], clause 14.1, "Namespace mapping (DVB Locator)" Transport dependent Service accessed via classic DVB netwo... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 15 Detailed platform profile definitions | This clause defines the capabilities of platforms as presented to applications. Products that claim to conform to a profile shall provide at least the minimum capabilities identified for the profile. In some cases this implies that specific hardware resources are present in the platform. All GEM platforms must support ... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 15.1 PNG - restrictions | PNG is defined as in PNG Version 1.0 [42]; later versions of PNG introduce additional chunk types, which are not required to be supported. Receivers should ignore gAMA (gamma) and cHRM (chromaticity) chunks in PNG files. GEM terminals are required to support all of the PNG colour types defined in PNG Specification Vers... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 15.2 Minimum media formats supported by DVB-J APIs | Table 63 specifies the minimum set of media types that implementations of the "Enhanced Broadcast Profile" and "Interactive Broadcast Profile" shall support (see clause 4.1.6, "Profiles"). It also identifies the APIs that shall provide this support: ETSI ETSI TS 102 728 V1.2.1 (2011-09) 274 Table 63: Media type support... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 15.3 JPEG - restrictions | The restricted JPEG specification is as specified in clause 7.1.1.2, "JPEG" except that the "progressive DCT-based" mode is excluded. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 15.4 Locale support | Support of resources for the following locales is required: • One guaranteed Locale java.util.Locale.UK. ("en". "GB"). • Zero (or more) implementation dependent ones. Further it is guaranteed that the default Locale shall have resources. The default Locale is implementation dependent. NOTE: Terminal specifications may,... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 15.5 Video raster format dependencies | This clause addresses the aspects of the present document that vary as a consequence of the video raster format. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 15.5.1 Standard Definition (PAL/SECAM or NTSC resolution) | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 15.5.1.1 Logical pixel resolution | The logical pixel resolution shall be 72 dots per inch. NOTE: This is the a convention adopted by the Java2D API. See the specification of java.awt.Font.getSize(). As a result of this convention, the return value of getSize() gives the size in pixels for a screen device. ETSI ETSI TS 102 728 V1.2.1 (2011-09) 275 |
238e580d718f360a78b094505f1c62e3 | 102 728 | 15.6 Functional equivalents | Table 64 lists the set of mandatory and optional functional equivalents. Those elements marked mandatory shall be defined in a GEM terminal specification. Those marked optional may be defined in a GEM terminal specification. Each functional equivalent is identified by a name in the leftmost column of table 64. If a GEM... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 15.6.1 Modifications to MHP Definitions of Functional equivalents | In certain cases, it may be necessary to slightly modify a functional equivalent. A GEM terminal specification that adopts a functional equivalent may modify it only as described in this clause. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 15.6.1.1 Carousel | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 15.6.1.1.1 NSAP Address | The DVB Carousel NSAP Address structure may be modified by replacing the definition of specifierType, specifierData, and dvb_service_location structures with structures specified in the GEM terminal specification. NOTE: This may be necessary because the dvb_service_location is based on transport_stream_id, original_net... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 15.6.1.1.2 Content type descriptor | If a content type descriptor is not present in a file object, GEM terminal specifications may define another mechanism to determine the MIME type of a file that takes precedence over the mapping based on the extension portion of the file name, provided that a correctly built MHP object carousel will be processed in a w... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 15.6.1.1.3 Application Icons Descriptor | GEM terminal specifications using the functional equivalent of application signalling may define new application types. If they do, they may define icon locator semantics for the application types they introduce in the application icons descriptor. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 15.6.1.2 Application Signalling | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 15.6.1.2.1 Transport protocol descriptor | GEM terminal specifications using the functional equivalent named "application signalling" may define new protocol_ids and corresponding selector bytes provided that new protocol_id values shall be registered with the DVB. 15.6.1.2.2 AIT descriptor tag values GEM terminal specifications that include the functional equi... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 15.6.1.3 Application Name Descriptor | GEM terminal specifications using the functional equivalent named "application signalling" may modify the encoding of the application_name_char field of the application name descriptor provided that all strings that start with the value 0x20 are interpreted as ASCII strings, in accordance with Annex A of EN 300 468 [14... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 16 Registry of constants | |
238e580d718f360a78b094505f1c62e3 | 102 728 | 16.1 System constants | Table 65: Registry of constants Entity Value Description PTimerMinRepeatInterval 40 ms This (or optionally a smaller) value shall be returned by javax.tv.util.TVTimer.getMinRepeatInterval(). See clause 11.9.1, "Timer support". PTimerGranularity 10ms This (or optionally a smaller) value shall be returned by javax.tv.uti... |
238e580d718f360a78b094505f1c62e3 | 102 728 | 16.2 DVB-J constants | Where this clause lists a constant for a class that is not required by the present document (e.g. a class in the package org.dvb.si), that constant is not required. This clause to be populated with the values of public final static symbols from the various Java APIs. |
238e580d718f360a78b094505f1c62e3 | 102 728 | 16.2.1 Public and Protected final static primitive fields from DVB packages | The following is a list of the values assigned for public and protected final static primitive fields defined in the DVB defined DVB-J packages: public final static int org.dvb.application.AppAttributes.DVB_J_application = 1; public final static int org.dvb.application.AppAttributes.DVB_HTML_application = 2; public fin... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.