Irene,
I'm actually figuring this out, finally.  I actually came up with that
specific naming scheme for
organizing foaf files in a directory.  I thought that it would be
useful to have some data like this
for a community site that I run for poets and writers.  You never know
when you will get noticed
for a job. :-)

I really appreciate all the help that I am getting.  I do need to
invest in one of the versions of this
for my projects as it will be more useful for creating applications
that using the free version.
For Genealogy, I noticed what http://familypedia.wikia.org was doing
for a naming convention
and how they are using Semantic MediaWiki (SMW) for genealogy.  They
didn't actually make full use of
SMW in that they aren't actually importing any vocabularies and
aligning data with the ontology(ies).  However, their
naming convention was to use "Firstname Lastname (dob - dod)" for
files/pages, and so that was my
idea for naming.

I was thinking about the issue of using XSL and realized that maybe
RDFa might be a better solution.  Unless one uses
server side XSL, then one isn't actually getting XHTML files that can
be indexed by search engines like Google.  I think that is the
motivation of the Linked Data effort.  Using SPARQL does seem to be a
better solution than just using XSL on a large
RDF graph.  And the ability to do this in TBC helps.
Bruce

On Jul 27, 12:30 am, "Irene Polikoff" <[email protected]> wrote:
> Bruce,
>
> As Holger said, for most of TopBraid functionality it really does not matter
> whether something is a class, property or not. Every RDF resource has a
> type. Types are classes. When you select a resource that is used as a type,
> you see in the Instances view resources that are members of this class.
> Resource you selected shows up in a form that can be edited.
>
> Resources whose type is Class and Property are special in that they have
> views of their own where they are shown in a hierarchical tree using
> rdfs:subClassOf and rdfs:subPropertyOf to build the hierarchy. Even if you
> are not creating new classes and properties, these views are still useful
> for you to understand the ontologies (data schemas) you are using and to
> navigate through the data that is organized based on these schemas. With
> that in mind, everything in the Getting Started Guide with the exception of
> working with OWL restrictions is teaching some skill I believe to be
> relevant to what you are working on. Especially, sections about organizing
> the workspace, imports, working with multiple graphs, SPARQL, etc.
>
> There is a number of ways you can organize your project. One approach that
> may work for you would be to name the project personalprofiles.fwwebdev.com.
> Then create a folder for each foaf file you are planning to create e.g.,
> BruceWhealton folder, JeanArthurJones folder, etc. Then, when you right
> click on a folder (e.g., BruceWhealton) to create 
> new,http://personalprofiles.fwwebdev.com/BruceWhealton/unnamed0will already be
> filled out for you. You will just need to replace unnamed0 with foaf.
>
> With this approach you can keep multiple files called foaf.rdf in one
> project. Of course, relying on uniqueness of a name is not particularly
> robust or scalable. The idea of having foaf files is that each person would
> create their own. So, the granularity is per person and the URIs end up
> being different because each person will put his file at whatever web domain
> they are hosting.
>
> In a Genealogy application you are describing, you would most likely use an
> RDF database rather than many files. You could still, of course, keep
> information about each person as an individual named graph, but the graphs
> ids may be based on some identifier that is more unique than a name.
>
> < I did notice that the second file when I created that, did not have
> the same imports or all the imports that the first one did.>
>
> This is really up to you. Each graph you create will have whatever imports
> you specify.
>
> < It would be interesting to be able to use xsl to convert the rdf file
> for html output so that people could see and browse different
> profiles.>
>
> HTML presentation is already part of TopBraid. When you select a resource
> you can click on the Browser tab in the form to see information about the
> resource presented in HTML. For viewing outside of TopBraid, yes, you could
> create XSLT that is specific to your data and your presentation
> requirements.
>
> Irene
>
>
>
>
>
>
>
> -----Original Message-----
> From: [email protected]
>
> [mailto:[email protected]] On Behalf Of brucewhealton
> Sent: Tuesday, July 26, 2011 10:52 PM
> To: TopBraid Suite Users
> Subject: [topbraid-users] Re: Stuck with a type of entry using TBC forms
>
> Some of this is fundamental understanding of what I want to do
> eventually.  I want to move to doing a Genealogy application for a
> client.  We can use the name spaces foaf, bio and rel, as well as geo,
> and some others.
> For practice I wanted to be able to learn this by looking at a
> foaf.rdf file that I created by hand and try to do it using TBC.  Then
> I can get all the foaf files created in TBC.
> So, the challenge was with the regard to the above, and with your
> explanation, I would create the resource that is equal to my blog's
> URL.  Then I want to say that the resource has a dc:title.
> I think the difficulty is that I am looking at the documentation and I
> keep finding information about creating ontologies.  I'm at the point
> of using an ontology or several to create a triple store in rdf, or in
> this case, specifically a foaf file.
>
> This is another related issue.  I thought I got an error when I tried
> to work with more than one file in a project but that doesn't make
> sense.  Maybe one should only have one file in a project open at one
> time.  I was using this naming convention when creating files, which
> seems to be ok:http://personalprofiles.fwwebdev.com/BruceWhealton/foaf.rdf
> andhttp://personalprofiles.fwwebdev.com/JeanArthurJones/foaf.rdf
> I did notice that the second file when I created that, did not have
> the same imports or all the imports that the first one did.
> For a large community it wouldn't make sense to put everyone in one
> foaf file.  Someone on this board said the same thing.
>
> It would be interesting to be able to use xsl to convert the rdf file
> for html output so that people could see and browse different
> profiles.
> So, for now, I'm looking at expanded foaf files that include other
> ontologies.
> I will also do this for all my web development clients so that they
> can contribute to the Semantic Web and as part of my training that I
> am pursuing.
> Thanks,
> Bruce
>
> On Jul 26, 7:40 pm, "Irene Polikoff" <[email protected]> wrote:
> > Bruce,
>
> > To add a statement about a resource (with the resource as a subject) you
> > need to first declare that it (the resource) exists. To do this, you need
> to
> > create a triple of the following pattern:
>
> > ?resource rdf:type ?someClass
>
> > If resource <http://futurewavedesigns.com/wordpress> is a foaf:Document,
> > then you need to create a triple:
>
> > <http://futurewavedesigns.com/wordpress> rdf:type foaf:Document
>
> > Once you do this, you will be able to navigate to this resource and say
> > whatever you want about it.
>
> > To do this, select foaf:Document and click on Add new in the Instance
> view.
> > When a Create foaf:Document dialog appears, enter
> > <http://futurewavedesigns.com/wordpress> in the "Name of the new instance"
> > field.
>
> > You will now see it in the list of instances for foaf:Document and will be
> > able to drag and drop it, place it into the basket and you will be able to
> > select it from the Add Existing dialogs when editing. You will not be able
> > to do auto-complete on it and if you try to ctrl Click on it in one of the
> > form fields, TopBraid will try to navigate to it on the web.
>
> > You could define a prefixhttp://futurewavedesigns.com/inthe file you are
> > editing and call it let's say future, then you should be able to switch
> > between a full URI of this resource and its QName future:wordpress and you
> > will be able to do auto-completion, etc.
>
> > I am not sure what you mean by "relative to my main project". I am also
> not
> > sure if the above helps you to do what you are trying to do. I find some
> of
> > your questions hard to understand, so we probably are not quite on the
> same
> > page.  
>
> > May be if you explained what you are trying to do with all these foaf
> file,
> > how you are planning to use/deploy them, it would help to achieve some
> > shared understanding.  
>
> > Regards,
>
> > Irene
>
> > -----Original Message-----
> > From: [email protected]
>
> > [mailto:[email protected]] On Behalf Of brucewhealton
> > Sent: Tuesday, July 26, 2011 5:58 PM
> > To: TopBraid Suite Users
> > Subject: [topbraid-users] Stuck with a type of entry using TBC forms
>
> > Hello,
> >          So, I've not been able to figure out how to handle a special
> > case when using the forms to enter data.  Suppose I have this in my
> > foaf profile:
>
> > <foaf:Person rdf:about="#me">
> >     <foaf:weblog rdf:resource="http://futurewavedesigns.com/
> > wordpress/" dc:title="Web Technology Blog" />
> > ...
> > </foaf:Person>
>
> > So, I can enter into the form under foaf:weblog the url above.  But
> > how do I associate the title with that resource?
> > The second triple will be:
> > <http://futurewavedesigns.com/wordpress./>
> <http://purl.org/dc/elements/1.1/title
> > > "Web Technology Blog"
>
> > When I try to go into the source code using TBC, and put that first
> > full statement that links to the weblog it doesn't update when i
> > return to the form.  If I try to create a new Document object it will
> > still be setup as relative to my main project.
> > This kind of thing will exist in various similar places where I want
> > to use Object resources.  All of the documentation seems to be with
> > regard to creating Object datatypes when you are defining the ontology
> > not when one is working with instance data.
> > Maybe I need a blank node that says that the url is a weblog it has
> > such and such title and then in the document I'd link to the node?
> > I'm not sure how to do that though.
> > Thanks,
> > Bruce
>
> > --
> > You received this message because you are subscribed to the Google
> > Group "TopBraid Suite Users", the topics of which include TopBraid
> Composer,
> > TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
> > To post to this group, send email to
> > [email protected]
> > To unsubscribe from this group, send email to
> > [email protected]
> > For more options, visit this group
> athttp://groups.google.com/group/topbraid-users?hl=en
>
> --
> You received this message because you are subscribed to the Google
> Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
> TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
> To post to this group, send email to
> [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group 
> athttp://groups.google.com/group/topbraid-users?hl=en

-- 
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en

Reply via email to