[whatwg] Vocabulary ambiguity with non-namespaced semantic languages (was: Ghosts from the past and the semantic Web)

[Kristof Zelechovski]

Please.  We both agree that a job position has a title.  This title
attribute, when applied to a job position, is just fine; you can apply it to
a book here and to a job position there and you see from the context what
kind of a title it is.  But you cannot apply a title of a job position to a
person; you need job-title for the purpose because otherwise you have no way
to attach "count", "marquis" and the like.  If you want your properties to
mean something unrelated to their ordinary vocabulary meaning, or only
indirectly related, choose ones that are not present in a vocabulary, such
as GUIDs, or you will confuse everybody.
Chris

-----Original Message-----
From: whatwg-bounces at lists.whatwg.org
[mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of Manu Sporny
Sent: Friday, August 29, 2008 6:10 AM
To: whatwg at lists.whatwg.org
Subject: Re: [whatwg] Vocabulary ambiguity with non-namespaced semantic
languages (was: Ghosts from the past and the semantic Web)

"""
That's fine and you have defined "title" for your own use... but what
about my use! I want to use "title" as a means to identify the title of
a job position in my resume vocabulary. There is no need to use
"job-title" as it is redundant in my vocabulary.

Your definition of title "A book has exactly one title" has nothing to
do with my definition of "title" "The title of the position that was
held for a period of time." Title most certainly is not a shortcut
property in my vocabulary.
"""