0% found this document useful (0 votes)

50 views37 pages

NSML 3.1 Specification

The document defines the News Story Markup Language (NSML), which is an SGML based markup used to express all the content and information about a news story. It describes the various elements and structure of NSML including the head, form, fields, body, and attachment sections. It also outlines changes made between different versions of NSML.

Uploaded by

myazazel

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

50 views37 pages

NSML 3.1 Specification

Uploaded by

myazazel

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 37

Avid Technology, Inc.

iNEWS NRCS

News Story Markup Language

Engineering Specification

Version 3.1
30 August 2010

NOTICE: Avid Technology, Inc. accepts no responsibility for the accuracy of the
information contained herein and reserves the right to change the contents without prior
notice.
News Story Markup Language v3.1 30 August 2010
Engineering Specification

NSML – A Markup Language for News Stories

Version 3.1

1 Introduction
The purpose of this document is to define the News Story Markup Language (NSML). NSML is an SGML
based markup which is used to express all the content and information about a story. It also can describe a
form that can be used to describe the presentation of fields when displayed.

NSML is used to express seven separate aspects of a story. NSML expresses meta information about a
story in the <head> section; it expresses the appearance of the story when displayed in the <form>
section; it expresses the story content in the <fields>, <body>, and <aeset> sections; and it expresses
arbitrary attachments in the <field-atts> and <aeset-atts> sections.

1.1 Changes from 2.7 to 2.8

The <password> tag was added.
Document the limitations on the idref of an <a/> tag and the id of an <ae> tag.
Note that the sequence of anchored elements conform to the sequence of anchors within the <body> in the
<ae> tag description.
The fields ITEM-CHANNEL, MOS-DURATION, and RUNS-TIME added to list of reserved fields in
section 7.1.
The example was replaced in section 12.

1.2 Changes from 2.8 to 3.0

NSML is now well formed XML. NSML documents can be validated against the NSML XML schema. As
a well formed XML document, tag names are case sensitive.
The <nsml version> attribute is now required and it is now simply a number.
The <look> tag has been removed.
The <story> tag has been removed.
The <form>, <fields>, <body>, and <aeset> tags are now children of the <nsml> tag.
The <img> tag has been removed.
The <meta deleted> attribute has been removed.
Two new attributes were added to the <meta/> tag, “wordlength” and “version”.
The <cell> tag was replaced by the <stringcell>, <comboboxcell>, <checkboxcell>,
<datecell>, and <durationcell> tags. All of these tags were added as content to the <row> tag.
A “wg” attribute was added to all cell tag types.
A “limit” attribute was added to all cell tag types to restrict the content of thefield to its edit size.
The <label>, <entry>, <group>, and <list> tags were added as part of the <comboboxcell>
content.
The <f> tag was replaced by the <string>, <boolean>, <date>, and <duration> tags. All of
these tags were added as content to the <fields> tag.
A “bg” attribute was added to the <string>, <boolean>, <date>, and <duration> tags.

2
News Story Markup Language v3.1 30 August 2010
Engineering Specification

The <bg> tag was added to allow background color highlighting to a sequence of characters. It is similar
to the <b>, <i>, and <u> tags.
The <rtl> tag was added to denote a right to left sequence of characters. It is similar to the <b>, <i>,
and <u> tags.
Font, family, and pitch attributes were added to the <body>, <p>, <aeset>, <ae>, <mc>, and
<ap> tags.
A <bg> tag was added to hold a background color for text.
The <link> tag was added as content to the <p> and <ap> tags. The <show> and <url> tags were
added as content of the new <link> tag.
The <egroup> tag was added as content of the <head> tag..
The <storygroupid> tag was added as content of the <head> tag..
The <form> and <row> tags no longer set default values for all of the cell tag attributes.
Empty tags are now denoted with the “/>” sequence (<a/>, <meta/>, <pb/>, <tab/>, <wp/>, etc.)
All tag attributes names are in lower case.
All tag attribute values are enclosed in quotes.
All tag attributes have the form: name="value"
End tags are no longer optional. Neither are any start tags.
Hidden text has been eliminated. Most of the content was converted to attributes added the <ae> and
<mc> tags. A <hidden> tag was added to the <ae> content to accommodate text unique to ‘J’ type
anchored elements.

1.3 Changes from 3.0 to 3.1

The <sb/>, <projects>, <project>, and <facet> tags were added.

1.4 Precedence
Where the descriptive text of this specification differs with the syntax of the NSML XML Schema, the
Schema takes precedence and should be considered the correct definition of NSML.

2 NSML Grammar
The elements of a story are identified with NSML tags. These tags are organized in a hierarchy. At the top
of the hierarchy is the <nsml> tag which delimits a complete NSML document and contains the story meta
information, story content, story presentation, and attachment elements. The other elements of a story are
nested inside these elements as described by the NSML grammar.

The story grammar defines the ordering and nesting of the tags and story elements. There are two sets of
language elements: terminal – the actual words in the NSML language – and non-terminal – everything else.
The terminals are formatted as tags with their enclosing brackets “<>”, non-terminals are displayed in italic.
There is one predefined non-terminal, plain_text. Plain_text is defined to be regular characters, and
character entities denoted by the ampersand character. A CDATA section can be used to encapsulate
plain_text that contains many NSML markup characters that would otherwise be converted into character
entities.

3
News Story Markup Language v3.1 30 August 2010
Engineering Specification

Elements followed by a ‘?’ are optional and occur at most one time.

Elements followed by a ‘*’ are repeatable zero or more times.

Elements must appear in the order they are listed. Elements that are listed as a group of elements separated
by a ‘|’ indicate a choice. When the group is defined to occur more than one time, the resulting set of
elements can occur in any order.

nsml_tag ::= <nsml>

head_tag ?
projects_tag ?
form_tag ?
fields_tag ?
body_tag ?
aeset_tag ?
field_atts_tag ?
aeset_atts_tag ?
</nsml>

head_tag ::= <head>

projects_tag ::= <projects> (project_tag | facet_tag) * </projects>

form_tag ::= <form> row_tag * </form>

field_atts_tag ::= <field-atts> attachment_tag * </field-atts>

aeset_atts_tag ::= <aeset-atts> attachment_tag * </aeset-atts>

project_tag ::= <project > single_uuid </project >

facet_tag ::= <facet > double_uuid </facet >

single_uuid ::= hexBinary *16

double_uuid ::= hexBinary *32

hexBinary ::= hexDigit hexDigit

row_tag ::= <row> row_content * </row>

4
News Story Markup Language v3.1 30 August 2010
Engineering Specification

row_content ::= <stringcell> plain_text ? </stringcell>

| <checkboxcell> plain_text ? </checkboxcell>
| <comboboxcell> label_tag ? comboboxcell_content * </comboboxcell>
| <datecell> plain_text ? </datecell>
| <durationcell> plain_text ? </durationcell>

label_tag ::= <label> plain_text ? </label>

comboboxcell_content ::= entry_tag

| <group> entry_tag * </group>
| <list> entry_tag * </list>

entry_tag ::= <entry> plain_text ? </entry>

fields_tag ::= <fields> fields_content * </fields>

fields_content ::= <string> plain_text ? </string>

| <boolean> boolean_value ? </boolean>
| <date> date_value ? </date>
| <duration> duration_value ? </duration>

boolean_value ::= “true” | “1” | “false” | “0”

date_value ::= a decimal number representing seconds since 00:00:00 UTC, January 1, 1970

