Open Geospatial Consortium
OGC Doc
09-134xx-xxx
CR-Form-v3
CHANGE REQUEST
CSW-ebRIM Registry
Service – Part 2: Basic
extension package
CR ?
rev-
Current version: For
HELP
on using this form, see bottom of this page or look at the pop-up text over the symbols.
Proposed change affects: AS Imp Spec X Best Practices Paper Other
Title: Add the InternationalString data type to the canonical DataType scheme.
Source: Frederic Houbie and Fabian Skivee
Work item code: Date: 2009-09-17
Category: B
Use one of the following categories: F (Critical correction)
A (corresponds to a correction in an earlier release) B (Addition of feature),
C (Functional modification of feature) D (Editorial modification)
Detailed explanations of the above categories can be found in the TC Policies and Procedures.
Reason for change: Current spec. does not allow storing internationalized values (I18N) for slots. In the CIM extension package context, some ISO 19115 files contain
internationalized information that must be stored in the ebRIM catalogue.
Summary of change: Add the InternationalString data type to the canonical DataType scheme like for spatial and temporal data types.
Consequences if not approved:
The ebRIM catalog will not be able to store internationalized information except in name and description where it’s possible with the standard ebRIM model. This means the CSW-ebRIM specification stack will not be able to fulfil metadata management use cases that include internationalized information.
Clauses affected: 6.1, 8.3
Other specs Other core specifications Affected: Abstract specifications
Best Practices Document Supporting Doc.
Other comments: Status
Disposition
OGC 08-089r2198
Add the following text in section 6.1
To support use cases where internationalization (I18N) is needed, the InternationalString data
type is defined and added to the canonical DataType scheme. This data type will use the
InternationString and LocalizedString Class defined in Section 2.3 of [OASIS regrep-rim-3.0-os].
Example A slot specifying an International String
<rim:Slot xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0" xmlns:wrs="http://www.opengis.net/cat/wrs/1.0"
name="http://purl.org/dc/elements/1.1/rights" slotType="urn:ogc:def:dataType:InternationalString"> <wrs:ValueList>
<wrs:AnyValue>
<rim:InternationalString>
<rim:LocalizedString charset="UTF-8" xml:lang="en-US" value="Example to be used without any restriction"/> </rim:InternationalString>
</wrs:AnyValue> </wrs:ValueList> <rim:Slot>
Add the following object to the Figure 2
The “InternationString” data type object must be added to the Figure 2 without any parent. Here
is the object to add:
InternationalString
<<dataType>>
Add the section “8.3.16 InternationalString”
The
InternationalString
data type could be used as a replacement of the
String
type
whenever a String attribute needs to be I18N capable. The lexical representation is a
<rim:InternationalString>
element.
Table 38 – Data type: InternationalString
Property Value
Identifier urn:ogc:def:dataType:InternationString Name InternationalString
Description Denotes an string with I18N capabilities, represented by the
rim:InternationalString element.
Parent urn:oasis:names:tc:ebxml-regrep:classificationScheme:DataType
