Duane:
It gets worse than that: the semantics of FirstNameofHuman are not
"neutral" either: in Iceland, for example, the first name is the
significant name - even the telephone directories are ordered by first
name; the family name is simply a sort of qualifier (daughter of..., son
of ...) but which is not considered as significant as the first name. I
remember dramas when I worked in the Council of Europe when newly
arrived Icelandic staff were faced with paperwork asking for their
family name or surname but where "Christian" name (there's a bombshell
in itself for some) or forename was not asked for - this was considered
as rude and indelicate as it still is for many English people to be
addressed by their first names by people they don't know. (01)
So in reply to John's point of packaging a section of text, even widely
accepted packaging does not detract from the problem of adding yet
further context - and the problem is, however careful you are, there
will often be situations where the context requires something else. (02)
Regards, (03)
Peter
-----Original Message-----
From: ontolog-forum-bounces@xxxxxxxxxxxxxxxx
[mailto:ontolog-forum-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Duane
Nickull
Sent: 08 January 2008 17:49
To: [ontolog-forum]
Subject: Re: [ontolog-forum] CL, CG, IKL and the relationship between
symbols in the logical "universe of discourse" and individuals in the
"real world" (04)
John: (05)
As someone who mapped XML to EDI and other formats, this statement gave
us
lots of things to think about: (06)
On 1/8/08 6:47 AM, "John F. Sowa" <sowa@xxxxxxxxxxx> wrote: (07)
> * Syntax. The syntactic function of context is to group,
delimit,
> quote, or package a section of text. (08)
The issue arises when one builds automatic mappers based on metadata
artifacts stored in a registry-repository. Even if we sit down and
agree on
the semantics of "First Name of Human Being" as a data element and give
it a
metadata representation term of "FirstNameOfHuman" (type=string) and
constrain the instance values of a list of pre-approved names, there is
a
syntactic context issue at mapping. (09)
If it appears in Xan XML instance of a purchase order using the Xpath
syntax
in the hierarchic context of: (010)
//PurchaseOrder/BuyerParty/FirstNameOfHuman (011)
The exact same data element has slightly different semantics (strictly
in
the context of mapping to another instance of XML) if it appears in a
different hierarchic context of: (012)
//PurchaseOrder/SellerParty/FirstNameOfHuman (013)
As the BuyerParty vs. Seller Party hierarchic context qualifies the data
element. (014)
Is this the type of syntax context you refer to? (015)
Duane (016)
--
**********************************************************************
"Speaking only for myself"
Senior Technical Evangelist - Adobe Systems, Inc.
Blog - http://technoracle.blogspot.com
Community Music - http://www.mix2r.com
My Band - http://www.myspace.com/22ndcentury
Adobe MAX 2008 -
http://technoracle.blogspot.com/2007/08/adobe-max-2008.html
********************************************************************** (017)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Subscribe/Config:
http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx (018)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx (019)
|