duration_value ::= a decimal number representing seconds

body_tag ::= <body> p_tag * </body>

p_tag ::= <p> p_content * </p>

p_content ::= content_tag

| text_content

content_tag ::= <pi> text_content * </pi>

| <cc> text_content * </cc>

text_content ::= style_tag

| <pb/>
| <sb/>
| <tab/>
| <wp/>
| <a/>
| text_and_links

text_and_links ::= <link> show_tag ? url_tag </link>

| plain_text

show_tag ::= <show> plain_text ? </show>

url_tag ::= <url> plain_text ? </url>

5
News Story Markup Language v3.1 30 August 2010
Engineering Specification

style_tag ::= <b> text_content * </b>

| <i> text_content * </i>
| <u> text_content * </u>
| <rtl> text_content * </rtl>
| <bg> text_content * </bg>

aeset_tag ::= <aeset> ae_tag * </aeset>

ae_tag ::= <ae> hidden_tag ? ae_content * </ae>

hidden_tag ::= <hidden> plain_text ? </hidden>

ae_content ::= mc_tag

| ap_tag

mc_tag ::= <mc> ap_tag * </mc>

ap_tag ::= <ap> ap_content * </ap>

ap_content ::= astyle_tag

| <tab/>
| <wp/>
| text_and_links

astyle_tag ::= <b> ap_content * </b>

| <i> ap_content * </i>
| <u> ap_content * </u>
| <rtl> ap_content * </rtl>
| <bg> ap_content * </bg>

space ::= a single space character (hex20)

attachment_tag ::= <attachment>

plain_text ?
</attachment>

3 NSML Basics
NSML defines a set of tags that are embedded in the story document. NSML tags are delimited by a set of
angle brackets (< and >) and contain a tag name and optional tag attributes. For example the tag
<string id=”title”> has a tag name of string and one attribute id=”title”. Each tag has its
own set of attributes that may be applied to it. In the previous example the attribute name id is set to the
attribute value title. In general, attributes are optional and defaults are assumed if they are not specified.
There are some exceptions to this. The description of each tag in this document points out all of the
required attributes.

3.1 Start and End tags

Most tags define and affect a specific part of an NSML document. This part of the document begins where
the tag with its attributes (known as the start tag) appears in the document and continues to the
corresponding end tag. The end tag has the same name as its corresponding start tag but starts with a </
sequence rather than just a < sequence. For example, </string> is the <string> tag’s end tag. End
tags have no attributes. The part of the document enclosed in a set of start and end tags is referred to as the
tag’s content.

6
News Story Markup Language v3.1 30 August 2010
Engineering Specification

The number of characters in a tag, including the tag name and all attribute names and values but not
including the tag delimiters, cannot exceed 500. This excludes comments and CDATA sections (described
below).

3.2 Empty tags

Some tags never have any content. They may have attributes. The format of these empty tags are similar to
start tags. The only difference is that empty tags end with the two character sequence “/>” . Some
examples are <a/>, <pb/>, <sb/>, <tab/> and <wp/> .

3.3 Character set

The set of characters allowed in tag names and attribute names is the ASCII characters a-z, 0-9, dot and
dash. The first character of a name is always in the set a-z. A name may have a maximum of 12 characters.

Attribute values can be divided into three categories, TEXT, TOKEN and NUMBER values. A NUMBER
value is a string of decimal digits from the ASCII set 0-9. A TOKEN value is a string of ASCII characters
which has the same lexical constraints as tag and attribute names (same character set , same restrictions,
case-insensitive, etc.) A TEXT value is a string of bytes in the range 0x20 to 0xff excluding the double
quote character. TEXT values are case-sensitive. If a TEXT value contains characters not allowed in a
TOKEN then it must be enclosed in double quotes. Values of type TEXT are limited to 100 bytes.

The characters allowed in plain_text content are undefined. The plain_text content is treated as a sequence
of bytes. There are only two exceptions to this. When the plain_text content is parsed byte values in the
range 0x00 to 0x1f are stripped from the content and character entity conversion is done on the plain_text
content. The characters in the range 0x00 to 0x1f may be included in the plain_text content if represented
as character entities.

Plain_text can be encapsulated in a CDATA section. CDATA sections are used to escape blocks of text
containing characters that would otherwise be recognized as NSML markup. A CDATA section starts with
the nine character sequence ( <![CDATA[ ) and ends with the three character sequence ( ]]> ). Within a
CDATA section, only the end sequence ( ]]> ) is recognized as markup, so that left and right angle brackets
and ampersands may occur in the literal form; they need not be escaped using character entities. CDATA
sections cannot nest. Byte values in the range 0x00 to 0x1f, except 0x09, 0x0A, and 0x0D will be stripped
from CDATA sections.

3.4 Character Entities

Anywhere in plain_text characters may be replaced with character entities. This is useful when the
plain_text contains NSML markup characters that could confuse an NSML parser. NSML recognizes the
full set of numeric character entities. Numeric character entities are 1 to 3 decimal digits preceded by &#
and followed by a semicolon, ‘;’. Leading zeros are ignored so > is the same as >. The named
character entities that may appear in plain_text are identified in table 2.1.

Table 2.1 – Character Entities

Named Entity Numeric Entity symbol Description
> > > Greater than
< < < Less than
& & & Ampersand

3.5 Comments
Comments may be included anywhere (outside of tags) within an NSML document. Comments can only be
seen when viewing the raw form of the document. In almost all cases comments should be hidden from the
user’s view. It is allowable for applications that process a document to strip the comments from the

7
News Story Markup Language v3.1 30 August 2010
Engineering Specification

processed document. A comment is any characters between the four character start , “” comment markers (i.e. ). No translation of
comment text is performed. This means that the characters ‘&’, ‘<’, and ‘>’ will be stored in the NSML
document unchanged. Comments cannot be nested - the first “ -->” encountered terminates the comment.

For details on other text that is not intended for display, see the < hidden> tag.

3.6 Base Units

Many of the attribute values are measurements expressed in base units. This measurement is equal to one-
fourth of the average character width of the “system font”. This unit is based on the Microsoft Windows
definition of its Dialog Base Unit. This measurement is device independent, so that applications can use a
single measurement to create a similar appearance on different types of display devices or different font
sizes.

4 NSML top level elements

The version attribute is optional. Its value is TEXT that defines the NSML version used to compose a
document. It must read: version=”3.1”

If not specified an NSML parser is to assume that the document is an earlier version of NSML.

8
News Story Markup Language v3.1 30 August 2010
Engineering Specification

4.4 The <form> tag – define the appearance of the story fields
<form>
Function:
Defines a presentation/appearance of the story’s fields.
Descendents inherit all attributes unless overridden.
Attributes:
None
Contains:
row_tag *
Used in:
nsml_tag

The <form> and </form> tags enclose a presentation description for the fields of a story. It does not
contain any story content. All story content is defined within the <fields>, <body>, and <aeset>
tags. A form is a definition of the layout of the story fields on a “page” when viewed. An NSML document

9
News Story Markup Language v3.1 30 August 2010
Engineering Specification

need not contain a form definition. The presentation of the story is the responsibility of the application
displaying the document that must acquire a form.

The <body> and </body> tags enclose the text of the story. All text must be within paragraphs in the
body element.

