This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Template Registry Technical Requirements"
Jump to navigation
Jump to search
m (Technical Requirements moved to Template Registry Technical Requirements: Whoops) |
|||
| (7 intermediate revisions by the same user not shown) | |||
| 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) | ||
;Database: Derby (or other SQL-92 Compliant Database) | ;Database: Derby (or other SQL-92 Compliant Database) | ||
;Web Services: JWSDP 1.6 | ;Web Services: JWSDP 1.6 | ||
| − | |||
;Mailing List Server: TBD | ;Mailing List Server: TBD | ||
* 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) | ||
| − | + | ===Libraries=== | |
| + | ;ebXML Registry: freebXMLRegistry 3.1 | ||
| + | ;OpenID Tools: TBD | ||
== User Interface Requirements and Design == | == User Interface Requirements and Design == | ||
== Template Metadata Format == | == Template Metadata Format == | ||
| + | Metadata will be stored using the [http://www.oasis-open.org/committees/regrep/documents/3.0/schema/ schema] for the [http://www.oasis-open.org/committees/regrep/documents/3.0/specs/regrep-rim-3.0-os.pdf 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"/><!-- User's Open ID --> | ||
| + | </Name> | ||
| + | <Description> | ||
| + | <LocalizedString value="Display Name"/><!-- What to display for this user --> | ||
| + | </Description> | ||
| + | <!-- Demographics (possibly obtained through OpenID APIs) --> | ||
| + | <!-- Address information --> | ||
| + | <Address city="" country="" postalCode="" stateOrProvince="" street="" | ||
| + | streetNumber=""/> | ||
| + | <!-- Person Name Parts --> | ||
| + | <PersonName firstName="" lastName="" middleName=""/> | ||
| + | <!-- Contact Phone Number --> | ||
| + | <TelephoneNumber areaCode="" countryCode="" extension="" number="" phoneType=""/> | ||
| + | <!-- e-Mail Address --> | ||
| + | <EmailAddress address=""/> | ||
| + | </User> | ||
| + | |||
| + | ===Organization=== | ||
| + | <!-- organization has a primaryContact attribute that must be the id of a user, see above --> | ||
| + | <Organization id="dummy" primaryContact="userID" | ||
| + | xmlns="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0" | ||
| + | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | ||
| + | > | ||
| + | <!-- The organization can be classified by some sort of internal coding | ||
| + | scheme to describe their role e.g., publisher, approver, et cetera. | ||
| + | Multiple classifications can be present. | ||
| + | --> | ||
| + | <Classification classificationNode="" classificationScheme="" | ||
| + | classifiedObject="dummy" id="" nodeRepresentation=""/> | ||
| + | <!-- The organization address --> | ||
| + | <Address city="" country="" postalCode="" stateOrProvince="" street="" | ||
| + | streetNumber=""/> | ||
| + | <!-- The organization telephone number --> | ||
| + | <TelephoneNumber areaCode="" countryCode="" extension="" number="" phoneType=""/> | ||
| + | <!-- The organization e-mail --> | ||
| + | <EmailAddress address="" type=""/> | ||
| + | </Organization> | ||
Latest revision as of 20:54, 1 April 2010
Contents
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
- Mailing List Server
- TBD
- Open Source
- Java Based (preferably but not absolute requirement, especially if RSS/Atom Enabled)
Libraries
- ebXML Registry
- freebXMLRegistry 3.1
- OpenID Tools
- TBD
User Interface Requirements and Design
Template Metadata Format
Metadata will be stored using the schema for 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"/><!-- User's Open ID --> </Name> <Description> <LocalizedString value="Display Name"/><!-- What to display for this user --> </Description> <!-- Demographics (possibly obtained through OpenID APIs) --> <!-- Address information --> <Address city="" country="" postalCode="" stateOrProvince="" street="" streetNumber=""/> <!-- Person Name Parts --> <PersonName firstName="" lastName="" middleName=""/> <!-- Contact Phone Number --> <TelephoneNumber areaCode="" countryCode="" extension="" number="" phoneType=""/> <!-- e-Mail Address --> <EmailAddress address=""/> </User>
Organization
<!-- organization has a primaryContact attribute that must be the id of a user, see above --> <Organization id="dummy" primaryContact="userID" xmlns="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > <!-- The organization can be classified by some sort of internal coding scheme to describe their role e.g., publisher, approver, et cetera. Multiple classifications can be present. --> <Classification classificationNode="" classificationScheme="" classifiedObject="dummy" id="" nodeRepresentation=""/> <!-- The organization address --> <Address city="" country="" postalCode="" stateOrProvince="" street="" streetNumber=""/> <!-- The organization telephone number --> <TelephoneNumber areaCode="" countryCode="" extension="" number="" phoneType=""/> <!-- The organization e-mail --> <EmailAddress address="" type=""/> </Organization>
