[Jslib] Re: RDF redesign
Martin T. Kutschker
Martin.T.Kutschker@blackbox.net
Tue, 13 Nov 2001 17:28:56 +0100
Eric Plaster <plaster@urbanrage.com> schrieb in im Newsbeitrag:
public.mozdev.jslib/3BEFFC1F.8090308@urbanrage.com...
>
>
> Martin T. Kutschker wrote:
>
> > Eric Plaster <plaster@urbanrage.com <mailto:plaster@urbanrage.com>
> > > schrieb in im Newsbeitrag:
> > public.mozdev.jslib/3BEC5192.7050709@urbanrage.com
> > <mailto:public.mozdev.jslib/3BEC5192.7050709@urbanrage.com>...
> >
> > Martin T. Kutschker wrote:
> >
> > * NC: This I felt was something that is completely
> > transparent. From what I learned, you don't need it for
> > anything. You can get a literal with out it, and it fills
> > it in for you. So for example, these are equivelant
> >
> > RDF.getResource( "http://jslib.mozdev.org/rdf#name");
> > RDF.getResource("name");
> >
> > Don't ask me why this is so, but it is. So if the NC is
> > unnessary, and it's only in the rdf file it's self, why even
> > have an option to set your NC? Just default to
> > "http://jslib.mozdev.org/rdf#" because your using our class.
> >
> > Well, but what about RDF files with multiple NCs?
>
> To tell you the truth, I don't know. I know that this works because I
> tested it with an example rdf file. If it's smart enough to figure out
> the NC on a single NC rdf, it should do the right thing.
>
> I think that this may be a small point at this time. If it becomes an
> issue in the future, we can change it.
I might do some experimenting
> I don't know if we should have short cuts, as it can be confusing as to
> what level your at, etc. Plus, it doesn't really fit in the rdf model.
> It's just as easy to get the container and reference them relative, or
> reference them by full path.
You're probably right.
> <snip/>
>
> > In rdf, to make a node into a container, you just have to make one
> > call:
> >
> > RDFCUtils.MakeSeq(this.dsource, myresource);
> >
> > Do you mean in RDF or in Mozilla's RDF implementation?
> >
> > I recall something on mozilla.org saying something about a defect in
> > the implementation
> >
> Yes, this is true in mozilla's implementation.
Well, so one may - but should not - try to make a node a li and a Seq at the
same time. The classes could take care of this.
Masi