The tabs= attribute is optional. Its value is a list of decimal numbers that, if specified, defines the tab stop
positions for all <tabs/> within the text. Each number in the list is the distance from the last stop. The
last value in the list may by a dash, this indicates that the last number in the list is to repeat indefinitely. The
numbers are in base units. For example, tabs=”40 -“ may be specified to place stops at every 40 base
units. If not specified tabs=”24” is assumed. If more than one number is specified in the list, the numbers
are separated by spaces (i.e. tabs=”72 144”).

The script= and width= attributes are optional. They are used to preserve the margin settings used for word
wrapping by the last application that modified the story. The width value is a decimal number that specifies
the width, in base units, used to word wrap the text contained in the <body> tag. The script value is a
decimal number that specifies the width, in base units, used to word wrap the text in the anchored elements.
If the script attribute is not present this indicates the story is not scripted. If the width attribute is not
present the application displaying the body text must choose an appropriate width. See description of
related <wp/> tag.

10
News Story Markup Language v3.1 30 August 2010
Engineering Specification

The pindent= attribute is optional. Its value is a decimal number that defines the left paragraph indent for
all paragraphs in the body of the story. The indent value is expressed in base units from the left. If not set it
is assumed to be zero.

The rindent= attribute is optional. Its value is a decimal number that defines the right paragraph indent for
all paragraphs in the body of the story. The indent value is expressed in base units from the right. If not set
it is assumed to be zero.

The findent= attribute is optional. Its value is a decimal number that defines the indent for the first line of
all paragraphs in the body of the story. The indent value is expressed in base units from the left. If not set it
is assumed to be the same as pindent.

The font= attribute is optional. Its value is a string that is the name of a font to be used for display
throughout the <body> of the story.

The family= attribute is optional. Its value is a decimal number in the range 0 to 5 that represents a font-
family. If not set it is assumed to be zero. The meaning of the font-family values are:
0 Don’t care
1 Roman
2 Swiss
3 Modern
4 Script
5 Decorative

The pitch= attribute is optional. Its value is a decimal number in the range 0 to 2 that represents a pitch
setting. If not set it is assumed to be zero. The meaning of the pitch values are:
0 default
1 fixed
2 variable

See the description of the attributes under the <body> tag description.

11
News Story Markup Language v3.1 30 August 2010
Engineering Specification

4.9 The <aeset-atts> tag – Defining anchored element set attachments

<aeset-atts>
Function:
Delimits the anchored element set attachments.
Attributes:
None
Contains:
attachment_tag *
Used in:
nsml_tag

5 Story Header - the <head> tag content

Contains:
Nothing
Used in:
head_tag

12
News Story Markup Language v3.1 30 August 2010
Engineering Specification

The wire= attribute is optional. If present it indicates that the story is an original, unmodified story received
from a wire service provider. Its value must be one of “f” (flash), “b” (bulletin), “u” (urgent), “r” (routine),
or “o” (other) to indicate the priority of the wire story. If not present, the story is not a wire story.

The mail= attribute is optional. If present it indicates that the story is an original, unmodified story received
as a mail message. Its value must be one of “read” or “unread” to indicate whether the receiver of the mail
message has viewed it. If not present, the story is not a mail message.

The locked= attribute is optional. If present it indicates that a user has locked the story. A user may restrict
access to a story by locking it in one of two ways. Its value must be one of “pass” or “user”. If the value is
“pass” then access is granted to users that can supply the correct password. If the value is “user” then
access is granted only to the user who locked the story. If not present, the story is not locked. See the
description of the <password> tag.

The words= attribute is optional. Its value is a decimal number that, if present, specifies the number of
countable words in the body of the story. Countable words are those words that contribute to the audio read
time of a story. If not present, the number of words is assumed to be zero.

The rate= attribute is optional. Its value is a decimal number that, if present, specifies the read rate to be
used to calculate the audio read time. The read rate is in words per minute. If not present, the rate is
assumed to be zero.

The break= attribute is optional. Its value is either either “true” / “1” or “false” / “0”. A true value indicates
that the story is a story in a rundown which marks a break or divider between segments of the rundown. If this
attribute is not present, false is assumed.

The mcserror= attribute is optional. Its value is either “true” / “1” or “false” / “0”. A true value indicates
that the story is a story in a rundown which contains machine control instructions and at least one of the
instructions cannot be understood by the machine control subsystem. If this attribute is not present, false is
assumed.

The hold= attribute is optional. Its value is either either “true” / “1” or “false” / “0”. A true value indicates
that the story is not eligible for automatic purge. A user will place a hold on a story that he wants to protect
from the automatic data base story purge policy. If this attribute is not present, false is assumed.

The float= attribute is optional. Its value is either either “true” / “1” or “false” / “0”. A true value indicates
that the story is a story in a rundown which has been “floated” by a user. A floating story deserves special
treatment in the rundown because it is not yet included as a story to go on-air. If this attribute is not present,
false is assumed.

The wordlength= attribute is optional. Its value is a decimal number that, if present, specifies the number
of characters that constitute a word in the body of the story.

The version= attribute is optional. Its value is a decimal number that, if present, specifies the version
number of the story. This number starts at 0 when a story is created.

13
News Story Markup Language v3.1 30 August 2010
Engineering Specification

The number= attribute is optional. It is a decimal number which is the internal group number associated
with the group name. It is valid to omit the group name and just specify the group number as in <rgroup
number=”20”/>. If not specified the story has no read group assigned to it.

The number= attribute is optional. It is a decimal number which is the internal group number associated
with the group name. It is valid to omit the group name and just specify the group number as in <wgroup
number=”20”/>. If not specified the story has no write group assigned to it.

The number= attribute is optional. It is a decimal number which is the internal group number associated
with the group name. It is valid to omit the group name and just specify the group number as in <egroup
number=”20”/>. If not specified the story has no editorial group assigned to it.

14
News Story Markup Language v3.1 30 August 2010
Engineering Specification

5.5 The <wcode> tag

<wcode>
Function:
Defines the wire distribution codes assigned to the story when it was originally received.
This is only relevant if the story originated from a wire service provider.
Not all wire stories will have a wire distribution code.
Attributes:
None
Contains:
plain_text ?
Used in:
head_tag

15
News Story Markup Language v3.1 30 August 2010
Engineering Specification

5.10 The <storygroupid> tag

<storygroupid>
Function:
Defines the string used by the News DataBase Server to identify a group of stories.
Each story in the group will have this same identifier.
The format and content of the <storygroupid> is not specified in NSML.
Attributes:
None
Contains:
plain_text ?
Used in:
head_tag

5.11 The <password> tag

<password>
Function:
Defines the password assigned to the story if it is locked with a password.
This should only be present if the locked=”pass” attribute is present in the <meta/> tag.
This will only be included in documents sent and received by iNEWS 2.5 and above systems.
Attributes:
None
Contains:
plain_text ?
Used in:
head_tag

16
News Story Markup Language v3.1 30 August 2010
Engineering Specification

6 Story Associations – the <projects> tag content

7 Story Presentation – the <form> tag content

7.1 The <row> tag

<row>
Function:
Defines a presentation/appearance of a row of fields.
Attributes:
None
Contains:
( stringcell_tag | checkboxcell_tag | comboboxcell_tag | datecell_tag | durationcell_tag ) *
Used in:
form_tag

17
News Story Markup Language v3.1 30 August 2010
Engineering Specification

7.2 The <stringcell> tag

<stringcell>
Function:
Defines a presentation/appearance of a field.
Attributes:
idref id of a tag in the <fields> section
length decimal number
style ”b” | “i” | “u” | “” | space separated list of those letters
align “left” | “right” | “center”
ro boolean_value
aready boolean_value
llength decimal number
lstyle ”b” | “i” | “u” | “” | space separated list of those letters
lalign “left” | “right” | “center”
lposition “left” | “right” | “top” | “bottom”
limit boolean_value
wg decimal number
mandatory boolean_value
Contains:
plain_text ?
Used in:
row_tag

The idref= attribute is optional. It identifies the specific field from the <fields> section which is to be
displayed in this cell. It is the id value that is matched. If not specified the cell is assumed to be blank and
read-only.

The length= attribute is optional. Its value is a decimal number that, if present, defines the length in base
units of the cell. If not specified the length of the cell is assumed to be zero.

The style= attribute is optional. It defines the physical style of the field content displayed in the cell. If not
specified the cell inherits a style from the enclosing <row> or <form> tags. If no style is specified in
either the <cell>, <form> or <row> then the style defaults to normal. The style value must be one of
“b” (bold), “i” (italic), or “u” (underline) or a space separated list of those characters. For example
style=”b u” specifies a style of bold-underline. To specify a normal style, style=”” may be used.

The align= attribute is optional. It defines the alignment of the field content displayed in the cell. The
value must be one of “left”, “right”, or “center”. If not specified, “left” alignment is assumed.

A cell that references a field can inherit some behavior that is associated with the field’s id. For example, a
cell that references the TOTAL-TIME field will be read-only and must contain the sum of the TAPE-TIME
field and the story’s AUDIO-TIME field. This behavior is an implied attribute of the field with id=TOTAL-
TIME.

The ro= attribute is optional. Its value is either “true” / “1” or “false” / “0”. A true value indicates that the
cell is read-only. A cell is either read-write or read-only depending on the behavior inherited from the
referenced field. A cell than has this attribute set to “true” overrides the read-write access of the referenced
field. A cell presenting a field that is read-only can not force the cell to read-write. If this attribute is not
present, false is assumed which means the cell is read-write.

The aready= attribute is optional. Its value is either “true” / “1” or “false” / “0”. A true value indicates
that the field referenced by the cell via the idref= attribute is to acquire the aready attribute when a new
story is created. If this attribute is not present, false is assumed.

18
News Story Markup Language v3.1 30 August 2010
Engineering Specification

The content of a stringcell_tag is the text of the cell label. Each cell may have one label, the label appears
in its own presentation area either to the left, right, top or bottom of the cell. The stringcell_tag has some
attributes that affect the appearance of the label.

The llength= attribute is optional. Its value is a decimal number that, if present, defines the length in base
units of the cell label. If not specified the length of the cell label is assumed to be zero.

The lstyle= attribute is optional. It defines the physical style of the cell label. If not specified the cell label
inherits a style from the enclosing <row> or <form> tags. The lstyle attribute value has the same values
as the style attribute.

The lalign= attribute is optional. It defines the alignment of the cell label. The value must be one of “left”,
“right”, or “center”. If not specified, “left” alignment is assumed.

The lposition= attribute is optional. It defines the placement of the label relative to the cell. It must be one
of “left”, “right”, “top”, or “bottom”. If not specified “top” is assumed.

The limit= attribute is optional. Its value is either “true” / “1” or “false” / “0”. A true value indicates that
the text content of the field referenced by the cell via the idref= attribute is limited to what fits into the
visible space of the cell as defined by the length= attribute. If this attribute is not present, false is assumed.

The wg= attribute is optional. It defines a write group that restricts editing of the field to members of that
group. It is a decimal number which is the internal group number of the group. If not specified the
cell/field has no write group assigned to it. If this attribute is present it affects the ro= attribute of the
corresponding field only when that attribute is false and the user attempting to edit the field is not a member
of the group.

The mandatory= attribute is optional. Its value is either “true” / “1” or “false” / “0”. A true value
indicates that the field referenced by the cell via the idref= attribute cannot be empty. If this attribute is not
present, false is assumed.

19
News Story Markup Language v3.1 30 August 2010
Engineering Specification

7.3 The <checkboxcell> tag

<checkboxcell>
Function:
Defines a presentation/appearance of a checkbox field.
Attributes:
idref id of a tag in the <fields> section
length decimal number
style ”b” | “i” | “u” | “” | space separated list of those letters
align “left” | “right” | “center”
ro boolean_value
aready boolean_value
llength decimal number
lstyle ”b” | “i” | “u” | “” | space separated list of those letters
lalign “left” | “right” | “center”
lposition “left” | “right” | “top” | “bottom”
limit boolean_value
wg decimal number
mandatory boolean_value
Contains:
plain_text ?
Used in:
row_tag

See the description of the attributes under the stringcell_tag description.

7.4 The <comboboxcell> tag

20
News Story Markup Language v3.1 30 August 2010
Engineering Specification

The locked= attribute is optional. It determines the behavior of the combobox field. Its value is either
”true” | “1” | “false” | “0”. A true value indicates only entries in the drop down list can be entered into the
field. Otherwise any text can be entered into the field. If this attribute is not present, “true” is assumed

See the description of the other attributes under the stringcell_tag description.

The bg= attribute is optional. It defines a background color that will be applied to the field when this entry
is selected from the combobox list. It is a decimal number which identies a system color. System colors
are not defined in this specification. If not specified it defaults to zero and implies that no background color
will be applied to the field.

The id= attribute is required. This is the name of a user group.

21
News Story Markup Language v3.1 30 August 2010
Engineering Specification

The bg= attribute is optional. It defines a background color that will be applied to the field when a member
of the group is selected from the combobox list. It is a decimal number which identies a system color.
System colors are not defined in this specification. If not specified it defaults to zero and implies that no
background color will be applied to the field.

The id= attribute is required. This is the name of a system list that contains zero or more text strings.

The bg= attribute is optional. It defines a background color that will be applied to the field when entry in
the system list is selected from the combobox list. It is a decimal number which identies a system color.
System colors are not defined in this specification. If not specified it defaults to zero and implies that the
background color contained in the system list for an entry will be applied to the field.

7.5 The <datecell> tag

<datecell>
Function:
Defines a presentation/appearance of a date field.
Attributes:
idref id of a tag in the <fields> section
length decimal number
style ”b” | “i” | “u” | “” | space separated list of those letters
align “left” | “right” | “center”
ro boolean_value
aready boolean_value
llength decimal number
lstyle ”b” | “i” | “u” | “” | space separated list of those letters
lalign “left” | “right” | “center”
lposition “left” | “right” | “top” | “bottom”
limit boolean_value
wg decimal number
mandatory boolean_value
Contains:
date_value ?
Used in:
row_tag

See the description of the attributes under the stringcell_tag description.

22
News Story Markup Language v3.1 30 August 2010
Engineering Specification

7.6 The <durationcell> tag

<durationcell>
Function:
Defines a presentation/appearance of a time duration field.
Attributes:
idref id of a tag in the <fields> section
length decimal number
style ”b” | “i” | “u” | “” | space separated list of those letters
align “left” | “right” | “center”
ro boolean_value
aready boolean_value
llength decimal number
lstyle ”b” | “i” | “u” | “” | space separated list of those letters
lalign “left” | “right” | “center”
lposition “left” | “right” | “top” | “bottom”
limit boolean_value
wg decimal number
mandatory boolean_value
Contains:
duration_value ?
Used in:
row_tag

See the description of the attributes under the stringcell_tag description.

8 Story Fields – the <fields> tag content

The <string> and </string> tags enclose plain_text which is uniquely associated with an identifier.

The id= attribute is required. It uniquely identifies the field in the story so that it may be referenced and
used. The id is referenced by the idref= attribute of a stringcell_tag or a comboboxcell_tag within the
<form> element of the NSML document. Each story will have only one field with a specific id. There are

23
News Story Markup Language v3.1 30 August 2010
Engineering Specification

some reserved ids that identify fields with specific meaning and in some cases contain system-supplied
content.

Reserved field identifiers

AIR-DATE decimal digits Seconds since Jan 1, 1970 00:00:00 GMT
AUDIO-TIME decimal digits Audio read time of story in seconds. Normally based on read-rate
and word-count but can be user entered.
BACK-TIME • Hard in-time of the story in seconds
special
CA-CAPTURED character string Connect session information – number of characters captured.
CA-DIRECTION character string Connect session information – direction of connection (in or out)
CA-ELAPSED character string Connect session information – duration as HH:MM:SS
CA-IDENT character string Connect session information – session identifier
CA-ORIGIN character string Connect session information – originating computer name
CA-RECEIVED character string Connect session information – number of characters received
CA-REMOTE character string Connect session information – remote computer name
CA-SENT character string Connect session information – number of characters sent
CG-ADDR character string MCS / BCS – CG device address
CG-TEMPLATE character string MCS / BCS – CG template address
CG-TEXT character string MCS / BCS – CG text
CHANNEL character string MCS / BCS – generic event channel
CREATE-BY character string User name of creator of first version of the story
CREATE-DATE decimal digits Seconds since Jan 1, 1970 00:00:00 GMT
CUME-TIME • Hard out-time of the story in seconds
special
DEVICE-MGR character string MCS / BCS – device manager name
DURATION character string MCS / BCS – generic event duration
EFFECT character string MCS / BCS – event effect
ENDORSE-BY character string Name of user who endorsed the story
EVENT-STATUS character string MCS / BCS – (video) event status
ITEM-CHANNEL character string MCS / BCS – playout channel for a primary event
MAIL-CC character string Mail information – cc addressee list
MAIL-TO character string Mail information – to addressee list
MODIFY-BY character string User name of the last modifier of the story
MODIFY-DATE decimal digits Seconds since Jan 1, 1970 00:00:00 GMT
MODIFY-DEV character string Device name on which story was last modified
MOS-ACTIVE character string MOS – event identifier
MOS-DURATION Decimal digits MOS – event duration
MOS-SUBEVENT character string MOS – event details
MOS-TITLE character string MOS -- event description
PAGE-NUMBER character string User entered story identifier
PRESENTER character string The name of the person who will read the story on-air
READY character string State of the story. Either READY or ?.
RESULT-INDEX character string Search result information – story indentifier
RESULT-LOC character string Search result information – story location (queue name)
RUNS-TIME decimal digits Sum of runs times specified in production cues.
SEARCH-ID character string Search result information – search request identifier
STATUS character string Status of some element of the story.
STILL-ID character string MCS / BCS – still store event identifier
STILL-PRESET character string MCS / BCS – still store event preset
STYLE character string MCS / BCS – event style
TAPE-TIME decimal digits The run time in seconds of a tape to be played with the story
TITLE character string User entered story title
TOTAL-TIME decimal digits Total story time in seconds, sum of audio-time and tape-time
VIDEO-ID character string MCS / BCS – video (tape / clip) identifier

24
News Story Markup Language v3.1 30 August 2010
Engineering Specification

WRITER character string User name of the writer taking credit for the story.

•
The back-time and cume-time field content has a special encoding. The hard in/out times are expressed in
seconds as either a relative time or an absolute time (a.k.a. time of day.) The time is assumed to be relative
unless the first character of the field is a @ character. For example a back-time content of 600 specifies a
hard in-time of 10 minutes relative to the start of the show. A back-time content of @600 specifies a hard
in-time of 12:10:00 am (10 minutes passed midnight.)

The uec= attribute is optional. Its value is either “true” / “1” or “false” / “0”. A true value indicates that a
user has entered content to override the system supplied content normally provided in the field. It is only
significant for fields that may contain system supplied content.

The urgency= attribute is optional. Its value may be a decimal number from the 1 through 9 (if not
specified “1” is assumed.) It is intended as a clue to the applications that the data in this field has some
exceptional meaning and may need to be brought to the users attention. The specific method for presenting
this information to the user is not defined by NSML. It could be ignored. The specific meaning of the
urgency is dependent on the specific id.

The aready= attribute is optional. Its value is either “true” / “1” or “false” / “0”. A true value indicates
that the content of the field affects the content of the READY field. Specifically, if any field with the
aready attribute has a ? (question mark) as the first character of its content or it has no content, the READY
field will have a ? as its content. If this attribute is not present, false is assumed.

The ro= attribute is optional. Its value is either “true” / “1” or “false” / “0”. A true value indicates that the
field is read-only. This attribute is used in conjuction with the same attribute in the <stringcell> tag that
references this <string>. Applications should only allow modifications to this <string> when the ro
attributes of the <stringcell> and the <string> cell are both “false”. If this attribute is not present, false is
assumed.

The bg= attribute is optional. It defines a background color that will be applied to the field. This attribute
is acquired when an entry is selected from a combobox list. It is a decimal number which identies a system
color. System colors are not defined in this specification. If not specified it defaults to zero and implies
that no background color will be applied to the field.

25
News Story Markup Language v3.1 30 August 2010
Engineering Specification

The id= attribute is required. It uniquely identifies the field in the story so that it may be referenced and
used. The id is referenced by the idref= attribute of a checkboxcell_tag within the <form> element of the
NSML document.

See the description of the attributes under the string_tag description.

The id= attribute is required. It uniquely identifies the field in the story so that it may be referenced and
used. The id is referenced by the idref= attribute of a datecell_tag within the <form> element of the
NSML document.

See the description of the attributes under the string_tag description.

The id= attribute is required. It uniquely identifies the field in the story so that it may be referenced and
used. The id is referenced by the idref= attribute of a durationcell_tag within the <form> element of the
NSML document.

See the description of the attributes under the string_tag description.

26
News Story Markup Language v3.1 30 August 2010
Engineering Specification

9 Story Body – the <body> tag content

The <p> and </p> tags enclose the text of a paragraph. All text is inside paragraphs. See the description
of the font=, family=, and pitch= attributes under the <body> tag description.

Content-based tags attach a specific meaning, context or usage to the enclosed text. Applications parsing
the NSML document can use these tags to do content based processing on the text.

Content-based tags may not be nested.

The <pi> and </pi> tags enclose text which are instructions to the presenter reading the story on-air.
This text is not included in the timing of the story. It is not intended for display on the closed caption
device and is intended for display on the prompter.

The <cc> and </cc> tags enclose text which is not read by the presenter on-air but is usually part of a
package voice-over which is to be closed captioned. This text is not included in the timing of the story. It is
not intended for display on the prompter.

The physical style tags may be nested in the content-based tags to create highlighting effects. Applications
are free to render nested styles in content-based text in any way that matches their capabilities. If an editing
application is limited in its ability to present the styles to the user in a meaningful way it is free to strip the
physical styles it cannot handle.

27
News Story Markup Language v3.1 30 August 2010
Engineering Specification

