You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 24, 2023. It is now read-only.
The Specification Document and related technical artifacts must be developed by the Project Team.
This is incorrect.
It is completely reasonable that technical artifacts (e.g., APIs or TCKs) be developed by a different project (or otherwise obtained from sources outside of the specification project.
Further, it is completely reasonable that the source for a specification document be obtained from outside of the project team. Theoretically, a project team could grab appropriately-licensed specification content from an external source and release it without modification.
I've going to remove this statement.
The text was updated successfully, but these errors were encountered:
The current revision makes this statement:
This is incorrect.
It is completely reasonable that technical artifacts (e.g., APIs or TCKs) be developed by a different project (or otherwise obtained from sources outside of the specification project.
Further, it is completely reasonable that the source for a specification document be obtained from outside of the project team. Theoretically, a project team could grab appropriately-licensed specification content from an external source and release it without modification.
I've going to remove this statement.
The text was updated successfully, but these errors were encountered: