Difference between revisions of "Oct. 3, 2005"
(→Agenda and Notes for Telecon, Oct. 3, 2005) |
(→Agenda and Notes for Telecon, Oct. 3, 2005) |
||
| Line 6: | Line 6: | ||
* RDF servers/data stores--[http://www.joseki.org/ Joseki], [http://www.openrdf.org/ Sesame], [http://idealliance.org/proceedings/xtech05/papers/04-02-04/ Kowari] etc.) | * RDF servers/data stores--[http://www.joseki.org/ Joseki], [http://www.openrdf.org/ Sesame], [http://idealliance.org/proceedings/xtech05/papers/04-02-04/ Kowari] etc.) | ||
* RDF query--[http://www.w3.org/TR/2004/WD-rdf-sparql-query-20041012/ SparQL] | * RDF query--[http://www.w3.org/TR/2004/WD-rdf-sparql-query-20041012/ SparQL] | ||
| + | |||
| + | [Discussion] Stuart talked about the value of using RDF, where the structure of the data is encoded in the data itself instead of relying totally on a relational database. Ryan and Stuart's experience has been that this is very useful, and supports inferencing. There are still issues of how much of the implementation is based on RDF. Jon feels that there are intrinsic limitations on what other technologies you can use. Jon is particularly concerned with what languages can be used, particularly if we want to distribute the software. Ryan agrees that we need to pick technologies that are supported over time. Stuart points out that we didn't promise to distribute software, rather to support distributed registries that could communicate with one another. Diane points out that we do need to think about distribution, lest we be the only extant registry (an unsustainable prospect). Stuart agrees that we need to think about this as we move along. | ||
| + | |||
2. SKOS as "default" scheme generation framework | 2. SKOS as "default" scheme generation framework | ||
3. Issues of Zope/Plone (or any other content management system) to handle select functionality | 3. Issues of Zope/Plone (or any other content management system) to handle select functionality | ||
| − | 4. (Time permitting) Immediate next steps in preparation for meeting in | + | 4. (Time permitting) Immediate next steps in preparation for meeting in Ithaca: |
| − | * Completion of first | + | * Completion of first iteration of draft Use Cases |
* Begin work on RDF resource modeling | * Begin work on RDF resource modeling | ||
** Agent class (stemming from Use Cases) | ** Agent class (stemming from Use Cases) | ||
Revision as of 12:37, 3 October 2005
Agenda and Notes for Telecon, Oct. 3, 2005
This conference call needs to be sharply focused on infrastructure/technology questions
1. Commitment to Resource Description Framework (RDF) and its possible implications:
[Discussion] Stuart talked about the value of using RDF, where the structure of the data is encoded in the data itself instead of relying totally on a relational database. Ryan and Stuart's experience has been that this is very useful, and supports inferencing. There are still issues of how much of the implementation is based on RDF. Jon feels that there are intrinsic limitations on what other technologies you can use. Jon is particularly concerned with what languages can be used, particularly if we want to distribute the software. Ryan agrees that we need to pick technologies that are supported over time. Stuart points out that we didn't promise to distribute software, rather to support distributed registries that could communicate with one another. Diane points out that we do need to think about distribution, lest we be the only extant registry (an unsustainable prospect). Stuart agrees that we need to think about this as we move along.
2. SKOS as "default" scheme generation framework
3. Issues of Zope/Plone (or any other content management system) to handle select functionality
4. (Time permitting) Immediate next steps in preparation for meeting in Ithaca:
- Completion of first iteration of draft Use Cases
- Begin work on RDF resource modeling
- Agent class (stemming from Use Cases)
- Organizations
- Maintainers
- Registry Managers
- System Administrator
- Visitor
- Registered User
- Organization Contact
- SKOS (working vocabulary representation)
- Concept Schemes
- Concepts
- Descriptive
- Administrative
- Agent class (stemming from Use Cases)
