[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Best Practice for URI construction?

• To: xml-dev@l...
• Subject: Re: Best Practice for URI construction?
• From: Klaus Backert <Klaus.Backert@t...>
• Date: Sat, 10 Dec 2005 22:07:37 +0100
• In-reply-to: <bibmp1l7ga1mflngltd4mqui8qn0tbb72t@h...>
• References: <C192E519-BE9A-4824-B249-6B2CF3161F85@t...> <20051210193334.18627gmx1@m...> <bibmp1l7ga1mflngltd4mqui8qn0tbb72t@h...>

Hi,

that's the way it is.

A simplified description of an example:
There is a list resource containing managers as subresources. When a  
manager is appointed to a certain responsibility (e.g. project  
management), he/she is added to the list, an URI is created for him/ 
her and stored in the list resource. The manager is not asked, if he/ 
she likes it. It's just done, because the employer want's it and  
needs it in the business process. Then it's possible to GET (directly  
or indirectly) representations of a manager by means of his/her URI  
containing: the kind of the responsibility, the person who had  
validated the appointment of the responsibility, communication  
address data, real world address data, his/her schedule, a picture  
perhaps, etc.

These managers are resources "on the web" now, additional to being  
human resources of the enterprise.

There are many countries today with a data protection law, where the  
data protection officer of the enterprise has to be involved, because  
URIs like the ones above are personal data similar to a personal id.

greetings
Klaus

Am 10.12.2005 um 20:44 schrieb Bjoern Hoehrmann:

> * Michael Kay wrote:
>>> Many of the resources in my work are non-electronic, e.g. persons,
>>> organisations, equipment. The resources got URIs. The resources (or,
>>> if you like: the representations of them) are accessible in a
>>> RESTafarian way.
>>
>> Well, I'm a person, and I don't have a URI, and I'm not accessible  
>> on the
>> web. The internet will get you only as far as my inbox, and my  
>> inbox is not
>> a representation of me.
>
> Resources don't determine which URIs do or do not identify them,
> that's for URI owners to decide. As a URI owner, I decide that
> http://xmlns.bjoern.hoehrmann.de/people/Michael_Kay/0.9/ identifies
> you. Now you are accessible on the web.
> -- 
> Björn Höhrmann · mailto:bjoern@h... · http:// 
> bjoern.hoehrmann.de
> Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http:// 
> www.bjoernsworld.de
> 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http:// 
> www.websitedev.de/
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>
>

• References:
  • Re: Best Practice for URI construction?
    • From: Klaus Backert <Klaus.Backert@t...>
  • Re: Best Practice for URI construction?
    • From: Bjoern Hoehrmann <derhoermi@g...>

• Prev by Date: What kind of content is allowed in simple types & simple content?
• Next by Date: Re: Best Practice for URI construction?
• Previous by thread: Re: Best Practice for URI construction?
• Next by thread: RE: Best Practice for URI construction?
• Index(es):
  • Date
  • Thread