The physical style tags enclose text that is to be enhanced when presented to the user. Physical style tags
may be nested within other physical style tags to combine highlighting effects. Applications are free to
render styles in any way that matches their capabilities but the standard or preferred renderings are <b> to
bold, <i> to italic and <u> to underline. If an editing application is limited in its ability to present the styles
to the user in a meaningful way it is free to strip the combinations of styles it cannot handle.

These tags are unlike the content-based tags in that they do not identify the enclosed content, they are just
available to the user to highlight words to improve readability.

This tag is to assist in the handling of numbers for right to left environments. This is not needed for
characters that have right-to-left Unicode property. It is needed for characters that do not have that property
but should be handled similarly. This is the case with digit characters.

9.5 Background color Text Tag

<bg>
Function:
Specify a background color for the contained text.
Attributes:
rgb [REQUIRED] Six hexadecimal characters.
Contains:
text_content *
Used in:
text_content

The <bg> tag encloses text that is to be enhanced when presented to the user. This tag may be nested within
other physical style tags to combine highlighting effects. Applications are free to render them in any way
that matches their capabilities.

28
News Story Markup Language v3.1 30 August 2010
Engineering Specification

The rgb= attribute is optional. Its value is a string of exactly six hexadecimal characters Each pair of
hexadecimal characters represent the red, green, and blue components of the color in that order.

The <pb/> tag indicates that when printing a story a page break is to occur at that position in the text.

The <tab/> tag indicates that the next character is to start at the next tab stop position.

The <wp/> tags will appear at the positions in the text where the word wrapping was performed by the last
application to modify the text. These wrap points may be used by an application if it wishes to present the
text of the story with the same appearance as it last appeared.

The <sb/> tag can be used by applications as a text marker and has no other significance in NSML. It can
be used in conjunction with video/audio sequences to indicate transition points of the sequence relative to
the text.

29
News Story Markup Language v3.1 30 August 2010
Engineering Specification

The <a/> tag marks the spot within a paragraph of the document body at which an anchored element is
referenced. The order and position of these anchors are intended to determine the order and position of the
anchored elements when displayed by an application.

The idref= attribute is required. Its value is a decimal number that identifies a specific anchored element in
the <aeset> that is referenced by this element. The value of the number must be between 0 and 255
inclusive.

The content of the <show> tag, if present, can be displayed and highlighted to denote the link.

30
News Story Markup Language v3.1 30 August 2010
Engineering Specification

The content of the <url> tag is the actual link to be used to retrieve or navigate to the referenced object.

10 Story Anchored Element Set – the <aeset> tag content

The <ae> and </ae> tags enclose an anchored element. An anchored element is an object that is
anchored at a specific position in the body of the document. How these objects are displayed is dependent
on the object content and the application displaying the object. Anchored elements are referenced by
anchors (a_tags) within body paragraphs. The anchored elements are expected to be the same sequence as
their corresponding anchors within the story body.

The id= attribute is required. Its value is a decimal number that uniquely identifies the anchored element in
the story so that it may be referenced and used. The id is referenced by the idref= attribute of the a_tag
within the <body> element of the NSML document. Each id is unique within an anchored element set
(<aeset>). The value of the number must be between 0 and 255 inclusive.

The version= attribute is optional. Its value is plain_text. It is typically a News Server version number or
a News Client version number of the agent that created or modified the ancored element. The iNEWS
Server typically supplies version=“S3.0”. This can be used to account for changes between versions of the
server and the client.

31
News Story Markup Language v3.1 30 August 2010
Engineering Specification

The type= attribute is optional. Its value is plain_text. It is used to determine the type of information that
may be contained in the anchored element. Known types are “G” (General), “M” (MOS), “V” (Video),
“J” (Journalist Editor). If this attribute is not present “G” is assumed. Applications should allow for other
types. Applications should preserve anchored elements with a type that is not known to the application.

The runs= attribute is optional. Its value is a decimal number that represents the runs time of the anchored
element. If not set it is assumed to be zero. For “G” and “M” type elements this value is the sum of all of
the “RUNS=” values found in the content of the anchored element.

See the description of the font=, family=, and pitch= attributes under the <body> tag description.

10.1.1 The <hidden> tag

<hidden>
Function:
Contains information relavant to an anchored element that is not for display.
Attributes:
None
Contains:
plain_text ?
Used in:
ae_tag
The text content is not for display. It is really metadata that is associated with the anchored element.
Currently only Journalist Editor (type=”J”) anchored elements contain such data. In any case, all
applications must preserve this information when modifying a story.

10.1.2 Anchored element content – ae_content

ae_content
Function:
Defines the optional content elements in an ae_tag.
Start tag:
None
Attributes:
None
Contains:
( mc_tag | ap_tag ) *
Used in:
ae_tag

32
News Story Markup Language v3.1 30 August 2010
Engineering Specification

The <mc> and </mc> tags enclose machine control instructions which are understood by Machine Control
Subsystem of the News System.

The error= attribute is optional. Its value is either “true” / “1” or “false” / “0”. A true value indicates that
the News System’s Machine Control Subsystem was not able to understand or carry out the instructions
contained within the tag. If this attribute is not present, false is assumed.

The idref= attribute is optional. It identifies a specific attachment in the <aeset-atts> section which
“belongs” to this machine control element. It is the id value that is matched. If not specified there is no
attachment that “belongs” to this machine control element.

The flags= attribute is optional. Its value is a sequence of characters that can be used by applications that
manipulate the machine control information. Currently there can be as many as five characters. The values
and meaning are:

Position Possible Values Meaning

1 Y,N Yes/No Editor available via ActiveX
2 Y,N Yes/No Player available via ActiveX
3 Y,N Yes/No Explorer available via ActiveX
4 A thru Z Changes if attachment changes since last written to database.
Cycles through 26 letters of English alphabet
5 M, B M=MOS(plain vanilla)
B=CAP event (formerly BCS)
(More possible values are likely to be added)

The runs= attribute is optional. Its value is a decimal number that represents the runs time of the machine
control element. If not set it is assumed to be zero.

The status= attribute is optional. Its value is a decimal number in the range 0 to 255 that represents the
status as reported from the the News System’s Machine Control Subsystem. The meanings of the values are
not defined in NSML.

See the description of the font=, family=, and pitch= attributes under the <body> tag description.

33
News Story Markup Language v3.1 30 August 2010
Engineering Specification

The <ap> and </ap> tags enclose the text of a paragraph in anchored elements and machine control
elements. Ap_text is differentiated from text because ap_text cannot contain <pb/> or <a/> tags.

See the description of the font=, family=, and pitch= attributes under the <body> tag description.

11 Field-atts and AEset-atts Content Definition

The id= attribute is required. It uniquely identifies the attachment in the story so that it may be referenced
and used. It is beyond the scope of the NSML specification to define where references to the attachment
reside or how they are used.

12 Example
<?xml version="1.0"?>
<nsml xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://avid.com/nsml nsml.xsd"
xmlns=http://avid.com/nsml
version="3.1">
<head>
<meta words="56" rate="180"/>
<formname>RUNDOWN-AIRDATE</formname>

34
News Story Markup Language v3.1 30 August 2010
Engineering Specification

