| | |
- term.Function(term.BuiltIn)
-
- BI_argv(term.LightBuiltIn, term.Function)
- BI_baseAbsolute(term.LightBuiltIn, term.Function)
- BI_baseRelative(term.LightBuiltIn, term.Function, term.ReverseFunction)
- BI_environ(term.LightBuiltIn, term.Function)
- term.LightBuiltIn(term.BuiltIn)
-
- BI_argv(term.LightBuiltIn, term.Function)
- BI_baseAbsolute(term.LightBuiltIn, term.Function)
- BI_baseRelative(term.LightBuiltIn, term.Function, term.ReverseFunction)
- BI_environ(term.LightBuiltIn, term.Function)
- term.ReverseFunction(term.BuiltIn)
-
- BI_baseRelative(term.LightBuiltIn, term.Function, term.ReverseFunction)
class BI_argv(term.LightBuiltIn, term.Function) |
| |
# Command line argument: read-only
# The command lines are passed though cwm using "--with" and into the RDFStore when init'ed.
# Not fatal if not defined
|
| |
- Method resolution order:
- BI_argv
- term.LightBuiltIn
- term.BuiltIn
- term.Fragment
- term.Term
- term.Function
Methods defined here:
- evaluateObject(self, subj_py)
Data and non-method functions defined here:
- __doc__ = None
- __module__ = 'cwm_os'
Methods inherited from term.BuiltIn:
- __init__(self, resource, fragid)
- eval(self, subj, obj, queue, bindings, proof, query)
- This function which has access to the store, unless overridden,
calls a simpler one which uses python conventions.
To reduce confusion, the inital ones called with the internals available
use abreviations "eval", "subj" etc while the python-style ones use evaluate, subject, etc.
Methods inherited from term.Fragment:
- dereference(self, mode='', workingContext=None)
- dereference an identifyer, finding the semantics of its schema if any
Returns None if it cannot be retreived.
- generated(self)
- A generated identifier?
This arises when a document is parsed and a arbitrary
name is made up to represent a node with no known URI.
It is useful to know that its ID has no use outside that
context.
- reification(self, sink, why=None)
- Describe myself in RDF to the given context
[ reify:uri "http://example.org/#whatever"]
- representation(self, base=None)
- Optimize output if prefixes available
- uriref(self)
- uriref2(self, base)
Methods inherited from term.Term:
- __repr__(self)
- This method only used for debugging output - it can be ambiguous,
as it is is deliberately short to make debug printout readable.
output as XML qnames [http://www.w3.org/TR/REC-xml-names/#NT-QName].
This could be beefed up to guarantee unambiguity.
- asPair(self)
- Representation in an earlier format, being phased out 2002/08
The first part of the pair is a constant number represnting the type
see RDFSink.py. the second is the value -- uri for symbols, string for literals
- debugString(self, already)
- occurringIn(self, vars)
- substituteEquals(self, bindings, newRedirections)
- Return this or a version of me with substitution made
- substitution(self, bindings, why=None)
- Return this or a version of me with subsitution made
- unify(self, other, vars, existentials, bindings)
- Unify this which may contain variables with the other,
which may contain existentials but not variables.
Return 0 if impossible.
return [({}, reason] if no new bindings
Return [( {var1: val1, var2: val2,...}, reason), ...] if match
- value(self)
- As a python value - by default, none exists, use self
Methods inherited from term.Function:
- evalObj(self, subj, queue, bindings, proof, query)
- This function which has access to the store, unless overridden,
calls a simpler one which uses python conventions.
To reduce confusion, the inital ones called with the internals available
use abreviations "eval", "subj" etc while the python-style ones use "evaluate", "subject", etc.
|
class BI_baseAbsolute(term.LightBuiltIn, term.Function) |
| |
The baseAbsolute function generates an absolute URIref from a string,
interpreting the string as a a relative URIref relative to the current
process base URI (typically, current working directory).
It is not a reverse function, because sereral different relativisations
exist for the same absolute URI. See uripath.py.
|
| |
- Method resolution order:
- BI_baseAbsolute
- term.LightBuiltIn
- term.BuiltIn
- term.Fragment
- term.Term
- term.Function
Methods defined here:
- evaluateObject(self, subj_py)
Data and non-method functions defined here:
- __doc__ = 'The baseAbsolute function generates an absolute ... exist for the same absolute URI. See uripath.py.'
- __module__ = 'cwm_os'
Methods inherited from term.BuiltIn:
- __init__(self, resource, fragid)
- eval(self, subj, obj, queue, bindings, proof, query)
- This function which has access to the store, unless overridden,
calls a simpler one which uses python conventions.
To reduce confusion, the inital ones called with the internals available
use abreviations "eval", "subj" etc while the python-style ones use evaluate, subject, etc.
Methods inherited from term.Fragment:
- dereference(self, mode='', workingContext=None)
- dereference an identifyer, finding the semantics of its schema if any
Returns None if it cannot be retreived.
- generated(self)
- A generated identifier?
This arises when a document is parsed and a arbitrary
name is made up to represent a node with no known URI.
It is useful to know that its ID has no use outside that
context.
- reification(self, sink, why=None)
- Describe myself in RDF to the given context
[ reify:uri "http://example.org/#whatever"]
- representation(self, base=None)
- Optimize output if prefixes available
- uriref(self)
- uriref2(self, base)
Methods inherited from term.Term:
- __repr__(self)
- This method only used for debugging output - it can be ambiguous,
as it is is deliberately short to make debug printout readable.
output as XML qnames [http://www.w3.org/TR/REC-xml-names/#NT-QName].
This could be beefed up to guarantee unambiguity.
- asPair(self)
- Representation in an earlier format, being phased out 2002/08
The first part of the pair is a constant number represnting the type
see RDFSink.py. the second is the value -- uri for symbols, string for literals
- debugString(self, already)
- occurringIn(self, vars)
- substituteEquals(self, bindings, newRedirections)
- Return this or a version of me with substitution made
- substitution(self, bindings, why=None)
- Return this or a version of me with subsitution made
- unify(self, other, vars, existentials, bindings)
- Unify this which may contain variables with the other,
which may contain existentials but not variables.
Return 0 if impossible.
return [({}, reason] if no new bindings
Return [( {var1: val1, var2: val2,...}, reason), ...] if match
- value(self)
- As a python value - by default, none exists, use self
Methods inherited from term.Function:
- evalObj(self, subj, queue, bindings, proof, query)
- This function which has access to the store, unless overridden,
calls a simpler one which uses python conventions.
To reduce confusion, the inital ones called with the internals available
use abreviations "eval", "subj" etc while the python-style ones use "evaluate", "subject", etc.
|
class BI_baseRelative(term.LightBuiltIn, term.Function, term.ReverseFunction) |
| |
The baseRelative of a URI is its expression relation to the process base URI.
It is 1:1, being an arbitrary cannonical form.
It is a reverse function too, as you can always work the other way.
|
| |
- Method resolution order:
- BI_baseRelative
- term.LightBuiltIn
- term.BuiltIn
- term.Fragment
- term.Term
- term.Function
- term.ReverseFunction
Methods defined here:
- evaluateObject(self, subj_py)
- evaluateSubject(self, subj_py)
Data and non-method functions defined here:
- __doc__ = 'The baseRelative of a URI is its expression rela...nction too, as you can always work the other way.'
- __module__ = 'cwm_os'
Methods inherited from term.BuiltIn:
- __init__(self, resource, fragid)
- eval(self, subj, obj, queue, bindings, proof, query)
- This function which has access to the store, unless overridden,
calls a simpler one which uses python conventions.
To reduce confusion, the inital ones called with the internals available
use abreviations "eval", "subj" etc while the python-style ones use evaluate, subject, etc.
Methods inherited from term.Fragment:
- dereference(self, mode='', workingContext=None)
- dereference an identifyer, finding the semantics of its schema if any
Returns None if it cannot be retreived.
- generated(self)
- A generated identifier?
This arises when a document is parsed and a arbitrary
name is made up to represent a node with no known URI.
It is useful to know that its ID has no use outside that
context.
- reification(self, sink, why=None)
- Describe myself in RDF to the given context
[ reify:uri "http://example.org/#whatever"]
- representation(self, base=None)
- Optimize output if prefixes available
- uriref(self)
- uriref2(self, base)
Methods inherited from term.Term:
- __repr__(self)
- This method only used for debugging output - it can be ambiguous,
as it is is deliberately short to make debug printout readable.
output as XML qnames [http://www.w3.org/TR/REC-xml-names/#NT-QName].
This could be beefed up to guarantee unambiguity.
- asPair(self)
- Representation in an earlier format, being phased out 2002/08
The first part of the pair is a constant number represnting the type
see RDFSink.py. the second is the value -- uri for symbols, string for literals
- debugString(self, already)
- occurringIn(self, vars)
- substituteEquals(self, bindings, newRedirections)
- Return this or a version of me with substitution made
- substitution(self, bindings, why=None)
- Return this or a version of me with subsitution made
- unify(self, other, vars, existentials, bindings)
- Unify this which may contain variables with the other,
which may contain existentials but not variables.
Return 0 if impossible.
return [({}, reason] if no new bindings
Return [( {var1: val1, var2: val2,...}, reason), ...] if match
- value(self)
- As a python value - by default, none exists, use self
Methods inherited from term.Function:
- evalObj(self, subj, queue, bindings, proof, query)
- This function which has access to the store, unless overridden,
calls a simpler one which uses python conventions.
To reduce confusion, the inital ones called with the internals available
use abreviations "eval", "subj" etc while the python-style ones use "evaluate", "subject", etc.
Methods inherited from term.ReverseFunction:
- evalSubj(self, obj, queue, bindings, proof, query)
- This function which has access to the store, unless overridden,
calls a simpler one which uses python conventions
|
class BI_environ(term.LightBuiltIn, term.Function) |
| |
# Read Operating sytem environment lookup - read-only
#
# Not fatal if not defined
|
| |
- Method resolution order:
- BI_environ
- term.LightBuiltIn
- term.BuiltIn
- term.Fragment
- term.Term
- term.Function
Methods defined here:
- evaluateObject(self, subj_py)
Data and non-method functions defined here:
- __doc__ = None
- __module__ = 'cwm_os'
Methods inherited from term.BuiltIn:
- __init__(self, resource, fragid)
- eval(self, subj, obj, queue, bindings, proof, query)
- This function which has access to the store, unless overridden,
calls a simpler one which uses python conventions.
To reduce confusion, the inital ones called with the internals available
use abreviations "eval", "subj" etc while the python-style ones use evaluate, subject, etc.
Methods inherited from term.Fragment:
- dereference(self, mode='', workingContext=None)
- dereference an identifyer, finding the semantics of its schema if any
Returns None if it cannot be retreived.
- generated(self)
- A generated identifier?
This arises when a document is parsed and a arbitrary
name is made up to represent a node with no known URI.
It is useful to know that its ID has no use outside that
context.
- reification(self, sink, why=None)
- Describe myself in RDF to the given context
[ reify:uri "http://example.org/#whatever"]
- representation(self, base=None)
- Optimize output if prefixes available
- uriref(self)
- uriref2(self, base)
Methods inherited from term.Term:
- __repr__(self)
- This method only used for debugging output - it can be ambiguous,
as it is is deliberately short to make debug printout readable.
output as XML qnames [http://www.w3.org/TR/REC-xml-names/#NT-QName].
This could be beefed up to guarantee unambiguity.
- asPair(self)
- Representation in an earlier format, being phased out 2002/08
The first part of the pair is a constant number represnting the type
see RDFSink.py. the second is the value -- uri for symbols, string for literals
- debugString(self, already)
- occurringIn(self, vars)
- substituteEquals(self, bindings, newRedirections)
- Return this or a version of me with substitution made
- substitution(self, bindings, why=None)
- Return this or a version of me with subsitution made
- unify(self, other, vars, existentials, bindings)
- Unify this which may contain variables with the other,
which may contain existentials but not variables.
Return 0 if impossible.
return [({}, reason] if no new bindings
Return [( {var1: val1, var2: val2,...}, reason), ...] if match
- value(self)
- As a python value - by default, none exists, use self
Methods inherited from term.Function:
- evalObj(self, subj, queue, bindings, proof, query)
- This function which has access to the store, unless overridden,
calls a simpler one which uses python conventions.
To reduce confusion, the inital ones called with the internals available
use abreviations "eval", "subj" etc while the python-style ones use "evaluate", "subject", etc.
| |