[wp-trac] [WordPress Trac] #35658: Provide additional data for registered meta through register_meta()
WordPress Trac
noreply at wordpress.org
Fri Jul 15 10:55:16 UTC 2016
#35658: Provide additional data for registered meta through register_meta()
-------------------------------------------------+-------------------------
Reporter: jeremyfelt | Owner: helen
Type: task (blessed) | Status: accepted
Priority: high | Milestone: 4.6
Component: Options, Meta APIs | Version:
Severity: normal | Resolution:
Keywords: needs-unit-tests needs-testing has- | Focuses:
patch rest-api needs-dev-note |
-------------------------------------------------+-------------------------
Comment (by schlessera):
If you want to provide a class for CURIEs, you should definitely stick to
how the CURIE is officially defined. Otherwise, please don't call it a
CURIE, as that comes with a certain set of expectations:
From https://www.w3.org/TR/curie/ :
''The following definition makes the set of CURIEs a syntactic superset of
the set of QNames. It is comprised of two components, a prefix and a
reference. The prefix is separated from the reference by a colon (:). It
is possible to omit both the prefix and the colon, or to omit just the
prefix and leave the colon. To disambiguate a CURIE when it appears in a
context where a normal [URI] may also be used, the entire CURIE is
permitted to be enclosed in brackets ([, ]).
''
This means that you would need to change the code with the following in
mind:
* The components are called `prefix` and `reference`
* It should still work when you omit the `prefix` and leave the colon
* It should be possible to enclose it in brackets (this is called a
`SafeCURIE`).
The currently proposed code snippets fail on some or all of this points.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/35658#comment:125>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list