<storyid>0d7bd190:00f0a7ee:43949af4</storyid>
</head>
<projects>
<project>fa8e61212f064ee0ae477c6225a54282</project>
<facet>fa8e61212f064ee0ae477c6225a54282f4ba2a87bed44344a04d35a5580baa9b</facet>
</projects>
<fields>
<string id="page-number">B01</string>
<string id="presenter">EC</string>
<string id="title">N:UNABOMBER HOUSE</string>
<string id="var-3">VO/W</string>
<string id="video-id">txfer310</string>
<string id="event-status"/>
<string id="status">OK</string>
<string id="item-channel"></string>
<duration id="audio-time">18</duration>
<duration id="runs-time">22</duration>
<duration id="total-time">40</duration>
<date id="modify-date">1133812468</date>
<string id="modify-by">csquire</string>
<string id="endorse-by"/>
<string id="cume-time"/>
<duration id="tape-time" />
<string id="back-time"/>
<date id="air-date">1121180576</date>
</fields>
<body>
<p>
<a idref="0"/>
<pi>((EILEEN ANIM. BOX))</pi>
</p>
<p>
<tab/>IN OTHER NATIONAL NEWS... THE COUNTRY'S MOST FAMOUS
SHACK IS ON THE MOVE TONIGHT.</p>
<p>
<a idref="1"/>
<pi>((TAKE vo))</pi>
</p>
<p>
<pi><b>bold<i>italic<a idref="5"/></i></b></pi>
<a idref="2"/>
<cc>xxx</cc>
<a idref="3"/> THE MONTANA HOME OF UNABOMBER SUSPECT TED
KACZYNSKI IS UNDER A TARP, ON THIS TRUCK, HEADING TO
SACRAMENTO.

35
News Story Markup Language v3.1 30 August 2010
Engineering Specification

</p>
<p>
<tab/> JURORS WILL BE GETTING A TOUR OF THE CABIN.</p>
<p>
<tab/>BY SHOWING HOW HE LIVED, DEFENSE ATTORNEYS ARE HOPING
TO PROVE KACZYNSKI IS MENTALLY ILL.</p>
<p>
<a idref="4"/>
<pi>((wipe vo))</pi>
</p>
<p> </p>
</body>
<aeset>
<ae id="0" version="S3.0">
<ap>EILEEN ANIM. BOX</ap>
</ae>
<ae id="1" version="S3.0" type="G" runs="0">
<ap>TAKE v/o</ap>
</ae>
<ae id="5" version="S3.0" type="M" runs="22">
<mc idref="1" flags="NNYAM" runs="22">
<ap>video Unabomber (VO)</ap>
</mc>
<ap>runs 0:22</ap>
</ae>
<ae id="2" version="S3.0" type="G" runs="0">
<mc>
<ap>CG NAT1</ap>
<ap>NEAR GREAT FALLS, MT</ap>
</mc>
</ae>
<ae id="3" version="S3.0" type="G" runs="0">
<mc>
<ap>CG NAT</ap>
</mc>
</ae>
<ae id="4" version="S3.0" type="G" runs="0">
<ap>wipe v/o----------------</ap>
</ae>
</aeset>
<aeset-atts>
<attachment
id="1"><![CDATA[<AttachmentContent><mos><mosID>mosid.inews</mosID>
<mosItemBrowserProgID> </mosItemBrowserProgID><mosAbstract>Unabomber
(VO)</mosAbstract>

36
News Story Markup Language v3.1 30 August 2010
Engineering Specification

<objID>60A10000</objID><objSlug>Unabomber</objSlug><objTB>60</objTB>
<objDur>1323</objDur><itemEdDur>1</itemEdDur>
<itemID>1</itemID></mos></AttachmentContent>
]]></attachment>
</aeset-atts>
</nsml>

