Re: Short briefing/background doc't regarding RDFa, prefixes and HTML

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nathan writes:

>   You've missed @profile which allows the importing of prefix and
>   term definitions from an external profile (read: hosted on the web
>   somewhere), also provides a default RDFa processor profile (meaning
>   some prefixes are always supported and mapped to a specific uri),
>   and also means that if a specified profile can't be dereferenced and
>   read correctly (yes at parse / process time) then the element on
>   which the @profile is declared, and all child elements, are skipped
>   (no triples will be extracted from these elements).

Thanks, I thought I had worked back from step 4 of 7.5 to all the
places URI mappings could come from, but I obviously missed @profile.
I've updated the document [1] to reflect this.

ht

[1] http://www.w3.org/2001/tag/doc/RDFa_HTML_prefix_issue.html
- -- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 651-1426, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFNSrNekjnJixAXWBoRAstgAJ99Kq02wyqtYpYd/kJGmnrRosgJowCeLFDE
Mogn/UFWR7NO1mMi2AlVF3Y=
=NXtq
-----END PGP SIGNATURE-----

Received on Thursday, 3 February 2011 13:54:04 UTC