PRISM Working Group
Document Change Control
Outcome:
Change Form
For working group use
Number:0728
For working group use
Request Title: Add element-refinement to specs
Requestor Information
Your Name
Dianne Kennedy
Company/Org
eMail address
Phone
Affected Documents
Document
All modules
Type the requested information in each table cell.
Replace the ˆ with an "X"; type the version; one document per form
Version
Basic Changes
(Complete this section if you are requesting a specific change: fix an error, add an explanation, delete a paragraph, etc.)
Add the DC concept of “element” and “element-refinement” to help clarify our documentation. This will show
which elements are refinements of others in DC and in our namespaces. Also update models for refinements to
show the element that they are refining.
From DC:
2. Elements and qualifiers
2.1. Elements
An Element is a property of a resource. As intended here,
"properties" are attributes of resources -- characteristics
that a resource may "have", such as a Title, Publisher,
or Subject.
2.2. Qualifiers
"Qualifiers" is the generic heading traditionally used
for terms now usually referred to specifically as Element
Refinements or Encoding Schemes.
2.2.1. Element Refinements.
An Element Refinement is a property of a resource which
shares the meaning of a particular DCMI Element but with
narrower semantics. In some application environments (notably
HTML-based encodings), Element Refinements are used together
with Elements in the manner of natural-language "qualifiers"
(i.e., adjectives) [3]. However, since Element Refinements are
properties of a resource (like Elements), Element Refinements
can alternatively be used in metadata records independently
of the properties they refine [9]. In DCMI practice, an
Element Refinement refines just one parent DCMI property.
Example:
Term Name: abstract
URI:
http://purl.org/dc/terms/abstract
Label:
Abstract
Definition:
A summary of the content of the resource.
Type of Term:
element-refinement
http://www.prismstandard.org/
Form version 1.1
Page 1 of 2
PRISM Working Group
Document Change Control
Refines:
Text Documents
Affected page(s)
http://purl.org/dc/elements/1.1/description
Paragraph
Change
Reason
Type the requested information in each table cell. "Reason" is required; please focus on business or implementation drivers in explaining your
request. Please attach examples on a separate page, if appropriate.
XML Objects
Affected files(s)
Line #(s)
Change
Reason
Type the requested information in each table cell. "Reason" is required; please focus on business or implementation drivers in explaining your
request. Please attach examples on a separate page, if appropriate.
Structural Changes
(Complete this section if you are requesting a general change: add elements, create new sections or entire new documents, etc.)
Change
Reason
Type the requested information in each table cell.
Send completed forms to:
Erin Clark, Chair
[email protected]
Copy:
Lee Vetton, Chair
[email protected]
Copy:
Dianne Kennedy, Editor
[email protected]
Editors' Recommendations
(This section to be completed only by the specification editor(s))
Make typo change.
Approved April 5, 2007
http://www.prismstandard.org/
Form version 1.1
Page 2 of 2
Current PRISM Documentation Style
prl:geography
Name
Identifier
Definition
Comment
Model #1
Element
Content
Attributes
Model #2
Element
Content
Attributes
Model #3
Element
Content
Attributes
Occurs In
Occurance
Example
Geography (as condition on use of a resource)
prl:geography
Name of, or authority file reference to, a geographic region of interest.
Recommended practice is to use the ISO 3166-1 and 3166-2 country and
region codes.
For profile 2, if there is more than one geography is related to a resource,
PRISM recommends listing the multiple locations inside one prl:geography
element using the RDF containers such as rdf:Bag, rdf:Seq or rdf:Alt to be XMP
compatible. For profile 1, just repeat the prl:geography element multiple times.
URI Resource (no element content)
Authority Reference.(rdf:resource)
Plain Literal
xml:lang (optional) designed for identifying the human language used
XML Literal
rdf:parseType=”Literal”
xml:lang (optional) designed for identifying the human language used
PRL clauses, which are contained in or referred to by a dc:rights element.
May occur 0 or many times
Model #1
<prl:geography rdf:resource=
”http://prismstandard.org/vocabs/ISO-3166/GB”/>
Model #2
<prl:geography>Oklahoma</prl:geography>
Model #3
<prl:geography rdf:parseType=”Literal”>
South &amp; East Counties
</prl>
Proposed PRISM Documentation Style
prl:geography
Name
Identifier
Definition
Field type
Occurrence
Comment
Model #1
Element
Content
Attributes
Model #2
Element
Content
Attributes
Model #3
Element
Content
Attributes
Example
Geography (as condition on use of a resource)
prl:geography
Name of, or authority file reference to, a geographic region of interest.
Element Refinement
Refines dc:rights
May occur 0 or many times
Recommended practice is to use the ISO 3166-1 and 3166-2 country and
region codes.
For profile 2, if there is more than one geography is related to a resource,
PRISM recommends listing the multiple locations inside one prl:geography
element using the RDF containers such as rdf:Bag, rdf:Seq or rdf:Alt to be XMP
compatible. For profile 1, just repeat the prl:geography element multiple times.
URI Resource (no element content)
Authority Reference.(rdf:resource)
Plain Literal
xml:lang (optional) designed for identifying the human language used
XML Literal
rdf:parseType=”Literal”
xml:lang (optional) designed for identifying the human language used
Model #1
<dc:rights>
<prl:geography rdf:resource=
”http://prismstandard.org/vocabs/ISO-3166/GB”/></dc:rights>
Model #2
<dc:rights><prl:geography>Oklahoma</prl:geography></dc:rights>
Model #3
<dc:rights><prl:geography rdf:parseType=”Literal”>
South &amp; East Counties
</prl></dc:rights>