This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 357 - Business name is not the same as personname in existing schema
Summary: Business name is not the same as personname in existing schema
Status: RESOLVED FIXED
Alias: None
Product: P3P
Classification: Unclassified
Component: Converting the P3P data schema to XML Schema (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: Giles Hogben
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-02 10:13 UTC by Giles Hogben
Modified: 2005-06-30 19:44 UTC (History)
0 users

See Also:

Attachments

Description Giles Hogben 2003-10-02 10:13:04 UTC 
Business name is not the same as personname. This creates semantic problems 
because it looks like a multiple subclass but it isn't. Suggest merging the 2
Comment 1 Rigo Wenning 2003-10-03 04:19:10 UTC 
Both semantics are needed as VCard e.g. uses also two different sets. The 
question whether we want to revise the Base Data Schema (BDS) should be a 
question for Version 2. Actually, your suggestion would break compatibility with 
VCard and would also break the Specification as it stands. The Specification has 
one place, where business-data is used (e.g. Entity ) and others places where 
the personname - scheme is used.

I think the issue could be clarified further.