This document is under discussion by members of the next generation PICS labels working group, and will probably be heavily revised over the next few weeks. Comments should be posted to w3c-labels-NG@w3.org.
Note that the working group will be reconstituted as part of the re-organization of metadata standardization within the W3C during the month of July.
A list of current W3C Recommendations and other technical documents can be found at http://www.w3.org/pub/WWW/TR/.
Not yet included or resolved:
This document, which has been prepared for the technical subcommittee of PICS (Platform for Internet Content Selection), defines a language for describing labeling services. Software programs will read service descriptions written in this language, in order to interpret content labels and assist end-users in configuring selection software.
Previous versions of this document had the title "Rating Services and Rating Systems".
Table of Contents
The application/pics-service document type
Explanation of Sample Labeling Service
Detailed syntax of application/pics-service
Inheriting from one application/pics-service Description to another
Transmiting more than one application/pics-service Description together
Appendix A: The Ages Labeling Service
Appendix B: RSAC Labeling Service
Appendix C: The SafeSurf~~ Labeling Service
Appendix D: Changes from PICS-1.1
This document, which has been prepared for the technical subcommittee of PICS (Platform for Internet Content Selection), defines a language for describing labeling services. Software programs will read service descriptions written in this language, in order to interpret content labels and assist end-users in configuring selection software.
A related document (PICS Label Distribution -- to be made available in late June) specifies the syntax and semantics of content labels and protocol(s) for distributing labels. (These labels are compatible with PICS-NG Metadata Model and Syntax).
The goal of the PICS effort is to enable a marketplace in which many different products and services will be developed, tested, and compared. Hence, the following considerations have had significant impact on this document:
A labeling service is an individual, group, organization, or company that provides content labels for information on the Internet. The labels it provides are based on a labeling system (see below). Each labeling service must describe itself using a newly created MIME type, application/pics-service. Selection software that relies on labels from a PICS labeling service can first load the application/pics-service description. This description allows the software to tailor its user interface to reflect the details of a particular labeling service, rather than providing a "one design fits all labeling services" interface.
This specification does not state how the application/pics-service description of a labeling service is initially located. For users of the World Wide Web, we expect that well-known sites will provide lists of labeling services along with their application/pics-service descriptions. It is expected that client programs will cache copies of application/pics-service descriptions, so any incompatible change in a service description should be accomplished by creating an entirely new service URL. Some software will pre-install one or more application/pics-services as individual files with filename ending in .RAT or .rat.
Each labeling service picks a URL as its unique identifier. It is included in all content labels the service produces, to identify their source. We recommend, but do not require, that this identifier include a version number, as shown in all of the examples in this specification, to simplify transitions due to incompatible changes over time. For example, our sample service "http://www.gcf.org/v2.0/" includes "v2.0" as its own version number. To ensure that no other service uses the same identifier, it must be a valid URL. In addition, the URL (when used within a query) serves as a default location for a label bureau that dispenses this service's labels (see PICS Label Distribution).
Since the service identifier is a URL, it can be used to retrieve a document. That document may be in any format, but we recommend that it:
We also recommend that the URL be of scheme "http:", and that if it is, requesting it using "Accept: application/pics-service" returns the application/pics-service described in this document.
A labeling system specifies the dimensions used for labeling, the scale of allowable values on each dimension, and a description of the criteria used in assigning values. For example, the MPAA rates movies in the USA based on a single dimension with allowable values G, PG, PG-13, R, and NC-17.
Each labeling system ("schema") is identified by a valid URL. This enables several services to use the same labeling system and refer to it by its identifier. The URL naming a labeling system can be accessed to obtain a human-readable description of the labeling system. The format of that description is not specified.
A content label contains information about a document. As described in PICS Label Distribution, a content label has three parts:
A labeling service is defined by a document of type application/pics-service. The detailed syntax and semantics are presented in the next two sections. Here is an example of such a document, intended only to illustrate the full set of features of a machine description:
((PICS-version 2.0)
|
The working group needs to decide if an XML dialect to describe the RAT file would be preferable. Only one RAT file format will be supported (either something like the example above, or something compatible with XML).
Here is the example document using XML:
<XML-PICS>
|
Here is the example document using XML more concisely:
<XML-PICS>
|
Notes:
application/pics-service :: labeling-service-description+
labeling-service-description ::
'(' version service-section labeling-system
schema-option* category-list+ ')'
version :: '(' 'PICS-version' '2.0' ')'
labeling-system :: '(' 'schema' quoted-URL
superSchema-Quoted-URL ')'
superSchema-Quoted-URL :: "http://w3.org/PICS/PICS-Schema" |
quoted-URL | ''
Note: quoted-URL names a schema, which must itself
specify
"http://w3.org/PICS/PICS-Schema"
as its superSchema, at least transitively. Omitting
quoted-URL
is only permitted for a schema which will always be used as an
imbedded label.
service-section :: '(' 'service-section' labeling-service
service-option* ')' |
''
Note: A schema which will always be used as an imbedded label
omits the service-section.
Note: Any particular service-option, with the exception of
extention, may appear at most once.
labeling-service :: '(' 'labeling-service' quoted-URL ')'
service-option :: description | extension
icondef | label-bureau-url | name |
sample-url
schema-option :: default | extension
category-list ::
'(' 'category'
'(' 'transmit-as' transmit-name ')'
(category-option | scale-option)*
category-list*
')'
defaultable-option :: boolean-option | extension
| integer | increment | isodate-option
| labeled
| max | min | multi | number |
unordered
| url-option
category-option :: abstract | category-default-value
description | icondef |
name | imbeddedlabel-option |
string-option
scale-option :: defaultable-option | enum-list
enum-list :: enum+
enum ::
'(' 'label' name [description]
'(' 'value' number ')'
[icondef]
')'
default :: '(' 'default' defaultable-option+ ')'
abstract :: '(' 'abstract' [boolean] ')'
boolean-option :: '(' 'boolean' [boolean] ')'
category-default-value :: '(' 'category-default-value' value ')'
value :: boolean |
number | quoted-ISO-date |
quoted-string |
quoted-URL
description :: '(' 'description' quoted-string ')'
extension :: '(' 'extension'
'(' mand/opt quoted-URL data* ')' ')'
icondef :: '(' 'icon' quoted-URL ')'
increment :: '(' 'increment' quoted-ISO-date ')' |
'(' 'increment' unsignedint ')' }
integer :: '(' 'integer' [boolean] ')'
isodate-option :: '(' 'isodate' [boolean] ')'
labeled :: '(' 'label-only' [boolean ] ')'
max :: '(' 'max' maxnum ')'
min :: '(' 'min' minnum ')'
multi :: '(' 'multivalue' [boolean] ')'
name :: '(' 'name' quoted-string ')'
number :: '(' 'number' [boolean] ')'
string-option :: '(' 'string' [boolean ')'
unordered :: '(' 'unordered' [boolean] ')'
url-option :: '(' 'url' [boolean} ')'
boolean :: 't' | 'f' | 'true' | 'false'
mand/opt :: 'optional' | 'mandatory'
transmit-name :: '"' transmit-name-char+ '"'
Note: Do not use the following as transmit-names:
"on" "until" "by" "at" "generic" "comment" "full" "extension"
"true" "false"
minnum :: number | '-INF'
maxnum :: number | '+INF'
number :: [sign]unsignedint['.' [unsignedint]]
sign :: '+' | '-'
unsignedint :: [0-9]+
data :: quoted-string | '(' data* ')'
Note: In many cases it is useful to be able to use a
URL as data. This syntax requires that, in such a case,
the URL must be UTF-7 encoded. This will rarely require
any additional work, but designers and implementers of
extensions should take care.
quoted-ISO-date :: '"'YYYY'-'MM'-'DD'T'hh':'mmStz'"'
based on the ISO 8601:1988 date and time standard, restricted
to the specific form described here:
YYYY :: four-digit year
MM :: two-digit month (01=January, etc.)
DD :: two-digit day of month (01 through 31)
hh :: two digits of hour (00 through 23) (am/pm NOT allowed)
mm :: two digits of minute (00 through 59)
s :: sign of time zone offset from UTC ('+' or '-')
tz :: four digit amount of offset from UTC
(e.g., 1512 means 15 hours and 12 minutes)
For example, "1994-11-05T08:15-0500" is a valid quoted-ISO-date
denoting November 5, 1994, 8:15 am, US Eastern Standard Time
Note: The ISO standard allows considerably greater
flexibility than that described here. PICS requires precisely
the syntax described here -- neither the time nor the time zone may
be omitted, none of the alternated formats are permitted, and
the punctuation must be as specified here.
quoted-string :: '"' UTF-7 '"'
UTF-7 :: Characters encoded using UTF-7, with direct
coding of US-ASCII set O except for the double-quote
(decimal 34) which must be encoded to allow for its use
as the string delimiter character. See note above.
quoted-URL :: '"' URL '"'
URL is as defined in RFC-1738 for URLs.
transmit-name-char :: alphanumpm | '.' | '$' | ',' | ';' |
':'
| '&' | '=' | '?' | '!' | '*' | '~' | '@'
| '#' | '_' | '%' hex hex
Note: Use the "%" escape technique (% followed by the two
hex digits that represent the character in the ASCII character
set) to insert single or double quotation marks or parentheses.
alphanumpm :: 'A' | ... | 'Z' | 'a' | ... | 'z' | '0' | ... | '9' |
sign
sign :: '+' | '-'
imbeddedlabel-option :: '(' 'imbedded-label' 'true' ')' |
'(' 'imbedded-label' quoted-URL+ ')'
label-bureau-url :: '(' 'label-bureau' quoted-URL ')'
sample-url :: '( 'sample' quoted-URL ')'
For reference, the following attributes are currently defined by the above BNF:
Recall that the MIME type application/pics-service is intended to describe a particular rating service in sufficient detail to automatically generate a user interface for configuring content selection software that relies on the rating service.
The quoted-URL in the labeling-service identifies the service. This identifier is included in all the labels provided by the labeling service. Dereferencing the URL yields a human-readable description of the service. If the optional URL for an icon for the labeling service is supplied, it is dereferenced relative to the rating service URL. The name of the labeling service is intended to be short and human-readable, with the description being a longer description (suitable, perhaps, for a pop-up box). A complete human-readable description is available from the rating service's URL.
The quoted-URL in the schema identifies the labeling system used by this service. Dereferencing the URL yields a human-readable description of the schema. All remaining relative URLs in the application/pics-service description are dereferenced relative to the schema URL, since they describe features of the schema. The first exception is the labeling service's icon, as described above, which is dereferenced relative to the labeling-service URL, so that the service can maintain its own (possibly copyrighted) identity even if it chooses to share a schema with other services. The second exception are the URLs in imbeded-label, which are dereferenced relative to the labeling-service URL. The third exception is the URL in label-bureau, which is dereferenced relative to the labeling-service URL.
The machine-readable description also describes the categories used in the schema. There may be one or more categories for a given schema. A single document may have a value on any or all of these categories. Categories can be nested within one another.
A category has a "transmission name" which is used in the actual label for a document. Transmission names should be as short as reasonable, but they may be complete URLs if desired. They must be unique within a given labeling system (i.e. two categories in the same rating system must not have the same transmission name; but see below for creating transmissions names from nested categories.) Unlike the name and description strings, transmission names are language-independent. That is, if a labeling system is offered in several languages, the transmission names must be the same in all of them. Transmission names are case sensitive (to allow URLs to be used as transmission names). In addition to the transmission name, which is required, a category may optionally have an icon and a human-readable description. The transmit name must not be true or false.
Categories may be nested within one another (as in the case of color in the example labeling system). In this case, the transmission name is created in the usual way by starting with the outermost category's transmit-as string, adding a "/" and proceeding inward in the nesting. Thus, the example labeling system has three categories, and their transmission names are color, color/hue, and color/intensity. In order to simplify the user interface of configuration software, it is wise to have few categories at any level of nesting; we recommend 10 or fewer. It is recommended that using an imbedded label as the value of an attribute is used instead of nesting categories. (We should explain why).
Icons, if provided, may be of any size. We recommend, however, that icons be as small as possible, since selection software is likely to embed them in displays that include other text and images as well. We also recommend that a labeling service's category icons all be the same size.
Values in PICS labels may be integers or fractions with no greater range or precision than that provided by IEEE single-precision floating point numbers. Values in PICS labels may also be strings or booleans. Values may be given names by using the label attribute. When a value is given a name, it may optionally have attached an icon and a human-readable description.
A value given in category-default-value must match the category attribute such as boolean true, number true, integer true, string true, isodate true, url true, min, max. If a category is imbedded-label true then category-default-value must not be specified. Software which has processed the application/pics-service and receives a label in which this category has been omitted will assume it is equivalent to a label in which the category had the value given in category-default-value. (Question from Bob: for dsig, does the label normalization pretend the category name and value were there or not?)
The description for each category can specify restrictions on the range of permissible values for certain named attributes. Values may be restricted in a variety of ways:
Here is an example:
(category (transmit-as "date") (name "document date")
(isodate true) (min "1900-01-01T00:00-0000") (increment
"0001-00-00T00:00-0000")
(max "2040-12-31T23:59-0000"))
which means that labels with this attribute will have a value between
January 1, 1900 00:00 and December 31, 2040 23:59, and that tools which
display a range (where the user can specify: "I only want documents
after
July of 1979" or "I only want documents before 1990")
should have a granularity of one year.
For schemas that contain large numbers of categories or deeply nested categories, it is convenient to allow for inheritance of some attribute values. In particular, the defaultable-options of a category ( boolean, extension, increment, integer, isodate, label-only, max, min, multivalue, unordered) and url are inherited by each category from its enclosing (parent) category. These attributes can be given default values for the entire labeling service by using the default attributes. This corresponds to value inheritance in object-oriented systems or lexical scoping in programming languages. (Notice that not all attributes can be inherited. Rationale: the set was chosen to include only those attributes that can be overridden. Thus, the enum-list is not inheritable because there is no way to say "don't give this value a name," which would be required to override an inherited name.)
Note: While it would be nice to restrict the numeric values of attributes to integers, the following examples motivate our decision to permit fractional values.
(Introductory text gets added here; I hope to get this from Renato, Ora, Eric ...)
Consider:
((PICS-Version 2.0)
(service-section
(labeling-service "http://www.xyz.org/labels"))
(schema "http://www.xyz.org/toplevel" "http://w3.org/PICS/PICS-Schema")
(category
(transmit-as "a")
(icon "a.gif")
(max 100)
)
(category
(transmit-as "b")
(icon "b.gif")
(description "this came from toplevel schema") )
)
((PICS-Version 2.0)
(service-section
(labeling-service "http://www.xyz.org/detailed-labels"))
(schema "http://www.xyz.org/midlevel" "http://www.xyz.org/toplevel")
(category
(transmit-as "a")
(icon "aicon.gif")
(integer true)
(min 0)
)
(category
(transmit-as "c")
(icon "cicon.gif")
(integer true)
)
)
This is exactly equivalent to:
((PICS-Version 2.0)
(service-section
(labeling-service "http://www.xyz.org/labels"))
(schema "http://www.xyz.org/toplevel" "http://w3.org/PICS/PICS-Schema")
(category
(transmit-as "a")
(icon "a.gif")
(max 100)
)
(category
(transmit-as "b")
(icon "b.gif")
(description "this came from toplevel schema") )
)
((PICS-Version 2.0)
(service-section
(labeling-service "http://www.xyz.org/detailed-labels"))
(schema "http://www.xyz.org/midlevel" "http://w3.org/PICS/PICS-Schema")
(category
(transmit-as "b")
(icon "http://www.xyz.org/toplevel/b.gif")
(description "this came from toplevel schema"))
(category
(transmit-as "a")
(icon "aicon.gif")
(integer true)
(min 0)
)
(category (transmit-as "c") (icon "cicon.gif") (integer true))
and in particular, the max value of the category
with transmit-as of "a" (in "http://www.xyz.org/detailed-labels")
is +INF, because when a subschema
declares a category with the same transmit-as string as a superschema, it
is as if
the superschema had omitted its category with the same transmit-as string.
The URLs appearing in imbedded-label may refer to a labeling-service-description which is transmitted with the labeling-service-description that contained the imbedded-label.
((PICS-Version 2.0)
(service-section
(labeling-service "http:/www.xyz.org/labels"))
(schema "http://www.xyz.org/toplevel" "http://w3.org/PICS/PICS-Schema")
(category
(transmit-as "a")
(max 100)
)
(category (transmit-as "b") (imbeded-label "http:#b-label-declaration")
)
)
((PICS-Version 2.0)
(service-section
(labeling-service "http://www.xyz.org/labels#b-level-declaration))
(schema "http://www.xyz.org/toplevel#b-level-schema-declaration")
(category
(transmit-as "a")
(integer true)
(min 0)
)
(category
(transmit-as "c")
(integer true)
)
)
More detail about how these categories are used will be found in PICS Label Distribution.
((PICS-Version 2.0)
(schema "http://w3.org/PICS/PICS-Schema")
(category
(transmit-as "at")
(isodate true)
(description "The last modification date of the item to which this
label
applies, at the time the label was assigned")
)
(category
(transmit-as "by")
(string true)
(description "An identifier for the person or entity within the
labeling service
who was responsible for creating this particular label")
)
(category
(transmit-as "generic")
(boolean true)
(category-default-value false)
(description "If this category is set to true, the label can be
applied to any URL
starting with the prefix given in the *for option. This
is used to
label entire sites or any subparts of sites.")
)
(category
(transmit-as "on")
(isodate true)
(description "The date on which this label was issued.")
)
(category
(transmit-as "until")
(isodate true)
(description "The date on which this label expires.")
)
(category
(transmit-as "comment")
(string true)
(description "A comment in the label.")
)
(category
(transmit-as "full")
(url true)
(description "In a label supplied by a label bureau, requesting
the label for the URL specified here will get
a label which includes every known field of the
w3.org/PICS/PICS-Schema.")
)
(category
(transmit-as "extension")
(description "The value must have a left parenthesis, the word
mandatory or the word optional, a space, a quoted-URL, a space,
and then zero or more values and end with a right parenthesis.
More than one extension may occur within the same label if
the quoted-URLs they contain are distinct.")
)
(category
(transmit-as "error")
Question from Bob: is this the way errors
returned from label bureaus should be handled,
by thinking of "error" as a category name?
)
)
Note: Fetching the sample-URL with no arguments, with the same transmit name appearing as the argument of vary and also as the name of another parameter, with less than all non-vary label-only true categories provided, or with invalid values, are all undefined cases. Some services may respond with a Java applet or Frameset which permits examination of samples, others will respond with an error HTTP response code.
The argument vary specifies a category transmit name.
The sample URLs that may be fetched are:
In each case, what is returned is a document containing 5 samples, one which gets the value 0 for the "vary" category, one which gets the value 1 for the "vary" category ... and one which gets the value 4 for the "vary" category (RSAC labels do not permit omitting a category). Each of these 5 samples has been rated on the other categories in accordance with the values that were specified in the 3 arguments transmit-name=transmit-value.
Given:
((PICS-version 2.0)
(service-section
(sample-url "http://www.labels.com/samp")
...
)
...
(category
(transmit-as "q")
(name "quality")
(label-only true)
(boolean true)
(label (name "good") (value true))
(label (name "bad") (value false))
(category
(transmit-as "t")
(name "type")
(imbedded-label "http://www.schemas.org/type01"))
)
and
((PICS-version 2.0)
...
(schema "http://www.schemas.org/type01")
(category
(transmit-as "g")
(name "gender")
(boolean true)
(label-only true)
(label (name "male") (value false))
(label (name "female") (value true) )
)
then the following sample URLs may be fetched:
Comments and suggestions from the following people are gratefully acknowledged:
Ora Lassila, Nokia Eric Miller, OCLC Jim Miller, W3C Paul Resnick, AT&T Bob Schloss, IBM Ralph Swick, W3C Misha Wolf, Reuters
Comments and suggestions, on previous versions of this specification, from the following people are gratefully acknowledged:
Brenda Baker, Lucent Scott Berkun, Microsoft Tim Berners-Lee, W3C Roxana Bradescu, AT&T Daniel W. Connolly, W3C Roy Fielding, W3C Jay Friedland, SurfWatch Henrik Frystyk Nielsen, W3C Wayne Gramlich, Sun Woodson Hobbs, NewView Rohit Khare, W3C Charlie Kim, Apple John C. Klensin, MCI Tim Krauskopf, Spyglass Breen Liblong, IFSI Ann McCurdy, Microsoft Rich Petke, CompuServe Eric Prud'hommeaux, W3C Dave Raggett, W3C Bob Schloss, IBM Ray Soular, SafeSurf Jason Thomas, MIT G. Winfield Treese, OpenMarket Richard Wolpert, Providence Systems
One of the simplest possible rating systems uses a single category, "Minimum recommended age." We present the machine description for a fictional service that uses this labeling system.
((PICS-version 2.0) (service-section (labeling-service "http://www.ages.org/our-service/v2.0/") (name "The Ages Rating Service") (description "We estimate the maturity required to view materials on the Internet.")) (schema "http://www.ages.org/our-system/" "http://w3.org/PICS/PICS-Schema") (category (transmit-as "age") (name "Minimum Recommended Age") (integer true)))
As a specific example of a deployed rating service encoded using the PICS machine-readable description format, we present the service supplied by the Recreational Software Advisory Council (RSAC). They use their own (copyrighted) rating system, which we include with their permission, updated by us to use PICS-2.0. The rating system contains four categories: Violence, Nudity, Sex, and Language. Each category is rated on a scale from 0 to 4, with a specific description for each value. Only values with names are permitted.
((PICS-version 2.0)
(service-section
(labeling-service "http://www.rsac.org/")
(name "The RSAC Ratings Service")
(description "The Recreational Software Advisory Council rating
service. Based on the work of Dr. Donald F. Roberts of Stanford
University, who has studied the effects of media on children for
nearly 20 years.")
(sample-url "http://www.rsac.org/ReferenceSamples")
)
(schema "http://www.rsac.org/ratingsv02.html"
"http://w3.org/PICS/PICS-Schema")
(default (label-only true))
(category
(transmit-as "v")
(name "Violence")
(label
(name "Conflict")
(description "Harmless conflict; some damage to objects")
(value 0))
(label
(name "Fighting")
(description "Creatures injured or killed; damage to objects;
fighting")
(value 1))
(label
(name "Killing")
(description "Humans injured or killed with small amount of blood")
(value 2))
(label
(name "Blood and Gore")
(description "Humans injured or killed; blood and gore")
(value 3))
(label
(name "Wanton Violence")
(description "Wanton and gratuitous violence; torture; rape")
(value 4)))
(category
(transmit-as "s")
(name "Sex")
(label
(name "None")
(description "Romance; no sex")
(value 0))
(label
(name "Passionate kissing")
(description "Passionate kissing")
(value 1))
(label
(name "Clothed sexual touching")
(description "Clothed sexual touching")
(value 2))
(label
(name "Non-explicit sexual activity")
(description "Non-explicit sexual activity")
(value 3))
(label
(name "Explicit sexual activity; sex crimes")
(description
"Explicit sexual activity; sex crimes")
(value 4)))
(category
(transmit-as "n")
(name "Nudity")
(label
(name "None")
(description "No nudity or revealing attire")
(value 0))
(label
(name "Revealing Attire")
(description "Revealing attire"
(value 1))
(label
(name "Partial Nudity")
(description "Partial nudit")
(value 2))
(label
(name "Frontal Nudity")
(description "Non-sexual frontal nudity")
(value 3))
(label
(name "Explicit")
(description
"Provocative frontal nudity")
(value 4)))
(category
(transmit-as "l")
(description "Language")
(label (name "Slang")
(description "Inoffensive slang; no profanity")
(value 0))
(label (name "Mild Expletives")
(description "Mild expletives")
(value 1))
(label (name "Expletives")
(description "Expletives; non-sexual anatomical references")
(value 2))
(label (name "Obscene Gestures")
(description "Strong, vulgar language; obscene gestures")
(value 3))
(label (name "Explicit")
(description "Crude or explicit sexual references")
(value 4))))
SafeSurf, a parents' organization, has established a rating system that is used for self-rating by a large and growing number of sites on the Internet. They have provided a machine-readable version of their service to PICS as a demonstration of a more complex rating system that includes sub-categories as well as a document classification system. The following specification includes a full description of the rating part of the SafeSurf system, with only a small stub to represent the classifications.
((PICS-version 2.0)
(service-section
(labeling-service "http://www.classify.org/safesurf/service/")
(name "SafeSurf Rating Service")
(description "The SafeSurf SS~~ Rating and Classification Standard.
Designed with input from thousands of parents and Net citizens worldwide to
specifically to handle the vast potential of the Internet, it empowers each
family to make informed decisions concerning accessibility of online
content. Copyright 1995. All Rights Reserved."))
(schema "http://www.classify.org/safesurf/"
"http://w3.org/PICS/PICS-Schema")
(category (transmit-as "SS~~000") (name "Age Range")
(label
(name "All Ages")
(value 1))
(label
(name "Older Children")
(value 2))
(label
(name "Younger Teens")
(value 3))
(label
(name "Older Teens")
(value 4))
(label
(name "Adult Supervision Recommended")
(value 5))
(label
(name "Adults")
(value 6))
(label
(name "Limited to Adults")
(value 7))
(label
(name "Adults Only")
(value 8))
(label
(name "Explicitly for Adults")
(value 9)))
(category (transmit-as "SS~~001") (name "Profanity")
(label
(name "Subtle Innuendo")
(description "Subtly Implied through the use of Slang")
(value 1))
(label
(name "Strong Innuendo")
(description "Expressly implied through the use of Slang")
(value 2))
(label
(name "Technical Reference")
(description "Dictionary, encyclopedic, news, technical references")
(value 3))
(label
(name "Non-Graphic-Artistic")
(description "Limited non-sexual expletives used in a artistic
fashion") (value 4))
(label
(name "Graphic-Artistic")
(description "Non-sexual expletives used in a artistic fashion")
(value 5))
(label
(name "Graphic")
(description "Limited use of expletives and obscene gestures") (value
6))
(label
(name "Detailed Graphic")
(description "Casual use of expletives and obscene gestures") (value
7))
(label
(name "Explicit Vulgarity")
(description "Heavy use of vulgar language and obscene gestures.
Unsupervised Chat Rooms.")
(value 8))
(label
(name "Explicit and Crude")
(description "Saturated with crude sexual references and gestures.
Unsupervised Chat Rooms.")
(value 9)))
(category (transmit-as "SS~~002") (name "Heterosexual Themes")
(label
(name "Subtle Innuendo")
(description "Subtly Implied through the use of metaphor")
(value 1))
(label
(name "Strong Innuendo")
(description "Explicitly implied (not described) through the use of
metaphor")
(value 2))
(label
(name "Technical Reference")
(description "Dictionary, encyclopedic, news, medical references")
(value 3))
(label
(name "Non-Graphic-Artistic")
(description "Limited metaphoric descriptions used in a artistic
fashion")
(value 4))
(label (name "Graphic-Artistic")
(description "Metaphoric descriptions used in a artistic fashion")
(value 5))
(label
(name "Graphic")
(description "Descriptions of intimate sexual acts")
(value 6))
(label
(name "Detailed Graphic")
(description "Descriptions of intimate details of sexual acts")
(value 7))
(label
(name "Explicit Vulgarity")
(description "Explicit Descriptions of intimate details of sexual
acts designed to arouse. Inviting interactive sexual participation.
Unsupervised Sexual Chat Rooms or Newsgroups")
(value 8))
(label
(name "Explicit and Crude")
(description "Profane Graphic Descriptions of intimate details of
sexual acts designed to arouse. Inviting interactive sexual participation.
Unsupervised Sexual Chat Rooms or Newsgroups")
(value 9)))
(category (transmit-as "SS~~003") (name "Homosexual Themes")
(label
(name "Subtle Innuendo")
(description "Subtly Implied through the use of metaphor")
(value 1))
(label
(name "Strong Innuendo")
(description "Explicitly implied (not described) through the use of
metaphor")
(value 2))
(label
(name "Technical Reference")
(description "Dictionary, encyclopedic, news, medical references")
(value 3))
(label
(name "Non-Graphic-Artistic")
(description "Limited metaphoric descriptions used in a artistic
fashion")
(value 4))
(label
(name "Graphic-Artistic")
(description "Metaphoric descriptions used in a artistic fashion")
(value 5))
(label
(name "Graphic")
(description "Descriptions of intimate sexual acts")
(value 6))
(label
(name "Detailed Graphic")
(description "Descriptions of intimate details of sexual acts")
(value 7))
(label
(name "Explicit Vulgarity")
(description "Explicit Descriptions of intimate details of sexual
acts designed to arouse. Inviting interactive sexual participation.
Unsupervised Sexual Chat Rooms or Newsgroups")
(value 8))
(label
(name "Explicit and Crude")
(description "Profane Graphic Descriptions of intimate details of
sexual acts designed to arouse. Inviting interactive sexual participation.
Unsupervised Sexual Chat Rooms or Newsgroups")
(value 9)))
(category (transmit-as "SS~~004") (name "Nudity")
(label
(name "Subtle Innuendo")
(description "Subtly Implied through the use of composition,
lighting, shaping, revealing clothing, etc.")
(value 1))
(label
(name "Strong Innuendo")
(description "Explicitly implied (not shown) through the use of
composition, lighting, shaping or revealing clothing")
(value 2))
(label
(name "Technical Reference")
(description "Dictionary, encyclopedic, news, medical references")
(value 3))
(label
(name "Non-Graphic-Artistic")
(description "Classic works of art presented in public museums for
family viewing")
(value 4))
(label
(name "Graphic-Artistic")
(description "Artistically presented without full frontal nudity")
(value 5))
(label
(name "Graphic")
(description "Artistically presented with frontal nudity")
(value 6))
(label
(name "Detailed Graphic")
(description "Erotic frontal nudity")
(value 7))
(label
(name "Explicit Vulgarity")
(description "Detailed provocative presentation")
(value 8))
(label
(name "Explicit and Crude")
(description "Explicit pornographic presentation")
(value 9)))
(category (transmit-as "SS~~005")
(name "Violence")
(label
(name "Subtle Innuendo")
(value 1))
(label
(name "Strong Innuendo")
(value 2))
(label
(name "Technical Reference")
(value 3))
(label
(name "Non-Graphic-Artistic")
(value 4))
(label
(name "Graphic-Artistic")
(value 5))
(label
(name "Graphic")
(value 6))
(label
(name "Detailed Graphic")
(value 7))
(label
(name "Inviting Participation in Graphic Interactive Format")
(value 8))
(label
(name "Encouraging Personal Participation, Weapon Making")
(value 9)))
(category (transmit-as "SS~~006")
(name "Sex Violence and Profanity")
(label
(name "Subtle Innuendo")
(value 1))
(label
(name "Strong Innuendo")
(value 2))
(label
(name "Technical Reference")
(value 3))
(label
(name "Non-Graphic-Artistic")
(value 4))
(label
(name "Graphic-Artistic")
(value 5))
(label
(name "Graphic")
(value 6))
(label
(name "Detailed Graphic")
(value 7))
(label
(name "Explicit Vulgarity")
(value 8))
(label
(name "Explicit and Crude")
(value 9)))
(category (transmit-as "SS~~007")
(name "Intolerance of another person's racial, religious, or gender
backround")
(label
(name "Subtle Innuendo")
(value 1))
(label
(name "Strong Innuendo")
(value 2))
(label
(name "Technical Reference")
(value 3))
(label
(name "Non-Graphic-Literary")
(value 4))
(label
(name "Graphic-Literary")
(value 5))
(label
(name "Graphic Discussions")
(value 6))
(label
(name "Endorsing Hatred")
(value 7))
(label
(name "Endorsing Violent or Hateful Action")
(value 8))
(label
(name "Advocating Violent or Hateful Action")
(value 9)))
(category (transmit-as "SS~~008") (name "Glorifying Drug Use")
(label
(name "Subtle Innuendo")
(value 1))
(label
(name "Strong Innuendo")
(value 2))
(label
(name "Technical Reference")
(value 3))
(label
(name "Non-Graphic-Artistic")
(value 4))
(label
(name "Graphic-Artistic")
(value 5))
(label
(name "Graphic")
(value 6))
(label
(name "Detailed Graphic")
(value 7))
(label
(name "Simulated Interactive Participation")
(value 8))
(label
(name "Soliciting Personal Participation")
(value 9)))
(category (transmit-as "SS~~009") (name "Other Adult Themes")
(label
(name "Subtle Innuendo")
(value 1))
(label
(name "Strong Innuendo")
(value 2))
(label
(name "Technical Reference")
(value 3))
(label
(name "Non-Graphic-Artistic")
(value 4))
(label
(name "Graphic-Artistic")
(value 5))
(label
(name "Graphic")
(value 6))
(label
(name "Detailed Graphic")
(value 7))
(label
(name "Explicit Vulgarity")
(value 8))
(label
(name "Explicit and Crude")
(value 9)))
(category (transmit-as "SS~~00A") (name "Gambling")
(label
(name "Subtle Innuendo")
(value 1))
(label
(name "Strong Innuendo")
(value 2))
(label
(name "Technical Discussion")
(value 3))
(label
(name "Non-Graphic-Artistic, Advertising")
(value 4))
(label
(name "Graphic-Artistic, Advertising")
(value 5))
(label
(name "Simulated Gambling")
(value 6))
(label
(name "Real Life Gambling without Stakes")
(value 7))
(label
(name "Encouraging Interactive Real Life Participation with Stakes")
(value 8))
(label
(name "Providing Means with Stakes")
(value 9)))
(category (transmit-as "SS~~100") (name "General Information")
(min 1) (max 100) (integer true)))
Appendix D: Changes from PICS-1.1
- string values
- imbedded-label
- url values
- isodate values
- increment
- abstract
- replacement of rating-system with schema
- change from rating-service to labeling-service
- label-bureau extension is now part of the spec as label-bureau
- transmitting more than one application/pics-service together
- superschema
- category-default-value
- boolean values
- recommendation that service URL start with http and that
Accept: application/pics-service retrieves it
- service-section
- schema appears after service-section(labeling-service URL)
whereas in PICS-1.1, rating-service appeared after rating-system
- sample-url
Webmaster
$Date:
1997/06/20 16:45:16 $