[Buildingdata] Re: Extension number
Colin Williams
crw104 at ecs.soton.ac.uk
Mon Jan 14 21:18:25 GMT 2013
Hi Alex,
Not exactly an answer to your question, but a related point…
Are you aware that you can represent local numbers using tel: URIs? These require a phone context, which can either be a global number prefix or a domain name. Southampton's ECS RDF system used such URIs, for example: tel:23269;phone-context=soton.ac.uk . See RFC3966, section 5.1.5 for more details.
Regards,
Colin Williams
crw104 at ecs.soton.ac.uk
On 14 Jan 2013, at 10:13, Alexander Dutton <alexander.dutton at it.ox.ac.uk> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all,
>
> At the moment we have
> <|http://vocab.ox.ac.uk/ad-hoc-data-ox/oxfordExtensionNumber> for
> internal telephone extension numbers. Is it worth generalising to
> oo:telephoneExtension, with the network being encoded in the datatype
> (like skos:notation)?
>
> e.g.:
>
> <#alex> v:tel <+441865613483> ;
> oo:telephoneExtension
> "13483"^^<https://data.ox.ac.uk/id/notation/extensionNumber> .
>
> Or:
>
> <#alex> oo:telephoneExtension [ a vcard:Voice ; rdf:value "13483" ;
> oo:telephoneNetwork <#network> ]
>
> Some extensions aren't on the public phone network, so we can't really do:
>
> |||<#alex> v:tel <+441865613483> .
>
> ||||||<+441865613483>|| oo:telephoneExtension ||
> |||[ rdf:value "13483" ; oo:telephoneNetwork <#network> ]| |
>
> Our phone directory lists about three networks (what with the
> hospitals), and tie lines between them. With a bit of craftiness this
> could be encoded, allowing clever agents to present the right tie prefix
> to users. ([ a tie:TieLie ; tie:from <#uni> ; tie:to <#hospital> ;
> tie:prefix "123" ])
>
> Yours,
>
> Alex
> |
>
> - --
> Alexander Dutton
> Linked Open Data Architect, Office of the CIO; data.ox.ac.uk, OxPoints
> IT Services, University of Oxford, ℡ 01865 (6)13483
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> Comment: Using GnuPG with undefined - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJQ89o2AAoJEPotabD1ANF7kLwH/1ey7EihxG2Pcp7EgDlGDDAm
> X1efRJc5R/xbRpOxz+P+Wa/TsrPOG0hPsgxvj/2f5it5tTsm5fcq7mbr45uKhb3f
> l9vNZul5wfki4ZiQeOqR9G30wHNssICMcDmtXuyqP3ZM1715uDEKQJR1yCXKUim/
> uYOpzFDmBFvtU5T8dq95PoXVYnWwxlvGzzLECih3CTJlZaqrXfclZfKvND4Cg1Yr
> ZqmSDtYOdAbWG/OMDDLQn3m8J/cBQJHoZeir9kiQWVu1cCLixyZCxIc2SIn1nRZ6
> 1Iv8weVQVgjQkCF5cwFp2DKXZzRJRQ/2ScbBQXJJoYaXe1XDx/kRbIAZu3vlONQ=
> =kHCS
> -----END PGP SIGNATURE-----
> _______________________________________________
> Buildingdata mailing list
> Buildingdata at ecs.soton.ac.uk
> http://mailman.ecs.soton.ac.uk/mailman/listinfo/buildingdata
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ecs.soton.ac.uk/pipermail/buildingdata/attachments/20130114/b37c298f/attachment.html
More information about the Buildingdata
mailing list