Thanks Jeremy.


Regards

David


On Monday, November 21, 2005, at 03:05 AM, Jeremy Wong
<fontfamily><param>Hiragino Kaku Gothic Pro</param>黃泓量</fontfamily>
wrote:


<excerpt>

David,


I use the xml:lang attribute in my RDFResourceBundle class. I copy and
paste one instance of it below as your reference.



Jeremy Wong

--

Miko-Kings Instruments Ltd.

Web: http://www.miko.com.hk/


<<?xml version="1.0" encoding="UTF-8"?>


<<!--

   Document   : Software.xml

   Created on : June 6, 2005, 12:06 PM

   Author     : Jeremy Wong

   Description:

       Purpose of the document follows.

-->

<<!DOCTYPE rdf:RDF [

<<!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#">

<<!ENTITY rb "http://1980.hk/2005/ResourceBundle#">

]>

<<rdf:RDF xmlns:rdf="&rdf;" xmlns="&rb;">


<<Resource rdf:ID="Title">

   <<string xml:lang="en">Software for Iwatsu DS-8812 (Beta version,
Not for resales)<</string>

   <<string
xml:lang="zh"><fontfamily><param>Hiragino Kaku Gothic Pro</param>岩通DS-8812軟件（試驗版，非賣品）<</string>

   <<string xml:lang="ja">岩通DS-8812のソフトウェア (開発版,ない販売のために)<</string>

<</Resource>


<<Resource rdf:ID="AboutTitle">

   <<string xml:lang="en">About Software for Iwatsu DS-8812<</string>

   <<string xml:lang="zh">關於岩通DS-8812軟件<</string>

   <<string xml:lang="ja">岩通DS-8812のソフトウェアのバージョン情報<</string>

<</Resource>


<<Resource rdf:ID="Version">

   <<string xml:lang="en">Version 1.0.0.6<</string>

   <<string xml:lang="zh">版本：1.0.0.6<</string>

   <<string xml:lang="ja">版：1.0.0.6<</string>

<</Resource>


<<Resource rdf:ID="CopyrightInformation">

   <<string xml:lang="en">Copyright (C) 2005 Miko-Kings Instruments
Ltd.. All rights reserved.<</string>

   <<string xml:lang="zh">版權(C) 2005 力高儀器有限公司 保留所有權利<</string>

   <<string xml:lang="ja">版權(C) 2005 力高儀器有限公司 複製権所有<</string>

<</Resource>


<<Resource rdf:ID="SoftwareAuthor">

   <<string xml:lang="en">Software Developer<</string>

   <<string xml:lang="zh">軟件開發者<</string>

   <<string xml:lang="ja">ソフトウェアの開発者<</string>

<</Resource>


<<Resource rdf:ID="ButtonOkay">

   <<string xml:lang="en">OK<</string>

   <<string xml:lang="zh">確定<</string>

   <<string xml:lang="ja">OK<</string>

<</Resource>


<<Resource rdf:ID="ButtonCancel">

   <<string xml:lang="en">Cancel<</string>

   <<string xml:lang="zh">取消<</string>

   <<string xml:lang="ja">キャンセル<</string>

<</Resource>


<</rdf:RDF>


----- Original Message ----- From: "David Pratt"
<<fairwinds@eastlink.ca>

To: "Semantic Web" <<semantic-web@w3.org>

Sent: Monday, November 21, 2005 12:33 PM

Subject: Four schema creation questions



<excerpt>

Hi.  I have been working on a schema for a while. I think the biggest
challenge is really distilling what  I want to have in the schema and
in my records and how explicit to be. I had started to put things into
my triples store I had put together based on rdflb - but based on what
I have so far but am realizing that there are some things that could
likely be better. The organization of data could also be better by
using bag, seq or alt which I am not using at this point. I had heard
they were a bit difficult to work with so had initially stayed away
from these structures. My questions follow:


1. Combining schemas:

I have tried to create a schema that is pretty stand-alone (except for
rdf namespaces) but there are some properties that are available in
dublin core. Should I drop these properties in favor of dublin core
and add its namespace or create a reference to dublin core, adding its
namespace, since these properties are pretty much equivalent. What are
my alternatives?


2. When to group

I am hoping someone can offer constructive comment on when to group
rdf data with bag / seq or alt.

As an example, I am using an author property and it is significant
that the primary author is listed first if there is more than one. It
seems like a good candidate for a seq but often there is only a single
author.. Another example is keywords. I don't think dublin core puts
these in a bag for example but it would seem like a good use for a bag
with list element. So the question is really when to use a bag and
when to use a property on its own where it can exist as more than one
instance in a record.


3. Use of Language attribute

I am planning on having multilingual data but likely 80% of all data
in the store will likely be in english.  Almost all the rdf I have
looked at thus far, I do not see very high use of language attributes
in rdf. Maybe it is simply because english is used much of the time.
Can someone provide a practical recommendation on use of language
attribute. I was thinking I ought to be explicit with pretty much any
literal that is unicode.


4. Datatype attribute

I am looking for any recommendations based on experience with the
datatype attribute.  My intention is to be more (as opposed to less)
specific about the type of data I will expect from the records since
records will be validated before being inserted into the triples
store. I have been looking at Sparta since it seems to try and match
python data types with rdf types. Just looking for any kind of advise
from anyone that has worked with a programming language and rdf types
to offer any general recommendations based on their experience.


Many thanks

David

</excerpt>


</fontfamily></excerpt>
