Difference (from revision 2 to 3)

Changed: 57c57

The wildcard character '*' can then be used in references to refer to the current column and/or row in an iteration. For example, if we wish to extend the previous example to perform mappings for rows 2 to 10 we can use the first range directive above and modify the earlier expression to use wildcards: {nid AYG}
The wildcard character '*' can then be used in references to refer to the current column and/or row in an iteration. {nid AZS}

Added: 58a59,68

Example references include: {nid AZT}

* @A3 {nid B0O}
* @A* {nid B0P}
* @** {nid B0Q}

The language will attempt to infer the types of the entities to be imported automatically based on its location in the clause (or will use a global default if it can't - see later). As mentioned, the default name encoding for an entity will use the value from the cell and encode it using the entity's rdfs:label. Again, as will be described later, a global default can be used to change this encoding. {nid AZW}

For example, if we wish to extend the previous example to perform mappings for rows 2 to 10 we can use the first range directive above and modify the earlier expression to use wildcards: {nid AYG}

Changed: 63c73,120

Here, a new necessary and sufficient condition will be created for each of rows 2 to 10.
Here, a new necessary and sufficient condition will be created for each of rows 2 to 10. {nid AZX}

A reference may be optionally followed by: (1) an entity type, which defines the type of entity to be imported; (2) a name encoding, which defines the name encoding of OWL entities; and (3) defining types, which defines the super types of the entity being imported. {nid AZY}

An entity type node is defined: {nid AZZ}

<nowiki>
entity_type ::= ( <RDFS_CLASS> | <RDF_PROPERTY> | <OWL_CLASS> | <OWL_THING> | <OWL_OBJECT_PROPERTY> |<OWL_DATATYPE_PROPERTY> | datatype ) ( "=" "(" value_specification_item ( "," value_specification_item )* ")" )?
</nowiki> {nid B00}

Example references using entity types include: {nid B06}

* @A4(owl:Class) -- create an OWL class from the contents of cell A4 {nid B07}
* @**(xsd:string) -- create an XSD string data value from the contents of the current cell in the grid iteration {nid B08}

The name encoding associated with a reference describes the encoding of the value extracted from a cell for OWL entities. {nid B09}

<nowiki>
name_encoding ::= ( <RDF_ID> | <RDFS_LABEL> | <MM_NONE> )
</nowiki> {nid B0A}

The default extraction is rdfs:label. A name encoding of mm:None means that the cell value is ignored (though an entity may still be created). {nid B0B}

Example uses of this clause are: {nid B0C}

* @A5(rdf:ID) -- create an entity and use value in A5 as its rdf:ID {nid B0N}
* @A6(owl:Class rdfs:label) -- create an OWL class and use the contents of A6 as its rdfs:label {nid B0D}

The defining types clause contains a list of classes or properties that are supertypes or defining types of the entities being created. {nid B0E}

<nowiki>
defining_types ::= ( name_or_reference )+
</nowiki> {nid B0F}

Example uses are: {nid B0G}

* @B76(owl:Class OilRig) {nid B0H}
* @B7(owl:ObjectProperty hasItem) {nid B0I}
* @B8(OilRig 'Mechanical item') {nid B0J}

In the default case, a value is extracted directly from a cell location. Entity types may optionally be followed by a comma-separated value extraction list, which is used to provide more control over this extraction process. {nid B0K}

<nowiki>
value_extraction_item ::= ( string | reference | ( "[" string "]" ) )
</nowiki> {nid B0L}

Each item in this list is either a string literal, a reference, or a capture expression in a regular expression. {nid B0M}