Page Tree:

Child pages
  • Morphological Analysis Service Description and Assumptions

This wiki space contains archival documentation of Project Bamboo, April 2008 - March 2013.

Skip to end of metadata
Go to start of metadata

This page is SUPERCEDED by v0.9 documentation in the final documentation set. Cf. Morphological Analysis Service Description and Assumptions - v1.1.1


Morphological Analysis pages: Home | Description | Use Cases | Questions | Models/Adoption/Delegation | Entity Diagrams | Contract


Summary Description:



Unknown macro: {multi-excerpt} Morphological Analysis




The summary description below will appear in summary pages. Please restrict to several lines, maximum.




Unknown macro: {multi-excerpt} Interacts with disparate morphology services and text repositories to provide the ability to process, retrieve and store morphological analyses for specified texts.




Full Description

The Morphological Analysis Service responds to requests for morphological analysis of texts, submits them to the appropriate morphology service for processing and returns the results in XML adhering to a standard morphology schema.  The Service supports retrieval of texts for analysis from remote repositories as well as user-supplied chunks of text.  Where retrieval from repository is requested, CMIS objectIDs and CTS URNs are supported as document identifiers. 


Key Concepts



  • Result Set Caching Service
  • Notification Service
  • Person/Profile/Group Service


  • Text Repositories (CMIS and CTS)
  • Morphology Services
  • CTS Reference Index Service
  • Data Storage Services


Gliffy Macro Error

Cannot find a diagram with these parameters:

  • Name: MAST-analyzeDocument sequence




Initiates Request, Supplies user auth info to person/profiles/services; Supplies personId and documentId to MAST service; retrieves cached results from result set service


Authenticates with IDP; supplies opaque personId to BSP services; validates personId;

MAST service

requests guid from result set cache; identifies repository for document; retrieves documents from remote repository; tokenizes documents into words; issues request(s) to remote morphology service; compiles and stores result set in result set cache service

Result Set Cache Service

creates guid for result set; notifies notification service when result set storage is complete

Notification Service

notifies client of result set availability

Remote Repository

supplies documents

Remote Morphology Service

analyzes words


  • general service config
    • list of supported output schemas (alpheios, tbd others)
    • list of supported output formats (xml or json)
    • list of supported languages
    • list of supported input/output encodings
    • list of available text repositories (listed according to default search order)
  • language-specific config
    • code
    • description
    • default engine
    • default encoding
  • engine-specific config
    • code
    • url
    • supported language(s)
    • engine/provider description
    • options
  • repository-specific config
    • code
    • description
    • type (cts or cmis)

Background Documentation

Scholarly Services - Linguistic Analysis

Morphological Analysis pages: Home | Description | Use Cases | Questions | Models/Adoption/Delegation | Entity Diagrams | Contract

1 Comment

  1. Unknown User (

    In the diagrams under Collaborations, I'm making a number of assumptions about the functionality to be supplied by the Person/Profile/Group , Notification and Result Set Cache services. I'm not sure if these are correct or not so this may need to be adjusted once those services are defined.

    I'm also a little unclear about where the responsibility lies for coordinating authentication and verifying the validity of the person identifier once authentication is complete.

    It also occurs to me that it might be nice if we could rely on the collections interoperability adapters to supply functionality like tokenization since this is likely to be somewhat collection-dependent.