RDF:Interfaces: Difference between revisions

Jump to navigation Jump to search
porting over literals from my old wiki. This includes major edits that have happened in my head since.
(we decided not to be threadsafe)
(porting over literals from my old wiki. This includes major edits that have happened in my head since.)
Line 62: Line 62:
     readonly attribute AUTF8String identifier;
     readonly attribute AUTF8String identifier;
  };
  };
== rdfILiteral ==
Literals are always obtained through the RDF service. Any script can obtain a literal.
interface rdfILiteral : rdfINode
{
    readonly attribute AString value;
    readonly attribute AUTF8String lang;
    readonly attribute rdfIResource datatype;
    boolean equalsLiteral(in rdfILiteral aOther);
};
Literals should probably expose their primitive value (dates, ints, strings) via nsIVariant. I would love to see XML literals hook up with e4x.
We need a generic mapping of more complex schema datatypes to js, probably, think about http://www.w3.org/2001/XMLSchema-datatypes#base64Binary. This should be somewhat sane for C++, too.


== rdfITripleVisitor ==
== rdfITripleVisitor ==
Line 87: Line 104:
                 in nsIRDFNode aObject, in boolean aTruthValue);
                 in nsIRDFNode aObject, in boolean aTruthValue);
  };
  };
RdfLiterals


== rdfIDataSource ==
== rdfIDataSource ==
Confirmed users, Bureaucrats and Sysops emeriti
2,976

edits

Navigation menu