conStruct: Todo List

Implementing the memcached caching tool at this level too (not only in WSF?)

Invalidating the cache for these scenarios: (1) create instance record, (2) update instance record, (3) template creation/update/deletation, (4) deletation of an instance record, (5) change in an ontology description.

Class ClassHierarchy

Load this structure from the database system instead of the file system (using include_once).

extending this class hierarchy to copy with equivalent classes.

Once the equivalent classes are know, we have to extend getSuperClasses and getSubClasses to include the equivalent classes of the super and sub classes of a target class

Member conStruct_access ($op, $node, $account): Implementing the access hook properly

Member conStruct_access_callback (): Implementing the callback function for the access hook

Member conStruct_browse ($baseLinksUrl, $showTitle): Finish to integrate the Datasets-Registry idea within conStruct

Member conStruct_create ()

the Create tool will be enhanced to use the description internal to the node's constituent ontologies to create these templated creation pages (rather than the current manual method). This enhancement will enable the easy addition and use of new ontologies. Because of known relationships from the source ontologies, further prompts can be presented when entering new resources. For instance, in the example above the property foaf:knows expects to get the URI of a foaf:Person resource. A ready enhancement is to present the user two choices: (1) put in the URI if known, or (2) prompt with a listing of matching resources for automatically inserting the URI. Finally, the user interface will be enhanced so that the resource creator can define multiple types for the same property if it is permitted by the ontology. Note, these enhancements are all examples of the "data drives the application" paradigm.

Removing $typesProperties and create a new mechanism to create this associative array automatically by analysing the ontologies directly (instead of creating these mappings by hand).

Finish to integrate the Datasets-Registry idea within conStruct

Member conStruct_dataset (): We should consider creating "admin" access on a WSF so that these "admin" access get special treatments.

Member conStruct_delete ()

Finish to integrate the Datasets-Registry idea within conStruct

Handling the "Dataset Removal" with another tool

Member conStruct_export (): Finish to integrate the Datasets-Registry idea within conStruct

Member conStruct_scones (): Finish to integrate the Datasets-Registry idea within conStruct

Member conStruct_scones_settings_validate ($form, &$form_state): Finish to integrate the Datasets-Registry idea within conStruct

Member conStruct_search ($baseLinksUrl, $showFilters)

the Search tool will be enhanced to further leverage the power of RDF by allowing more complex and complete search queries such as: give me the list of resources that are person, where its name is "Jim" and that has a picture.

Finish to integrate the Datasets-Registry idea within conStruct

Member conStruct_update ()

the Update tool will be able to add information about a resource that has been created elsewhere. Let's take an example of two BKN nodes, A and B. Node A describes a person X. Using the Import tool, node B imports some resources from node A, including that for person X. However, users of node B know some more information about person X that can now be added using the Update tool. While this additional information is indexed locally (node B), a useful enhancement would also therefore be to alert node A that new, additional information is now available to include on node A's local index. An expanded Update would aid synchronicity of distributed information across the BK Network. This enhancement could also allow resource updates from outside the network on the broader Web.

Removing $typesProperties and create a new mechanism to create this associative array automatically by analysing the ontologies directly (instead of creating these mappings by hand).

Finish to integrate the Datasets-Registry idea within conStruct

Member conStruct_view ($uri, $dataset=""): the View tool will be enhanced beyond its current "table" view. By adhering to the principle of the "data drives the visualization", future versions will detect the resource type returned as a result and then display it via appropriate templates. For example, if a property refers an image, the image will be displayed; if the property refers a geographical location, a map will be displayed, etc.

Member file_upload_error_message ($error_code): fix the size of the error message with the one of the setting of the node

Member generateClassHierarchyHtmlTreeRecur ($class, $counts, $dataset, $attribute, $type, $page, $ignores): re-enable counts once we fixed some apparent errors in the inference of Solr indexes.

Class PropertyHierarchy: Load this structure from the database system instead of the file system (using include_once).

Class SmartyAggregate: This method could be changed by Drupal Views 2 in the future; if CCK is properly linked to the RDF World.

Member SmartyAttribute::setAttribute ($attribute, $attributeLabel, $value, $valueType, $valueDataset, &$classHierarchy, $reifiedStatements, $reifiedObjectLabel, $setAttributeIgnoreResourceLabel): Checking in the classHierarchy of the system for the label of this type

Member structAppend_access ($op, $node, $account): Implementing the access hook properly

Member structAppend_access_callback (): Implementing the callback function for the access hook

Member structBrowse_access ($op, $node, $account): Implementing the access hook properly

Member structBrowse_access_callback (): Implementing the callback function for the access hook

Member structCreate_access ($op, $node, $account): Implementing the access hook properly

Member structCreate_access_callback (): Implementing the callback function for the access hook

Member structDataset_access ($op, $node, $account): Implementing the access hook properly

Member structDataset_access_callback (): Implementing the callback function for the access hook

Member structDelete_access ($op, $node, $account): Implementing the access hook properly

Member structDelete_access_callback (): Implementing the callback function for the access hook

Member structExport_access ($op, $node, $account): Implementing the access hook properly

Member structExport_access_callback (): Implementing the callback function for the access hook

Member structImport_access ($op, $node, $account): Implementing the access hook properly

Member structImport_access_callback (): Implementing the callback function for the access hook

Member structNetworks_access ($op, $node, $account): Implementing the access hook properly

Member structNetworks_access_callback (): Implementing the callback function for the access hook

Member structOntology_access ($op, $node, $account): Implementing the access hook properly

Member structOntology_access_callback (): Implementing the callback function for the access hook

Member structResource_access ($op, $node, $account): Implementing the access hook properly

Member structResource_access_callback (): Implementing the callback function for the access hook

Member structScones_access ($op, $node, $account): Implementing the access hook properly

Member structScones_access_callback (): Implementing the callback function for the access hook

Member structSearch_access ($op, $node, $account): Implementing the access hook properly

Member structSearch_access_callback (): Implementing the callback function for the access hook

Member structUpdate_access ($op, $node, $account): Implementing the access hook properly

Member structUpdate_access_callback (): Implementing the callback function for the access hook

Member structView_access ($op, $node, $account): Implementing the access hook properly

Member structView_access_callback (): Implementing the callback function for the access hook

OpenStructs

Todo List