:

On the Classification of the Node

Error message

  • Warning: Declaration of SparqlViewsResource::view($view_mode = 'full', $langcode = NULL) should be compatible with Entity::view($view_mode = 'full', $langcode = NULL, $page = NULL) in include_once() (line 1112 of /home/customer/www/lisaerb.com/public_html/old/includes/bootstrap.inc).
  • Deprecated function: implode(): Passing glue string after array is deprecated. Swap the parameters in drupal_get_feeds() (line 394 of /home/customer/www/lisaerb.com/public_html/old/includes/common.inc).
  • Create own meta ontology
  • Find / include Relevant ontologies / namespaces (owl, rdf)
  • Declare URIs, classes / concepts content types / relations
  • set tree / entrances / interfaces / paths

 


 

Relevant misc:

2.5 Datatype dichotomies

  • 2.5.1 Atomic vs. list vs. union datatypes http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#atomic-vs-list
    • The first distinction to be made is that between ·atomic·, ·list· and ·union· datatypes.
    • [Definition:] Atomic datatypes are those having values which are regarded by this specification as being indivisible.
    • [Definition:] List datatypes are those having values each of which consists of a finite-length (possibly empty) sequence of values of an ·atomic· datatype.
    • [Definition:] Union datatypes are those whose ·value space·s and ·lexical space·s are the union of the ·value space·s and ·lexical space·s of one or more other datatypes. For example, a single token which ·match·es Nmtoken from [XML 1.0 (Second Edition)] could be the value of an ·atomic· datatype (NMTOKEN); while a sequence of such tokens could be the value of a ·list· datatype (NMTOKENS).
semantic
ontology