This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Template Registry Technical Requirements"

From HL7Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
== Infrastructure Requirements (Hardware, Software, Etc) ==
 
== Infrastructure Requirements (Hardware, Software, Etc) ==
;Operating System: Linux and/or Windows
+
Work has started on setting up a local development/build environment.  After I (Keith) have a working build environment, I will be setting up a deployment/test server.  Subsequently, I will be putting the necessary build components in a Source control system using OHT.
 +
 
 +
;Operating System: Linux (deployment/test) and/or Windows (development/build)
 
;Programming Language: Java 1.5 or later
 
;Programming Language: Java 1.5 or later
 
;Web Server: Apache Tomcat 5.0.28 or Later (or other JSP 2.0/Servlet 2.3 Compatible Container)
 
;Web Server: Apache Tomcat 5.0.28 or Later (or other JSP 2.0/Servlet 2.3 Compatible Container)
Line 9: Line 11:
 
* Open Source
 
* Open Source
 
* Java Based (preferably but not absolute requirement, especially if RSS/Atom Enabled)
 
* Java Based (preferably but not absolute requirement, especially if RSS/Atom Enabled)
 
  
 
== User Interface Requirements and Design ==
 
== User Interface Requirements and Design ==
 
== Template Metadata Format ==
 
== Template Metadata Format ==
 +
Metadata will be stored using the ebXML Registry Information Model.
 +
 
===Authenticated Users===
 
===Authenticated Users===
 
User who are storing information or updating the registry would have a user record stored in the registry that would be referenced by a template registry entry or an audit record.  We are proposing here to use OpenID to support authentication as a simlpifier.   
 
User who are storing information or updating the registry would have a user record stored in the registry that would be referenced by a template registry entry or an audit record.  We are proposing here to use OpenID to support authentication as a simlpifier.   

Revision as of 20:34, 25 March 2010

Infrastructure Requirements (Hardware, Software, Etc)

Work has started on setting up a local development/build environment. After I (Keith) have a working build environment, I will be setting up a deployment/test server. Subsequently, I will be putting the necessary build components in a Source control system using OHT.

Operating System
Linux (deployment/test) and/or Windows (development/build)
Programming Language
Java 1.5 or later
Web Server
Apache Tomcat 5.0.28 or Later (or other JSP 2.0/Servlet 2.3 Compatible Container)
Database
Derby (or other SQL-92 Compliant Database)
Web Services
JWSDP 1.6
ebXML Registry
freebXMLRegistry 3.1
Mailing List Server
TBD
  • Open Source
  • Java Based (preferably but not absolute requirement, especially if RSS/Atom Enabled)

User Interface Requirements and Design

Template Metadata Format

Metadata will be stored using the ebXML Registry Information Model.

Authenticated Users

User who are storing information or updating the registry would have a user record stored in the registry that would be referenced by a template registry entry or an audit record. We are proposing here to use OpenID to support authentication as a simlpifier.

This is the proposed metadata that would be stored in the registry for users that are updating the registry.

<User id="dummy" xmlns="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0">
 <Name>
  <LocalizedString value="OpenID"/>
 </Name>
 <Description>
  <LocalizedString value="Display Name"/>
 </Description>
 <Address city="" country="" postalCode="" stateOrProvince="" street=""
  streetNumber=""/>
 <PersonName firstName="" lastName="" middleName=""/>
 <TelephoneNumber areaCode="" countryCode="" extension="" number="" phoneType=""/>
 <EmailAddress address=""/>
</User>

Publisher