e-Gov Language Processing

Requirements, Approach, References

Requirements• Build geopolitical hierarchies

• Support industry domains and legacy content

• International coordination of common needs

• Enable in-country use and extensions

• Language localization mechanics and context

• Develop Registries / Semantics / Dictionaries

• Libraries of templates for postal address delivery, and

other shared information processing

• Legal documents shared meanings

• Accessibility and language

Approach (1)

• Build geopolitical hierarchies

– Classifications and Ontologies for registry content access

• Support industry domains and legacy content

– Existing standards such as UCC and UPC/EAN, UN/CEFACT,

X12/EDI as enablers.

• International coordination of common needs

– Agreements and standards, e.g. EPA formats for chemicals reporting,

alignment of terms and meanings. Collaboration on defining

information nouns and regulations.

• Enable in-country use and extensions

– Design in ability for local extensions and support in-country variations

Approach (2)

• Language localization mechanics and context

– Provide interoperable term dictionaries (e.g. CEFACT BSR)

– Develop context mechanisms

– Use labelling systems (UID) to cross-reference like nouns, not the local

words (avoids synonyms issues).

• Develop Registries / Semantics / Dictionaries

– Leverage registry software tools to break ‘Catch 22’ impasse.

• Libraries of templates for postal address delivery, and other

shared information processing

– Tools like OASIS CAM – to capture business semantics of structured

use rules and the associated contexts.

Approach (3)

• Legal documents shared meanings

– Libraries of documents that have been certified as equivalent in local

languages

– Commonly used phrases and agreement fragments (e.g. privacy

statements for user sign-up acceptance, liability statements).

– Ability to cross-reference between local content use, and associated

legal context via interactive links to registry definitions.

• Accessibility

– US Gov Section: 508 requirements as model

– http://www.section508.gov/

References

• Federal IT R&D research community:– http://www.itrd.gov/pubs/blue03/broadening_it_01.html

• UN/CEFACT BSR work.– http://forum.afnor.fr/afnor/forum/TC154WG1/doc00002.doc

• Dublin Core?– Relevance for eBusiness integration?– Use in legal context?

• CEFACT Core Component work• OASIS CAM TC work• OASIS CIQ TC work