Subject: Re: [Geopriv] URI in civic-lo - Street Address Data Standard

From: "Winterbottom, James" <[email-masked]>
Date: Thu, 10 Nov 2005 13:28:03 -0600

I have changed the title to move back to the thread that is actually
answered in this email.

Agreed.

I can go with that.
So to summarize, if you want to have specific schema representations for
fields you may do one of three things:

1) Use the extension capability already provided in the civic lo
definition
2) Create your own location type and transport it in the <location-info>
element.
3) Add documentation to your XML.

Are there any objections to this?

Assuming that we agree to solve the concern in this manner, the next
thing is where to put this recommendation. I see two possible places,
either in the civic-lo draft or in PIDF-LO profile. My preference is the
latter since this is a "using" concern, not a raw schema one.

Cheers
James

> -----Original Message-----
> From: Henning Schulzrinne [mailto:[email-masked]]
> Sent: Friday, 11 November 2005 6:16 AM
> To: Winterbottom, James
> Cc: GEOPRIV WG
> Subject: Re: [Geopriv] Taiwanese street section numbers
> 
> > I am still not sure what the consensus is on the Schema mapping URI
> > discussion. If we are going to have one we need to have a
description as
> > to what it is going to provide, and so far I think the best example
is
> > that it provide a web page for a human reader to say this is how we
plan
> > to interpret these fields.
> 
> Schema can have embedded documentation. Wouldn't it make sense to just
> use this feature?
> 
> Or are you looking for embedding a "dear recipient of this PIDF-LO,
> here's a web page with a general description of the data items".
> Unfortunately, any time you add a URL like that, this also adds a
> security exposure, as this URL might contain a reference to goatse.cx
or
> worse.
> Henning

------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.  
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]

_______________________________________________
Geopriv mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/geopriv