Component: Topic
Stay organized with collections
Save and categorize content based on your preferences.
outlined_flag
Topics are labels attached to concepts and are hierarchically organized, containing textual information and potentially child topics.
Each topic has a unique identifier ("id") and an optional parent topic identifier ("parentTopic").
Child topics can be nested within their parent topic, with their order signifying importance for display.
The "info" element provides textual information about the topic, including name, description, and URL.
Element: Topic / info
Namespace
http://schemas.google.com/dspl/2010
Annotations
Textual information about the topic.
Diagram
Type
Info
Properties
Model
name , description{0,1} , url{0,1}
Children
description , name , url
Instance
<info>
<name>{1,1}</name>
<description>{0,1}</description>
<url>{0,1}</url>
</info>
Source
<xs : element name = "info" type = "Info" >
<xs : annotation >
<xs : documentation>Textual information about the topic .</ xs : documentation >
</ xs : annotation >
</ xs : element >
Element: Topic / topic
Namespace
http://schemas.google.com/dspl/2010
Annotations
Child topics can be inlined inside their parent topic. If so,
the order of children is meaningful and should be respected by
applications that display these topics.
Diagram
Type
Topic
Properties
content:
complex
minOccurs:
0
maxOccurs:
unbounded
Model
info , topic*
Children
info , topic
Instance
<topic id="" parentTopic="">
<info>{1,1}</info>
<topic id="" parentTopic="">{0,unbounded}</topic>
</topic>
Attributes
QName
Type
Fixed
Default
Use
Annotation
id Id required
The unique identifier of the topic in the
dataset.
parentTopic xs:QName
optional
The id of the parent topic of this topic, if it has one.
parentTopic cannot be specified for topics that are inlined inside
other topics.
Source
<xs : element name = "topic" type = "Topic" minOccurs = "0" maxOccurs = "unbounded" >
<xs : annotation >
<xs : documentation>Child topics can be inlined inside their parent topic . If
so , the order of children is meaningful and should be
respected by applications that display these topics .</ xs : documentation >
</ xs : annotation >
</ xs : element >
Complex Type: Topic
Namespace
http://schemas.google.com/dspl/2010
Annotations
A topic is a label that can be attached to concepts. Topics are
organized hierarchically.
Diagram
Used by
Model
info , topic*
Children
info , topic
Attributes
QName
Type
Fixed
Default
Use
Annotation
id Id required
The unique identifier of the topic in the
dataset.
parentTopic xs:QName
optional
The id of the parent topic of this topic, if it has one.
parentTopic cannot be specified for topics that are inlined inside
other topics.
Source
<xs : complexType name = "Topic" >
<xs : annotation >
<xs : documentation>A topic is a label that can be attached to concepts . Topics
are organized hierarchically .</ xs : documentation >
</ xs : annotation >
<xs : sequence >
<xs : element name = "info" type = "Info" >
<xs : annotation >
<xs : documentation>Textual information about the topic .</ xs : documentation >
</ xs : annotation >
</ xs : element >
<xs : element name = "topic" type = "Topic" minOccurs = "0" maxOccurs = "unbounded" >
<xs : annotation >
<xs : documentation>Child topics can be inlined inside their parent topic . If
so , the order of children is meaningful and should be
respected by applications that display these topics .</ xs : documentation >
</ xs : annotation >
</ xs : element >
</ xs : sequence >
<xs : attribute name = "id" type = "Id" use = "required" >
<xs : annotation >
<xs : documentation>The unique identifier of the topic in the dataset .</ xs : documentation >
</ xs : annotation >
</ xs : attribute >
<xs : attribute name = "parentTopic" type = "xs:QName" use = "optional" >
<xs : annotation >
<xs : documentation>The id of the parent topic of this topic , if it has one . parentTopic
cannot be specified for topics that are inlined inside other topics .</ xs : documentation >
</ xs : annotation >
</ xs : attribute >
</ xs : complexType >
Attribute: Topic / @id
Namespace
No namespace
Annotations
The unique identifier of the topic in the dataset.
Type
Id
Properties
Facets
Used by
Source
<xs : attribute name = "id" type = "Id" use = "required" >
<xs : annotation >
<xs : documentation>The unique identifier of the topic in the dataset .</ xs : documentation >
</ xs : annotation >
</ xs : attribute >
Attribute: Topic / @parentTopic
Namespace
No namespace
Annotations
The id of the parent topic of this topic, if it has one.
parentTopic cannot be specified for topics that are inlined inside other
topics.
Type
xs:QName
Properties
Used by
Source
<xs : attribute name = "parentTopic" type = "xs:QName" use = "optional" >
<xs : annotation >
<xs : documentation>The id of the parent topic of this topic , if it has one . parentTopic
cannot be specified for topics that are inlined inside other topics .</ xs : documentation >
</ xs : annotation >
</ xs : attribute >
Created using the
oXygen XML Editor .
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-06-26 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-06-26 UTC."],[],["The core content describes the \"Topic\" element and its \"Info\" component within a data structure. A topic has an `id` for unique identification and an optional `parentTopic` to establish hierarchy. Topics contain `info` (textual information), and can have child `topic` elements, respecting their order. The `info` includes `name`, `description`, and `url`. Applications should maintain this hierarchical structure. `id` is required, `parentTopic` is optional, and child topics are inlined.\n"]]