300+ Top Web Technology Lab Viva Questions and Answers PDF
No ratings yet
300+ Top Web Technology Lab Viva Questions and Answers PDF
47 pages
HTML Tag
100% (1)
HTML Tag
6 pages
STD 10 Computer Chapter 1 Introduction To HTML
No ratings yet
STD 10 Computer Chapter 1 Introduction To HTML
6 pages
Unit II WT Notes
No ratings yet
Unit II WT Notes
32 pages
XML Introduction
No ratings yet
XML Introduction
42 pages
This Element Is What The Hyperlinked Structure of The
No ratings yet
This Element Is What The Hyperlinked Structure of The
5 pages
See Working Example. Anchor Tutorial
No ratings yet
See Working Example. Anchor Tutorial
7 pages
8.8 - XML API Developer Guide
No ratings yet
8.8 - XML API Developer Guide
220 pages
Document 1
No ratings yet
Document 1
6 pages
HTML Tags for Beginners
No ratings yet
HTML Tags for Beginners
5 pages
Xmlbasics
100% (1)
Xmlbasics
669 pages
UNIT-II Introduction - HTML
100% (1)
UNIT-II Introduction - HTML
53 pages
HTML Notes11
No ratings yet
HTML Notes11
14 pages
XML For Dummies
No ratings yet
XML For Dummies
34 pages
HTML Unit 1
No ratings yet
HTML Unit 1
33 pages
Webtechnologyies Final
No ratings yet
Webtechnologyies Final
74 pages
NextGen Connect Programming Reference
100% (2)
NextGen Connect Programming Reference
35 pages
Applications of XML
No ratings yet
Applications of XML
19 pages
XML Basics for Tech Learners
No ratings yet
XML Basics for Tech Learners
41 pages
Website Design For A Purpose Ict Exam
No ratings yet
Website Design For A Purpose Ict Exam
52 pages
Unit Three HTML & XML
No ratings yet
Unit Three HTML & XML
25 pages
Web Technology Notes Part 2
No ratings yet
Web Technology Notes Part 2
10 pages
HTML Syntax: Tag Description
No ratings yet
HTML Syntax: Tag Description
8 pages
Don't Unpack Kernel Archives Using Software Prov. Man. 1.0
No ratings yet
Don't Unpack Kernel Archives Using Software Prov. Man. 1.0
2 pages
Semantic HTML Cheat Sheet
No ratings yet
Semantic HTML Cheat Sheet
3 pages
Comprehensive HTML Guide
No ratings yet
Comprehensive HTML Guide
1 page
HTML
No ratings yet
HTML
6 pages
HTML Reviewer
No ratings yet
HTML Reviewer
3 pages
Website Design For A Purpose
No ratings yet
Website Design For A Purpose
52 pages
HTML Element Reference
No ratings yet
HTML Element Reference
13 pages
HTML Basics and Website Survey
No ratings yet
HTML Basics and Website Survey
47 pages
Web Application Development - Lecture 6
No ratings yet
Web Application Development - Lecture 6
73 pages
HTML Tags List
No ratings yet
HTML Tags List
11 pages
L02 HTML
No ratings yet
L02 HTML
32 pages
Semantic HTML Tags Cheat Sheet
No ratings yet
Semantic HTML Tags Cheat Sheet
8 pages
HTMLComplete Notes
No ratings yet
HTMLComplete Notes
18 pages
Open Book Chapter 1 - 6
No ratings yet
Open Book Chapter 1 - 6
35 pages
HTML5 Tags
No ratings yet
HTML5 Tags
3 pages
Untitled Document
No ratings yet
Untitled Document
14 pages
UNIT 1-Ost
No ratings yet
UNIT 1-Ost
25 pages
XML ImportExport Interface UniFLOWHelix - V1.4
No ratings yet
XML ImportExport Interface UniFLOWHelix - V1.4
25 pages
HTML 5
No ratings yet
HTML 5
6 pages
HTML Tags
No ratings yet
HTML Tags
4 pages
XML for z/OS COBOL Developers
No ratings yet
XML for z/OS COBOL Developers
50 pages
HTML Tag Reference Guide
No ratings yet
HTML Tag Reference Guide
4 pages
CACS 205: Web Technology XML: Prepared by Krishna Pd. Acharya (Mechi Multiple Campus)
No ratings yet
CACS 205: Web Technology XML: Prepared by Krishna Pd. Acharya (Mechi Multiple Campus)
67 pages
Record IT8211
No ratings yet
Record IT8211
43 pages
Chapter 1
No ratings yet
Chapter 1
16 pages
HTML Tagovi
No ratings yet
HTML Tagovi
5 pages
Wit Unit Iv Pmfa
No ratings yet
Wit Unit Iv Pmfa
39 pages
Complete HTML Tags List With Examples Free Pdf1
100% (3)
Complete HTML Tags List With Examples Free Pdf1
7 pages
XML, COBOL and Application
No ratings yet
XML, COBOL and Application
51 pages
Beautiful Soup 4 Documentation Guide
No ratings yet
Beautiful Soup 4 Documentation Guide
61 pages
HTML Tag List
No ratings yet
HTML Tag List
8 pages
Tag Description
No ratings yet
Tag Description
5 pages
Voice Tape
No ratings yet
Voice Tape
3 pages
HTML Komande
No ratings yet
HTML Komande
25 pages
Trulia Dev Guide
No ratings yet
Trulia Dev Guide
27 pages
Markup Languages Overview
No ratings yet
Markup Languages Overview
63 pages
Document Overview: ...
No ratings yet
Document Overview: ...
24 pages
Programming XML
No ratings yet
Programming XML
65 pages
Basic HTML: Tag Description
No ratings yet
Basic HTML: Tag Description
12 pages
Html5 - Tags Reference
No ratings yet
Html5 - Tags Reference
5 pages
Chapter 1 Lesson 3 PDF
No ratings yet
Chapter 1 Lesson 3 PDF
16 pages
XML
No ratings yet
XML
33 pages
List of Experiments
No ratings yet
List of Experiments
30 pages
HTML Basics for CS Students
No ratings yet
HTML Basics for CS Students
55 pages
Differences Between HTML and XHTML
No ratings yet
Differences Between HTML and XHTML
18 pages
XML For Dummies
No ratings yet
XML For Dummies
34 pages
Ordered by Function: Tag Description Basic
No ratings yet
Ordered by Function: Tag Description Basic
4 pages
NSML 3.1 Specification
No ratings yet
NSML 3.1 Specification
37 pages
HTML
No ratings yet
HTML
5 pages
KML Basics for Beginners
No ratings yet
KML Basics for Beginners
13 pages
Ag Description
No ratings yet
Ag Description
5 pages
Web Development Unit - 4
No ratings yet
Web Development Unit - 4
7 pages
Htmlpurifier Org Live Smoketests Xssattacks PHP
No ratings yet
Htmlpurifier Org Live Smoketests Xssattacks PHP
12 pages
Top 40+ Web Developer Interview Questions and Answers For 2024
No ratings yet
Top 40+ Web Developer Interview Questions and Answers For 2024
19 pages
Tag Description
No ratings yet
Tag Description
5 pages
HTML Tags Overview
No ratings yet
HTML Tags Overview
8 pages
Web Technology Unit 3
No ratings yet
Web Technology Unit 3
30 pages
HTML What Is HTML?
No ratings yet
HTML What Is HTML?
8 pages
TCP3151 Integrative Programming and Technologies Assignment
No ratings yet
TCP3151 Integrative Programming and Technologies Assignment
3 pages
XML Quick Guide
No ratings yet
XML Quick Guide
32 pages
Unit-3 XML
No ratings yet
Unit-3 XML
22 pages
XML Feed Documentation: ZR Feeds Team
No ratings yet
XML Feed Documentation: ZR Feeds Team
15 pages
HTML Element Reference: Tag Description
No ratings yet
HTML Element Reference: Tag Description
12 pages
Extensible Markup Language
No ratings yet
Extensible Markup Language
29 pages

NSML 3.1 Specification

Uploaded by

NSML 3.1 Specification

Uploaded by

Avid Technology, Inc.

News Story Markup Language

NSML – A Markup Language for News Stories

1.1 Changes from 2.7 to 2.8

1.2 Changes from 2.8 to 3.0

1.3 Changes from 3.0 to 3.1

Elements followed by a ‘*’ are repeatable zero or more times.

nsml_tag ::= <nsml>

head_tag ::= <head>

projects_tag ::= <projects> (project_tag | facet_tag) * </projects>

form_tag ::= <form> row_tag * </form>

field_atts_tag ::= <field-atts> attachment_tag * </field-atts>

aeset_atts_tag ::= <aeset-atts> attachment_tag * </aeset-atts>

project_tag ::= <project > single_uuid </project >

facet_tag ::= <facet > double_uuid </facet >

single_uuid ::= hexBinary *16

double_uuid ::= hexBinary *32

hexBinary ::= hexDigit hexDigit

row_tag ::= <row> row_content * </row>

row_content ::= <stringcell> plain_text ? </stringcell>

label_tag ::= <label> plain_text ? </label>

comboboxcell_content ::= entry_tag

entry_tag ::= <entry> plain_text ? </entry>

fields_tag ::= <fields> fields_content * </fields>

fields_content ::= <string> plain_text ? </string>

boolean_value ::= “true” | “1” | “false” | “0”

duration_value ::= a decimal number representing seconds

body_tag ::= <body> p_tag * </body>

p_tag ::= <p> p_content * </p>

p_content ::= content_tag

content_tag ::= <pi> text_content * </pi>

text_content ::= style_tag

text_and_links ::= <link> show_tag ? url_tag </link>

show_tag ::= <show> plain_text ? </show>

url_tag ::= <url> plain_text ? </url>

style_tag ::= <b> text_content * </b>

aeset_tag ::= <aeset> ae_tag * </aeset>

ae_tag ::= <ae> hidden_tag ? ae_content * </ae>

hidden_tag ::= <hidden> plain_text ? </hidden>

ae_content ::= mc_tag

mc_tag ::= <mc> ap_tag * </mc>

ap_tag ::= <ap> ap_content * </ap>

ap_content ::= astyle_tag

astyle_tag ::= <b> ap_content * </b>

space ::= a single space character (hex20)

attachment_tag ::= <attachment>

3.1 Start and End tags

3.2 Empty tags

3.3 Character set

3.4 Character Entities

Table 2.1 – Character Entities

3.6 Base Units

4 NSML top level elements

4.1 The <nsml> tag

4.2 The <head> tag – define information about the story

4.3 The <projects> tag

4.5 The <fields> tag

4.6 The <body> tag

4.7 The <aeset> tag

4.8 The <field-atts> tag – Defining field attachments

4.9 The <aeset-atts> tag – Defining anchored element set attachments

5 Story Header - the <head> tag content

5.1 The <meta/> tag – Define story meta information

5.2 The <rgroup> tag

5.3 The <wgroup> tag

5.4 The <egroup> tag

5.5 The <wcode> tag

5.6 The <dist> tag

5.7 The <source> tag

5.8 The <formname> tag

5.9 The <storyid> tag

5.10 The <storygroupid> tag

5.11 The <password> tag

6 Story Associations – the <projects> tag content

6.1 The <project> tag

6.2 The <facet> tag